As far as I know there is no advantage in using FB over real time bounce as far as quality is concerned just that there is no difference. I have BFD Eco and BFD2 and BFD3 all of which I FB.
 
Beep I am fine and doing well. I hope you are in good cheer and happy.
 
Its always a pleasure to see you here.  

There are a couple absolutes.
 
If you're going through external effect inserts or other hardware processors (in my experience, sometimes even external hardware fed by FireWire), then you need to use real time bounce.
 
If you're using MIDI plug-ins, then you need to do fast bounce (unless you render first, of course).
 
I never noticed any difference between using the two, but I often use real time bounce so I can hear the bounce "just one more time."

AndertonIf you're using MIDI plug-ins, then you need to do fast bounce (unless you render first, of course).

if i'm following this correctly, this is because real-time bounce ignores midi-plugin settings?

BlixYZ
...My message is primarily for people who mistakenly think there is some sonic/quality advantage to real-time export.

Good point. Unfortunately, for me I always use real time bounce because of my heavy use of EastWest's Play libraries. If I try to FB, it works sometimes, sometimes not so I just don't take the chance.  However, if I'm just bouncing audio, then it's Fast Bounce away!

i've tried using real time bounce however, the issue i faced before was the envelopes (MIDI CC) does register during the process. The audio printed to track does not reflect the MIDI CC changes. If however, i use Fast Bounce, the printed audio track will sound perfect.
 
Those who have this working do kindly advice. many thanks.
 
i have posted in a previous thread but there was only one kind reply. The reason for real time bounce on my end are due to either external hardware and or sometimes Kontakt 5.
 
On another note, i would like to confirm that so far in null tests, i have not detected any differences between Fast Bounce and Real Time Bounce except for round robin samples. 

I once had a problem similar to what keyzs is describing. It happened with SampleTank 2.5, when using MIDI CCs to control one of ST2's parameters. The CCs were ignored with the slow bounce but worked find with a fast bounce. That's the only time I ever had issues with slow bounce. Fast bounce problems, OTOH, have been far more common. Omnisphere in particular, so it always gets a slow bounce.

@John... glad to hear it. I'm busy doing some pretty wacky stuff at the moment but I think it'll be worth it so reasonably cheerful. Cheers.
 
@Anderton... That is interesting but confusing. I have not as of yet really used or needed MIDI FX but have been meaning to try them out for the sake of... well just knowing how to use them and figuring out how much use they may be to me. Could you perhaps elaborate a bit as to why Fast Bounce would cause an issue and under what circumstances? That is if you know otherwise mayhaps we could get a Baker in here to comment on it.
 
To the Bakers (if any are watching)...
 
In regards to the MIDI CC stuff... that's another (or perhaps related) issue I would definitely like to know more about and why FB would work better than real time. Is this a reported issue?
 
I have always been under the impression the FB was a convenience and was simply a sped up version of real time. If somehow the real time bounce has been allowed to become outdated or something under the assumption people will be using FB as SOP then that should probably be fixed or some documentation put forth detailing potentially problematic circumstances with real time. I've always viewed real time as a sure bet but if that's not the case for certain procedures I'd definitely like to know... especially if CC data is getting mangled which makes absolutely no sense to me.
 
I'm glad it was brought up because I'll now keep an eye out for it but honestly I'm not even really understanding how this would manifest itself. Could those who have experienced the problem describe what happens in a little more detail for a dum dum like me? I'd appreciate it.
 
If I'm not back (I'll be watching the thread but may not be logged in) thanks in advance. Cheers.

I've just tried it but I had a real job keeping up with my "live input" solo and fast bounce engaged.  
 
//

I have also noted cymbal cutoffs in BFD2 which appear to have been resolved with FB disabled. Seeing John has no problem makes me think it might be a system resource issue, or perhaps related to an aversion to freezing tracks (always finding I missed a tweak and have to go back and unfreeze everything).
 
FB can be a valuable time saver and productivity improvement compared to some alternatives.
 
Sounds like I need to test this with BFD3 on a newer PC with more resources at hand.

Beepster
@Anderton... That is interesting but confusing. I have not as of yet really used or needed MIDI FX but have been meaning to try them out for the sake of... well just knowing how to use them and figuring out how much use they may be to me. Could you perhaps elaborate a bit as to why Fast Bounce would cause an issue and under what circumstances? That is if you know otherwise mayhaps we could get a Baker in here to comment on it.

For some reason, fast bounce is needed to take MIDI effects and CCs into account. Not sure why. The Bakers are aware of this. Maybe MIDI FX process in real time rather than calculating first and then spitting out the data? I dunno.
 
BTW I have an upcoming article in Keyboard magazine about MIDI effects...I think it's the November issue. MIDI effects are great. I'd like to see more development. Of course, now that Logic has them, Apple fans will think Apple invented them so interest will spike 
 
In case you didn't know Cakewalk invented the MFX standard and made it open so people didn't have to pay any licensing fees. Back in the day of Cubase SX, Steinberg even offered a wrapper so you could run MFX effects within Cubase. Cakewalk was one of the first companies to really pay attention to MIDI effects...maybe it's time for them to reclaim the crown.