I shouldn’t have been so vague. All previous versions run great. 12.1 hangs when starting the program. I never got to try the beta or the stable release.
I think someone up-thread mentioned some issue related to some bad sample names or tags causing issues with the new auto-tagging feature.
Maybe try moving samples out of your library and then add them back once you’ve got Live going?
There’s some things to try:
https://help.ableton.com/hc/en-us/articles/209775545-Live-is-slow-to-start-or-hangs-on-launch
Weird. It runs just fine - i.e. awesomely! - on my recently purchased 14’’ M2 Pro MacBook Pro.
Yeah, you shouldn’t have.
12.1 also works perfectly on my 16" M2 Max Macbook pro. Just finished mastering the latest EP with 12.1 last Sunday. Now to finish the album art!
1 Like
Runs excellent on mine. M2 mac mini 16gb Ram.
1 Like
What happens? I’m on a M1 Macbook Air.
Well I’ve done a complete uninstall of all Ableton files as well as the user library and reinstalled and it now works! Before that it would open, scan plugins, and then not respond. Removing samples and plugins from the process didn’t help, nor did resetting preferences and the other suggestions (at least as well as I understood them).
4 Likes
That’s strange. Live 12.1 works just fine on my M1 MacBook Pro.
I think it performs very well for my purposes. My M1 Macbook Air has 16GB of RAM and I can run sessions with heavy VSTi usage and plugins at 64 samples without problems. This isn’t the machine I build up the heaviest mix sessions on (I use an M2 Studio for mixing now which has helped a lot for very heavy plugin use), but for getting ideas going and keeping workflow smooth, it’s very nice.
2 Likes
Global/project scale and the scale device: has anyone else had issues with seemingly random changes to these devices when interacting with their project? For example, currently working with a project/track, project/global scale is A Lydian. In attempting to arm a resampling track, the whole project returns to default C Major and knocks everything out…
2 Likes
Just to clarify, on the Track Input, you selected Resample?
Are you on the main 12.1 release, or the beta?
I haven’t had anything like this happen, but I don’t usually use the Resample option. It still shouldn’t have an effect on the global scale.
I’ll try and reproduce it.
No luck on the beta. The track resampling was automatically set to A Lydian.
1 Like
I feel like I’m always having to reset the Global scale at the top, as well as within clips. Maybe I’m just doing something wrong? But it seems like my scale choices never stick across the project.
2 Likes
Thanks for attempting to replicate @elxsound!
Eventually deleting the pre-existing resample track and introducing a new one resolved the issue.
As you say @Bwax, not my first experiences with this…
On 12.1, main/public release, Mac M1. Haven’t yet identified a pattern but I’ll start logging and report to Ableton.
2 Likes
I think I’ve noticed this though I don’t really use the scale feature. However I’ve noticed that if you set the scale on the top before you create any clips and set scales there, the behaviour seems to stick through the project. But if you create a clip then set the scale there and the top is still at default it’s not going to be as consistent.
1 Like
This is my least favorite part of how Ableton designed this feature. I get why it’s up there instead of the clip inspector; all new clips will use that scale, but it’s also the only thing in the bar that changes depending on selection (following two decades of the transport bar not having any selection-dependent controls!) and the default changes based on your last selection.
I would have had it global but automatable, just like tempo and time signature.
6 Likes
Anyone else using the Beta version with P3 and finding that you can’t adjust trigs that are in a clip when you hold them to choose them from the clip view?
What I mean is - editing a clip and the trigs that exist within it. When you have the clip selected for a drum pattern and the pads are lit where the samples are triggered - you can typically hold one of the trigs and have access to the velocity of that event and nudge etc. However, the last few Beta releases don’t allow me to chance the value of the velocity when I am holding the trig.
I went back to 12.1 non beta and it works fine there.
Ideas?
Cheers,
Adam
Like how it is in Logic?
If you’re structuring out a song based on chord progression it makes perfect sense to see Scale / Chord as an automatable lane/track. At least in Logic it’s extremely cool to build out a song using the chord track tool. I mean, it’s entirely allowed me to build songs and track progressions in the box without having to remember, or write it on a note pad lol. If i’m thinking of it correctly, it would be huge of Ableton to implement this.
2 Likes