@AlbertA shouldn't we be compensating for possible latency cause by the click going all the way back into the Axe fx after d/a and d/conversion from the 'reamping' of the click?
Because when we're playing guitar we're only going through one A/D, but when we're reamping the click through the loop we're getting another extra D/A.
Perhaps we should add -265 (or whatever number is was) to the result of the offset measuring test?
When you record the loopback you are measuring all of the latency encountered, both playback and recording - that's why it's the most accurate thing you can do. This includes the DAC and ADC latency because you are using an external loopback cable.
If you change the ASIO settings (including checking/unchecking safe mode) or the USB Buffer size in the Axe-Fx III, you'll have to change the compensation.
Yes I understand, but if you compare the test to 'regular' recording, isn't there one stage of conversion less than during the test, thus making you need to compensate for that one more stage for recording?
Hope this makes sense...
I edited the post above while your wrote this
I was recording a riff today.
It has super fast but steady 16th notes in the high D string.
Each time I got a very satisfying take it sounded just a little too fast when I played back the take.
I know from experience that I usually tend to play slightly laid back but never really too fast so I decided to try 900 and I think that offset is more accurate for me despite the test result being 1160.
Strange...
IDK. It seems like asking the Axe Fx III to serve as an audio interface is a bit much. I'd suggest getting a good audio interface. No? I don't know. What do I know? I've never used it as an audio interface. I have plenty of high end ones so I don't need to. But it's a speciality tool.
No problem with my 2XL+ but I’m maybe too sloppy to notice...
I know but why wouldn’t the III be able to do correctly what the 2XL can do ?
It’s indeed a problem with the 3 or its driver that should be solved.
I know but why wouldn’t the III be able to do correctly what the 2XL can do ?
It’s indeed a problem with the 3 or its driver that should be solved.