I thought that it could have been better to open a new thread because the issue is different and so are the requests.
After several tries I got to a point that is 100% reproducible :
MG3 pushes the CPU when loaded as an AU Plugin in Ableton Live. After that event Ableton crashes 9 times out of 10.
Case 1 Steps to reproduce : Use a default Ableton Template with MG3 already loaded and create a new project. As tracks appear, Ableton CPU indicator lights up and load goes to 25%. If you open MG3 at that point Ableton Crashes. If you remove MG3 from your template then CPU does not light up when you create a new project and load stays at 4%.
Case 2 : Steps to reproduce: Use a Default template without MG3. Create a new project or use the default shown after live starts. Load MG3 (drag and drop from plugins in the Live browser) and immediately CPU (ableton) lights up and Live meter goes up to 25% (usually 4%). After this event MG3 window pops up and when you try to close it, Ableton Crashes.
MacOS 15.7.4 on MacStudio 2022 M1 Max, 32GB RAM.
In order to go on with the tests I need to uninstall MG3 and Guitar Mods (which I need to eliminate from the scenario to test a clean situation) but I am afraid I will lose the activation of MG3 and MG3 HEX. So if there’s a way to remove Guitar Mods without affecting current installation pls let me know. As a second train of tests I also need to remove MG3 completely and reinstall it from scratch, then test, that way I need activation again once removed.
Hope this helps @JamO to iron out the final release, that if I am not mistaken would not include Guitar MODS anyway.
Sorry, I cannot reproduce a crash in either case. My CPU meter sits at about 4% the whole time in both cases.
I’ll say this, though. I had a very weird problem with Live 12 about 12-18 months ago. It started registering all my audio interface’s channels as channel 1. Other DAWs worked fine but Live went totally crazy. I deleted and reinstalled Live, no joy. I created an alternate macOS user account and Live 12 worked fine under that. In the end, I gave up and wiped my device and reinstalled macOS.
Even deleting my config files and every related file for Live 12 couldn’t solve the problem. Ableton support had no idea how to help and had never seen anything like it.
So, I’m suggesting trying a new macOS user account for Live 12 and MG3 on your existing device. See if they work there. If they do, you might be looking at a clean start.
does anyone else think that this is an insane situation? why on earth would some cloud-based account setting completely bork ableton? and why would anyone design it to work that way? what was wrong with local config files?
when i fire up my music system i want to record my next hit record, not debug some weird account issue or re-install an operating system.
@JamO both win and mac platforms have been completely ‘enshittified’ and can no longer be relied upon for music making.
we need a linux option. if i may be so bold, please consider exploring this path before you start to work on mg4.
I have done done more tests. CPU indicator in Live lights up with any plugins but without crashing. One can hide this CPU indicator as it’s only a source of anxiety. A look at the MacOS monitor show that CPU cores are playing softball and getting bored while CPU in Live goes Red.
I have disabled Guitar MODS and MG3 loads fine. Because it loads fine I was able to detect that moment that got lost just a tad before the sudden crash. MG3 asks to scan plugins. I think that might be the cause. I was successful in scanning plugins and selecting a proper patch (only MIDI processing and redirection to MIDI OUT nothing else) while the one shown just after load was MINI MIDI OUT. I can’t tell if that it’s a stock patch or mine at this point. I was able to play and record after this. Let’s see in the next days how it goes. Once I have learned how to uninstall Guitar Mods I can test more.
Just switched off Live CPU ‘Warn of current CPU overload’ tick and at least I got rid of that insane and boring indicator. Since the beginning it has been criticized when it was introduced in Live 12. How it works it’s a mystery and it’s also misleading. So now I can concentrate on crashes. So far it looks that disabling Guitar MODS helped.
Thanks. That enables better understanding and rules out Drivers as it runs with CoreAudio. I have a UMC404HD (no drivers) and all channels - IN & OUT are selectable in lIve so I can say that my Audio Interface is innocent. It works very well… except for MIDI that cannot sustain a serious sysex data exchange with my VG99, albeit working fine with Notes streams. In the last two years I haven’t used my Audio Interface MIDI IN/OUT.
