Quote:
|
Originally Posted by spacewars Yes, but in order for this to be the case, the software has to know the precise number of samples of delay introduced by the hardware that's doing the DA and AD conversion for the I/O insert. I doubt that SX and Nuendo "know" this information when it comes to I/O, because that would involve them already knowing the specs of any interface that was connected. |
Yes any ASIO driver must report its input/output latency so the sequencer applications already know this. (ASIO applications often add the hardware latency to the ASIO buffer latency to calculate/display the total latency to the user.)
Quote:
|
Originally Posted by spacewars HD also calculates the delay for all TDM plugins, of course. I don't use SX or Nuendo, so I can't speak from practical experience here, but I'd be a bit surprised if this issue is handled seamlessly by those apps as it is in HD. Anyone with experience with those programs in this scenario, feel free to jump in and correct me, |
It's relatively seamless in SL3/SX3/Nuendo3, the external fx channel can be set up in VST connections, the delay to be compensated can be set along with the gain compensation. The effect can then be used anywhere in any channel (such as in a chain of software and hardware fx), there is also a 'ping' button to automatically detect the total latency of the hardware chain. (see image below.)
As I understand it, it will be integrated further in a future version (further integration of the device panel for automating MIDI controlable hardware etc).
Quote:
|
Originally Posted by spacewars In fact, I believe that on the early Neve Capricorns, there was no delay compensation so this reared its ugly head even then. Imagine spending six figures on a high-end digital desk and getting phase problems when you plug in an outboard compressor and return it on a fader! |
Ouch.
