Sudden CPU Issues - Ableton Reset Needed?

[adam_mc]

Hi and Happy New Year.

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?

Thanks for any help,
Adam

[jestermgee]

I would recommend raising discussions about Beta versions in the Beta forums on Centercode since anyone with the Beta will be registered on there...

But possibly if it's doing it after a crash it could have a corrupt library database and be rescanning the library. Maybe leave it for 10 minutes with live open and see if it settles. Though i'd collect a crash report and send it to Ableton at the very least if it crashes again and if the issue continues maybe start a thread in centercode.

[adam_mc]

Yeah,
I was going to post on the Beta forum but the fact that my 9.7 was also presenting the samee issues encouraged me to post here too.

I've left the machine and live for over 30 minutes: no change.

[Mark Williams]

sounds like a database issue, have you tried a rebuild on database?

Does it occur with other vst's?

See your only down road from me in Kent.

[adam_mc]

Cheers Mark.
Any advice is welcome at the moment.
Yeah I'm just down the road; I worked in Deal for nearly 3 years at the secondary school there.

With your database idea; how do I do a rebuild.

Thanks for your help and Happy New Year.
Adam

[chrk]

With your database idea; how do I do a rebuild.

Here's the instructions: "Can't access file database: Database Error: Disk I/O error"

But be patient, a full rebuild may take longer than the 30 mins you've let Live idle in the other post.

There's another knowledge base article on how to reset preferences: How to reset Live. But I'd try the database first.

[adam_mc]

Tried all these things. No change.

Not sure whether to try using Sierra OS to latest version. May bugger other things up though and not solve this.

[Mark Williams]

Is it just Repro this happens with. Anything else running in background taking up disk/cpu usage. Im PC so no nothing about Macs.

which school Walmer sec or Castle, or whatever there names are now, - why o why do schools keep changing names. lol.

[adam_mc]

Finally solved this issue last night.

I run a Geekbench test on my Macbook; it came back with results that were a third of what the machine should have been capable of.

Read around a bit; did an SMC reset; restarted the machine and then Live. Everything suddenly as right as rain.

Thanks to those who responded with suggestions. Happy New Year to you.

Adam