Quote:
Originally Posted by Arksun  So if I understand this correctly, if you have more than one UAD-1 card, don't get the lynx.
If you have 1 UAD card, there may still be a few dropouts so its a questionable buy.
If one uses no UAD card or outboard fx, the Lynx runs just fine?
Seems there's a lot of anti-Lynx talk around giving the impression their drivers suck period, when the reality seems to be more like, they're rock solid and fast UNLESS you run UAD cards. |
I only have experience with the Lynx Two and the AES16, not the AES16e. Preliminary reports from one other user suggests that the AES16e might have similar issues. I don't know from personal experience, so I can't comment.
The AES16 and Lynx 2 have a sensitivity to dropouts, UAD-1 or no UAD-1. Why exactly this is, I don't know. But this phenomenon has been reported by numerous users with different systems.
With two or more UAD-1s, the problem is more much more accute: loading more than one plugin = dropout. This has been confirmed. I used this in my procedure 1 in the thread linked to earlier because this is 100% repeatable, even with a buffer of 1024.
But a dropout can occur independent of any UAD-1s. Setting the buffer low (or not so low) and taxing the system will do it. The dropouts can occur during playback but also in stop mode (transport not running). They can occur when you first load you DAW. They can occur when you rest the ASIO driver. They can occur when you minimize/maximize the DAW window.
There seems to be dropout problem with Samplitude, but since I am not a Samplitude user, I won't comment.
That's issue #1.
Issue #2 is that when a dropout occurs, you are not always alerted that this is the case. When the dropout occurs in stop mode, e.g. when loading a second UAD-1 plugin in a multicard system or when you first launch the DAW, you get no notification unless you look at the Lynx Mixer application. Frequently there is no error, message, nor audible glitch to alert you that this has happened. So unless you know to check, a dropout that has occurred can go undetected. If it weren't for issue #3 described below, undetected dropouts during stop mode wouldn't be a big deal.
Issue #3 is that once a dropout has occurred, any recording made thereafter is out of sync (delayed by a multiple of the buffer size) relative to any pre-existing tracks until the ASIO driver is reset. The recording does not get ruined in the sense of having an audible crackle or pop, rather it is just late relative to the rest of the tracks. To me, this is the big problem. I'd rather have audible dropouts but in-sync recordings as opposed to concealed dropouts and out-of-sync recordings. Lynx seems to feel differently, as near as I can tell.
It's possible that there may be other issues ...
My workaround is to set up my Lynx Mixer window and Cubase window as in the image below. As soon a dropout occurs, I see it in red and reset the ASIO driver. It'a hassle but it allows me to work without out-of-sync tracks (something I was not able to do for over a year until I figured out what was happening -- I thought my timing sucked). [EDIT: couldn't attach image, see the thread drmad69 linked to on the previous page of this thread.]
There is an HDSPe in my future ...