PDA

View Full Version : Clock Jitter/Sync Problem with 2 MOTU 896's linked...


Roach
September 20th 04, 12:01 AM
Hey everyone,

I've owned one MOTU 896 for about a year and a half and decided that i would
get a second one to expand my recording ability to 16 tracks. Supposedly
it's a easy as daisy chaining another 896 onto the existing 896. Well, i
found out that this wasn't the case. I can set the clock speed no problem
within the 896's control panel and the two machines will change the sample
rate appropriately and appear to function properly. Upon launching either
Nuendo 2, or Logic 5, 896 #2 falls out of sync and the clock starts bouncing
between 44.1 and 48, (or 88.2 and 96 if i try to set a higher rate). It
never settles and i get extremely chopped up playback and recording. I tried
installing MOTU's new firewire driver that just came out about a month ago,
and still no luck syncing. I tried the whole uninstall driver, uninstall
software, reinstall, reboot, and every other combination of those steps i
could think of....

Neither machines are defective since they both operate properly on their
own. The problem only occurs when daisy chained, and running an audio
application. The sync/jitter problem always occurs to the second motu that
was turned on. The first one to be started always locks it's clock just
fine.

My system setup is PC, Asus P4C800-Deluxe, 1 gig 400Mhz DDR, 800Mhz FSB, 100
gigs free between two seperate drives. My firewire port is onboard the Asus
board.

I found a message about this exact problem in the archives from '02, but
unfortunately the thread was only 4 messages long and didn't include any
fixes.

Has anyone else ever encountered this problem??

I have heard that firewire isn't often the best way to lock devices together
(but it should still work....), is this true?

Thanks muchly,

Roach

Eric K. Weber
September 20th 04, 01:04 AM
Do you have a bnc cable from the world clock out of the one chosen as master
to the world clock in of the one chosen as clock slave?

Rgds:
Eric

"Roach" > wrote in message
. cable.rogers.com...
> Hey everyone,
>
> I've owned one MOTU 896 for about a year and a half and decided that i
would
> get a second one to expand my recording ability to 16 tracks. Supposedly
> it's a easy as daisy chaining another 896 onto the existing 896. Well, i
> found out that this wasn't the case. I can set the clock speed no problem
> within the 896's control panel and the two machines will change the sample
> rate appropriately and appear to function properly. Upon launching either
> Nuendo 2, or Logic 5, 896 #2 falls out of sync and the clock starts
bouncing
> between 44.1 and 48, (or 88.2 and 96 if i try to set a higher rate). It
> never settles and i get extremely chopped up playback and recording. I
tried
> installing MOTU's new firewire driver that just came out about a month
ago,
> and still no luck syncing. I tried the whole uninstall driver, uninstall
> software, reinstall, reboot, and every other combination of those steps i
> could think of....
>
> Neither machines are defective since they both operate properly on their
> own. The problem only occurs when daisy chained, and running an audio
> application. The sync/jitter problem always occurs to the second motu that
> was turned on. The first one to be started always locks it's clock just
> fine.
>
> My system setup is PC, Asus P4C800-Deluxe, 1 gig 400Mhz DDR, 800Mhz FSB,
100
> gigs free between two seperate drives. My firewire port is onboard the
Asus
> board.
>
> I found a message about this exact problem in the archives from '02, but
> unfortunately the thread was only 4 messages long and didn't include any
> fixes.
>
> Has anyone else ever encountered this problem??
>
> I have heard that firewire isn't often the best way to lock devices
together
> (but it should still work....), is this true?
>
> Thanks muchly,
>
> Roach
>
>

Eric K. Weber
September 20th 04, 01:04 AM
Do you have a bnc cable from the world clock out of the one chosen as master
to the world clock in of the one chosen as clock slave?

Rgds:
Eric

"Roach" > wrote in message
. cable.rogers.com...
> Hey everyone,
>
> I've owned one MOTU 896 for about a year and a half and decided that i
would
> get a second one to expand my recording ability to 16 tracks. Supposedly
> it's a easy as daisy chaining another 896 onto the existing 896. Well, i
> found out that this wasn't the case. I can set the clock speed no problem
> within the 896's control panel and the two machines will change the sample
> rate appropriately and appear to function properly. Upon launching either
> Nuendo 2, or Logic 5, 896 #2 falls out of sync and the clock starts
bouncing
> between 44.1 and 48, (or 88.2 and 96 if i try to set a higher rate). It
> never settles and i get extremely chopped up playback and recording. I
tried
> installing MOTU's new firewire driver that just came out about a month
ago,
> and still no luck syncing. I tried the whole uninstall driver, uninstall
> software, reinstall, reboot, and every other combination of those steps i
> could think of....
>
> Neither machines are defective since they both operate properly on their
> own. The problem only occurs when daisy chained, and running an audio
> application. The sync/jitter problem always occurs to the second motu that
> was turned on. The first one to be started always locks it's clock just
> fine.
>
> My system setup is PC, Asus P4C800-Deluxe, 1 gig 400Mhz DDR, 800Mhz FSB,
100
> gigs free between two seperate drives. My firewire port is onboard the
Asus
> board.
>
> I found a message about this exact problem in the archives from '02, but
> unfortunately the thread was only 4 messages long and didn't include any
> fixes.
>
> Has anyone else ever encountered this problem??
>
> I have heard that firewire isn't often the best way to lock devices
together
> (but it should still work....), is this true?
>
> Thanks muchly,
>
> Roach
>
>

