Multiple interfaces: ideal Loopsync and Digilink cabling?

[Eric Lambert]

I'll have an Avid HD IO interface and a Prism Titan interface (w/ HDX module installed). I'd like the Titan to be the master clock with the Avid slaving to that clock. I have a Native Thunderbolt box which has two Digilink ports.

What's the ideal way to connect these? Should I daisy chain: sending one Digilink cable from the Native Thunderbolt to the Titan's primary HDX port and then connect the Titan's expansion port to the Avid IO's primary port?

Or, should I use both of the HD Native's ports? One going to the Prism, the other going to the Avid? This seems wrong, but that's why I'm asking.

As far as Loopsync, the Prism doesn't have Loopsync, it has wordclock in and out. How do I connect both boxes so that clocking is correct?

[JFreak]

It does not matter how you connect digilinks (except daisy chaining hop cable should be short) but you need to mind the clocking. Prism is your master clock so you send word clock output to Avid's WC input, not loop sync.

[Eric Lambert]

That was my assumption. Thanks!

[BScout]

And then make sure and go to Session Setup and in the top option, flip to the HD I/O and then select wordclock. The HD I/O will stay on internal otherwise. The "master clock" setting in Hardware Setup does NOT tell all the other hardware where to get clock. And despite the Session Setup clock choices at the top looking like a selector, it is actually not other than the last one set becomes the loop master. BUT to set where each piece of hardware looks for clock, you have to flip to each one in that list and select where it should find clock (you'll see the lights on the interface change.)

[Eric Lambert]

Thanks BScout. These are things I dealt with often 15 years ago but I haven't changed hardware in ages. I could easily have missed those wordclock settings.

[Eric Lambert]

Prism says to use the Avid's loopsync ports. This makes since because the Prism is essentially operating as an Avid HD.

So it's Prism WC output to Avid loopsync input, then Avid loopsync output back to Prism WC input. In this scenario the clock is stable.

I actually did start this process by using the Avid's WC input but things were a bit haywire when switching sample rates.

[Darryl Ramm]

(I even read the manual) Not just running a word clock off the sync, but they actually implement the loop sync master/slave selection.... very nice.

[Eric Lambert]

Originally Posted by Darryl Ramm

(I even read the manual) Not just running a word clock off the sync, but they actually implement the loop sync master/slave selection.... very nice.

They're impressive! The lengths they'll go to to appease the 13 people who've bought their HDX module...

[Darryl Ramm]

They make some really great high end stuff, I remember drooling over a rack of ADA-8XR in the past. Had to have a little lay down.

I'm glad you did not go with messing around with upgrades.

[Eric Lambert]

Originally Posted by Darryl Ramm

They make some really great high end stuff, I remember drooling over a rack of ADA-8XR in the past. Had to have a little lay down.

I'm glad you did not go with messing around with upgrades.

Me too!