Ableton Forum

I have another issue with this update.
I seem to have lost my MIDI in from my Novation Launchkey mk2.
I reinstalled 10.0.2 and it worked fine, then installed 10.0.3 again and lost the MIDI in.
Anyone else have this issue too?

Hey everyone,

we've just released our latest beta, Live 10.0.4b2, which fixes several issues Live might have while starting on machines with older GPUs - laggy behavior, crashes, blank windows, basically everything that would be cured by the "-_ForceGdiBackend" option in Live 10.0.3.

Please check out the specific topic on this and try Live 10.0.4b2 if you suffer from these issues.

10.0.3 was terrible for me - CPU spikes and glitches. The 10.0.4 beta is fine.
Nothing is more scary than "old hardware causing problems". My 2012 Thinkpad still rocks with Win7 and a FF400. I don't want to be forced into a hardware upgrade, puhleez.

Ive installed a new ssd instead of my old hd, and a totally new and clean system setup with win 10. After that live 10.03 and the latest beta lags like h.., even with a single instrument like abletons own instrument operater its lagging and the cpu goes up like a rocket. Before my cpu never spiked more than 40% when i was running tons of vst,s, ive tryed the option.txt thing as mentioned before but nothing helps, ive closed all background programs running like win update, anti virus . Im running win 10, 16gb ram, 8 core intel i7 3.60, and apogee duet. Is there any other txt than the "-_ForceGdiBackend" i can write in the option.txt ? Im wondering if it has anything to do with the places thing is running finding files because it a new setup, its only a few folders like loops, midi patterens and song folder...

Solved

Ive followed this https://support.focusrite.com/hc/en-gb/ ... Windows-10

And everything is working flawless ...Also in version 10.04.

I solved it by simply grouping more tracks together
- seems having 53 VU meters all running at once is asking too much, lol.

Here is a video about a lagging issue which I know the culprit for but still no fix?

https://youtu.be/PB9erCWUtaM

This solved my issues with 10.1 on my 2013 MacBook Pro. Not just limited to PC apparently!

I found A solution For GTX/Nvidia Graphic Card users. Open Control panel For Nvidia(Nvidia Control Panel) then use these settings for nvidia. If you set all these settings as is it should run smooth. But you have to restart Ableton Live once.

This worked for me as well.

mr.adl wrote: ↑

Tue Sep 04, 2018 8:46 am

EDIT:
Here is the fix (at least it worked for me)
-Create an option text file like in the description here:
https://help.ableton.com/hc/en-us/artic ... s-txt-file

-copy this this inside the text file: -_ForceGdiBackend

-put it in the folder as described in the upper link

-restart Live 10.03 (or install it)

I am on Mac OS 10.14.5. and Live become so laggy I could not use it anymore.

This fixed it completely. Thank you so much for posting this!!!

I've changed the zoom display at 98% in the preferences menu and it fixed my Lagging issue. Very strange...

I thought this worked, BUT

Turns out my lagging issue was because I had left an instance of Sir2 open on each track, so that when I clicked on each of the ~40 tracks, that instance would already be open so I could check the settings. Apparently this does not make ableton happy, and even though the audio worked fine and the CPU never went above 6%, the scrolling, clicking, zooming - literally anything on the visual front end - was unusable.

So when I quit out, all these closed and didn't remain open upon opening the set. So I guess moral of the story is to close your plugin windows because... well honestly I don't know why I think that's a bug that should be sorted, my CPU was barely lifting a finger.

Peace!

Running Live 10.1.7 (suite) on Mac (imac pro 2017)

coleboillat wrote: ↑

Fri Feb 21, 2020 9:28 pm

I thought this worked, BUT

Turns out my lagging issue was because I had left an instance of Sir2 open on each track, so that when I clicked on each of the ~40 tracks, that instance would already be open so I could check the settings. Apparently this does not make ableton happy, and even though the audio worked fine and the CPU never went above 6%, the scrolling, clicking, zooming - literally anything on the visual front end - was unusable.

So when I quit out, all these closed and didn't remain open upon opening the set. So I guess moral of the story is to close your plugin windows because... well honestly I don't know why I think that's a bug that should be sorted, my CPU was barely lifting a finger.

Peace!

Running Live 10.1.7 (suite) on Mac (imac pro 2017)

It'd be cool if you could report this to support@ableton.com to see if there's anything wrong here.

Just did this with version 10.1.14 etc etc etc, and win 10 64bit, and it is like day and night. I have my old Ableton back.