I’ve posted this on the Ableton website and also contacted support but I thought I would also post here as this forum has many Live users and also is a very helpful and often viewed place.
So, I have this set that triggers my OT which in turn controls my MD and A4. All the audio then into Live and I VST stuff with it. Then . . .
Up until yesterday morning, everything on my Macbook running Sierra was working fine.
I have been using Live 10 Beta but also have Live 9.7 installed.
Yesterday morning I experienced a programme crash while using the beta. Nothing worrying about that. However, I didn’t reopen live. I closed my machine down and went and started to prepare for the celebrations of the new year.
Yesterday evening I return to my macbook. I switch everything on. Open Live 10 Beta (which has been pretty solid regardless of the rare crash that had taken place). It asks if I want to recover my set; I said no.
Live opens but the CPU is hitting 135% when only having Repro 5 loaded. Playing more than one key and the audio collapses. Playing one key is just about manageable. Prior to the crash I could have 3 instances Repro.
I have removed Repro and tried Diva. Same issues. Any VSTs that I load cause the CPU to jump to insane levels.
This happens if I open Live 9.7 also.
So . . .
I will send this into Ableton but imagine it’ll be a while before I hear back; New Year’s Hangovers take a while to clear.
In the meantime - what files are there that I can delete that may be holding historical data that is corrupting Live?
I’ve had experiences like this with ableton, where for some unknown reason, suddenly the cpu usage goes crazy, and I can’t figure out what is wrong. The project wasn’t taxing to the cpu at all, and suddenly we’re over 100%.
The only tip I have is to try and group tracks and drag them into a folder in the browser. This will save the entire groups with all the tracks, and I think the arrangement as well, but I’ve only tried it with clips. Then create a new project and drag the group or tracks into that. Might fix it, and it’ll take you less time than waiting for Ableton to respond Good luck.
Thanks for your advice.
I’ve tried similar actions.
Even starting a whole new project. From search. Just load one VST. Crunch. It’s not able to process any of it.
Hmmmm.
Sometimes deleting the preference file can clear up issues with an app that crashed…
You will loose all the preferences you set for Ableton but it will create a new default preference file and you can redo them…
I have not done this with Ableton but have with Logic and a few other apps, so perhaps Google some more info about deleting ableton preference files (.plist) to feel more comfortable about it.
The folder is ~/Library/Preferences and you can access it by holding option under the go menu…
Again do some more research, but usually anything in that folder can be deleted and a fresh one will be made next time the app is open, so you may be able to delete anything with ableton in the filename…
After deleting, empty trash, reboot, open ableton, redo preference settings…
Good luck!
Diva also causes the same issue. That’s been working fine for months and months and months. To the point I could run 4 instances. Currently cannot successful run 1.
Hmmmm. Weird.
Good luck.