error: bounce handler cannot ....

[Locash]

i go to bounce to disk and it says:
bounce handler cannot keep up.
what am i doing wrong? it worked 10 minutes ago.
trying to bounce 16 bit, stereo interleaved, aiff file.

[Avid]

Search the Answerbase for the words:
bounce handler

and you'll find 4 results.
See if any of the suggestions there help.

[Locash]

i just did, i did all things it told me to do. if they werent done already.
it worked fine 20 minutes ago.

i did import some audio to tracks.

its a 30 second commercial spot. it hardly has any tracks or plugins.

i need this done today. ahhhh.

what are some other things i could try?

[Avid]

Did you try this one?
http://answerbase.digidesign.com/detail.cfm?DID=5124

In one case: It was narrowed down to a particular track that was corrupt within the session. However, Importing Tracks did not help. Moving the audio to a fresh channel/track within the new session fixed the problem.

<font size="2" face="Verdana, Arial">Also, how much RAM do you have and how much is assigned to DAE and Pro Tools?
You need to make sure you have left enough extra RAM for the Mac OS itself, since Pro Tools uses QuickTime during some bounce functions, which increases the memory needed by the Mac OS.

[Locash]

i have 640 meg of ram.
i did everything on that page.
except move all tracks to fresh tracks.
i did have a quicktime movie i was viewing.
and it seems once i closed the preview window of the movie my problems happened.

how do i check how much ram is allocated to the OS?

[Avid]

List how much RAM you have allocated to DAE and Pro Tools, from the Get Info->Memory window. That would tell us how much is left over for the Mac OS. You can't "assign" memory to the Mac OS, but you can tell how much it is using by switching to the Finder while Pro Tools is running and checking About This Computer in the Apple menu.

(by the way, I'm just the web admin, not a tech, so if any users that probably have better knowledge and suggestions on this can jump in, it would be appreciated)

[Avid]

Since you've already done the Answerbase search, try a Search in this forum for the words:
bounce handler

Search Subject Only
Any Date

There are a number of threads that have some other suggestions.

You might also try the same subject only search in the TDM Mac section.

You might try bouncing a different way by choosing "Convert After Bounce" or "Convert During Bounce" setings to see if that makes any difference.

[Locash]

what i ended up doing is rebuilding the track.

i re-imported all the tracks and everything worked fine.

something must have got corrupted.

[John H]

In my experience memory fragmentation can cause this problem and a simple restart usually solves it. I've only ever had it happen once where a corrupt track was the problem.

You might also try allocating extra RAM to DAE and protools. I increased DAE ram allocation to 40Mb and protools to 50Mb. It does make things run a little smoother even though you'll notice a lot of the memory is wasted until the session you're working on becomes fairly large with lots of plug-ins.

I've only got a beige G3 with 192Mb, it only takes 15 seconds to startup with my custom extension set and I've got 168Mb of free RAM to use.

Have you tried extension tweaking for a little extra performance ?

It certainly goes a long way to speeding up both starting up protools, how responsive the interface is with a large session and general performance if you run with a very minimum extension set and set you're monitor to either 256 or thousands of colours.

[rmo]

a better way than to bounce, is to rerecord the whole thing.
switch all your output's to an unused bus-pair (i allways use 15-16). also switch your master to bus15-16 then.
open a new stereo track with the 15-16 as input channel.
hit record.
done.

the fine thing is, if it crashes anyway, you've recorded parts of it and can continue recording where the machine has ended. (especially usefull when u want to bounde a whole cd!!!)
and..as i figured out. it sound better this way!