Will VCV Rack for DAW support multichannel audio I/O?

[giohappy]

I haven’t been able to find mentions of this inside the development blog. I wonder if the upcoming VCV Rack Studio (with VST support) will support multichannel audio I/O. My intention is to integrate it with Bitwig and its CV modules.

[gc3 (gc)]

It will, per this update–and, in fact, that screenshot shows an 8-channel configuration running.

I seem to have inadvertently memorized the devblog

[giohappy]

Amazing. It looks really promizing! The screenshot doesn’t show the outputs, but I guess they will be multiple the same.

Thanks @gc3 for being my trustworthy devblog human search engine

[giohappy]

Sorry for abusing your memory @gc3 but can you confirm that Rack SDK will let anyone build (open source) modules for Rack Studio and, consequently, Rack for DAW?

[gc3 (gc)]

The short answer is emphatically yes. The only additional feature planned for Rack Studio Edition (which replaces Rack for DAWs as a name, BTW) is the link to DAWs via (initially) VST2. Other than that, there’s no difference (based on everything that’s been said so far).

Best place for this question is the linked thread, with official statement here:

GPL3 licensed plugins can be used with closed source VCV Rack?

Yes, GPLv3 plugins can be released to be loaded in proprietary software. For example, if you make a VST2 plugin intended to be loaded in proprietary DAWs (Cubase, Ableton, FL Studio), you can license and distribute your plugin under the GPL (such as Surge) as long as you sign the VST2 license agreement with Steinberg. Since Rack plugins are compiled with the Rack SDK and the Rack SDK is open-source (GPLv3), you already have explicit permission to release a GPLv3 plugin, so no need to sign a lic…

[Vortico (VCV - Andrew)]

VCV Rack Studio Edition will include a 2, 8, and 16 channel audio in/out VST2 plugin, which is perfect for its three audio interface modules.