Post by rayancaleb on Jan 29, 2018 3:18:48 GMT -5
Hi,
Typically the machines will start up fine and the LynxTWO Mixer Tool will show that it has correctly locked to the 48kHz input from the Studercore(Digital In 1). Sometimes, shortly afterwards the Lynx Mixer will drop the input and switch to internal for its source. In doing so the LynxTWO Mixer will state that it is currently locked to an internal source of 48kHz but on play back the audio sounds like it is operating at a lower clock rate frequency. We have also verified that the "Allow Clock Change if Active" under the advanced settings table is disabled, so it shouldn't be switching.
There doesn't appear to be any reason as to why the input is being dropped, also manually enabling internal and then re-enabling the "Digital In 1" will typically solve the issue, the input from the Studercore appears to be fine. The problem is also very intermittent, I can't reproduce it on command. We have over 40 studios using the exact same configuration as stated in the first paragraph, but only 2 of the studios have this issue?
Please help.
Thanks!
I didn't find the right solution from the Internet.
References:
www.lynxstudio.com/forum/clock-rate-issue_topic5409.html
Field Management Video
Typically the machines will start up fine and the LynxTWO Mixer Tool will show that it has correctly locked to the 48kHz input from the Studercore(Digital In 1). Sometimes, shortly afterwards the Lynx Mixer will drop the input and switch to internal for its source. In doing so the LynxTWO Mixer will state that it is currently locked to an internal source of 48kHz but on play back the audio sounds like it is operating at a lower clock rate frequency. We have also verified that the "Allow Clock Change if Active" under the advanced settings table is disabled, so it shouldn't be switching.
There doesn't appear to be any reason as to why the input is being dropped, also manually enabling internal and then re-enabling the "Digital In 1" will typically solve the issue, the input from the Studercore appears to be fine. The problem is also very intermittent, I can't reproduce it on command. We have over 40 studios using the exact same configuration as stated in the first paragraph, but only 2 of the studios have this issue?
Please help.
Thanks!
I didn't find the right solution from the Internet.
References:
www.lynxstudio.com/forum/clock-rate-issue_topic5409.html
Field Management Video