User16807436167065621122 (txshonk) asked a question.
Potential Clocking Issue
I have two windows machines that I getting a slight clicking in my Atmos signal routing back to ProTools. I am guessing it is a clocking issue.
I have PT HDX cards with rednet5 boxes passing audio to the renderer. I May need to upgrade my switch so I am working on trouble shooting to be sure the Dante isnt the root cause.
But if it is a clocking issue, I assume the next upgrade would be an AVID Sync or something similar. But I am not sure what/how I would route the LTC to the renderer machine. Can anyone help educate me on the hardware and protocols that would be used on the renderer?box if I were to venture into an HD Sync or something?
I have PT HDX cards with rednet5 boxes passing audio to the renderer. I May need to upgrade my switch so I am working on trouble shooting to be sure the Dante isnt the root cause.
But if it is a clocking issue, I assume the next upgrade would be an AVID Sync or something similar. But I am not sure what/how I would route the LTC to the renderer machine. Can anyone help educate me on the hardware and protocols that would be used on the renderer?box if I were to venture into an HD Sync or something?
If you were to go with an external LTC generator you could use an analog to Dante converter from Audinate: https://www.audinate.com/products/devices/dante-avio
What are you using to generate LTC now? Are you creating .atmos files with the Renderer or just using it for monitoring with Pro Tools and bouncing to mix?
I think your first assumption is correct and this is a clocking issue. If there is drift/jitter in LTC the Renderer will show timecode discontinuities in the logs and/or drop out of record if these are persistent.
Thanks,
Adam
So, on the renderer side things wouldn't change that much. from what I have tried so far.
Since I am working in windows I have tried the following.
On a PT track I have tried two things:
1) https://txl20.com/txl-timecode-plug-in/ - however it does have issues and cause the audio engine to error and stop on busy sessions.
2) https://txl20.com/ltc-wav-generator/ - I have also used their timecode generator to create an audio fie and placed it on a track in my session - doesn't cause PT audio engine issues.
Then I route these out to Dante via a channel on a RedNet5, and in Dante Controller route that to the renderers Rednet PCIeR card.
Any other info would be greatly appreciated.
Dave
Yes, you need to create a muliticast flow of the last eight channels so you can route the converter to input 128 without losing the preceding audio inputs. This is covered in the installation guide. But I don't think this is a time code issue as much clocking issue. Are you using a word clock generator? Which device is the preferred leader for the Dante network enabled for external sync?
Thanks,
Adam
So here is some more info.
For Avid interfaces I have an Omni and HD I/O.
In ProTools I have the clock master set to Internal and using the Omni as the LoopMaster.
I have the Loop Synh connected between the Omni - HD I/O - and the two RedNet5.
I actually tried only connecting the leader Rednet5 to the Loop Sync - based on Focusrite documentation saying that connecting more than the Leader wasn't needed.
The RedNet PCIe (renderer and second RedNet5 are Dante followers.
I have also tried sending the LTC signal over both RedNet devices and get the same clicking.
I believe the issue were the primary Focisrite RedNet5 clocking settings reset. However, I touched every part of the chain, so I cannot say that with 100% certainty.
That seems a plausible culprit. Glad you got it working.
Adam