@t0m Thanks a lot for cherry-picking this to master. I really appreciate that.
Unfortunately this doesn’t resolve the issue on my end.
I reported the problem and tested this same change, few hours before this topic was posted and I saw no change in the behavior of Cubase.
Just tested again with latest master (I see the commit and the change), but the long tail that I’ve set in my processor doesn’t get acknowledged by Cubase (latest) and the tail still gets cut-off after about 12s.
Here is how I set my subcategory in AppConfig:
//==============================================================================
// [BEGIN_USER_CODE_SECTION]
#define JucePlugin_Vst3Category Vst::PlugType::kFxReverb
// [END_USER_CODE_SECTION]
...
And this is how I override the tail length in my PluginProcessor:
double PluginProcessor::getTailLengthSeconds() const
{
#undef max
return std::numeric_limits<double>::max ();
}
I haven’t upgraded to latest VST3 SDK - I am at 3.6.7 because I haven’t noticed when Steinberg released and now I am too close to a release myself, to update dependencies. I am on latest official JUCE (5.2.0) and currently test on Windows 10 with latest Cubase Elements (with enabled “Suspend VST3 plugin processing when no audio signals are received”). BTW, @klus do you have this feature enabled in Cubase → File → Preferences → VST → Plugins? Perhaps it’s disabled on your end? I am not sure if you test in Cubase, sorry if I missed that somewhere in the thread.
P.S.:
- In the VST3 documentation it says you can achieve this (endless tail) by adding a second subcategory to be kFxGenerator. Sorry for the dumb question, but how do I do that (setting multiple categories)?