iPad recording latency… Help me

metropolis_4

Rock Star
Messages
4,065
I used to use GarageBand on my old iPad to record and it worked great. With my new iPad I can’t figure out how to make it work.

Using my fm3 as an AI I’ve got instrument plugged into the fm3 -> usb to iPad -> monitoring from the output on the fm3. The problem is I’m getting latency somewhere so when I play back something I recorded it is behind the beat.

I’m trying to figure out why this same thing worked fine with my old Lightning iPad but it doesn’t work with the new usb-c one. Is there some difference in how the two work?
 
Crap, I can’t try it right now, but I will first thing tomorrow if someone doesn’t answer you. FWIW, I’ve got the FM9 and an iPad A16 (current base model with USB-C).
 
The USB recording function of the FM3 doesn’t report the latency of the blocks it seems. It reports the device latency, but I think Amp+Cab blocks add something in the 40ms range. If you search around on the Fractal forums, you’ll find threads on the topic.

I think it got fixed on the FM9 and Axe-FX III, but is still an issue on the FM3. I unfortunately couldn’t find a way to enter latency offset in GarageBand to automatically compensate for this problem.

What worked for me when recording and overdubbing with the FM3 as an audio interface on a computer or iOS device:
-Load up your typical FM3 patch with an amp and cab block. Pick a clean amp.
-Pick a test audio file with an identifiable transient like an IR.
-Send the audio file to Output 3+4 on the FM3.
-With the Input 1+2 Source in the I/O setting set to USB, record arm and record the reamped signal.
-Figure out the offset required to align your recorded signal with the test audio file.

On a full fledged DAW, I can figure out the exact number of samples to enter an offset into the DAW settings (somewhere in the 2100 range). On my iOS recording app (Cubasis), adjusting for 49ms gets it close enough for me. I think I typically have UltraRes IRs pulled up when checking this latency. Not sure if Dynacabs or the shorter length IRs change the latency.
 
The USB recording function of the FM3 doesn’t report the latency of the blocks it seems. It reports the device latency, but I think Amp+Cab blocks add something in the 40ms range. If you search around on the Fractal forums, you’ll find threads on the topic.

I think it got fixed on the FM9 and Axe-FX III, but is still an issue on the FM3. I unfortunately couldn’t find a way to enter latency offset in GarageBand to automatically compensate for this problem.

What worked for me when recording and overdubbing with the FM3 as an audio interface on a computer or iOS device:
-Load up your typical FM3 patch with an amp and cab block. Pick a clean amp.
-Pick a test audio file with an identifiable transient like an IR.
-Send the audio file to Output 3+4 on the FM3.
-With the Input 1+2 Source in the I/O setting set to USB, record arm and record the reamped signal.
-Figure out the offset required to align your recorded signal with the test audio file.

On a full fledged DAW, I can figure out the exact number of samples to enter an offset into the DAW settings (somewhere in the 2100 range). On my iOS recording app (Cubasis), adjusting for 49ms gets it close enough for me. I think I typically have UltraRes IRs pulled up when checking this latency. Not sure if Dynacabs or the shorter length IRs change the latency.

Solid information, and mine would have been irrelevant anyway, had I not seen a squirrel and forgotten about this thread.
 
Here’s the most informative thread about stuff not lining up with the FM3 USB recording:
https://forum.fractalaudio.com/threads/latency-compensation-measurement.177851/

Using the FM3, either through its analog outs or SPDIF, into another audio interface is a workaround for those who don’t want to mess around with offsets.

I think the little Black Lion 2x2 has SPDIF, and works with iOS/iPadOS, which is a cool, albeit not cheap solution:

 
Back
Top