this feature, auto arm on selection and show device slots should become mandatory . ooh... and for the love of god ARA. Really cool to see some traction in feature requests. Also today i have noted say you're using a kick as a sc trigger in my case kickstart 2, once you freeze your drums buss the trigger is no longer detected to duck the bass.
Sometimes we want to process several tracks together, so we group them and apply effects to the group. But then we may want to turn the whole group into an audio clip, for example for editing purposes. Freeze and flatten makes it much quicker, than having to resample (which is essentially recording the audio in real-time). Or simply freeze it so that the effects don't overload our computer's processing power.
When I freeze my drum group, the effects are turned off, but there is no reduction in my CPU load. I don't want to flatten it; I just want to freeze it so I can go back whenever I want. Do you have any idea why this is happening?
Yeah, good point, you will have to re-enable it for every update, just copy the options.txt into the folder of the next version as it updates. I think if it was in the beta without the need to use the options.txt, it would have been documented in the release notes.
Great, thanks for sharing! May be useful to someone who is still on 12.0 even though I don't see a reason to stay on it, 12.1 has been working great for me.
That won't happen. Freezing means bouncing to audio in the background and locking the state of the track. Freezing a specific effect or group in a chain means nothing before that group/effect will further alter the output
@@yeezythabest I could be wrong, but I think that Bitwig could be doing something similar. Also they have hybrid tracks where I can flat out half of the melody for example. This is super cool
Before I updated Ableton from 12 to 12.1, I could zoom in on a long sample anywhere using the magnifying glass tool. Now, after the update, I can't seem to do that anymore. It's making it a lot harder to chop up samples. Has anyone else experienced this or know how to fix it?
When I freeze my drum group, the effects are turned off, but there is no reduction in my CPU load. I don't want to flatten it; I just want to freeze it so I can go back whenever I want. Do you have any idea why this is happening ?
Most likely because there's another track in the project that uses more CPU. The CPU meter in Live doesn't really show the overall CPU usage but rather how close you are to overloading one of your CPU cores. And since a track can only be processed by a single core, a single track may push your CPU meter higher, with the group having no effect on it. In my project I saw a noticeable decrease in CPU when I froze it.
@@LowHeatBeats I have a plugin called Orion on my drum bus channel. The other materials don't use much CPU, but Orion uses a lot of CPU. When I freeze my drum bus channel to save CPU, the CPU usage doesn't change at all. Am I doing something wrong?
@@BurakKaya-y6j I don't think you're doing anything wrong. But my advice is to ignore the CPU meter. Unless you're getting pops and crackles, it really doesn't mean anything. I never look at it tbh.
@@LowHeatBeats I have an i7 11700k processor. However, when I try to mix a beat project along with the vocals, I end up hearing crackles at the end. I'm using an Apollo Twin USB audio interface, but it's not taking much of my CPU load. Honestly, I was excited about the solution in this video, but it didn’t help with my CPU power. Still, thank you for the video, it was great
If you turn off the drum bus entirely, is there still high CPU usage? This would help you determine if the Orion on your drum bus is actually the issue or not. Also, this feature is still experimental so you might be doing nothing wrong and it just won't benefit this particular track right now.
Fair enough, it might be a bit buggy, it's an experimental feature after all. Also, undo doesn't affect it after you freeze. But a lot of people would use it for resampling, so if you freeze and flatten, you're good and no issues when re-opening the project.
I'd rather a proper bounce-in-place*. This is just ridiculous! * yes, I'm aware I can resample, but it's a process vs. one click in Bitwig, Reason, Studio One, Cubase, etc.
My Ableton Live packs ► lowheat.gumroad.com
Thank you, this worked well!
Glad it worked!
Big thanks
My pleasure!
❤ watching my man doing windows tutorials as well gives me hope in humanity again 😂
lmaooo
Thanks!!!
thanks!
My pleasure!
powerful info sir,, thank u
OMFG! Finally! ❤
this feature, auto arm on selection and show device slots should become mandatory . ooh... and for the love of god ARA. Really cool to see some traction in feature requests. Also today i have noted say you're using a kick as a sc trigger in my case kickstart 2, once you freeze your drums buss the trigger is no longer detected to duck the bass.
What is the purpose of freezing a group in ableton live. I'm a newbie, thanks.
Sometimes we want to process several tracks together, so we group them and apply effects to the group. But then we may want to turn the whole group into an audio clip, for example for editing purposes. Freeze and flatten makes it much quicker, than having to resample (which is essentially recording the audio in real-time). Or simply freeze it so that the effects don't overload our computer's processing power.
When I freeze my drum group, the effects are turned off, but there is no reduction in my CPU load. I don't want to flatten it; I just want to freeze it so I can go back whenever I want. Do you have any idea why this is happening?
Cool feature. I have a feeling it's disabled everytime Live updates. Wonder if it's implemented on the beta version or same Options.txt file
Yeah, good point, you will have to re-enable it for every update, just copy the options.txt into the folder of the next version as it updates. I think if it was in the beta without the need to use the options.txt, it would have been documented in the release notes.
It works in 12.0 too we just didn’t know the option existed
Great, thanks for sharing! May be useful to someone who is still on 12.0 even though I don't see a reason to stay on it, 12.1 has been working great for me.
Yay!
wow finally
Now they have to add the feature to freeze a group of effects in my chain and i will be sold forever on Ableton
That won't happen. Freezing means bouncing to audio in the background and locking the state of the track. Freezing a specific effect or group in a chain means nothing before that group/effect will further alter the output
@@yeezythabest I could be wrong, but I think that Bitwig could be doing something similar. Also they have hybrid tracks where I can flat out half of the melody for example. This is super cool
Before I updated Ableton from 12 to 12.1, I could zoom in on a long sample anywhere using the magnifying glass tool. Now, after the update, I can't seem to do that anymore. It's making it a lot harder to chop up samples. Has anyone else experienced this or know how to fix it?
I haven't had any problems with zooming tbh. Is this on the timeline or in Simpler?
@@LowHeatBeats it’s in the timeline!
When I freeze my drum group, the effects are turned off, but there is no reduction in my CPU load. I don't want to flatten it; I just want to freeze it so I can go back whenever I want. Do you have any idea why this is happening ?
Most likely because there's another track in the project that uses more CPU. The CPU meter in Live doesn't really show the overall CPU usage but rather how close you are to overloading one of your CPU cores. And since a track can only be processed by a single core, a single track may push your CPU meter higher, with the group having no effect on it. In my project I saw a noticeable decrease in CPU when I froze it.
@@LowHeatBeats I have a plugin called Orion on my drum bus channel. The other materials don't use much CPU, but Orion uses a lot of CPU. When I freeze my drum bus channel to save CPU, the CPU usage doesn't change at all. Am I doing something wrong?
@@BurakKaya-y6j I don't think you're doing anything wrong. But my advice is to ignore the CPU meter. Unless you're getting pops and crackles, it really doesn't mean anything. I never look at it tbh.
@@LowHeatBeats I have an i7 11700k processor. However, when I try to mix a beat project along with the vocals, I end up hearing crackles at the end. I'm using an Apollo Twin USB audio interface, but it's not taking much of my CPU load. Honestly, I was excited about the solution in this video, but it didn’t help with my CPU power. Still, thank you for the video, it was great
If you turn off the drum bus entirely, is there still high CPU usage? This would help you determine if the Orion on your drum bus is actually the issue or not. Also, this feature is still experimental so you might be doing nothing wrong and it just won't benefit this particular track right now.
AT LAST.
Thanks maan!
No.if you save the project and reopen it,freeze is not there..But YES this is Big if finally works as it should..
Fair enough, it might be a bit buggy, it's an experimental feature after all. Also, undo doesn't affect it after you freeze. But a lot of people would use it for resampling, so if you freeze and flatten, you're good and no issues when re-opening the project.
I'd rather a proper bounce-in-place*.
This is just ridiculous!
* yes, I'm aware I can resample, but it's a process vs. one click in Bitwig, Reason, Studio One, Cubase, etc.
You have the freeze and flatten command that does it with one click here too.
@@LowHeatBeats Sure, but it applies to whole track that can sometimes takes minutes to process. BiP works in selection.
Aahh yeah true, I get what you mean
i tried to phase cancel with no luck at all. I guess this feature is still not entirely well developed.
Well yeah, they probably wouldn't hide it if it was perfect. But honestly, it doesn't bother me if it doesn't cancel completely in a null test
what??