Home » The PARIS Forums » PARIS: Main » OT: Tascam FW-1804
|
|
|
|
|
|
| Re: OT: Tascam FW-1804 [message #88323 is a reply to message #88317] |
Thu, 19 July 2007 19:05   |
Aaron Allen
Messages: 1988
Registered: May 2008
|
Senior Member |
|
|
I'm hoping this will be cool... the features and Tascam throwing in a free
copy of Giga Solo makes it a pretty unbelievable deal at around $400.
I'm currently using a M Audio Audiophile FW interface, and it's been dead
solid on that rig at 1.5mS/44.1, so I think my chances are pretty decent. I
noted in the 1084 manual I can essentially shut off inputs and cut my over
head. Another veeeery cool trick I picked up was the one to do with FW and
WinXP SP2 being throttled back incorrectly. I'm hoping I don't have to go
there so I'll try it 'as is' first, but it gives me some options along with
double dawg. Laptop/Tablet machines aren't notorious for great bus
bandwidth, so I may get a bit of a challenge.
Also being the Dice II, I might have a harder look at the universal or ideal
driver we talked about earlier in the week. 1804 isn't listed in the 'known
to work' on the CEntrance site, but I have a strong suspicion that it'll
pick up the unit based on the Dice II chip, and that the DM3200 is on that
list... could be wrong, have you tried it?
AA
"Chris Ludwig" <chrisl@adkproaudio.com> wrote in message
news:469f76d4$1@linux...
> HI Aaron,
>
> If you have a compatible Fire wire chipset you "might" be OK. Even on new
> Core2Duo based machines the Tascam seems to have trouble running at lower
> than 10ms.
> I can regularly use 1.5 to 3ms on MOTU and RME fire wire interfaces but
> they both use their own proprietary firewire designs. About support let me
> put it this way. MOTU has way better support at this point and it still
> has allot to be desired
>
Yeah, I've bumped uglies with their support years back when they essentially
acted like they'd been forced to deal with lowly sub-human Windows PC users,
and we were all idiots... I still have some MOTU gear, but it's still a
bitter apple (all puns intended) seeing/hearing that name.
> Chris
>
>
>
> Aaron Allen wrote:
>> Anyone got one of these? I'm looking to mainly dump synth's down through
>> it, seems to have all the right drivers. I have heard tascam support
>> really blows these days, but I'm more concerned I suppose with not having
>> the convertors suck eggs or having the latency so flippin high it's
>> useless. Dice II firewire, so I know it's probably going to be running
>> around 10 ms to be stable on my chosen (Toshiba tablet) system.. but
>> dumping midi synths, this isn't a huge deal to me.
>>
>> Any input greatly appreciated!
>>
>> AA
>>
>>
>
> --
> Chris Ludwig
> ADK
> chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
> www.adkproaudio.com <http://www.adkproaudio.com/>
> (859) 635-5762
|
|
|
|
|
|
|
|
|
|
| Re: OT: Tascam FW-1804 [message #88329 is a reply to message #88328] |
Thu, 19 July 2007 22:39 |
Aaron Allen
Messages: 1988
Registered: May 2008
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0024_01C7CA66.6945B740
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Yeah, I'll be dumping pre programmed midi tracks to a DAW for moving to =
Paris to mix down.. latencies probably not an issue. Coupla tricks =
though:
1.. Go to networking properties... kill the firewire port. It appears =
to have stopped a multitude of issues for many users.=20
2.. www.musicxp.net well, those of us around here know about this =
any way :)
3.. Apply this patch http://support.microsoft.com/kb/885222 then go =
in and reg the sidspeed info. below is one guy's info on that:
It turns out its not just enough to install this patch. In fact all this =
patch does is configure SP2 so that the firewire bandwidth can now be =
set in the registry, you still have to manually change the registry =
setting yourself to configure it. I.e both my firwire cards were still =
running at 100.=20
I went into the registry and located both my firewire cards =
HKEY_LOCAL_MACHINE/SYSTEM/CURRENTCONTROLSET/ENUM/yourcardpar t1/yourcardpa=
rt2. To find out your specific card numbers go to device manager and =
look up there properties there, big long alphanumeric no's one long line =
seperated by a /.=20
Anyway once into your firewire card(s) in the registry go to the Device =
Parameters folder in here you will need to add a DWORD value called =
SidSpeed. This value can then be configured accordingly in decimal.=20
0 =3D 100=20
1 =3D 200=20
2 =3D 400=20
3 =3D 400-800=20
Hopefully someone will find this info useful also
AA
"LaMont" <jjdpro@ameritech.net> wrote in message news:46a03abe@linux...
>=20
> Ok.. I forgot to mention, that I monitor thur an analog mixer..My Asio =
setting
> is always set to 1024ms..or 2048...
>=20
> That's the beauty of using a mixer.=20
>=20
> "LaMont" <jjdpro@ameritech.net> wrote:
>>
>>Yeah..Sometimes..Ona Rhodes Vsti.. I made it work..
>>
>>
>>"Neil" <OIUOIU@OIU.com> wrote:
>>>
>>>Chris Ludwig <chrisl@adkproaudio.com> wrote:
>>>>HI Aaron,
>>>>
>>>>If you have a compatible Fire wire chipset you "might" be OK. Even =
on
>=20
>>>>new Core2Duo based machines the Tascam seems to have trouble running =
at
>>>
>>>>lower than 10ms.
>>>
>>>10ms??? That's fucking USELESS! I mean, seriously, who could
>>>even utilise that for ANYTHING? Comb-filter city at 7 ms is
>>>borderline useless, and between 3 & 5 is even no good for some
>>>more timing-sensitive people, I've found.
>>>
>>>Is anyone here really using anything in the 10 ms range?=20
>>>
>>>Neil
>>
>
------=_NextPart_000_0024_01C7CA66.6945B740
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16481" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Yeah, I'll be dumping pre programmed =
midi tracks to=20
a DAW for moving to Paris to mix down.. latencies probably not an issue. =
Coupla=20
tricks though:</FONT></DIV>
<OL>
<LI><FONT face=3DArial size=3D2>Go to networking properties... kill =
the firewire=20
port. It appears to have stopped a multitude of issues for many users. =
</FONT></LI>
<LI><A href=3D"http://www.musicxp.net"><FONT face=3DArial=20
size=3D2>www.musicxp.net</FONT></A><FONT face=3DArial =
size=3D2> well,=20
those of us around here know about this any way :)</FONT></LI>
<LI><FONT face=3DArial size=3D2>Apply this patch </FONT><A=20
href=3D"http://support.microsoft.com/kb/885222" target=3D_blank><FONT =
face=3DArial=20
size=3D2>http://support.microsoft.com/kb/885222</FONT></A><FONT =
face=3DArial=20
size=3D2> then go in and reg the sidspeed info. below is =
one guy's=20
info on that:</FONT></LI></OL>
<DIV><FONT face=3DArial size=3D2>It turns out its not just enough to =
install this=20
patch. In fact all this patch does is configure SP2 so that the firewire =
bandwidth can now be set in the registry, you still have to manually =
change the=20
registry setting yourself to configure it. I.e both my firwire cards =
were still=20
running at 100. <BR><BR>I went into the registry and located both my =
firewire=20
cards=20
HKEY_LOCAL_MACHINE/SYSTEM/CURRENTCONTROLSET/ENUM/yourcardpar t1/yourcardpa=
rt2. To=20
find out your specific card numbers go to device manager and look up =
there=20
properties there, big long alphanumeric no's one long line seperated by =
a /.=20
<BR><BR>Anyway once into your firewire card(s) in the registry go to the =
Device=20
Parameters folder in here you will need to add a DWORD value called =
SidSpeed.=20
This value can then be configured accordingly in decimal. <BR><BR>0 =3D =
100 <BR>1=20
=3D 200 <BR>2 =3D 400 <BR>3 =3D 400-800 <BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Hopefully someone will find this info =
useful=20
also</DIV></FONT>
<DIV><FONT face=3DArial size=3D2>AA</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>"LaMont" <</FONT><A=20
href=3D"mailto:jjdpro@ameritech.net"><FONT face=3DArial=20
size=3D2>jjdpro@ameritech.net</FONT></A><FONT face=3DArial size=3D2>> =
wrote in=20
message </FONT><A href=3D"news:46a03abe@linux"><FONT face=3DArial=20
size=3D2>news:46a03abe@linux</FONT></A><FONT face=3DArial=20
size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>> <BR>> Ok.. =
I forgot to=20
mention, that I monitor thur an analog mixer..My Asio setting<BR>> is =
always=20
set to 1024ms..or 2048...<BR>> <BR>> That's the beauty of using a =
mixer.=20
<BR>> <BR>> "LaMont" <</FONT><A=20
href=3D"mailto:jjdpro@ameritech.net"><FONT face=3DArial=20
size=3D2>jjdpro@ameritech.net</FONT></A><FONT face=3DArial size=3D2>> =
wrote:<BR>>><BR>>>Yeah..Sometimes..Ona Rhodes Vsti.. I made =
it=20
work..<BR>>><BR>>><BR>>> "Neil" <</FONT><A=20
href=3D"mailto:OIUOIU@OIU.com"><FONT face=3DArial=20
size=3D2>OIUOIU@OIU.com</FONT></A><FONT face=3DArial size=3D2>>=20
wrote:<BR>>>><BR>>>>Chris Ludwig <</FONT><A=20
href=3D"mailto:chrisl@adkproaudio.com"><FONT face=3DArial=20
size=3D2>chrisl@adkproaudio.com</FONT></A><FONT face=3DArial =
size=3D2>>=20
wrote:<BR>>>>>HI =
Aaron,<BR>>>>><BR>>>>>If=20
you have a compatible Fire wire chipset you "might" be OK. Even =
on<BR>>=20
<BR>>>>>new Core2Duo based machines the Tascam seems to have =
trouble=20
running at<BR>>>><BR>>>>>lower than=20
10ms.<BR>>>><BR>>>>10ms??? That's fucking USELESS! I =
mean,=20
seriously, who could<BR>>>>even utilise that for ANYTHING? =
Comb-filter=20
city at 7 ms is<BR>>>>borderline useless, and between 3 & 5 =
is even=20
no good for some<BR>>>>more timing-sensitive people, I've=20
found.<BR>>>><BR>>>>Is anyone here really using =
anything in=20
the 10 ms range?=20
<BR>>>><BR>>>>Neil <BR>>><BR>></FONT></BODY></H=
TML>
------=_NextPart_000_0024_01C7CA66.6945B740--
|
|
|
|
| Re: OT: Tascam FW-1804 [message #88338 is a reply to message #88329] |
Fri, 20 July 2007 06:34 |
Chris Ludwig
Messages: 868
Registered: May 2006
|
Senior Member |
|
|
HI Aaron,
You don't need to manually edit the registry as long as you are using
the current 885222 version on the MS web site.
Chris
Aaron Allen wrote:
> Yeah, I'll be dumping pre programmed midi tracks to a DAW for moving
> to Paris to mix down.. latencies probably not an issue. Coupla tricks
> though:
>
> 1. Go to networking properties... kill the firewire port. It
> appears to have stopped a multitude of issues for many users.
> 2. www.musicxp.net <http://www.musicxp.net> well, those of us
> around here know about this any way :)
> 3. Apply this patch http://support.microsoft.com/kb/885222 then
> go in and reg the sidspeed info. below is one guy's info on that:
>
> It turns out its not just enough to install this patch. In fact all
> this patch does is configure SP2 so that the firewire bandwidth can
> now be set in the registry, you still have to manually change the
> registry setting yourself to configure it. I.e both my firwire cards
> were still running at 100.
>
> I went into the registry and located both my firewire cards
> HKEY_LOCAL_MACHINE/SYSTEM/CURRENTCONTROLSET/ENUM/yourcardpar t1/yourcardpart2.
> To find out your specific card numbers go to device manager and look
> up there properties there, big long alphanumeric no's one long line
> seperated by a /.
>
> Anyway once into your firewire card(s) in the registry go to the
> Device Parameters folder in here you will need to add a DWORD value
> called SidSpeed. This value can then be configured accordingly in
> decimal.
>
> 0 = 100
> 1 = 200
> 2 = 400
> 3 = 400-800
> Hopefully someone will find this info useful also
> AA
>
>
> "LaMont" <jjdpro@ameritech.net <mailto:jjdpro@ameritech.net>> wrote in
> message news:46a03abe@linux...
> >
> > Ok.. I forgot to mention, that I monitor thur an analog mixer..My
> Asio setting
> > is always set to 1024ms..or 2048...
> >
> > That's the beauty of using a mixer.
> >
> > "LaMont" <jjdpro@ameritech.net <mailto:jjdpro@ameritech.net>> wrote:
> >>
> >>Yeah..Sometimes..Ona Rhodes Vsti.. I made it work..
> >>
> >>
> >>"Neil" <OIUOIU@OIU.com <mailto:OIUOIU@OIU.com>> wrote:
> >>>
> >>>Chris Ludwig <chrisl@adkproaudio.com
> <mailto:chrisl@adkproaudio.com>> wrote:
> >>>>HI Aaron,
> >>>>
> >>>>If you have a compatible Fire wire chipset you "might" be OK. Even on
> >
> >>>>new Core2Duo based machines the Tascam seems to have trouble
> running at
> >>>
> >>>>lower than 10ms.
> >>>
> >>>10ms??? That's fucking USELESS! I mean, seriously, who could
> >>>even utilise that for ANYTHING? Comb-filter city at 7 ms is
> >>>borderline useless, and between 3 & 5 is even no good for some
> >>>more timing-sensitive people, I've found.
> >>>
> >>>Is anyone here really using anything in the 10 ms range?
> >>>
> >>>Neil
> >>
> >
--
Chris Ludwig
ADK
chrisl@adkproaudio.com <mailto:chrisl@adkproaudio.com>
www.adkproaudio.com <http://www.adkproaudio.com/>
(859) 635-5762
|
|
|
|
Goto Forum:
Current Time: Fri Nov 29 01:52:59 PST 2024
Total time taken to generate the page: 0.00979 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
