| Author |
 Topic Search  Topic Options
|
Jperkinski 
Wildcat
Joined: January/20/2014
Location: Milwaukee, WI
Points: 159
|
 Topic: New AES16e behavior (delayed audio dropout)
Posted: July/15/2016 at 6:56am |
Sometime in the last few months, I started noticing something. If I load my preferred Lynx Mixer scene, sometimes I get a major half second audio dropout about 45 seconds to ~1 minute later.
This happens even when I don't use Syncrolock in the saved scene which I know can take some time to work.
Are there any settings that would cause this delayed dropout?
Edited by Jperkinski - July/15/2016 at 6:57am
|
 |
PaulTech
Admin Group
Joined: August/13/2004
Location: United States
Points: 5495
|
Posted: July/15/2016 at 2:07pm |
|
Is this Windows or Mac OS? What type of computer?
|
|
|
|
Jperkinski
Wildcat
Joined: January/20/2014
Location: Milwaukee, WI
Points: 159
|
Posted: July/15/2016 at 2:13pm |
I'm sorry, I should know better than to be so vague.
OSX 10.11.5 iMac 3.5GHz Quad i7 32GB RAM SSD for OS and audio
|
|
PaulTech
Admin Group
Joined: August/13/2004
Location: United States
Points: 5495
|
Posted: July/15/2016 at 3:26pm |
OK, so no thunderbolt chassis, this is an older MacPro? What is the AES16e connected to digitally? How are the clocks set between the AES16e and your converter? Does increasing the buffer size help? From the Lynx Mixer click mixer > About. What is the mixer and firmware versions for the card?
|
|
|
|
Jperkinski
Wildcat
Joined: January/20/2014
Location: Milwaukee, WI
Points: 159
|
Posted: July/15/2016 at 3:38pm |
Hi Paul,
It's an iMac as noted in the previous post, and the AES16e is in a Sonnet TB chassis. When the dropout happens I'm using Digital Input 2 as the clock source. I already had the buffer at 64.
I'm not sure if the Disable CPU Management or Enable Safety offset would help or hurt, information on that is vague.
Edited by Jperkinski - July/15/2016 at 3:41pm
|
|
PaulTech
Admin Group
Joined: August/13/2004
Location: United States
Points: 5495
|
Posted: July/15/2016 at 3:41pm |
Both of those are worth trying. Have you tried setting the buffer to 128 or 256 as a test? What is the converter?
|
|
|
|
Jperkinski
Wildcat
Joined: January/20/2014
Location: Milwaukee, WI
Points: 159
|
Posted: July/15/2016 at 3:46pm |
My DAW software buffer is @ 1024 or 2048 usually. I'm referring to the Lynx Mixer buffer being at 64.
I have two standalone converters, a Crane Song HEDD (Digital 2) and Lynx Hili (Digital 3).
This happens in both Pro Tools 12 and REAPER 5.x
More importantly at the moment, I'm also having serious issue with clicks and pops as of today, doing some fast zooming within the DAW or trying an email in another app is triggering some serious pops and clicks and is unfortunately in my recordings from my analog gear loop.
WaveLab is also clicking/popping on fast zooms and other things.
It seems that the system has become very sensitive to any other computer activity.
Any ideas how to remedy ASAP? Here are my specs:
Edited by Jperkinski - July/15/2016 at 3:47pm
|
|
David A Hoatson
Admin Group
Forum Administrator
Joined: October/01/2003
Location: Idaho
Points: 4993
|
Posted: July/15/2016 at 11:25pm |
|
You should really leave the hardware buffer at 'Auto'. Setting it to 64 can have negative consequences at certain software buffer sizes and sample rates.
Also, I don't know of anything in the hardware or driver that would take 45 seconds to a minute to happen. That is a huge amount of time to the computer. What else has changed in the system that might have caused this issue, since it seems that things were working for you before?
|
|
Thank you,
David A. Hoatson
Lynx Studio Technology, Inc.
Co-founder, Chief Software Engineer
|
|
Jperkinski
Wildcat
Joined: January/20/2014
Location: Milwaukee, WI
Points: 159
|
Posted: July/16/2016 at 7:21am |
Nothing had really changed that I'm aware to cause issues.
The big delayed dropout is strange. Sometimes there is a clocking issue happening and when I play a test tone, you can hear major clicks so usually reloading my scene clears that up.
At some point however, reloading the scene started causing that dropout nearly a minute later, then it's fine.
|
|
Jperkinski
Wildcat
Joined: January/20/2014
Location: Milwaukee, WI
Points: 159
|
Posted: July/16/2016 at 8:53am |
It may be too soon to declare victory but I think I traced my recent pop/click issue to the Avid Application Manager app for Pro Tools which was recently updated.
This app while a cool idea has been extremely buggy from the start and only gotten worse.
Something about the latest update seems to have been wreacking havoc on my system/setup the last few days. I had been hearing all these tiny little clicks/pops on playback when doing simple tasks that were never an issue before. After a lot of messing around I noticed that the issue went away when I fully quit the Avid Application Manager applet that lives in the upper menu bar for OSX.
I'm stress testing now as I type this and so far so good. I did a full uninstall of that that Avid app because I can't even find the settings to prevent from opening on login as you can with most other apps.
Maybe this info will help somebody else out that is having intermittent clicks/pops and recently updated to that new version of Avid Application Manager app.
The larger delayed dropout is less critical as at least I know when to expect it and how to work around it. The frequent/random clicks thing was making me panic though. Glad it seems to be resolved.
|
|
Jperkinski
Wildcat
Joined: January/20/2014
Location: Milwaukee, WI
Points: 159
|
Posted: July/27/2016 at 11:24am |
I can't help but wonder if my recent findings in the other thread about "Should I Be Using An External Clock" will also solve this.
Will report back with more info after I have time for some real-world tests.
|
|
PaulTech
Admin Group
Joined: August/13/2004
Location: United States
Points: 5495
|
Posted: July/27/2016 at 5:06pm |
|
Could be a combination of buffer underruns and a clocking issue. Hopefully you've addressed both, and now things are smooth sailing
|
|
|
|
Jperkinski
Wildcat
Joined: January/20/2014
Location: Milwaukee, WI
Points: 159
|
Posted: July/29/2016 at 8:02am |
|
Does it make sense that only the clock wire from the 2nd AES16e snake would cause the HEDD to sync to it? I assumed that since the HEDD is connected to I/O 3-4 (or AES 2), that I would want to use the clock cable from the first snake (channels 1-8) but some reason, it only gets sync from the clock wire of 9-16.
|
|
PaulTech
Admin Group
Joined: August/13/2004
Location: United States
Points: 5495
|
Posted: July/29/2016 at 3:16pm |
There is only one BNC clock connector on the cable set. When it is connected to Port A (channels 1-8) it is a clock Input. When it is connected to Port B (channels 9-16) it is a clock Output. What you see is normal.
|
|
|
|
Jperkinski
Wildcat
Joined: January/20/2014
Location: Milwaukee, WI
Points: 159
|
Posted: July/29/2016 at 3:28pm |
Thanks. This explains a lot. When first got the AES16e I only got one snake/cable set because I didn't need to use all the I/O, and I didn't realize that the clock cable for Port A was an input. Then I recently expanded my setup and got a 2nd snake/cable set.
So this explains that when I first tried using the word clock cable on Port A only, it didn't help.
Since I figured this out, my setup has been much more stable. I'll have to do some further tests/analysis to see if I'm still getting that delayed dropout.
|
|
PaulTech
Admin Group
Joined: August/13/2004
Location: United States
Points: 5495
|
Posted: August/01/2016 at 4:21pm |
|
Sounds like good progress
|
|
|
|
New AES16e behavior (delayed audio dropout)