Latency Compensation / Lookahead RNBO

https://cycling74.com/forums/reporting-plugin-delay-to-daw-for-compensation

i would always leave it fixed at the maximum and use a sampledelay to "extend" the latency to this fixed value. you never know what a pre 3.6 host does.

Shit so I have to export to code, implement it manually and then compile? I'll give that a try and report back (will probably take me a long time haha) I don't think I can do the "extend" trick unfortunately afaik... but I'll think about it some more, maybe it will work for me. What do you mean by "pre 3.6". Vst3.6? Or...?

i vaguely remember that there were hosts which have problems with dynamic latency values.

in theory the plug-in can propagate what and when it wants, but don´t you think it i easier to set things to a fixed value?

mind you, there are also hosts like this "max" which does not have latency compensation at all. a fixed latency of 500ms no matter the FIR size or lookahead parameter will make life easier for those. ;)

Fair point, I generally wouldn't want to exclude anyone just cause of the daw they use. Then again, for some users, being able to get the minimum latency is probably important and since the plugin is geared towards these kind of "detail focused" artists I still think dynamic latency might still be the best choice. Also it's not a particularly innovative idea so I'm sure there are lots of alternatives. I'll think about making a static latency version maybe. Any thoughts on the other things I asked? I had a look at JUCE the other day and just the thought of having to dig through docs and stuff in a framework I'm not familiar with had me stressing out. Also what do you mean by pre 3.6?

using namespace RNBO;