Has anyone had an issue with VST3 in JUCE where it builds successfully but does not pass audio; yet the AU executable does pass audio?
I can verify this problem is not just that of my own project. I tried compiling one of the built-in JUCE NoiseGate modules and ran into the same problem.
How are you testing the plugin? Which host are you using, and on which platform?
I’m on MacOS Catalina 10.15.7, using XCode to build from Projucer, testing on Ableton Live 10 and Live 11. Some of my colleagues on MacOS ran into the same issue as I did. I had another colleague who had no problems with the VST3 on Windows.
There’s nothing particularly unusual about your combination of OS and DAWs, so it’s very hard to see what could be going wrong.
Could you please try the AudioPluginDemo? JUCE/AudioPluginDemo.h at master · juce-framework/JUCE · GitHub
Otherwise pluginval might provide a little more information, or the Test Host in the VST3 SDK: 3rd-party developers support & SDKs | Steinberg
Note that this plugin is designed to only pass audio when there’s a trigger on the sidechain input. It would be expected for the plugin to produce silence in the absense of a sidechain input. I was able to see audio appearing at the output in Live after adding an active sidechain input.
I’d echo what @t0m said, and suggest trying out a few more of the JUCE demos. The DSPModulePluginDemo is a fairly standard effect plugin with stereo input and output, so that’s probably worth trying out.
Got it, thanks all for the help! The problem was that the prepare to play function was being called multiple times which broke the audio graph, but it is resolved now.