Quote:
Originally Posted by Tale
Exactly. Do note though that this is not as "bad" as it seems, because lots of external (semi) hardware also introduce latency, non of which is reported obviously.
|
Filling a plugin's data buffers using the "look ahead and delay" method I suggested here solves the problem of producing valid data on the very first output sample - but creates more latency when used "live".
So the point of my thread here is that there CAN BE differences in how plugins are initialized for offline vs. live uses. How is this handled? Is there code in WDL-OL that detects whether a plugin is being used "off line" vs. "live"? I think VST has something for that (or used to).