-
**Thanks for taking the time to write a bug report!** Use the following prompts to help you describe what's going on. The more info you provide, the easier it'll be to understand how to fix it for yo…
-
**Describe the bug**
VST2 version of plugins that have "baked in" MakePresets don't load properly when a saved project is re-opened in some DAWs . The parameters and controls initially load correctl…
-
There are a few things that should be reviewed here:
- You can turn contextual menus off, but only globally, not per control, and multi-parameter controls will simply provide the contextual menu …
-
Currently the plugin editor state is valid only during the lifetime of the plug-in and is not reloaded. VST3 has a infrastructure to support recall, but other APIs are less obvious. This needs discuss…
-
Offered as a simple-to-reproduce example showing problems with factory presets with VST2 and VST3, primarily for the purpose of discussing wider problems with VST2 and VST3.
Repro—add factory prese…
-
-
**Problem**
The plugin now oversamples if the input signal is e.g., 48kHz and the capture is e.g., 192kHz. I appreciate that the oversampling algorithm was chosen to be the one with lowest latency, b…
-
Is it possible to support IR in stereo mode in the future? In other words, can I count on downloading stereo WAV files containing IR in order to apply convolution for the left and right channels separ…
-
It would be great if the developer can add the feature to allow the users preferred GUI size to be saved as either default in any DAW and for the current saved size of the plugin interface to be recal…
-
https://github.com/iPlug2/iPlug2/blob/b91b3abdba4639aa589d8e0baacf7e8e8cee1f6d/IPlug/VST3/IPlugVST3_ProcessorBase.cpp#L45
Does this mean VST3 support is limited to 16 channels?