Live lost my first finished song

kovacs · Post by **kovacs** » Tue Sep 14, 2004 11:38 pm

I got Live 4.0.1 three weeks back. Today I was just going to listen to the first full song I'm working on and Live fails to load it. It is a 5-track set with 4 MIDI and 1 audio track.

I used Sytrus, Absynth 2.0.5, and Kompakt 1.0.3, and BFD (latest build, I think).

I had recorded the set to the arrangement view and then recorded a guitar track which is 50 megabytes. I still have the ALS file, the guitar .wav, and a wav.asd file next to the guitar .wav (in the sounds folder for the song).

Live refuses to load the set. It just freezes on me.

Is there any way I can recover it? I have not yet rendered this song in any other format...

I don't know why this is happening. If someone can explain maybe I can avoid this in the future. Is there some kind of test I can do or anything?

None of the tracks are very complicated, mostly basic MIDI stuff into the synths. The guitar track is quite long (about 6 minutes) but I have 768 MB RAM (I though Live streamed directly from disk so should that matter much, anyway?). I used 1 sample from a DVD which is still in the drive.

Aaaaaaaaaaaaaaaaah. It seems I just lost my FIRST song written with Live. Not a good feeling.

kovacs · Post by **kovacs** » Tue Sep 14, 2004 11:41 pm

I should add that this is happening on my PC workstation (not on the Powerbook).

kovacs · Post by **kovacs** » Tue Sep 14, 2004 11:48 pm

Live 4.0.1 stays in memory after I force it to shut down. I've reported this before but now it happens every time. I have tried to reboot three times now to see if Live will load my song. Each time it freezes, and after shutting down the application the process stays in memory, taking up around 120 megabytes. The process is unstoppable and I have to reboot to end it.

sdfak1234 · Post by **sdfak1234** » Wed Sep 15, 2004 1:12 pm

This has happened to me too.. very annoying and makes Live practically useless as I cant rely on it for a live show... you've gotta patch this bug!!!!

The problem is quite intermitant, I cant seem to lock down exactly what causes it to occur, but sometimes happens when I'm saving up... I also saw another bug where a ni battery patch disappeared.. I had 3 other battery midi tracks and they were all fine.. so strange.

I'm using an Audigy 2 Platinum and an Oxegen 8. Windows XP Athlon 3000, 1gig ram.

SkeptikTank · Post by **SkeptikTank** » Wed Sep 15, 2004 2:08 pm

One thing you can try: open a new session or a song that can be opened in live. The disable vst's (or au's) in the preferences. Now, try to open your crashed song. Sometimes it is openable, even though it complains that it cant load the plug-ins. Then enable vst's in preferences again. If the vst's load successfully after that. Save the song using save as.. under a new name. Try to open the newly saved song. Several times songs using Reaktor has gone lost for me like this, but after following these procedures, I've been able to resurrect them. I'm on osx though, so I'm not sure it works on windows.

mdifonzo · Post by **mdifonzo** » Wed Sep 15, 2004 3:49 pm

I started a thread about this earlier, but I just thought I would add to this one. This bug is absolutely horrible and if it isn't fixed soon, there will be no reason to use Live 4. Why waste time writing something if you can't come back to it ever again?

Happens on my G5 2.5GB Ram Panther

kovacs · Post by **kovacs** » Wed Sep 15, 2004 11:17 pm

I followed Skeptictank's suggestion and it worked. Thanks! I was able to open my Live set again and reapply the instruments. Now my intelligence did not stretch to keep a note of which presets I'd used, so this will take a while.

However, I think the culprit is Sytrus. When I messed around with it it suddenyl froze Live and emitted an awful sound which did not go away until I rebooted. So I'm back to square one but at least I know I can open my set - all the midi data and wav recordings were intact.

I have applied the 4.0.2 update but the memory problem persists - when exiting Live the process does not die, but remains in the Task Manager, consuming 100s of megabytes of RAM.

Mehalic · Post by **Mehalic** » Thu Sep 16, 2004 12:48 am

That's crazy, because it's happening to me too and it's getting to the point where I don't want to work in Live until this gets fixed (dell inspiron 8600/1G RAM/60G 7200RPM HD/Centrino 1.5Mhz/FireWire 410) - practically everthing I work on crashes (save for a few things). Except, my problem occurs after I open the file and start working on something, upon clicking on a scene, I get "a serious program error has occured, please save your file and exit", I can click on ok and keep working on the track, save it, but then I eventually get shut down by windows (using no vst's in some cases). Sent in logs to tech support and haven't heard back yet.

Sorry to hear that this is affecting others as well. Let's hope it's fixed in .0.2 which I'm d/l'ing right now! Don't get me wrong, when I can work, v4 is amazing!

Haven't tried that trick yet to open bad files, but will - thanks for the tip!

Mehalic · Post by **Mehalic** » Thu Sep 16, 2004 5:08 pm

Hate to say 4.0.2 didn't do anything to aleviate the matter. Seems I'm at the mercy of tech support.... please someone get back to me and give me a status update on my issue - PLEASE!

The trick mentioned above doesn't really apply to me cuz I can open the files, but when clicking on random scenes, I get the error. This sucks.

beardedone · Post by **beardedone** » Mon Feb 14, 2005 3:50 pm

Sytrus is crashing for me as well in 4.1. I assume that you guys have already addressed this issue to support?

Gordon

bigdog · Post by **bigdog** » Wed Feb 16, 2005 10:44 pm

sytrus is the culprit here....once i got rid of it no probs with this again...cool

Live lost my first finished song

Live lost my first finished song

Same thing