Disk Space requirements for 5.1 bounce?

[ppine]

When bouncing a 5 minute 5.1 mix to a 9 gig drive with 1.3 gigs available, at the finish of the bounce, I get a dialog bounce that says "Not enough disk space to complete, another X.X MB's needed.

I did this with a 74 minute bounce, with 10 gigs free, and at the end it gave me the crappy news that it needed 7.9 MORE gigs to complete.

Is there some HUGE temp files that are created when bouncing 5.1 mixes? I have to bounce to an empty 18 gig, then copy them to the production drive..

lots of DAE ram allocated, as well as app ram.

seems like sompin ain't right in surrounds-ville. [img]images/icons/tongue.gif[/img]

[F.J.]

It could be that the drive is fragmented and even though there is enough space to fit the session, the largest block left may not be big enough to hold the largest file.

[ppine]

I considered that possibility due to the fact that I did not get the "not enough space" BEFORE the bounce started, like ALL other Mac apps kindly tell you.

[ppine]

That's exactly what we did to work around this problem. The only snag we ran into is some files needed to be converted from 48k to 44.1, which would have been easier using "bounce to disk"

BTW, Did you give up on "bounce to disk" because of the same issues I'm having? Just curious....

[ekuehnl]

Three things:

1. There seems to be a slight difference in quality when using "bounce to disk".
2. Errors (bounce handler can't keep up and not enough disk space, etc.)
3. The ability to stop the bounce, make a change, punch back in and keep bouncing. This has saved me TONS of time on feature length projects.

-Eric

[ekuehnl]

I gave up on "bounce to disk" long ago. Why not bounce to an adjacent 5.1 track? Works great for me. Also, then you have the flexibility of punching in to make fixes.

-Eric