I know. This is not the first old thread he was in being brought up. The first time it happened it made me pause. It caught me off guard. It reminded me of how much I miss him. 

Exactly the same thought here.
 
RIP Billy, wherever you are.

Wow ancient thread. Just to clarify oversampling in general should not require realtime playback.
Its just a DSP process that requires more computation. If anything its more costly to do during realtime playback.
 
When we do plugin upsampling the results are identical during slow and fast bounce.
 
This thread makes me wonder if we should be setting the render flag on even when we are doing realtime bounces because some plugins seem notice that and change behavior. hmmm...

Noel Borthwick [Cakewalk]
This thread makes me wonder if we should be setting the render flag on even when we are doing realtime bounces because some plugins seem notice that and change behavior. hmmm...

Couldn't it lead to situations when real-time bounce would be impossible, if plug-ins would take render settings, requiring more resources than when just playing. So project would play, but there would be lack of resources when real-time rendering. Am I right?
But now it is possible just to record output, so it might be an option.

Yes it would be risky to enable the render flag since if a plugin starts doing more costly operations it could drop out.
That's why I kept the behavior identical to playback.

Sorry to have commented on an ancient thread!   Didn't notice.   But it is still a possible situation of interest, it is not at all uncommon to get everything sounding just right on playback, then bounce a bunch of stuff and the mix seems (I only say "SEEMS" so far) different somehow ... and then in big complicated projects tracking down differences can get very difficult --- even misplaced audio and mis-transpositions can sneak in, ahem, from other issues. 
 

Everything old is new again.
 
Noel, if you're still listening, I have a question regarding slow/fast bounces and MIDI automation. This doesn't happen often, but I've seen it several times with sample libraries (both SampleTank2 and Kontakt 3, 4 and 5). And that is that MIDI automation is sometimes ignored when you're doing a slow bounce, but works correctly with a fast bounce. Any theories as to why this might be?

williamcopper
Sorry to have commented on an ancient thread!   Didn't notice.   But it is still a possible situation of interest, it is not at all uncommon to get everything sounding just right on playback, then bounce a bunch of stuff and the mix seems (I only say "SEEMS" so far) different somehow ... and then in big complicated projects tracking down differences can get very difficult --- even misplaced audio and mis-transpositions can sneak in, ahem, from other issues. 

I would say that is incumbent upon you to create a project that factually reproduces what you are stating. I see no such issues when bouncing. I am certain if it was a common problem the noise on the forums would be deafening.
 
Regards,
Dan

bitflipper
Everything old is new again.
 
Noel, if you're still listening, I have a question regarding slow/fast bounces and MIDI automation. This doesn't happen often, but I've seen it several times with sample libraries (both SampleTank2 and Kontakt 3, 4 and 5). And that is that MIDI automation is sometimes ignored when you're doing a slow bounce, but works correctly with a fast bounce. Any theories as to why this might be?

I believe that is an old bug that was fixed in a later version. You are still on 8.5?

John
This is an old thread.

It's new to me since I've been frozen in Carbonite hanging on Craig Anderson's  studio wall.  Great thread and great remembering  Ba Midi
 
D