Post
by Eanna » Thu Mar 07, 2024 8:35 pm
At the end of the day, there should be zero code in the Ableton sourcebase that directly depends on AVX2 instruction set.
It's a flag you pass to the compiler, whether to bind to those lowest-level instructions or not.
Yes there would then be two builds of Ableton Live 12, for those of us with AVX and another for AVX2 CPUs. Yes, that would involve some logistics to manage. And yes there's a minor performance hit with AVX only... But on a CPU that's 11 years old (like mine), I am not going to notice. Not as much as I notice that Live 12 installs successfully but silently crashes out when I launch it!
I've raised a support ticket, asked if they would do a build with AVX extensions only, otherwise to offer for a refund.
I was refunded... So I guess that means that, for now at least, they are not going to support us guys.
This has been upsetting! I have been looking forward to the Live 12 release since its announcement. I couldn't wait to dig into the Midi tools! And the other bits. A Live release is quite a significant event! As it has been in my life for the last 15 years.
I was looking at computer replacements last night, in sheer depression at the prospect - cash outlay (there's a good reason why I'm on an 11 year old machine) - and the time it takes to set up the system the way I've honed this one.
But this morning, I realised that I'm not looking at these computers because my laptop is borked! Live 11 still works, all my plugins work, all my Ableton sets are intact. Just can't run Live 12. Boooo to Ableton! But I move on. Stick to the M4L midi devices I've been using instead of the new Live 12 Midi features I guess..