Music Skips During Bounce to Disk

[Superbee]

Has anyone had this problem. I have had the music skip during BTD a couple times now.
It does end up in the file. I am running HD2 on a Mac G5 Dual 2.0 OSX 10.4 ProTools 7.3

Let me know if you have a fix. I searched teh DUC but came up empty.

Thanks!
Brian

[Superbee]

Also using Apogee 800's

[bashville]

Try searching again--I thought there was a thread recently about this.

Consider recording through a bus to an audio track instead of bouncing?

[crizdee]

Has anyone had this problem. I have had the music skip during BTD a couple times now.
It does end up in the file. I am running HD2 on a Mac G5 Dual 2.0 OSX 10.4 ProTools 7.3

Let me know if you have a fix. I searched teh DUC but came up empty.

Thanks!
Brian

Hi,

Usual cause is the CPU nearing max and the bounce to disk just pushing it over the edge!! are you using RTAS plugs/instruments? if so try making the hardware buffer bigger, this will give more CPU headroom. are you using 1 or 2 RTAS processors in the playback engine! maybe try setting to 1 processor! if you are close to maxing the cpu then can you bounce any RTAS instruments or audiosuite any RTAS processors? you can also try different DAE buffer sizes, this sometimes helps! you can also try making the bounce region longer by extending both ends if possible.

Or, You can do RTD, record to disk, back on to a stereo track in the session! route everything to a mix bus(a stereo aux) the route that to a stereo track and record it into the session then use export audio region and send to your hard drive etc.

Chris

[Superbee]

Excellent! Thank you!

Brian

[Ray Lyon]

BTD is unreliable with complex mixes using ADC, especially those with lots of automation, MIDI and VI usage. Putting the H/W buffer anything past 512 makes things sloppy with sync between MIDI and audio tracks. So recording the mix to another stereo track is the way to go.

[PhilSchroeder]

I gave up on BTD a long time ago. I set up one of my buses to be "Stereo" just like a typical console, and I monitor on that for the entire session, then make an audio track at the end of the day and record it and "export as..." to .aif or whatever. There are so, so many advantages to doing it this way, not the least of which is last-minute tweaking as you're listening to the mix.

One major thing to watch if you're going to work this way...you have to set up the defaults in your I/O setup so that any new tracks you create output to the stereo bus, NOT to the main output of your I/O. I've been burned many times by tracks that were created late in a session that were sending straight to my 96 I/O instead of the stereo bus. It all sounds the same (or close enough to be fooled...) but those tracks are not, obviously, in your mix after all.

Good luck, it's ultimately a much better way to work. And the failures of automation during BTD are pretty well documented.

[Oli P]

I'm using BTD...and have been for 8-9 years.
To me it actually sounds better, and I much prefer the workflow of having a dedicated master output.

My mixes have often tons of VI's running, and there doesn't seem to be any problems...other than the sessions that get totally messed up like the thread suggests.
But in those cases it always helps just to have one processor assigned to RTAS.

What baffles me, is that Digi doesn't respond to this issue at all

[DigiTechSupt]

What baffles me, is that Digi doesn't respond to this issue at all

Click on the 'Help Us Help You' link below my signature.

[Oli P]

Click on the 'Help Us Help You' link below my signature.

Hmm...that sure helped

I do have my setup specs in my signature...and this problem only occurs every now and then...on some random session. I haven't been able to find a pattern in plug-ins or track counts etc.
But the remedy seems to be the "one RTAS processor" setting.

It would be nice with a simple explanation why the session can play perfectly well...and then screw up once you try to bounce.