Would think it's unlikely to work at all, we had to rewrite everything script wise for Live 10.0.2 and above....
Cheers
D
Would think it's unlikely to work at all, we had to rewrite everything script wise for Live 10.0.2 and above....
What if you create a new set, and drag every tracks from the offending set (from Live's Browser) in it?nrg242 wrote: ↑Wed Jun 05, 2019 5:21 pmFWIW, i'm having the same exact issue with a project, although mine won't load in the beta release either. have been having issues loading this project since updating to 10.1, but usually a reboot of the PC would then allow it load upon relaunching Ableton. as of this morning though, have launched and crashed ableton at least 10 times with this project, while trying different combos of disabling other programs or even renaming vsts used in the project.
Its not actually the song which is the problem, because any song containign M4L will trigger the issue.
You are correct, it does seem to be Convolution reverb.[jur] wrote: ↑Fri Jun 14, 2019 2:29 amDid you try loading any other M4L than Convolution? There's a specific crash with this one when using the currently bundled Max which was fixed with Max 8.0.6.
In any case that's quite a shitty situation. Are you sure there wasn't any Win invisible update happened recently on your system?
Hi there, yeah I was planning on getting in touch with you but wanted to try and nail down a few specifics first. These seem to be multi-layered issues so I'm trying to gather as much data first to save everyones time - and so I don't want to bother you with an issue which may be entirely specific to my machine, or may be a consequence of Max / Live.
Any answer from the support since then?Myattmode wrote: ↑Sun Jun 16, 2019 9:05 amHi all. I've been having exactly the same issue with Live 10.1 and I was going to start a thread about this until I saw this one.
I have done everything I can think of: reset, checked plugins (Reaktor 5 had a funny so I reinstalled it), checked for latest/reinstalled drivers, ran windows checks using the SFC and DISM options in the command prompt, reinstalled my graphics drivers and so on. The only thing I haven't done is reinstall any versions of Live as I'm concerned I may not have enough reactivations left.
I can open new sets no problem - I just can't open almost all my projects (only the really small simple ones open). I use mainstream plugins like NI, Izotope, Synthmaster and so on. I don't use any Max plugins (see edit below).
I opened a ticket with Ableton support on the morning of the 13th June with crash files etc. Very disappointingly I have heard absolutely nothing from them. I've added more crash files to my original ticket as well as tweeting them - nothing. If my livelihood depended on this, I would be seriously p*ssed off!
Edit: Reading through this thread in fine detail I did experiment by installing conv reverb as I've never used it. The crashes seem to happen after this so I deleted the conv reverb suspecting this to be the case but the crashes have continued. How do you know if you've removed all traces of this to he sure it's still not been picked up on?