rendering long & complex projects crashes live?
-
muzza23
rendering long & complex projects crashes live?
im having severe problems rendering a large complex project... it's roughly 96 minutes long, runs across 20 tracks, all of which have at least 1 insert effect, there's an insert on the master as well... and everytime i try to render it, one of the following happens:
1: it goes through the rendering process but live hangs when it reaches 100% and stays hanging... windows recognises it as "Not Responding. The rendered file exists in the designated folder, and is the right size, but no audio editor or player can read it.
2: it goes through the rendering process but upon reaching 100% live tells me that it's encountered a serious error and that i should save the project to a new file and try again. clicking ok results in the message popping up again (and again and again.....) Windows never thinks it's not responding, but there's no file in the folder i wanted to render to.
3: on the odd occasion it will render properly but when it does, live is totally non-responsive (can't even access the menus), but luckily the rendered file is there & is complete.
this is really starting to annoy me, ive had to correct errors in the project that i missed the first few times and tried to do the final bounce today but i keep getting a mixture of problem 1 and 2 above... hasn't bounced properly at all yet.
anyone with problems bouncing big projects like this? any clue what's causing it or any workaround?? im running 3.0.4 on a P4 2.8C, 512mb PC3200 RAM, Abit IC7-G Mobo, RME digi9632 with drivers 2.70a... help!!
1: it goes through the rendering process but live hangs when it reaches 100% and stays hanging... windows recognises it as "Not Responding. The rendered file exists in the designated folder, and is the right size, but no audio editor or player can read it.
2: it goes through the rendering process but upon reaching 100% live tells me that it's encountered a serious error and that i should save the project to a new file and try again. clicking ok results in the message popping up again (and again and again.....) Windows never thinks it's not responding, but there's no file in the folder i wanted to render to.
3: on the odd occasion it will render properly but when it does, live is totally non-responsive (can't even access the menus), but luckily the rendered file is there & is complete.
this is really starting to annoy me, ive had to correct errors in the project that i missed the first few times and tried to do the final bounce today but i keep getting a mixture of problem 1 and 2 above... hasn't bounced properly at all yet.
anyone with problems bouncing big projects like this? any clue what's causing it or any workaround?? im running 3.0.4 on a P4 2.8C, 512mb PC3200 RAM, Abit IC7-G Mobo, RME digi9632 with drivers 2.70a... help!!
-
Guest
Hmmmm, do you have your audio files on a fast (7,200 RPM) hard drive? Are you audio files on a seperated hard drive than your apps (it helps a good deal if they are)? Have you tried putting some of the audio files in the set into RAM? Are you running short on hard drive space? I'm just trying to help trouble shoot off the top of my head. Is the rendered file you're creating 90 minutes long? Wondering because I have a huge set like that two--30+ gigs of audio, 20 track, 45 takes of songs--I've never had any probs with it, or with rendering from it, but the renders are all 5 minutes or so. Anyhow, hope you figure it out.
Ryan
Ryan
-
muzza23
-
spiderprod
- Posts: 1120
- Joined: Wed Mar 31, 2004 10:11 pm
do some clean up
do a defrag first,cleanup,then before opening live go to window task management (crtl+shift+esc) & end the processes you don't need in live like internet programs etc..(service.exe,iexplore.exe,explorer.exe,etc...)
don't worry when you restart it all comes back to normal.this progs don't take lot of cpu but disabling them help saving some cpu & ram.
i don't know if it will help you but it's what i do when i reach the end of a track & end up having a massive arrangement that start crashing.
once you get your arrangement on the screen take off everything you don't use in the arrangement(fx,audio) then press play.if it still crash the best way is to record each tracks separately to disable the fxs & save some power.
don't worry when you restart it all comes back to normal.this progs don't take lot of cpu but disabling them help saving some cpu & ram.
i don't know if it will help you but it's what i do when i reach the end of a track & end up having a massive arrangement that start crashing.
once you get your arrangement on the screen take off everything you don't use in the arrangement(fx,audio) then press play.if it still crash the best way is to record each tracks separately to disable the fxs & save some power.
-
muzza23
my machine isn't on the net, i use it for nothing but music so ive already got the bare minimum of services running and no other resource hogs whatsoever...
playing back the project normally within live never crashes, it plays fine & runs like a dream, its just rendering that is crashing... just can't get it to render at all
playing back the project normally within live never crashes, it plays fine & runs like a dream, its just rendering that is crashing... just can't get it to render at all
-
Guest
-
muzza23
thanks for the tip, will try that one man...
i got it to render properly last night, i saved it as an inclusive live set and then bounced & it worked... amazing!! but after it was done bouncing, live crashed with an error message about a rewire dll, so maybe the problem is related to the rewire engine??
opened live again & rendered again & to my surprise it worked, but got the same rewire error/crash when it was done... maybe its bouncing nicely now because it was saved to a new file & has no undo history?
i got it to render properly last night, i saved it as an inclusive live set and then bounced & it worked... amazing!! but after it was done bouncing, live crashed with an error message about a rewire dll, so maybe the problem is related to the rewire engine??
opened live again & rendered again & to my surprise it worked, but got the same rewire error/crash when it was done... maybe its bouncing nicely now because it was saved to a new file & has no undo history?
-
Guest
-
Guest
hey muzza, funny thing just happened--I had the behaviour you described while rendering for the first time. Here's the only two things that are different from hundreds of problem-free renders:
1) I had a bit of automation on one Waves C1 effect on one track
2) I had soloed that track (I almost always am rendering the whole mix) and was just trying to render it.
Surprisingly, I had previously rendered the whole mix without a glitch, and just for a test, I tried rendering the track with the automated C1 soloed a few times to see if it was consistent. Seemed like every other render or so caused the freeze-up. this blows. The waves are so damn expensive, and they forget their settings in Live when you re-open a project. My previous work-around was to always save presets for the waves effects so I can re-load the preset when I re-open a set. Another new workaround I was trying was automating the effect parameters in order to avoid having to re-load all my presets each time I open a song--now it seems this may cause rendering issues. Were your Waves automated at all in your problem sets? Other Waves users out there, whats up with your rendering (we're both on pc)?
Ryan
1) I had a bit of automation on one Waves C1 effect on one track
2) I had soloed that track (I almost always am rendering the whole mix) and was just trying to render it.
Surprisingly, I had previously rendered the whole mix without a glitch, and just for a test, I tried rendering the track with the automated C1 soloed a few times to see if it was consistent. Seemed like every other render or so caused the freeze-up. this blows. The waves are so damn expensive, and they forget their settings in Live when you re-open a project. My previous work-around was to always save presets for the waves effects so I can re-load the preset when I re-open a set. Another new workaround I was trying was automating the effect parameters in order to avoid having to re-load all my presets each time I open a song--now it seems this may cause rendering issues. Were your Waves automated at all in your problem sets? Other Waves users out there, whats up with your rendering (we're both on pc)?
Ryan
-
noisetonepause
- Posts: 4938
- Joined: Sat Dec 28, 2002 3:38 pm
- Location: Sticks and stones
-
muzza23
i never try to render while running live as the rewire slave coz it obviously doesn't work, it was the only app running when i was bouncing this mix and it still gave an error in the rewire dll during the crash after the file had successfully bounced...
my waves L2's also had some automation, albeit only turning the instrument on & off so that when i was progressing through the mix i wouldn't end up with 20 active L2's by the end (about 3 or 4 would kill the cpu totally, let alone 20) so maybe its related to automation on waves plugins during bouncing?? doesn't seem to happen with shorter bounces though...
my waves L2's also had some automation, albeit only turning the instrument on & off so that when i was progressing through the mix i wouldn't end up with 20 active L2's by the end (about 3 or 4 would kill the cpu totally, let alone 20) so maybe its related to automation on waves plugins during bouncing?? doesn't seem to happen with shorter bounces though...