Page 1 of 1

"A serious problem.....

Posted: Tue Feb 01, 2005 6:49 am
by live4live
..has occurred save your work under a different name and restart the application"

I get this message almost everytime I render to disk. You can imagine how annoying this could be. Does anyone have a similar problem?
It only happens at the very end of a render and the render is always complete but it still drives me crazy. I have tried the self contain command and saved the work prior to the render and have also tried doing the render without the normalization process. I've emailed Ableton with the details but no response yet. Can anyone here help?

Sorry for the bit of a rant. :cry: :oops:

Posted: Tue Feb 01, 2005 11:22 am
by hacktheplanet
Not sure how to solve the problem, but you could work around it by resampling the entire track into a new audio clip. Then save the set self contained. The mixed down clip should be in the folder.

If you want better help, include what OS you are using, and some basic info about your computer.

Posted: Tue Feb 01, 2005 1:46 pm
by tylast
Try disabling the audio driver just before you render, then re-enable it after rendering completes...that might work.

Posted: Tue Feb 01, 2005 4:40 pm
by live4live
@ the planet
Yes I have tried that one (resampling) to get around the problem however I like the fact that you can normalize at the same time using the render.

I am on windows OS.


Thanks for the reply.

@ tylast

Do you mean disable the driver in the Live preferences dialogue?

Thanks for the reply.

Posted: Tue Feb 01, 2005 6:29 pm
by tylast
Yes! Go into Audio options & set audio to No Audio...then render.

Posted: Thu Feb 03, 2005 11:39 pm
by Livewire
i had this problem before. i got that message and Live wouldnt even start for me, but then i ran a virus scan and it was fixed so try that.

Are you normalizing? I have had similar probs...

Posted: Fri Feb 04, 2005 7:58 pm
by mikemc
If you are normalizing, turn it off and try againg... similar problems, and when I turned off normalizing, everything went fine. Reported this on the bugs forum.