Live 10 midi-overdub causing crashes. (capture related?)

[lalakulo]

Did you try to run live as administrator?

Yes, it's even set to start as admin automatically. What is it about Win Defender? Do you suggest turning it off?

For protection turned it on with controlled folder acces on for malware protection. But noticed it blocks certain acces with live 10, not with 9. So had to whitelist certain folderaccess, and also let it run as admin. Just trying to rule out any problems that can have any effect on live.

[salvodaze]

That is interesting indeed. Somehow Windows Defender doesn't let me change applications settings (this setting is enforced by your administrator) but the setting is already off. I will let you know if I come up with anything that helps!

[salvodaze]

As you have suggested in your original post; I have pinpointed the problem as midi overdub as well. I have just left live playing for 70 minutes without a crash with midi overdub turned off. It's a big hassle for me to not be able to use overdub but I think I will try to work around it for now or just use it minimally, until Ableton provides a solution for this. Thank you for the help, I will keep you updated.

[legbiter]

I believe I am having the same issues. I have had the retail version of Live10 since it came out and it is so frustrating to to experience it crashing during a recording session . I have reverted back to Live 9 to stay productive and am hoping that Ableton will find a solution soon. Approximately every second recording crashes (statistically). Funnily enough, it doesn't crash doing anything else, regardless of size of project.

On anther note,
Wavetable is cool and the upgrade as a whole is worth the money, as soon as the bug gets fixed, however many of the presets in the packs I purchased such as AAS stuff etc. are now in suite. That sucks, I'd rather have seen new ones rather than the ones I had already purchased for Live 9. So, that means, the money I invested in those is now down the drain.

Win 7 64, AMD 8 Core, 16 GB RAM, 500 GB SSD, 2TB HDD, FullHD + 4 K dual monitor. LIVE10, Komplete, Maschine 2, APC.

[salvodaze]

Funnily enough, it doesn't crash doing anything else, regardless of size of project.

Have you tried turning midi overdub off in the options menu? This is the workaround I found after about 50 crashes I decided to stick with 10 for now, only enabling overdub when I record and see if I can get away with it.

[lalakulo]

Funnily enough, it doesn't crash doing anything else, regardless of size of project.

Have you tried turning midi overdub off in the options menu? This is the workaround I found after about 50 crashes I decided to stick with 10 for now, only enabling overdub when I record and see if I can get away with it.

Another thing to test this, is get midi from another track, for example a arp vst. midioverdub on, the armed channel in a loop, push rec and let it feed for a while. ( this way you just can walk away and get some coffee ha)
Offtopic but does live 10 load fast? here it's extremely slow compared to 9. (wished ableton had a simple startup log which showed where the cullpit lays. instead of sending bug reports, for these kind of things that one can fix easy.)

[salvodaze]

OK so Ableton support investigated the whole thing and traced the problem. It wasn't midi overdub like I thought, it was something else I seem to have disabled with midi overdub: a very specific pattern of arpeggiator. They sent me the exact instructions to reproduce the error, I haven't had time to do that yet as it's my work hours but I did remove the arpeggiator and turned midi overdub back on and set playback to run for over 20 minutes without a problem. I will try to reproduce the error later tonight or tomorrow though (I'm a bit behind on the RPM challenge ).

I hope this helps!

[lalakulo]

OK so Ableton support investigated the whole thing and traced the problem. It wasn't midi overdub like I thought, it was something else I seem to have disabled with midi overdub: a very specific pattern of arpeggiator. They sent me the exact instructions to reproduce the error, I haven't had time to do that yet as it's my work hours but I did remove the arpeggiator and turned midi overdub back on and set playback to run for over 20 minutes without a problem. I will try to reproduce the error later tonight or tomorrow though (I'm a bit behind on the RPM challenge ).

I hope this helps!

Glad your problem is solved. Are you refering to abletons arp?
Because i ran into different scenarios
Also with 3th party vst arp.
And no arp, just playing notes in with overdub.

[lalakulo]

3 weeks later after the install of live 10 and many random crashes.

It crashed again on midi, now with stock arp.

Summed up:
* Crash with midioverdub
* Crash with 3rd party vst midi feeds
* Crash with abletons arp

Compared to older versions before Live 10 which ran rock solid i start to think this all could have to do with the new function capture somehow? Since it always listens to midi. It might conflict?

Is there a way to turn this capture mode off?

[RadioOnMars]

I'm afraid it won't be Capture related. The best way would be to send in the crash report.

[lalakulo]

Did send.
Hope it will be fixed in a update.
Love the new addons in 10, but this drives me back to the stable 9.

[legbiter]

Hi All,

has anyone foound a fix for this?

I am still having crashing problems and have reverted back to using Ableton 9 suite 64 which, BTW, is absolutely rock solid and worth every penny.

How can Ableton just stay quiet through this? It is an abvious case of slack programming. I have paid for an update which I can't use and they don't even answer any more to say they have found the problem - WHICH OBVIOUSLY MEANS THEY DON'T KNOW HOW TO FIX IT!!!!


ABLETON - I AM STILL WAITING FOR A SOLUTION

[Stromkraft]

ABLETON - I AM STILL WAITING FOR A SOLUTION

We people here are not necessarily working for Ableton! We're users, just like you. Do you need help getting in touch with support? This is the address: Submit a request. The email adress is [email protected].

[[jur]]

It might sound like stupid questions but:

Have you tried unplugging every midi keyboard/controller?
If you're using 3rd party synths, have you tried using Live native's ones instead?

[Transient101]

any updates on this???
I downloaded the demo and am having the same problem.

I am trying to loop and record midi, I have the drum pad set up and a pad on another midi channel.

I can change between the two, but I can't hear the pad until I arm the track and it is recording is there aw ay for me to preview the sound before I record it well I am looping?

The program is crashing (just the program) every once in a while for me, motley when looping I have only been trying the program for 1 hour and 2 crashes, my PC is not a issue, new windows PC.