As you probably know Audacity has been going through some redesigns on its way to eventually become a fully fledged DAW. So I decided to try the plugins I’ve made with IPlug2 in it but for some reason they don’t work right. They sound like they are continuously processing the same block over and over again, making this strange noise. The thing is, all these plugins work fine on Reaper, Cubase, Logic, &c. but not on the latest Audacity and, on the other hand, the only plugins that don’t work in Audacity are mine, and other 3rd party plugins work fine.
So the question is, has anyone else tried their plugins in Audacity, and how did it go? I know this programme is still being developed, now as part of the Muse Group, and so anything can change in the next versions.
I just discovered this same problem in our plugins - all 17 of them, many of which have been around for years. The VST2 versions work fine but the VST3 versions do what you say - they loop a small snippet (block size) continuously in “preview” mode and produce no output at all when rendered. This problem seems to exist with all versions of Audacity since VST3 implementation in v3.2 on both Windows and Mac.
Will try to dig in with the debugger but, as you also said, these plugins work properly in other DAWs and other brands of VST3 plugins do not do this. Doesn’t make sense.
I have since tested VST3 plugins from other known iPlug2 developers in Audacity and they work properly - so someone here knows something and apparently tweaked their code to fix it. Please share!
In the meantime, I ran it briefly in MSVC debugger on Win10 and I don’t see any obvious problem with the plugin. The plugin receives and indexes through nFrames of samples as it should but Audacity doesn’t seem to be advancing to the next block for some reason. I don’t think that’s the plugin’s fault - but then why do other VST3 plugins work in Audacity?
