KVR Audio

dBiz · Post by **dBiz** » Fri Jul 13, 2018 6:18 pm

Hi, first of all, thx a lot for the awesome work!
I see you've add my modules but they have some some graphics issue for the knobs (my res folder of binaries has some problems), i'll send you the corrected and updated modules!

bsp804 · Post by **bsp804** » Fri Jul 13, 2018 7:04 pm

Code: Select all

** July 13th, 2018
- add support for dynamically loaded plugins ("plugin.dll")
- add module Template_shared.MyModule
- change: the dBiz.* modules are now linked dynamically

Good news, everyone ! This plugin now supports plugins !
- actual, dynamically loaded ones !

That was one hell of a (holi-)day. I still can't believe that I was in the middle of making a track when I suddenly decided to do this VST port (how hard can it be ?). That was two weeks ago but I hope my work here will be done soon.

The plugin binaries are not compatible with the VCV rack plugins (that wasn't technically possible) so whether there will be any (closed source) 3rd party add-ons for this VST depends on the good will of the 3rd party devs.

The source code changes required to adapt a VCV plugin for VeeSeeVST are quite minimal, though.

If you are a plugin dev, then please take a look at this example plugin.

veeseevstrack_0_6_1_win64_bin-13Jul2018.7z

bsp804 · Post by **bsp804** » Sat Jul 14, 2018 10:23 am

For those (3rd party devs) who don't want to check out a huge GIT repository, I've created a (precompiled) plugin SDK.

The SDK requires the (free) Microsoft Visual Studio 2017 Community Edition.

It also includes a simple example plugin ("Template_shared").

resynthesis · Post by **resynthesis** » Sat Jul 14, 2018 10:36 am

Nice, excellent project, thanks!

lalo · Post by **lalo** » Sat Jul 14, 2018 12:05 pm

Marvellous!!!

In the meantime yesterday VCVRack 0.6.2 was released with the folllowing change log

0.6.2 (2018-07-13)
Added module presets
Added command line arguments for setting Rack directories
Improved UI/engine communication stability
VCV Bridge 0.6.2
Added VST FX plugin

I try to spread the voice a little more on VCV Facebook group.
I noticed that strangely enough there is not so much talking about this great port.

bsp804 · Post by **bsp804** » Sat Jul 14, 2018 4:18 pm

Think of this fork as an alternate timeline.

The VCV Rack author has expressed his feelings towards VST plugins on Hacker News a while ago (i.e. a VST version isn't on his agenda).

I for one don't fully agree with them but I think that this is a very cool project that was worthy of some practical-working-musician TLC.

lalo · Post by **lalo** » Sat Jul 14, 2018 4:38 pm

bsp804 wrote:Think of this fork as an alternate timeline.

The VCV Rack author has expressed his feelings towards VST plugins on Hacker News a while ago (i.e. a VST version isn't on his agenda).

I for one don't fully agree with them but I think that this is a very cool project that was worthy of some practical-working-musician TLC.

Yeah. In my humble opinion as a working musician/producer, total recall and VST parameter automation offered by your solution are great things for a DAW production enviroment! please keep loving it

!

Koshdukai · Post by **Koshdukai** » Sat Jul 14, 2018 5:07 pm

bsp804 wrote:Think of this fork as an alternate timeline.

The VCV Rack author has expressed his feelings towards VST plugins on Hacker News a while ago (i.e. a VST version isn't on his agenda).

I for one don't fully agree with them but I think that this is a very cool project that was worthy of some practical-working-musician TLC.

I'm curious to see what'll happen with non-VST VCV once Cherry Audio's Voltage Modular is released, since it's basically what I thought Softube's Modular was going to be (GUI UX-wise) and VCV ended up being, minus the VST part, so I was all decided on going Voltage Modular when possible.

VeeSeeVST is making me rethink that decision.

I guess the only way to lean towards Voltage again is if they create a module enclosure (like a folder for modules, Reason Combinator-style)

lalo · Post by **lalo** » Sat Jul 14, 2018 5:34 pm

koshdukai wrote:
I'm curious to see what'll happen with non-VST VCV once Cherry Audio's Voltage Modular is released, since it's basically what I thought Softube's Modular was going to be (GUI UX-wise) and VCV ended up being, minus the VST part, so I was all decided on going Voltage Modular when possible.

I was just thinking about that. Those are all good products. Let's see what Voltage Modular will offer (with module desing coding/scripting support to).
And don't forget about SoloStuff modular. VCV Rack is a really great piece of software and i respect Andrew's desing choices. Nevertheless i think that a proper VST shell for VCV as VeeSeeVst, is fundamental for a producion DAW enviroment. I think that VCV Bridge VST is a not so good devision. But anyway everybody goes for his own workflow choices. I'm using SuperCollider with Rearoute and loopMidi and i would really like to have SC as a VST but i guess it won't happen very soon or not at all. Life is tough

bsp804 · Post by **bsp804** » Sat Jul 14, 2018 8:11 pm

Nothing's set in stone. Opinions may change, just like software.

vortico · Post by **vortico** » Sat Jul 14, 2018 8:52 pm

As with any feature requests for Rack, I need funding to implement each feature. Rack is funded through purchases of the (currently four) commercial plugins on https://vcvrack.com/. A rough estimate of an official VST plugin is low 5-figures. Whether this happens depends entirely on your funding support. If you feel that you would only use these plugins if Rack was already a VST plugin, I can understand that, which is why VCV itself can support a fraction of this cost as an investment in hopes of obtaining them later, rather than having funds already secured. Thanks to those who have already purchased these plugins, as you have already contributed to this fund, along with other vital Rack features.

bsp804 · Post by **bsp804** » Sat Jul 14, 2018 9:30 pm

Please feel free to back-port any changes I did to your software. Musicians want a VST version, that's for sure. Good luck and god speed !

EvilDragon · Post by **EvilDragon** » Sat Jul 14, 2018 10:14 pm

I also agree that having a proper VST plugin is much MUCH MUCH more convenient than the current bridge solution, so thanks to bsp804 for providing it to us. I'd definitely like to see the official VCV in the same manner, so that commercial modules could be used as well within a DAW, without any externals.

Host automation is a big and important thing that is simply not there with the bridge. And no, MIDI learn is not a solution.

Koshdukai · Post by **Koshdukai** » Sat Jul 14, 2018 11:46 pm

Well, either way i.e. even if there's not enough funding (yet) to back-port/do the structural changes to VCV to support both standalone and VST builds/versions (because, from a user POV that is what makes sense, having both choices), VCV being Open-Source is what's allowing useful forks like this (or interesting ones like this) to happen, so thank you vortico for VCV and thank you bsp804 for coming up with a way to do it and most importantly, doing it, share it and keep on improving it.

Hopefully, something that will please everyone involved and interested in this may come up in time.

tl · Post by tl » Sun Jul 15, 2018 3:34 pm

VeeSeeVST doesn't get scanned properly on my system (Win 10 x64).
I have the same problem with everyone of my DAWs, Bidule, Reaper, Bitwig...
The scan process kind of freezes with VeeSeeVST. When the host starts to scan the plugin a window - maybe the plugin window - flashes up for a very short moment and then the scan process freezes; the VeeSeeVST logfile shows "loading settings.json" as the last task. Made some edits in the settings file (window size, etc.) but the behaviour didn't change.

Regards,
tl.

[announce] VeeSeeVST Rack VST2 plugin