Hi, I’m following the tutorial in 2025, and found a bug probably with the python script, was running from the SDK, I was wondering the docs could use some polishing any idea where to start working/contributing to the dev guide, and maybe starting by the topic of
When to use Rack src and when to use the SDK, which skill levels are needed, its a bit confusing for me.
Any pointers would be appreciated, also any ideas from other devs who maybe had problems solved during following the tutorial.
from my experience the panel part was a bit challenging, and still is.
I’m developing my first module for rack 2 as a vintage scope, to get acquainted with the ecosystem and contribute to this beautiful community after a long break I had since rack 1 from dev modules.
VCV is closed to contributions (documentation, too as far as I know). The way to improve it and its documentation is by reporting the issues you encounter to VCV - Support…
One of the first issues people run into is that Helper.py relies on 6-digit hex format for the key colors to position widgets, but some SVG editors will emit 3-digit hex colors or use rgb/hsl. [ed: according to the change log, fixed in Rack 2.6.5]
The code-generation approach doesn’t age well as you evolve your plugin, and almost everyone abandons using it. They instead adopt a variety of strategies to make panel design and maintenance easier or happily have very plain panels.
I personally recommend building Rack versus using the SDK, especially if you want to get deeper into how Rack works and if you’re wanting to make custom UI widgets. I love being able to debug into Rack and having the source code always available locally to reference.
I have a series of dev notes here #d dev notes for VCV Rack: Check out the one for “Build Rack” for that subject. The intro is universal, but the detail is Windows-specific. Worth reading still because a lot is common between platforms.
If you haven’t invested too much time on your plugin following the tutorial, check out the “Use GenericBlank” dev note and the Github template repo it points to as a better way to start a new plugin for many users. There are also tips for panel development, and so on.
