Ableton Forum

Hey Christian.

Sorry about that. I presumed this was a generic fix for a common problem, but I'll edit the previous post to remove Michael Duehrs email.

Im back again. I first experienced this problem in may 2008. I eventually stopped by doing an archive and install of the OS. I assumed that was the end of that bug but last nite during the soundcheck for a performance the same issue reappeared causing me to cancel the show. I wont go into how pi**ed off i am but this bug needs to be solved once and for all or at least a proper explanation for its cause. After this happened i did an "archive and install" of the operating system and while running the demo of Live (7.0.14) the same error kept appearing, so it would seem theres more to it than a copy protection error.

It seems more and more people are starting to come across this problem, even people using Live beta 8, so obviously the problem hasn't been solved. I think its unreasonable for customers who've paid and give support to a software package to have have to suffer at the hands of copy protection devices written into the software.

I know people have gripes about having to use dongles, cd re-authoriztion and so on but those worries are insignificant to a bug that stops you dead in your tracks and even after you think you've fixed it is still there like a ticking time bomb waiting to go off.

I use Live for live performances so a bug like this is a disaster. As this problem has been around for a good while now i would of thought Ableton you a clearer unstanding of the cause.

Things i've tried in vain to fix this problem; trash abletons preferences file, trash the unlock file and re-authorize(although this bug happens in demo mode so it wouldn't seem to be an authorization problem), Archive and install the OS, re-install Live. This bug happened while using OSX version 10.5, 10.5.2, 10.5.5, 10.4.10. Happens with or without using and external soundcards,or interfaces.

I've written to support, lets hope for good news

I believe if you had a project open when you got the copy violation error, the project then gets flagged and each time you try to open that project you get the same copy violation error.. some sort of anti-piracy countermessure.

Thanks for the suggestion Imaulle but once this started happening i trashed the preferences and unlock files, re-authorized but as soon as i relaunched it would happen even in a blank session. I've done another archive and install of the OS(originally happened when using 10.5.5 now on 10.4.10 but will be upgrading) and am working off a blank session again and no crash yet. Sounds so obvious it could be the solution, though the support team never menioned it last time the problem occured. Will post my findings.

Im using the session that the problem surfaced on again so its wasn't the cause of the repeat corruptions. After doing what i mentioned in my previous post the problem hasn't re-occurred so far. When i have the time i'm going to reformat the drive and do a fresh install to try and avoid the problem re-occurring for a third time.

thanks