DP 11 creating much longer bounces then spec'd

[dreamuse]

I've actually seen this behavior for a while now, but thought I'd either get to the bottom of it, or hopefully others have seen it and have workarounds:

I have a piece that's 3 minutes long. As usual, I specify the start and ending measures. When I go to do an offline bounce, however, the resultant file is over 5 minutes long.

I don't have "Select all before running save bounce", though I'd assume the region selected would override this, length-of-time-wise.

Thanks in advance,

Len

[mikehalloran]

I've actually seen this behavior for a while now, but thought I'd either get to the bottom of it, or hopefully others have seen it and have workarounds:

I have a piece that's 3 minutes long. As usual, I specify the start and ending measures. When I go to do an offline bounce, however, the resultant file is over 5 minutes long.

I don't have "Select all before running save bounce", though I'd assume the region selected would override this, length-of-time-wise.

Thanks in advance,

Len

Bouncing from what to what? If a conversion is involved, say .wav to mp3, this will take longer.

Some plug-ins can get in the way. If their GUI windows are open, certain plugs can slow BTD to a dead crawl.

If your files are on an external drive, that can slow things down as well.

What OS?

There are workarounds for a lot of these issues.

[bayswater]

I have a piece that's 3 minutes long. As usual, I specify the start and ending measures. When I go to do an offline bounce, however, the resultant file is over 5 minutes long.

He probably means that the resulting bounce is 5 minutes long, not that it took 5 minutes, although that might be true too.

[dreamuse]

I have a piece that's 3 minutes long. As usual, I specify the start and ending measures. When I go to do an offline bounce, however, the resultant file is over 5 minutes long.

He probably means that the resulting bounce is 5 minutes long, not that it took 5 minutes, although that might be true too.

Yes, exactly: The length of the bounced file is indeed 5 minutes long. Since posting this, though, I found something interesting: There were 2 MIDI tracks that were disabled. If I deleted their contents? The bounce was the correct length. I'm not sure if files' lengths were 5 minutes long--didn't have time to delve that deeply--but it seems like a bug, especially if they're turned off.

[mikehalloran]

I have a piece that's 3 minutes long. As usual, I specify the start and ending measures. When I go to do an offline bounce, however, the resultant file is over 5 minutes long.

He probably means that the resulting bounce is 5 minutes long, not that it took 5 minutes, although that might be true too.

Yes, exactly: The length of the bounced file is indeed 5 minutes long. Since posting this, though, I found something interesting: There were 2 MIDI tracks that were disabled. If I deleted their contents? The bounce was the correct length. I'm not sure if files' lengths were 5 minutes long--didn't have time to delve that deeply--but it seems like a bug, especially if they're turned off.

I think that when you investigate, you won't find a bug.

[dreamuse]

He probably means that the resulting bounce is 5 minutes long, not that it took 5 minutes, although that might be true too.

Yes, exactly: The length of the bounced file is indeed 5 minutes long. Since posting this, though, I found something interesting: There were 2 MIDI tracks that were disabled. If I deleted their contents? The bounce was the correct length. I'm not sure if files' lengths were 5 minutes long--didn't have time to delve that deeply--but it seems like a bug, especially if they're turned off.

I think that when you investigate, you won't find a bug.

I'd be thrilled if this was the case, but I've seen this before, so happy to be told "Hey, dummy, do this..."

[mikehalloran]

…
I'd be thrilled if this was the case, but I've seen this before, so happy to be told "Hey, dummy, do this..."

I select regions, not measures. Anything outside the selected region will not be in the included bounce and the entire bounce ends at that exact point.

I the picture below, you'll see that I included part of a click track. Of course, I don't bounce clicks unless making guide tracks but I did this just to illustrate the point.

[James Steele]

Anything outside the selected region will not be in the included bounce and the entire bounce ends at that exact point.

I need to double check this. I recall doing a bounce to disk where I had a very long sustaining MIDI note in another track that extended well beyond the selection boundaries and DP bounced beyond the end of the selection all the way to the note-off of that MIDI note, since the note-on was inside the selection range.

[dreamuse]

…
I'd be thrilled if this was the case, but I've seen this before, so happy to be told "Hey, dummy, do this..."

I select regions, not measures. Anything outside the selected region will not be in the included bounce and the entire bounce ends at that exact point.

I the picture below, you'll see that I included part of a click track. Of course, I don't bounce clicks unless making guide tracks but I did this just to illustrate the point.

I think to DP the process is the same, though? I often create a range from the first measure to fadeout using "New saved time", and use that for bouncing. I think James' comment about sustain MIDI notes fits what I'm seeing, but I'd consider this a "not cool", if not a bug, especially if that MIDI track is disabled. If I don't include that track, then things seem to work, but I think this is counter-intuitive at best. A selected range should be a selected range, ya know?

[Tritonemusic]

There were 2 MIDI tracks that were disabled.

Just curious; how do you disable a MIDI track? I know it's possible for audio, but don't see how to do it for MIDI tracks.

Also, why are you selecting unused tracks and including them for BTD?

[dreamuse]

Sorry--I muted the MIDI track, not disabled it. Perhaps by DP's continuing to bounce to the last MIDI note per James, as opposed to the region we specify, DP is doing what we think we want it to do, as opposed to what we say we want it to do.

As far as bouncing all tracks, even if they're not on: There are often occasions I'm doing mix options where a lot of MIDI tracks may not be used. Thus, I'm not looking to create special track sets, etc...to do this. Perhaps in my naivete, I expected (and still expect?) DP to "Do as I say", region-wise and muted track-wise. Maybe I'm wrong in this assumption--in fact, apparently, I am.