First figure out which track is causing the CPU hick up. Duplicate the track and mute the duplicated version and even turn off the sound source. Bounce the left over track to audio… hide the disabled track at the bottom of my project and color it dark grey or some distinguishable color. If I ever need to make changes, just duplicate the disabled track and enable one and make changes. Then, bounce it to audio again.
Or get a M4 pro chip and pretty much solve most of any CPU issues.
This is your friendly reminder to read the submission rules, they're found in the sidebar. If you find your post breaking any of the rules, you should delete your post before the mods get to it. If you're asking a question, make sure you've checked the Live manual, Ableton's help and support knowledge base, and have searched the subreddit for a solution. If you don't know where to start, the subreddit has a resource thread. Ask smart questions.
The usual freeze, but if I’m playing back a project in progress that a live performer wants to record over I typically just resample the entire track into an audio file and open in it in a new project to save CPU so I can crank the sample rate for latency.
Can also group the whole chain for midi instruments/ effects and automate it off for parts of the song it’s not being used. But yeah why not just bounce it
Also you can up your buffer size while creating and recoding etc. but just make sure to put it back before you bounce (don’t even know if it makes a huge difference or not but I always do it)
Use low quality modes Im vsts.
Close other applications on your computer.
Bounce to audio. (Do a save as first so you have the old tracks if needed).
Have nothing on the master bus.
Be smarter with insert fx. Use groups and sends.
Freeze tracks. Don’t flatten. That way you can go back and make adjustments.
Freeze - duplicate, then flatten. Take the duplicate and put it in a separate group well labeled and disable everything on it.
Even less CPU and a saved area where you can go back to tweak :)
the beauty of bounce to new track. also, one can store those disabled tracks as templates within the project and then delete them from the set.
wait you can save disabled tracks as templates? didn't know that
tracks in general. just drag them into the browser. I like to create a folder within the project named Templates and drag them there.
yeah that's the move. flatten and keep the original disabled. I do that all the time
This is what I do!
Same for me.
Commit to audio. Old school I know, but you’ll be amazed how little you ever need to go back
First figure out which track is causing the CPU hick up. Duplicate the track and mute the duplicated version and even turn off the sound source. Bounce the left over track to audio… hide the disabled track at the bottom of my project and color it dark grey or some distinguishable color. If I ever need to make changes, just duplicate the disabled track and enable one and make changes. Then, bounce it to audio again.
Or get a M4 pro chip and pretty much solve most of any CPU issues.
all midi goes to bounce
This is your friendly reminder to read the submission rules, they're found in the sidebar. If you find your post breaking any of the rules, you should delete your post before the mods get to it. If you're asking a question, make sure you've checked the Live manual, Ableton's help and support knowledge base, and have searched the subreddit for a solution. If you don't know where to start, the subreddit has a resource thread. Ask smart questions.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
The usual freeze, but if I’m playing back a project in progress that a live performer wants to record over I typically just resample the entire track into an audio file and open in it in a new project to save CPU so I can crank the sample rate for latency.
Can also group the whole chain for midi instruments/ effects and automate it off for parts of the song it’s not being used. But yeah why not just bounce it
Also you can up your buffer size while creating and recoding etc. but just make sure to put it back before you bounce (don’t even know if it makes a huge difference or not but I always do it)
buffer size doesn't affect the bounce. it's just for monitoring latency while you're working
Currently, the bounce function in ableton Live is independent of cpu saving.Eventually, we need to use the freeze function
Other daws use bounces to save cpu because the freeze and bounce functions are performed at the same time when bouncing.
Right now, Live is not 100% making use of Bounce's advantages.
increase buffer to max
Use low quality modes Im vsts. Close other applications on your computer. Bounce to audio. (Do a save as first so you have the old tracks if needed). Have nothing on the master bus. Be smarter with insert fx. Use groups and sends.
If all else fails get a used M1 Max