stop disabling "fast bounce"

that is all.

James I don't understand what you are asking?

Sounds like a directive.
 
OK, I won't do it any more.  (well, I actually never did but...)

I've read that for some VSTi's the "real time" bounce is necessary. (older plugins, slower plugins, hardware) Some sample information may go missing with the "fast bounce" method. Another example, BFD3 drums, some long ringing cymbal articulations may get cut off.

I used to have problems with fast bounce until I figured out I was using the wrong driver (WDM vs ASIO). Once I got that sorted, I started having problems with real time bounce. :)
 

I don't have BFD3 but would be interested to hear about any other "problematic" plugs. I have quite a varied collection and have never had a single problem.

Kev999

noynekker
I've read that for some VSTi's the "real time" bounce is necessary...Some sample information may go missing with the "fast bounce" method...

Indeed. I've had some issues with missing notes/beats with some softsynths and unticking Fast Bounce always solves the problem. I tend not to use Fast Bounce anyway unless I'm bouncing audio only.

Ditto...if I freeze most tracks I never have a problem with fast bounce but there have been times when I've had many MIDI tracks with lots of data on them (especially lots of mod data) that I've noticed a note may hang in the final render.
It's nice to have the option I think.
 

OK Now I understand, never had a problem with fast bounce but then I tend not to have more than 6 or 7 track unless I have drums and then it only doubles to 12 to 14 depending on how many drum tracks I split the kit into. 

Just popping in to say... I respectfully disagree. Certainly FB is an awesome thing but I rarely, if ever, use it. Not that I've had any problems with it as far as I can tell but my rig is really overspec and my interface has been rock solid since I got it... so yeah, I would expect it to work. However I am not going to assume that it will and as stated up thread finding out there is a problem with a bounce after the fact (or even worse not noticing it at all before releasing the material or whatever) is a huge PITA/disappointment. I figure if I can listen to a track over and over and over again while editing/mixing I can sure as heck wait for a real time bounce to do its thing.
 
The real issue though is this seems to be implying that a real time bounce would be the source of a problem and fast bounce is the solution to that problem. I ain't no expert but that does not seem like it could ever be the case (except perhaps as a cure for impatience). Fast Bounce is a convenience for those of us blessed with powerful systems and/or small loads being fed into said systems. The advice (or at least my advice) is usually the exact opposite. If you have a problem with a bounce/export (like dropouts or system freezes/crashes) one of the first things to try when troubleshooting would be to DISABLE fast bounce features.
 
Perhaps I'm missing some context here (haven't been around due to extreme preoccupation so maybe there has been a slew of complaint threads that this relates to) but that's how I roll when doing these things.
 
tl;dr
 
Bounce problems?
 
Real Time > Fast Bounce.
 
Hope everyone is well. Cheers.

Right. Under ideal conditions they should be identical but it is, AFAIK, more resource intensive thus more prone to dropouts and other flubs/hiccups related to the system tripping over itself. You know me. I'd rather err on the side of extreme (perhaps paranoid) caution than to risk even a tiny problem because a) I have so little time to screw around with the DAW (unfortunately), b) I'm not quite as experienced as others so if something does go wrong and I don't catch it right away I may end up chasing my tail thinking it was something else and c) I'm one of those people that seems to always encounter little problems if I'm not vigilant.
 
Great feature and it certainly should be employed and enjoyed but implying that using real time is going to cause some kind of issues that will be solved by using FB instead doesn't make sense to me and I think if a beginner were to read this they may misconstrue the intent of the thread. A couple years ago I may have read something like this and thought that real time was a source of problems and then erroneously avoided it.
 
Knowaddimean? Also... howdy, John.

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.  

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?

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. 

@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 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.