Help! Rendering to new Track with Acid Pro 4.0a hangs -ACID Product Family

ACID Product Family

Subject:Help! Rendering to new Track with Acid Pro 4.0a hangs Posted by: MixManiac Date:10/12/2002 11:07:44 AM Hi I've got a Acid project that contains about 50 different tracks with a total time of 72 minutes. When I want to render (save) the hole project to a new track (PCM 16Bit 44khz), the rendering process stops at 29% everytime (this is after 21 mins. 5 secs). The size of the generated wav file is about 200MB. I've got 80GB free space on this drive, so this could not be the problem. I also use this drive as temporary drive for Windows and Acid. My system: Windows XP SP1 Acid Pro 4.0a Build 237 Intel Pentium 4 2.26GHz 512MB RAM 40GB Local Harddrive 80GB FireWire Harddrive Soundblaster Live Player 5.1 Thans for any help!
Subject:RE: Help! Rendering to new Track with Acid Pro 4.0a hangs Reply by: Iacobus Date:10/12/2002 1:44:28 PM Instead of bouncing down, have you tried just rendering the project to a specific format like WAV or PCA and then add it to the project? Does that work? What if you bounced down incrementally, like bouncing down 10 tracks at a time and then bounce the final 5 tracks together? Make sure you're not also doing anything with your system during the render and not running anything in the background. Users might think they can do anything with that type of fast system, but I'm sure that even the fastest Pentium 4 will be more than taxed when processing digital audio like that. HTH, Iacobus
Subject:RE: Help! Rendering to new Track with Acid Pro 4.0a hangs Reply by: pwppch Date:10/12/2002 5:50:06 PM That would produce a file ~ 720 meg in length! (assuming stereo 44.1 16 bit.) That would make the 29% ~200 meg, so the numbers check out. The only thing I can think of is that you are hitting some limit, though I can't figure out what limit. When you render to new track, select Sonic Foundry Wave 64 (w64) as the rendering format. Peter
Subject:RE: Help! Rendering to new Track with Acid Pro 4.0a hangs Reply by: MixManiac Date:10/13/2002 2:29:16 AM ok. I think I found the problem. Everytime when the rendering proces hangs, the pagefile of Windows is about 2GB. Is it possible that Windows can not handle larger files (ntfs should do...)? Why Acid needs so much virtual memory? I've tried also with creating a .w64 Acid file - with the same result. I'm rendering now 20min. parts and merge them together. This seems to work fine...but it's only a work around. Thanks
Subject:RE: Help! Rendering to new Track with Acid Pro 4.0a hangs Reply by: pwppch Date:10/13/2002 12:04:53 PM ACID stores all loops (and MIDI) in memory, so if you have a lot of loops this could force Windows to use virtual memory. Sounds like a bug then if w64 also has a problem. Will have a look. Thanks Peter
Subject:RE: Help! Rendering to new Track with Acid Pro 4.0a hangs Reply by: anon Date:10/13/2002 10:19:32 PM Man, I just started having similar problems. I have previously rendered a few tracks to .wavs and then opened them all up in a new project so I could tweak them before burning them onto CD. It's 4 complete tracks (all one shots) with 5 more short tracks (less than one minute) of vocals and sound effects (mix of oneshots and beatmapped) that I wanted to throw onto the final mix. It's only 26 minutes long and my ram meter doesn't go above 10/256. If I try to render these 9 total tracks to a .wav it doesn't happen. It will get to about 55% and then it hangs just as neo77 described. With trial and error I found that I have to successfly render I have to cut it into approx. 3 minute segments. Pretty weird since all the orginal tracks were between 6-7 minutes and all rendered fine on their own. And also pretty weird since with Acid 3 I rendered stuff that had more tracks for a signficantly longer amount of time. Even more, if I try to render above this 3 minute mark and it hangs, it won't cancel the render, it just sticks and I have to Ctrl/Alt/Delete. But then it says that there is a background operation in progress and I have to let it sit for a minute or two before it closes. I've tried to just burn straight to CD, but then this opens up a whole new problem as it always says there is a write error and that the disc may be corrupted or dirty. I've tried this with several different CD-R's. Here is the error that accompanies the write error message: 'ATAPI MMC Compatible'-(0) 'ESDI_506'-(0) -'ATAPI CD-R/RW 10X8X32 8.CZ'-(1) Module atapimmc.cpp Line 1472 A medium error occurred. A write error occurred. Make sure your media is approved for this drive. Status: 00040200 Command: 2a 00 00 00 88 dc 00 00 1a 00 Sense: 03 0c 00 Info: 00 00 00 00 Specific: 00 f9 f9 Extra: 04 00 24 dd f7 06 ff ff ff ff I had zero problems with Acid 3 using the same burner. My specs: Win 98se PIII 256MB
Subject:RE: Help! Rendering to new Track with Acid Pro 4.0a hangs Reply by: SonyJennL Date:10/14/2002 12:14:57 PM anon- What burner are you using? Thanks. -Jenn
Subject:RE: Help! Rendering to new Track with Acid Pro 4.0a hangs Reply by: anon Date:10/15/2002 2:06:34 AM Hey Jenn, I have an ATAPI CD-R/RW 10X8X32 8.CZ (0,1). Thanks.

Go Back