Ableton recording latency issue
-
- KVRist
- Topic Starter
- 37 posts since 25 Jun, 2020
Lately, I've been experiencing some latency issues with Ableton when recording.
Using Ableton 10.1, Focusrite Saffire Pro DSP 24.
I've never had this issue before but now, even when recording in a new session, even when 'Low latency monitoring' is ticked, I get a huge amount of latency. This happens even with buffer size set to 64 samples and I can't seem to shake it off. Impossible to record anything. Tried uninstalling and re-installing, tried changing the buffer a few times, clearing the cache folder. Nothing helps.
In Pro tools - everything works great. No latency, same setup.
Does anyone have any idea what's going on?
Using Ableton 10.1, Focusrite Saffire Pro DSP 24.
I've never had this issue before but now, even when recording in a new session, even when 'Low latency monitoring' is ticked, I get a huge amount of latency. This happens even with buffer size set to 64 samples and I can't seem to shake it off. Impossible to record anything. Tried uninstalling and re-installing, tried changing the buffer a few times, clearing the cache folder. Nothing helps.
In Pro tools - everything works great. No latency, same setup.
Does anyone have any idea what's going on?
-
- KVRer
- 28 posts since 25 May, 2020
Running at 64 samples can still give you lots of latency, depending on what's going on in and around Ableton. Try a higher buffer size like 512 + direct monitoring through your sound card. Do you have a lot of CPU-heavy plugins running? Other programs running apart from Ableton, even something like Google Chrome? This kind of stuff can contribute to latency as well.
- KVRAF
- 15269 posts since 8 Mar, 2005 from Utrecht, Holland
Check setup of the audio device. Is driver type WDM or Asio selected? It should be Asio. See step 4 here:
https://help.ableton.com/hc/en-us/artic ... -Interface
https://help.ableton.com/hc/en-us/artic ... -Interface
This is wrong. Larger buffers give more latency. But less chance of drop-outs.
Again, nope. Maybe causing dropouts, but other running programs can not contribute to latency.Other programs running apart from Ableton, even something like Google Chrome? This kind of stuff can contribute to latency as well.
We are the KVR collective. Resistance is futile. You will be assimilated.
My MusicCalc is served over https!!
My MusicCalc is served over https!!
-
- KVRist
- Topic Starter
- 37 posts since 25 Jun, 2020
Yeah, it's selected as ASIO, still, I'm getting a huge amount of latencyBertKoor wrote: ↑Tue Jul 14, 2020 3:32 pm Check setup of the audio device. Is driver type WDM or Asio selected? It should be Asio. See step 4 here:
https://help.ableton.com/hc/en-us/artic ... -Interface
will try a different audio interface in the next few days and check if the issue remains.
It's very odd as it happens even with new projects (one track, no plugins whatsoever) and my computer is very strong and I can't spot any CPU peaks as well.
-
- Banned
- 1780 posts since 26 Aug, 2012
could be a plugin dats causing dis shit. ozone and adaptiverb and little alter boy cause latency on other tracks
-
- addled muppet weed
- 105825 posts since 26 Jan, 2003 from through the looking glass
- KVRAF
- 9788 posts since 18 Aug, 2007 from NYC
+1
What else do you have in your Live set?
Do you have other plugins already there? Anything saved in your template set that maybe you forgot about? - Such as on a return track or the master track?
Some delays effect plugins also cause latency (if you've added to a return track)
For the plugins added in your set, you can view the latency added just by hovering the mouse cursor over the title bar of the plugin added.
https://help.ableton.com/hc/en-us/artic ... ive-device
Like the ones Kinh mentioned as examples... those cause lots of latency. Removing them (not just deactivating them) will resolve your issue.
**EDIT** Also double check if there are any native effects anywhere. I just noticed that Live's Limiter introduces 128 samples of latency too.
-
- Banned
- 1780 posts since 26 Aug, 2012
wha?
-
- KVRist
- Topic Starter
- 37 posts since 25 Jun, 2020
Thanks! I'll double-check all of that during the weekend.elxsound wrote: ↑Wed Jul 15, 2020 3:50 pm+1
What else do you have in your Live set?
Do you have other plugins already there? Anything saved in your template set that maybe you forgot about? - Such as on a return track or the master track?
Some delays effect plugins also cause latency (if you've added to a return track)
For the plugins added in your set, you can view the latency added just by hovering the mouse cursor over the title bar of the plugin added.
https://help.ableton.com/hc/en-us/artic ... ive-device
Like the ones Kinh mentioned as examples... those cause lots of latency. Removing them (not just deactivating them) will resolve your issue.
**EDIT** Also double check if there are any native effects anywhere. I just noticed that Live's Limiter introduces 128 samples of latency too.
As far as I can remember, there were absolutely no plugins on this project and it happens every time. Also, another thing is that there are occasional clicks and pops (CPU overload-like) but my computer is very strong and I wasn't able to notice anything on the task manager.
I'll check all of that and maybe try uploading a short video showcasing it.
-
- Banned
- 1780 posts since 26 Aug, 2012
my money's on da other pluginscurtiscole wrote: ↑Thu Jul 16, 2020 9:57 amThanks! I'll double-check all of that during the weekend.elxsound wrote: ↑Wed Jul 15, 2020 3:50 pm+1
What else do you have in your Live set?
Do you have other plugins already there? Anything saved in your template set that maybe you forgot about? - Such as on a return track or the master track?
Some delays effect plugins also cause latency (if you've added to a return track)
For the plugins added in your set, you can view the latency added just by hovering the mouse cursor over the title bar of the plugin added.
https://help.ableton.com/hc/en-us/artic ... ive-device
Like the ones Kinh mentioned as examples... those cause lots of latency. Removing them (not just deactivating them) will resolve your issue.
**EDIT** Also double check if there are any native effects anywhere. I just noticed that Live's Limiter introduces 128 samples of latency too.
As far as I can remember, there were absolutely no plugins on this project and it happens every time. Also, another thing is that there are occasional clicks and pops (CPU overload-like) but my computer is very strong and I wasn't able to notice anything on the task manager.
I'll check all of that and maybe try uploading a short video showcasing it.
- KVRAF
- 9788 posts since 18 Aug, 2007 from NYC
A few more questions...
When you say you never experienced this before... What if anything can you remember changing? Any recent upgrades either to the operating system, driver for Focusrite or update for Live?
Any updates to anything else?
Is it safe to assume that you used to be able to record into Live 10.1 without these same latency problems?
When you say you never experienced this before... What if anything can you remember changing? Any recent upgrades either to the operating system, driver for Focusrite or update for Live?
Any updates to anything else?
Is it safe to assume that you used to be able to record into Live 10.1 without these same latency problems?
-
- KVRAF
- 4276 posts since 8 Mar, 2005
Disable PDC and try again. iZotope ozone plugins are notoriously heavy on CPU and buffer-size. Use these when you're in the mix process, not while tracking. This is what I do in logic - i.e. disable PDC during recording and re-enable during mixing.
Other items to watch: Convolution plugins, any "linear phase eq", etc.
Other items to watch: Convolution plugins, any "linear phase eq", etc.
-
- KVRist
- Topic Starter
- 37 posts since 25 Jun, 2020
ACTUALLY - I SOLVED IT!!!
It was my audio interface all along or the driver itself, not sure yet. Anywho, I updated it to the latest version but still - no cigar. Unplugged the interface, plugged in an RME Babyface and - problem solved.
It was my audio interface all along or the driver itself, not sure yet. Anywho, I updated it to the latest version but still - no cigar. Unplugged the interface, plugged in an RME Babyface and - problem solved.
-
- KVRist
- Topic Starter
- 37 posts since 25 Jun, 2020
I'd still like to try another Focusrite interface that uses the same driver to satisfy my pervy audio-loving brain and understand whether the interface was the issue or whether it was the driver all along. But either way, for now - I'm good