Quote:
Originally Posted by nsureit
My setup is Dell laptop connected to external HD Native card. Native card is Digi- linked to HD IO on port 1, and Digi-linked to Focusrite Red4 on port 2. I clock HD IO to Red4 then to Hilo. HD IO is my clock source (internal). PT hardware shows “internal, 44.1”, and everything plays nice with each other. I use the Hilo for its converters/two bus and to a patch bay to use outboard gear. I route tracking signal into Hilo via ADAT. I send audio from Hilo to a Drawmer MC3.1 monitor controller via AES, then out to my monitors.
|
Thanks for sharing your setup! Curious, do you notice a difference between your Hilo and your HDIO (or your Red4), in the input or output AD/DA? I haven't gotten around to setting mine up so I can easily switch between the two at the same time, but the HDIO sounds pretty good to me... thinking of just removing my Hilo from the chain, maybe add another HDIO and sell the Hilo.
Quote:
Originally Posted by LukeHoward
The Grimm clocking paper is good for the details but, I would just use the internal clock of your primary HD I/O interface to keep it simple and clock the Lynx from that. Or, experiment with both and see which one sounds the best.
Re: your other question, from memory Pro Tools doesn't leave any “holes” in I/O setup but I'm not 100% sure. |
Thanks! That is a good reference! And I agree, after more reading myself to catch up on the state of clocking, it's better to just use the internal clock on whatever is master. SOS had a particular good one where they tested internal vs external, and only the very high end converters even work well with an external clock - so much so, that no matter how cheap the interface, the internal clock will fare much better! Seems that it's simply more difficult to build an interface that follows external clock very well, or as well as its own internal clock can be adhered to. So indeed, the Hilo might be a better follower! (prioritize the perhaps higher end gear as receivers, vs. than the master)
I seem to remember hearing that advice now a decade+ ago, but had forgotten about it. Nice to see they tested it... this is the link in case anyone who sees this thread is interested:
https://www.soundonsound.com/techniq...l-master-clock
(and that's from 2010 - I guess on one hand, perhaps more interfaces slave to clock better nowadays, but on the other, even back then, cheap interfaces on their own internal quartz clocks seemed to work fine!)
Oh, and yes, you are right - when I finally got it set up, I went with making my analog HDIO first, and the MADI on the second card... there don't appear to be any gaps left in the numbering. So I am guessing/hoping that, if I add another HDIO, it will simply insert them in the list, but any existing channel assignments would seem to be tied to the hardware, which is actually pretty cool! Never really thought of that as a possible advantage of the HD closed ecosystem. (whereas with general purpose ASIO, one would have to carefully manage the hardware's I/O to the software's I/O, right - and even then, I think if you wanted to insert some into the range of inputs, it would throw off existing project's I/O assignments, since they just go numerically... not completely sure though, just thinking about Live and Cubase and how they map I/O)