Roach
September 20th 04, 05:20 AM
Thanks for the reply, I did connect the word clock out of 896 #1 to word
clock in of 896 #2, in the control panel you cannot select one motu to slave
to another motu. The word clock setup is designed to synched to a clock
generator.

The only options for Clock Source are #1 internal (which is supposed to be
the firewire means of sync), #1 ADAT, #1 AES/EBU, #1 Word Clock In, and then
the same options replacing "#1" with "#2". So basically setting it to "#1
Word Clock in" will slave both machines to whatever is coming into MOTU #1.
I tried all combinations of this as well. Argh!

Any ideas?

sincerely

Roach

"Eric K. Weber" > wrote in message
...
> Do you have a bnc cable from the world clock out of the one chosen as
> master
> to the world clock in of the one chosen as clock slave?
>
> Rgds:
> Eric
>
> "Roach" > wrote in message
> . cable.rogers.com...
>> Hey everyone,
>>
>> I've owned one MOTU 896 for about a year and a half and decided that i
> would
>> get a second one to expand my recording ability to 16 tracks. Supposedly
>> it's a easy as daisy chaining another 896 onto the existing 896. Well, i
>> found out that this wasn't the case. I can set the clock speed no problem
>> within the 896's control panel and the two machines will change the
>> sample
>> rate appropriately and appear to function properly. Upon launching either
>> Nuendo 2, or Logic 5, 896 #2 falls out of sync and the clock starts
> bouncing
>> between 44.1 and 48, (or 88.2 and 96 if i try to set a higher rate). It
>> never settles and i get extremely chopped up playback and recording. I
> tried
>> installing MOTU's new firewire driver that just came out about a month
> ago,
>> and still no luck syncing. I tried the whole uninstall driver, uninstall
>> software, reinstall, reboot, and every other combination of those steps i
>> could think of....
>>
>> Neither machines are defective since they both operate properly on their
>> own. The problem only occurs when daisy chained, and running an audio
>> application. The sync/jitter problem always occurs to the second motu
>> that
>> was turned on. The first one to be started always locks it's clock just
>> fine.
>>
>> My system setup is PC, Asus P4C800-Deluxe, 1 gig 400Mhz DDR, 800Mhz FSB,
> 100
>> gigs free between two seperate drives. My firewire port is onboard the
> Asus
>> board.
>>
>> I found a message about this exact problem in the archives from '02, but
>> unfortunately the thread was only 4 messages long and didn't include any
>> fixes.
>>
>> Has anyone else ever encountered this problem??
>>
>> I have heard that firewire isn't often the best way to lock devices
> together
>> (but it should still work....), is this true?
>>
>> Thanks muchly,
>>
>> Roach
>>
>>
>
>

Roach
September 20th 04, 05:20 AM
Thanks for the reply, I did connect the word clock out of 896 #1 to word
clock in of 896 #2, in the control panel you cannot select one motu to slave
to another motu. The word clock setup is designed to synched to a clock
generator.

The only options for Clock Source are #1 internal (which is supposed to be
the firewire means of sync), #1 ADAT, #1 AES/EBU, #1 Word Clock In, and then
the same options replacing "#1" with "#2". So basically setting it to "#1
Word Clock in" will slave both machines to whatever is coming into MOTU #1.
I tried all combinations of this as well. Argh!

Any ideas?

sincerely

Roach

"Eric K. Weber" > wrote in message
...
> Do you have a bnc cable from the world clock out of the one chosen as
> master
> to the world clock in of the one chosen as clock slave?
>
> Rgds:
> Eric
>
> "Roach" > wrote in message
> . cable.rogers.com...
>> Hey everyone,
>>
>> I've owned one MOTU 896 for about a year and a half and decided that i
> would
>> get a second one to expand my recording ability to 16 tracks. Supposedly
>> it's a easy as daisy chaining another 896 onto the existing 896. Well, i
>> found out that this wasn't the case. I can set the clock speed no problem
>> within the 896's control panel and the two machines will change the
>> sample
>> rate appropriately and appear to function properly. Upon launching either
>> Nuendo 2, or Logic 5, 896 #2 falls out of sync and the clock starts
> bouncing
>> between 44.1 and 48, (or 88.2 and 96 if i try to set a higher rate). It
>> never settles and i get extremely chopped up playback and recording. I
> tried
>> installing MOTU's new firewire driver that just came out about a month
> ago,
>> and still no luck syncing. I tried the whole uninstall driver, uninstall
>> software, reinstall, reboot, and every other combination of those steps i
>> could think of....
>>
>> Neither machines are defective since they both operate properly on their
>> own. The problem only occurs when daisy chained, and running an audio
>> application. The sync/jitter problem always occurs to the second motu
>> that
>> was turned on. The first one to be started always locks it's clock just
>> fine.
>>
>> My system setup is PC, Asus P4C800-Deluxe, 1 gig 400Mhz DDR, 800Mhz FSB,
> 100
>> gigs free between two seperate drives. My firewire port is onboard the
> Asus
>> board.
>>
>> I found a message about this exact problem in the archives from '02, but
>> unfortunately the thread was only 4 messages long and didn't include any
>> fixes.
>>
>> Has anyone else ever encountered this problem??
>>
>> I have heard that firewire isn't often the best way to lock devices
> together
>> (but it should still work....), is this true?
>>
>> Thanks muchly,
>>
>> Roach
>>
>>
>
>