Bounce To Disk Fails in 6.1.1 after upgrade

[Blind Dog]

I just installed 6.1.1 (upgrading from 5.3.1) Everything seems to work fine except that now I get a "bounce handler cannot keep up (-9132)".

I did install the Windows Media support. I also own the MP3 Option. This happens when bouncing to any option - WMA/WAV/ MP3. This worked fine with the same project on 5.3.1 - I was simply testing the new bounce to WMA when it started happening - now I can't bounce to anything.

Is this a bug in the code? reasoning: Project A bounces fine in 5.3.1- upgrade and now project A does not bounce - what changed? The PT software.

I've removed plugs, changed DAE/Playback settings, etc. Anyone know just what the code means? Anyone having this problem?

[tele_player]

You're not the first person to run into this problem since upgrading to 6.1 or 6.1.1.

[JMS40]

Here are a couple of threads.
Rail lists other important threads in the first link, second post.

Also search this forum with "Search the DUC" link (above or below). Lots of info there.

http://duc.digidesign.com/showflat.p...rue#Post548216

http://duc.digidesign.com/showflat.p...rue#Post558663

[Blind Dog]

Thanks - I've read most of this stuff - it won't fix the problem. It should be pretty clear now to all that this is most likely a problem with the PT software's bounce engine - if I had to speculate I'd point to the changes that support the inclusion of the new target file types.

Digi states that you should turn off paging and disable all apps that execute with the run command on startup - I agree with the later but not the former - that's just a misunderstanding of the Windows Kernel and paging works. Digidesign has suggested that there is a patch forth-coming - looks like my PT production is severly crippled until they can fix the problem.

[Keith Owens]

When I got this same error, I defragmented my OS hard drive and then things were back to normal. I've only seen this error that one time and I have been using 6.1.1 from the first day it was out.
I hope this helps.

[Keith Owens]

I figured it was my Audio HD first but it wasn't, it was the Operating System HD (C: where PT is installed) and it was in a mess after just two days.

I hope this helps.

[tele_player]

Where and when did Digi state this?

Digi states that you should turn off paging and disable all apps that execute with the run command on startup
.
.
.
Digidesign has suggested that there is a patch forth-coming - looks like my PT production is severly crippled until they can fix the problem.

[Blind Dog]

well, I can't tell you when, tele - but I expect you don't really care anyways - my impression is that you're being antagonistic - sorry in advance if I got the wrong idea.

the "where" is easy - search the answerbase for the bounce handler error dialog text and you'll find it.

the patch is hear-say from a post on DUC where a user claimed he called customer support.

As far as the drives go, my drives are not fragmented - like I stated: This problem did not exist in 5.3.1 - it was introduced immediately upon upgrading to 6.1.1.

[nikki-k]

Hi!
Digidesign did in fact state that, "..we are looking into it.." in a thread quite some time ago.

I am not sure of the exact total number of Sandra reports that Rail and I have received, but I know it is not very high, under 10 last I checked. Of those received, some did have reasons that could account for the BTD issue(s) some were/are seeing.

I have said it before, and will say it again: PT seems to want to live under certain conditions. These conditions are a bit more strict than with many other apps. With 6.1+, PT seems to be holding a bit closer to the constraints of the software/system/OS outlines provided by Digi. Additionally, it has also been mentioned that Digi in fact does NOT perform any tweaks other than those stated in the various "Getting Started" guides, and the PT Reference Guide. Follow the compat docs, and follow the Getting Started and Reference Guide FIRST before doing a "tweakfest." Once solid, tweaking should be done ONLY to improve performance, or to alter the enviornement to personal taste. Extra tweaks should NOT have to be performed to attain a solid work enviornment with PT.

Many, if not most, users have seen no BTD problems. As such, it appears that it is not a bug within the software, but simply an individual aspect, or aspects, of individual machines, and additionally the "tailoring" and/or customization of said system causing this. Does it suck? Of course! Systems that worked with 5.3 and earlier do not carry a gaurantee of operating correctly with 6.1+. However, if a system fits within the Digi compat docs, and has been installed and setup according to Digi instructions, it should work.

Small problems that may not be apparent (such as sticks of memory that have faults) can also add to, or even be the sole cause.

[Jsc162003]

Here's a story....and it's true!

Ever since the move to a 002 and 6.1.1 on windows xp pro.....I was having trouble bouncing to mp3.
( I have Digi's MP3 Option). I would get consistent "access violations".and BTD handler can not keep up errors.

A little poking, probing and testing shows that (on my set up at least) it must be a 24 bit session to bounce to mp3. 16 bit sessions will not bounce to mp3.

I did not have this problem with the old setup (AMIII and 5.3.1).

Hope this helps somebody.