GlennO
Axe-Master
This issue comes up frequently on the forum, but the discussion always ends the same, so I wouldn't expect to see any new developments on this topic.Any new insights?
This issue comes up frequently on the forum, but the discussion always ends the same, so I wouldn't expect to see any new developments on this topic.Any new insights?
My 2013 MacBook Pro w intel I7 requires me to set a recording offset, and then everything’s fine. Interestingly enough, my son has a 2019 Macbook running Logic and hasn’t touched the recording offset setting Lol. My nephew, same thing. It’s definately not a fractal or driver issue, but a computer issue. I’m guessing that the new Macs are so fast, that there’s no need for a recording offset. Time for dad Here to get a new Mac anyway. It’s on the obsolete list. I’ll wait for the Second iteration of the M1 thoughI've been questioning myself if this has been accentuated by my Macbook Pro being almost 11 years old, running High Sierra. Actually, for it's age it still works pretty good, but I've been telling myself this latency issue is the perfect excuse for upgrading to the new M1 Mac Mini, but I'll be keeping an eye on this issue and the M1's SSD problem before commiting to the upgrade.
what latency are you guys talking about? latency when recording (hearing you play a little bit later than it should) or on playback (the just recorded track)?
I wish this video existed when I started with logic. . Explains it pretty well what should and should not be done and what are the outcomes of messing with setting you should not use unless in an extreme situation (which I guess this is not)
When recording I set my FM3 as audio input in logic. Also, plug the headphones in the FM3 to hear the reference signal and my playing. Buffer size to 128 and low-latency-mode on. Don't mess with any other options.
And don't use the monitor feature on the armed track. listen through the headphones plugged in the unit itself
Only time I had issues with latency was with Cubase on Windows and that was because I didn't had enough memory on the laptop I was using at the time, and the disk was pretty slow...
Yes, you should use the recording delay preference when working with an AxeFX. As AJ Vargas explained, the problem is only with the alignment of the recorded track, not latency.Explains it pretty well what should and should not be done and what are the outcomes of messing with setting you should not use unless in an extreme situation (which I guess this is not)
The additional latency is contributed by the USB Buffer size in the Axe-FX itself. The bigger the setting the bigger the USB latency.
Between 90-100 ms in my measurements.
That would suggest you’re getting latency over usb of at least 90 msec! Is that right? If so, what buffer size are you using in Logic?
Did a quick test between USB direct and S/PDIF into a Scarlett 18i20. Using the Axe's metronome to send a click through the digital outputs, doesn't matter Logic Pro's i/o buffer setup (32 samples in my example), the S/PDIF signal always gets recorded first, before the USB one. Between 90-100 [Edit] SAMPLES of difference in my measurements.
(Edit: The Axe FX buffer setting was at 8, the lowest possible)
View attachment 79681
I'm working on trying to sync tempo between Logic and the axe so I can setup the recording delay, but even subtracting the ping given by the I/O plugin, still can't get the recorded audio to fall in time into the grid.