Ableton Forum

alright. two nights ago when i saw i could get the beta I became very excite. so i load it up on OSX 10.5.6 and everything is working just fine. i suppose my enthusiasm got the best of me because I decided to open a set i had been working on in Live 6. it worked for about 2 minutes then crashed, and continued to crash after trying to reopen. I never saved the set in Live 8. "thats a shame" i thought, and opened the set up in 6 again to continue to work on it but it crashed in a very similar fashion to what had happened when i opened it in live 8. so now this set and all others that have particular vst plugins crash in this manner in live 6. a way to make it crash sooner rather than later is to open up the window for the vst and try to fiddle with knobs, which immediately results in a crash. the vst plugs in question will play for a while (different clips) and then crash. AU plugins do this too. a set with just audio works fine. ive got time machine running and have tried to restore earlier versions of the set, library and vst folder, to no avail.

what did opening the set in the 8 beta do?

even if you don't save anything, there are dangers...e.g. live 8 might rebuild .asd files, modify the library, etc.
1. trash all you prefs.
2. if you think the vsts are the issue, open the set in live 6 and delete all the vsts w/o doing anything else, and re-save if possible.
3. if you got this far, reinstate your vsts.

Hi turok2step,

which plugin is creating the problem (you say ... all sets having a particular vst plugin ....)?

Best, Friedemann

I figured out it was massive. i have resolved this with native instruments and everything is working now. apparently the copy protection on massive is not as sound as it should be and is susceptible to detecting false positives. somehow opening in the beta triggered this.