Ableton Forum

baseinstinct wrote: ↑

Wed Apr 10, 2024 12:35 am

As I think of it, it is a huge surprise after the fact to find out none of the beta testers came back here to let everyone know. Probably bound by NDA.

As I said, the minimum CPU requirements were listed on ableton.com the day L12 was announced.

[jur] wrote: ↑

Wed Apr 10, 2024 9:47 am

baseinstinct wrote: ↑

Wed Apr 10, 2024 12:35 am

As I think of it, it is a huge surprise after the fact to find out none of the beta testers came back here to let everyone know. Probably bound by NDA.

As I said, the minimum CPU requirements were listed on ableton.com the day L12 was announced.

But people are mostly musicians and many missed this, which itself got overlooked. Think of sock fineprinted in sushi menu. Ouput was fine but not the outcome, as evidence by this thread.

baseinstinct wrote: ↑

Wed Apr 10, 2024 10:22 am

[jur] wrote: ↑

Wed Apr 10, 2024 9:47 am

baseinstinct wrote: ↑

Wed Apr 10, 2024 12:35 am

As I think of it, it is a huge surprise after the fact to find out none of the beta testers came back here to let everyone know. Probably bound by NDA.

As I said, the minimum CPU requirements were listed on ableton.com the day L12 was announced.

But people are mostly musicians and many missed this, which itself got overlooked. Think of sock fineprinted in sushi menu. Ouput was fine but not the outcome, as evidence by this thread.

Count me among the disappointed. I am tech-savvy and would have remembered reading something about this before I upgraded. I can run Live 12 on my Mac M3, but that's a work machine; my studio computer is an i7-2600k. So I guess I'll be reinstalling Live 11 there. Anyone know whether the project files are backwards compatible?

Otherwise, I can run Reaper on the Windows machine...

This could have been handled much more deftly by Ableton. Too bad.

Same problem for me

Faulting application name: Ableton Live 12 Suite.exe, version: 1.0.0.1, time stamp: 0x66163aa1
Faulting module name: Ableton Live 12 Suite.exe, version: 1.0.0.1, time stamp: 0x66163aa1
Exception code: 0xc000001d
Fault offset: 0x000000000407b9c1
Faulting process id: 0x5f2c
Faulting application start time: 0x01da9bce8a7183a0
Faulting application path: C:\ProgramData\Ableton\Live 12 Suite\Program\Ableton Live 12 Suite.exe
Faulting module path: C:\ProgramData\Ableton\Live 12 Suite\Program\Ableton Live 12 Suite.exe
Report Id: 237df2c1-a0d3-4421-b71e-9200e2b1bab8

I finally broke down and bought a new motherboard, cpu, and RAM. Running live 12 now.

Xarkon wrote: ↑

Wed Apr 10, 2024 9:23 pm

. Anyone know whether the project files are backwards compatible?

Yeah they always have been backward but not forward compatible.
If saving it will prompt you to save under different name..

Same problem here. I have dual xeon, 128gB of RAM, Windows 10 Pro v22H2. I decided to jump into the Ableton world to see how it compares with Cubase (which I've been using since it was on the Atari). Anyhow, Ableton won't launch. I presume my processor isn't supported. I'm sure many will say it's my fault for not checking BUT to be honest I'm a musician and not a computer whizz. I read in an earlier post that it might be possible for the Ableton developers to compile a version that runs on non AVX2 instruction set. Whether this is the case or not, I have no idea. BUT, if it's possible then Ableton should do it to support purchasers of their software that bought it in good faith.

Also, surely Ableton can see (through the online registration system) whether I am using a registered (bought) copy of Ableton Intro. If they can, then they will see that my purchase isn't operating on my system. SO - HOW ABOUT A REFUND!!!!!!!!

At the moment I'm incredibly disappointed in Ableton and won't bother upgrading to a more expensive version - which I probably would have done had it worked.

Jon

Best to contact Ableton and ask for a refund

Cheers, I've already done that. Also, I asked if they won't refund, would they give me a licence for Ableton Intro 11 (seeing as they've got my money for a product I can't use). Still waiting on an answer. Jon

jonnoras62 wrote: ↑

Sat May 04, 2024 9:45 pm

Cheers, I've already done that. Also, I asked if they won't refund, would they give me a licence for Ableton Intro 11 (seeing as they've got my money for a product I can't use). Still waiting on an answer. Jon

I got a refund myself, so you should be ok

That's good to hear. Cheers Jon

I have read a few pages of this topic, but I want to be sure to not miss something:

Is there a trick (option in a hidden config file?) to disable the AVX2 performance improvements, and make Live 12 run on a Intel i5 less than 5th generation?

Or one specific Live12 beta version that supports these older i5 CPU? (I am in the beta program)

As I understand it, Ableton chose to statically bind to the avx2 library at compile and link time. So it would require Ableton to recompile without this option, which would create a new executable and installer. Others have said that avx2 is used to make the new ‘similar sounds’ feature performant, but I would be very happy with a build of Live 12 without the avx2 dependency and that new ‘similar sounds’ feature greyed-out.
We live in hope..

Hello Ableton, bit of an oversight to create such a specific CPU-bound executable!

+1 to releasing a general x64 version please! I can run Elden Ring but not your DAW.

Starkad23 wrote: ↑

Wed Mar 06, 2024 5:09 am

I have the same problem.

When I run the program as administrator, in the task manager box it says "Ableton Live Suite 12.exe" running and then instantly says "Suspended".
I do not know what is the problem. My PC should run it with no problem.
I feel a little sad because I made an effort to upgrade to Ableton 12 to get new and interesting things. I hope that Ableton troubleshooting team will provide us with a solution for this issue.

I had the exact same problem.
My solution was:

Uninstall ASIO4ALL

Now Ableton launches without any issues. Try it.