"A serious error has occured" loading set with fro

[volley]

I've been using Ableton Live for a long time without problems (versions 4 and 5). Recently I tried freezing a track, and after that I could no longer open up the live set. The error message says a serious error has occured and that I should save my work and restart the application. I click Ok, and the message reappears until I kill the application or restart the computer. Both actions take a very long time to complete; it seems Live is trying to stay alive.

I've tried disabling all audio, and clearing the VST folder. I've also tried freezing a track in another live set, and the same thing happens when trying to reload it.

The problem occurs in both versions I tried: 5.0.2 and 5.0.3. Most of you don't seem to have this problem; I've searched the forums etc, but found nothing. Has anyone else experienced this? Or, if you're able to help me find the problem, I'd happily supply any info needed..

BR,
volley

[mezzmerized]

I just wanted to confirm this problem. I too have experienced this message several times.

I'm not sure that it hasn't happened without a frozen track issue, though.

Once, I loaded the set and opted not to search for the "questionable files" and was able to work in the set. When I tried to freeze the same track again, the freeze stuck at 100% and I had to shut down the program.

You might try exporting the midi file, then importing it to another track.

Anyone else?

Help!!!!!!!!!

[volley]

Wellll I can't open it, so I can't export it... :/ But I have an old copy lying around; I'm a save-a-holic... =)

[kineticUk]

I have not used the freeze function very much but I think you should check this is still happening with the latest beta version.
If it is still happening you can send ableton feedback [email protected], they seem to be working on fixes right now, so it would be the best chance of getting this sorted.
Thanks

[mezzmerized]

I've got a new eror message now.

* Failed to access the undo history file. Switching to memory-based undo. Live will not be able to recover Sets after crashes anymore. Please consult www.ableton.com/support if this problem persists after rebooting.*

I'm still crashing about once an hour or so, but Live has been "able" to recover each time.

Saving under a new file name doesn't seem to help.

I registered with M-Audio (u.s.a) in an attempt to contact "support", but haven't received a password e-mail yet [about 12 hours]

Maybe I should downgrade to 4?

[volley]

I have not used the freeze function very much but I think you should check this is still happening with the latest beta version.

Good idea; checked beta 2 version 4, and it still happens (although the error message is now more elaborate, detailing where the log file is placed etc). I'm already in contact with support, so I'll supply this additional information directly to them...

mezzmerized, it seems you're having a bunch of random problems.. I had that after upgrading my comp a while ago (not only with Ableton), and it turned out to be a weak power supply AND a broken motherboard. It created all sorts of weird errors.. Have you changed your hardware setup recently (eg when switching to Live 5)..?

[mezzmerized]

mezzmerized, it seems you're having a bunch of random problems.. I had that after upgrading my comp a while ago (not only with Ableton), and it turned out to be a weak power supply AND a broken motherboard. It created all sorts of weird errors.. Have you changed your hardware setup recently (eg when switching to Live 5)..?


No, Volley. It's a brand new computer. Compaq Presario SR1750NX; Windows XP Media Center;AMD Athlon 3500+; 2 GB ram; Presonus Firebox; Evolution MK461C

I can't remember the Motherboard Model # right now (not at home), but it's an Asus.

5.0.3 and 5.2b4 crash too though.

I'll check into it, thanks

[volley]

Found the problem!

Ableton's swift support (crk) sent back a new file with a fix. It turned out one of the return tracks had a corrupt output. Given that piece of info, I've figured out what happened:

1. I added a sidechain-enabled compressor effect (Voxengo demo of some sort) to one audio track.
2. I routed the output of return track "C sidechain" to the sidechain inputs (tracks 3 and 4) of the compressor.
3. I removed the compressor from the original audio track.
4. Ableton Live! tried to retain the routing for the return track, resulting in the corrupt return.

I could fix the problem myself by manually clearing the retained routing, or by using the fixed set returned by Ableton's support.

Thank you Ableton for the swift resolution! =) Didn't realize I should update this page until now though..

BR,
volley