Creating a package

Development
1

Hello all, I have created a few modules (first time developer in VCV). I was wondering what is the best way to create a package for distribution: should I just put them on in a GitHub repo as separate plugins? What are my options? Thankful for any advice

2

Are they closed source?

3

How many modules did you code so far?

Usually you put all your modules into one single plugin.

I assume, your modules are open-source (because you mentioned GitHub). So read the guidelines for licening to see the options here: VCV Rack Manual - Plugin Licensing

4

Some questions to ask yourself:

  • Are you doing builds for all of Mac, Windows and Linux? Or are all your consumers running the same OS?
  • Are all your consumers already building plugins, so they can clone your repo and build for themselves?
  • Do your consumers know how to install and uninstall plugins not part of the Library?
  • Are you prepared to manage the identities of plugins+modules and their versions so that there aren’t conflicts, duplications, or issues on upgrades?
  • Do your consumers only use standalone or expect to use it in their DAW?
5

Release them to the VCV Rack library.

1 Like
6

No, open source

7

It’s going to be 4 modules for now adding more later. I am not sure what you mean by a “single plugin” these modules cannot be consolidated into one. But I see on GitHub that multiple plugins are contained into a unique src folder, as a single family of plugins. That is what I would like to do but not sure how.

8

Are you doing builds for all of Mac, Windows and Linux? Or are all your consumers running the same OS?

Ideally any of the three OS

Are all your consumers already building plugins, so they can clone your repo and build for themselves?

I don’t expect them to, no. I don’t have a specific audience in mind though. I would just like for people to use them

9

For example, Fundamental is a sinlge plugin that contains several modules.

See also: VCV Rack Manual - Plugin Manifest

IMO the best is to analyze how it is done by looking at GitHub - VCVRack/Fundamental in detail.

1 Like
10

Got it, thanks!

1 Like
11

If you just want anyone to use them, then you should get your plugin added to the library. Publishing only on the side will have a far smaller user base. Of course, as part of preparing for publishing to the library, you will want to publish on the side to a limited number of beta testers. To find beta testers, you can post here, and maybe the Discord, too.

2 Likes
12

Thanks, I will make sure to post it here first. I will join the discord too. Much appreciated