Quote:
Originally Posted by FatStudio  Hay
About test 2 ,I think you should have a delay as big as your latency settings.
If you want to eliminate it you should give Nuendo/Cubase a way of knowing It is looping by setting this as an External plug-in 1/1/I/O and hitting the little button on the small window it has to represent it.
This will compensate for the delay ,every DAW has this as it takes time for the computer to send sound out.
The test shows latency on your system is PERFECT :-)
And..about the spike changing ,when you send a spike to a D/A converter it overshoots ,there are no perfect spikes in the physical world.
The D/A is doing its best to create an electrical square wave which is not possible.
When this approximation of a square is feeding back to the A/D this is distorted again as the signal you sent got louder then 0DB .It might be louder by 3-6DB.. |
I'm not sure I understand your point. Forgive me if I have not understood.
If I do understand correctly, you are referring to the DAW's automatic compensation for the buffer latency. I am aware of this. Cubase (other DAWs presumably?) further has a way to manually offset recordings in increments of samples. I have made this setting so that the recorded "spike" lines up where it should and is sample accurate. In other words, my procedure 2 works perfectly. As long as no dropout occurs, this continues to work. (For the record, on my system, that setting was 1 sample with the v14 driver and is now 67 samples with the v15 driver).
However, once even one dropout happens, repeating procedure 2 reveals that any subsequent recording is now delayed (out of sync relative to previously recorded tracks) by an integer multiple of the buffer samples. Eg. with the buffer set at 1024, the delay will be 1024 samples (23 ms at 44.1K) or 2048 samples (46 ms at 44.1K), etc.