Quote:
Originally Posted by Nonlinear
A possible difference between the plugin that does NOT work and the one that DOES work is that the faulty plugin reports latency to the host. Is there a special requirement - or place in the code blocks - for reporting plugin latency to Pro Tools? I am currently using GetSampleRate() followed by SetLatency() in the Reset() function (also called as the last step in the constructor).
|
I use GetSampleRate/SetLatency in my Reset, successfully.
You say, "also called as the last step in the constructor". I'm not sure whether that's a problem, but I think Reset is called for you (from EffectInit, I think). I don't have time to check that out, but offhand it seems the only thing you're doing different from me is calling Reset or SetLatency in the constructor.
I'm using
https://github.com/earlevel/wdl-ol/tree/earlevel, but I don't think I changed anything that affects SetLatency directly.