As you use and explore Rack modules on the VCV Library, sometimes you encounter behavior, features, or metadata that aren’t quite correct. To help improve the quality of these plugins, consider reporting the following issues to plugin developers.
Missing metadata, such as module descriptions, module tags, and URLs. Have you searched for a tag and not found a module that falls in that category? Could the module description be more descriptive about the module does or is emulating? Suggest it to the developer. Manifest reference
Incorrect polyphony support: Does a monophonic module not sum polyphonic audio inputs? Does a polyphonic modules not support up to 16 channels? Do some parameters not accept polyphonic signals? See https://vcvrack.com/manual/Polyphony and https://vcvrack.com/manual/VoltageStandards#polyphony to learn exactly how polyphony should work in VCV Rack.
Bug reports for crashes, audio glitches, and UI issues. If Rack crashes when you interact with a module in some way, send your
<Rack user folder>/log.txtto the module’s developer with a description of how to reproduce the crash and the version of your OS, Rack, and the plugin.
If the plugin’s source code is hosted on GitHub, register for a GitHub account and open an issue explaining the above issue(s). If not, use the provided contact information by clicking on the email icon or author’s website on its VCV Library page.
Remember to be constructive when reporting issues by only offering beneficial time-saving information! Many developers, particularly of open-source and freeware plugins, make plugins for fun and are not obligated to fix issues, although they may appreciate your positive suggestions. Premium/commercial plugin developers are obligated to provide a working plugin but may make a judgment not to implement your suggestion.