Ableton Forum

I recently upgraded to Live 10 Standard. Often but not always, if I open Live 10 and then open a Live Set that includes the Amplitube 3 plug-in, I get an error message that tells me "some plug-ins could not be loaded and are disabled - VST 'Amplitube 3': the VST plug-in could not be opened". If I open the Live Set directly from the Finder window on my Macbook Pro, this problem does not occur and the Set runs reasonably well. This error message never appeared with Max for Live 8 or 9, though. Is this an indication of any issue or incompatibility?

I also find that running Amplitube 3 in Live 10 seems to be demanding on my CPU. My CPU meter seems to drop significantly when I delete an instance of Amplitube 3. (I am desperately searching for anything that will help me eliminate glitches when performing live.) Could this be related in any way? If anyone has tried it, has upgrading to Amplitube 4 helped with either problem? I'm a little wary of upgrading since it's not cheap but if it can help things run more smoothly, I'm happy to do it.

This issue doesn't appear with Amplitude 4. But this v4 is a CPU hog...
Maybe there's a good news though: since the last few betas I haven't encountered this v3 problem.
I can't think of anything mentioned in the release notes about such thing, so it might have been solved unintentionally as a consequence of solving another bug. I've noticed this really recently and I can't guarantee anything as I'm still waiting for someone to dig in my report for an answer.

Ironically I've just experienced the issue back again...
Did you report to [email protected] ?

I mentioned it in the context of a broader question I was having about Live 10's performance. All they really said was "if you think that a newer version of Amplitube is available I always recommend keeping Live and Plug-in up to date".

Yeah, but still Amplitude 4 needs way more CPU.
I've to do some more testing, but from the last ones I did this morning I have the feeling that Amplitude 3 loads only with sets originally created with L10.
You also have to make sure not to load any pre-L10 sets that contains this plugin. If you do so, then you need to completely stop the program and launch again.
So far these observations look reliable, but as I said, I need to spend a bit more time testing other situations.

Thanks, that helps. Extra CPU usage is what I was worried about with Amplitube 4.