Ableton Forum

If I open a Live Set and make some simple changes like turning the volume up or down, or anything inside of Live, and I don't like what I did and simply try to close it out, I get an error message that says that I should change the name of the set and try to resave it. At that point, Live will refuse to close and I have to unplug all of my midi devices and wait for Live to shut down, or I can reboot. I don't have a problem if I like what I have done and rename the Set, but if I simple try to close it without saving the changes, that's when the problem occurs. Also, if I rename the Live set that I don't want to keep, and save it that way, Live will shut down properly, but I don' think I should have to do that.


Is there anything that I can do to prevent this from happening?


Just so you guys know, I am using Live 5.2 on a pc with Windows XP Home Service Pack 1, AMD 64 3200+ with 1 GIG of RAM. The Set that I was running had SonikSynth, z3ta+, and Battery running, one instance for each VST. My Motif ES is my soundcard through the mlan connection.

try unplugging anything that uses M-Audio drivers. I cannot shut down live unless i unplug my O2 and my trigger finger.

If I unplug my Trigger Finger, and turn off my mlan connections, Live will close, but there is still the issue of my not being able to simply close a Set that I don't want to keep. If I alter a set and experiment with it, and really don't like what I have done with it, I can't "Close Set without Saving changes". That's the problem. When I do, Live says "A Serious Error has occurred, you need to try renaming your set and save it." If I do try to rename the set, just to appease the error message, it gives me another error message that says the data was lost, and at that point if I try to close Live, I get the first error message "A serious error, etc. etc." continuously. The only way to close Live after this is to hit ctrl/alt/delete, and shut it down under the Applications menu. Then I still have to unplug my Trigger Finger and turn off my mlan connection for Live to truly shut off.

I have never seen a software program behave like this. I have owned Cakewalk Home Studio XL, Sonar 4 PE, Sonar 5 PE, Project 5 Version1 and 2, and with all of those programs, you can open a project, or "Set" (as Live calls it) experiment to your hearts content, and choose to save or not save your experiments without any crashes or errors. Sometimes it's fun just to completely change a project around by experimeting. This is suppose to be about creativity. I just want to be able to experiment without fear of crashing.

I sent tech support an email describing the problem. I guess it's up to them to figure it out now. I must say that I am disappointed in Live already. With Cakewalk, something as basic as exiting the program without saving changes was never a problem. Sure all programs have some glitches, and that's to be expected, but something this simple should definitely not be. I just installed it on Saturday, so I truly don't believe that I have owned it long enough to have done something to trigger this sort of behavior.

don't worry, it doesn't normally do that

you'll get it sorted, the Abes have great tech support. Nothin's pissier than splurging on a piece of software only to have it crap out on you.

It killed the good mood I was in about finally owning LIve.

It sucks!

i have that too sometimes only with some projects though, not all the time.
its killing me as well
i have a clean pc, no internet, no usb controllers (only midi hooked up) and a simple audiophile pci and an emagic mt4
Im not sure I want to pay for an upgrade.. been thinking of downgrading instead but then my projects arent compatible anymore
im not sure what happened (lack of interest, lack of knowledge, just lazy perhaps?) but after ableton Live 3 it went downhill like FAST. live 1,2,3 were bug free as far as I know!
Its kind of weird. Robert Henke talks about a self made midi controller beause he hates all other hardware because it crashes on him (duh? excuse me?) but he and the other Abletonners give us the most buggy software sequencer available
(this last "Henke part" should become my signature ... )

I contacted tech support, but the problem is still there. I wonder is it because I am using a VST. I actually tried doing the same thing with some of the demo songs, and the glitch does not occur. It's only if I change a parameter on a VST, and then try to close the set witout saving.