Part of one track at cut off when using Bounce To Disk

[Babz]

This is a new one for me.

I did a bounce to disk and a soundbite at the beginning of one track was not included in the mixdown. I tried various attempts at a fix -- moving it to a separate track, restarting, repair permissions, etc.

Eventually, the only thing that would fix it was to add an extra bar of silence at the beginning, and then finally it would be included as part of the bounce.

I've read threads in the past of stuff getting cut on with bounces (but never experienced it). The strange part is that it was only part of one track getting not cut off, not all the tracks. The soundbite getting excluded did not start at the very beginning. Other tracks which DO start at the beginning are not cut off.

It could have something to do with lookahead (UAD Precision Limiter on the Master Track), but I did several bounces on this project earlier and didn't experience this issue. I use this limiter all the time and have never gotten this.

This happened after I had done the final mix with no problems. I then decided it needed a few minor tweaks, so I opened it and did a Save As (so I could keep the earlier version). I moved, and trimmed, and crossfaded a few soundbites (but did nothing to the problem soundbite, and none of my edits were near the beginning of the sequence).

Anyone ever experience anything like this?

Now that I finally have a complete bounced WAV file, what is the best way to trim off this extra silence at the beginning?

Best,
Babz

DP 8.07. 64-bit. About 10-12 audio tracks. No MIDI. Minimal plugins used (2-3 DP plugins, a couple of UAD, one NI delay plugin). OS X 10.8.5 (Mountain Lion).

[stubbsonic]

Now that I finally have a complete bounced WAV file, what is the best way to trim off this extra silence at the beginning?

Can't speak to the main part of your quarry but for this, I use the Waveform editor, I turn off the snap to checkbox so I can freely select. Zoom in, select silence from right to left. COMMAND-J to snip it out.

[MIDI Life Crisis]

Workarounds are great, but I suggest contact MOTU to find a solution. If I'm BTD for a film or TV or other score to picture, I need precise file lengths to match the picture or I have to f#$% with sync and that is really unnecessary if the software is working correctly. There is something a miss. Contact MOTU! Pre-render?

[Babz]

I created a new DP file to do the trimming.

This project was originally started in DP 6, so maybe that had something to do with it. Hopefully this was just an isolated incident.

But I still would like to know if anyone else has had problems with stuff getting cut off or not included when bouncing to disk.

Best,
Babz

[daniel.sneed]

I've had, in the past, severe but inconsistent bugs with DP bounce.
Never with audio tracks, but *sometimes* with MIDI tracks.

AFAICR, two kinds of bugs:
- first MIDI notes not present in the bounce, with *some* VIs.
- *some* MIDI notes not present in the bounce. This last one was a deal breaker, for the missing notes were only in heavy fast rhythmic contents, so quite hard to check out after bounce. I went with real time recording of the final mix.

[niharsavala]

I am getting the same problem. fraction of the audio in the beginning getting cut off. It never happened before.

Did you guys find a sol to this, I wud be very eager to know? This is really frustrating. I have to manually get them in sync, thanks to the age-old habit of putting cow-bell count-ins at the start.

[mikehalloran]

I am getting the same problem. fraction of the audio in the beginning getting cut off. It never happened before.

Did you guys find a sol to this, I wud be very eager to know? This is really frustrating. I have to manually get them in sync, thanks to the age-old habit of putting cow-bell count-ins at the start.

Not enough information. What version of DP? What OS? How are you selecting tracks? What are you bouncing to? Is it audio only? Audio and MIDI? What plugins are you using?

This thread is two years old. Most of us have never had the problem.

[daniel.sneed]

This has been covered in another thread.

AFAICR, I *sometimes* get unreliable bounces when there are heavy plugs on master fader, such as Ozone and the like.

This does happen with very low audio track count, and a few fades and track overlaps.
But, AFAICT, never when there is only one stereo audio track.

So, nowadays I always bounce in two steps :
- first step *mix* with all tracks and *light* master fader (i.e. MW limiter only).
- second step *mastering* with one single stereo audio track only, and *heavy* master fader (i.e. Ozone and such).

[mikehalloran]

Yea, I was thinking of Ozone 5 when I asked even though I've never had that issue. It could be, because I use Ozone Advanced, that I can use the various tools independently without loading those I don't use.

A generic "this just started..." Yikes. Without context, there's no way to help.