"Could Not Complete Bounce To Disk..."

[Aussie169]

"Could Not Complete Bounce To Disk...command because: Assertion in "\code\azores_Handel\AlturaPorts\NewFileLibs\FF\Au dio\FF_AudioProperty.cpp", line 33

Digi.....

please please please, when are you going to fix this?
It is driving me crazy and making me look stupid in front of clients.
It happens now on 95% of bounces!

[lemix]

Mark,
I remember this error.
Try to change to a different destination directory, reduce plug-in load, and purge the Digidesign databases before opening the session.
How much empty room is currently open on your destination drive ?
Just ideas here..hope it helps..
cheers,

[Aussie169]

Happens on big sessions, small sessions, internal drives, external drives, both with loads of free space.

I'm sick of the work arounds..... I really don't think I'm asking too much to have it fixed....... finally

[lemix]

Have you checked the answerbase ?
Sorry to hear about your frustration mate...
cheers,

[albee1952]

Need more info. What PT version, computer specs, tweaks done...

[Aussie169]

Well, not that it matters, because this is something Digi needs to fix. I know and use all the workarounds.


PTLE 7.0
Mbox2
Dell Inspiron6000 (Which is on Digi's Recommended list for the Mbox)
1.86 Centrino with 1GB RAM
60GB internal drive.
300GB external drive.

Haven't done any tweaks except for what Digi says in the install guide. Resources aren't a problem. I've had big sessions that work and small sessions that don't.

[lemix]

From the Digi Answerbase :

"Could Not Complete Bounce To Disk...command because: Assertion in "\code\azores_Handel\AlturaPorts\NewFileLibs\FF\Au dio\FF_AudioProperty.cpp", line 33 when attempting to Bounce To Disk in PT 6.4.

In one case, trashing databases and preferences fixed the issue and bounce performed successfully

- Try adjusting the length of the bounce (make the selection longer or shorter).

- If the DAE buffer is set to level 8 in Setups > Playback engine, try reducing this value to level 4 or level 2.

Workaround:
Bus the tracks to a new stereo track, record the session in real time, then export the new 'stereo' files using the Region Bin's Export Selected command.

I know... But, as I've mentioned earlier, dumping the database folders did fix it for me on OSX/TDM/Mac..
cheers,

[Aussie169]

As I've said, I know and use all the workarounds.

I'm trying to make the point to Digi that SHOULDN'T HAVE TO use a workaround.