Topic: HDSP 9632 sample accurate looping problems
I sent this as a letter to support, but I wanted to post it here to see if anyone else had noticed the problem.
I own an RME 9632 HDSP PCI card and an AI4S-192 that I use in my home rig with a Presonus Digimax FS connected via ADAT giving me 14 inputs and 10 outputs. I was running some tests on my system a few weeks ago when I realized I can't get all the inputs to sync together sample accurately. The problem lies in the card misreading the latency on an input specific basis.
When the firmware for the card was updated with the 32 sample buffer for increased stability, it did not compensate for the ADAT inputs, so they are now 32 samples AHEAD of the analog inputs. The AI4S connected by the supplied ribbon cable is 13 samples AHEAD of the analog inputs.
I have tested this in both Reaper and Nuendo, and the results are the same. The drivers seem to be reporting the latency correctly for the analog out and in on the card itself, putting other inputs ahead of real time.
1. Looping a signal from the Analog out on the 9632 to the Analog IN on the 9632 gives you a perfect sample accurate locked signal.
2. Looping a signal from the Analog out on the 9632 to the Analog IN on the Presonus via ADAT gives you a signal that is 32ms ahead of the original signal. Ahead of "real time."
3. Looping a signal from the Analog out on the 9632 to the Analog IN on the AI4S gives you a signal that is 13ms ahead of the original signal. Once again, ahead of "real time."
4. Looping a signal from the Presonus Analog output via ADAT to any input increases this by yet another 32 samples ahead of the original signal.
This causes all kinds of problems with phase, etc, when using multiple inputs for a signal and is a pain to deal with in some cases. It seem obvious to me that the 9632 is reporting this new latency of 32 samples added some time ago and the ADAT is not being delayed by those 32 samples along with the Analog Ins and Outs. I'm not quite sure what would be causing the 13 sample offset of the AI4S, as this is bridged right to the card itself.
Any help on this matter would be appreciated. Also an update to fix these problems would be a big help to your user base, rather they realize it or not.