Maybe there is some description for it, but i did not find it ( that said the Cubase manual for latency compensation is not much longer, but this is off topic here )
Cubasis 3 does display the device latency plus some values in a drop down list.
It is not clear if the “plus” means, that the real latency is the sum of both values.
And if so only for input or input + output.
Then there is the “Audio Recording Offset Compensation”.
No drop down list, but a slider , it takes some patience to set low values with this slider control.
Question: Shouldn’t the values of the offset compensation aligned to the latencies ( “plus” or not ) ?
What i found by trial and error, that the device latency displayed seems a good value for the offset compensation, when recording audio with the metronome.
When monitoring an audio track, the latency is different, i did not found what a good value is for this use-case, which isn’t so uncommen i guess e.g. when some AU effects are used for recording especially.
Sure i’ve read ( in the Cubase manual ) that you should prefer direct monitoring and then no offset compensation should be necessary, but this seems not to work with cubasis and its metronome which seems to include some latency.
All i wrote is for iPad and an iRig HD interface ( has no audio out, therefore also no direct monitoring possibility ).
Maybe i misunderstand the offset compensation completely and only my timing is bad, but because there is a clear difference in the recording result when recording to the cubasis metronome and track monitoring as i describe above i think the offset compensation matters.
Therefore it would be helpful to have some advice, how the latency settings and the offset compensation is intended to be used for different use cases.
( “Calibrate” seems to work with the internal iPad microphone, results are more or less stable, but connecting the iPad Audio output to the iRig HD input or with a microphone connected to the iRig HD resulted only in varying results, often 0ms, which is obviously wrong, so its not working for that use case ).