Pro Tools MTRX

[creativecontrol]

Yes - that should be listed as 1500x1500 not 384x384. I will let them know. MTRX can be clocked several different ways including Word Clock. If you have a SYNC HD you can feed Word Clock out into the MTRX input. You can set DADman to adapt Sample Rate to Pro Tools via DigiLink. You can also use an external clock DA if you have a more complex setup to distribute Word Clock to all of your converters and external digital devices.




Jeff

[LukeHoward]

Originally Posted by creativecontrol

Yes - that should be listed as 1500x1500 not 384x384. I will let them know. MTRX can be clocked several different ways including Word Clock. If you have a SYNC HD you can feed Word Clock out into the MTRX input. You can set DADman to adapt Sample Rate to Pro Tools via DigiLink. You can also use an external clock DA if you have a more complex setup to distribute Word Clock to all of your converters and external digital devices.

Well, I have a "simple" setup today with SYNC HD, Omni and HD I/O, to which I'll add a MTRX. Only the SYNC or the MTRX would need to be the master clock. Can I feed base rate WC from the MTRX to the Loop Sync inputs of the Omni and HD? Should I manually terminate this?

[creativecontrol]

If you are using the SYNC HD currently to resolve your system to SD or HD Video Ref I would keep the SYNC HD as the master and feed Word Clock into the MTRX while continuing to distribute Loop Sync between the SYNC, OMNI and HD IO.


If you don't need to resolve to Ref, I would set the MTRX as the Master -> Synchronization: Internal and feed Word from the MTRX to the SYNC HD Word in while continuing to Loop Sync between your SYNC HD, HD OMNI and HD IO.




Jeff

[LukeHoward]

Originally Posted by creativecontrol

If you are using the SYNC HD currently to resolve your system to SD or HD Video Ref I would keep the SYNC HD as the master and feed Word Clock into the MTRX while continuing to distribute Loop Sync between the SYNC, OMNI and HD IO.

If you don't need to resolve to Ref, I would set the MTRX as the Master -> Synchronization: Internal and feed Word from the MTRX to the SYNC HD Word in while continuing to Loop Sync between your SYNC HD, HD OMNI and HD IO.

I use the SYNC mainly for vari-speeding and it depends on the session – it's kind of inconvenient to have to re-plug in order to change between the scenarios, surely I'm not the only one who assumed that the MTRX would integrate more seamlessly with existing Avid I/O?

In any case, the second scenario should work for most of my use cases. I suppose I could feed WC from the SYNC to the MTRX to cover the first scenario and WC from the MTRX to the HD I/O, and loop sync all the Avid I/Os. In theory I can switch between the use cases in software (even if not purely within PT).

[JFreak]

Originally Posted by creativecontrol

The DA converters feature over 128 dB of dynamic range.

Wow, that's nice :)

[LukeHoward]

BTW can someone from Avid explain how Loop Sync is terminated? Is it at the master device?

[creativecontrol]

Here's a document that talks about Loop Sync, defining a Loop Master and integrating external clock sources. It is a bit dated but still relevant.

http://akmedia.digidesign.com/suppor...tter_30957.pdf




Best,




Jeff

[LukeHoward]

Originally Posted by creativecontrol

Here's a document that talks about Loop Sync, defining a Loop Master and integrating external clock sources. It is a bit dated but still relevant.

Seems to suggest that WC base clock from the MTRX could be fed directly to the Loop Sync In of other HD I/Os (and this would work at 2x/4x Fs). FWIW, Buccanears (may he rest in peace) noted earlier in this thread that Loop Sync worked with the AX32. Not sure if he needed to change the termination when the MTRX was not the master, but at least this can be done in software.

Anyway, when my MTRX arrives, I will try a few things and report back.

[JFreak]

Originally Posted by LukeHoward

BTW can someone from Avid explain how Loop Sync is terminated? Is it at the master device?

It isn't. As the name implies, it is a loop. Don't break it!

[LukeHoward]

Originally Posted by JFreak

It isn't. As the name implies, it is a loop. Don't break it!

Sorry, I meant electrically, not physically in terms of cabling (if that makes sense).