One Synth Challenge #149: VeeSeeVSTRack (liqih Wins!)

[doctorbob]

@RR I just copied all folders and the 8 files to a folder in my 64-bit c:\vst\64-bit\vcv\ folder.

Fired up Reaper and it worked ...

dB

[Leonard Bowman]

This is a special one for me. I found out about Rack right around the same time I learned that VST plugins existed. That was back in Rack 0.4.0 and both it and I have gotten much better since then.

Don't be surprised to find a MIDI-less one-instance or one-patch piece from me this month; the multitude of sequencing and modulation options available here can do just about anything your CPU can handle.

[RuediRena]

@RR I just copied all folders and the 8 files to a folder in my 64-bit c:\vst\64-bit\vcv\ folder.

Fired up Reaper and it worked ...

dB

Hmm, seems everybody else can fire it up on Reaper. Strange ... I really hope this issue resolves. Such a tempting thing to have VCV Rack in my DAW. I didn't know this wrapper existed.

[z.prime]

Such a tempting thing to have VCV Rack in my DAW. I didn't know this wrapper existed.

Keep in mind, it's a really old version of VCV. It would be great to get an official plugin version of VCV. I thought we were supposed to get that last year or so (but for $) but it hasn't materialized.

[doctorbob]

@RR have you re-scanned in Reaper Prefs? Note there's new options to the Scan button these days! Also, double check you have it in the right place and have the VST path correct.

dB

[Ranoka]

Make sure you have the VS runtimes (redistributions) installed, in case you don't. Should be in the zip, I think.
I had them already, thus it ran right away in MuLab.

I've followed the instructions to copy the Content of the VeeSeeVST archive into the VST path, and I copied the updated dlls to replace the old ones.

VeeSeeVST_BitwigError.png

When I try to use the plugins in Bitwig I get this error.
I have also tried scanning in FL Studio 20 and it doesn't show up.

I have installed the VC 2015-2019 redistributable from here, and restarted (Win10 64bit):
https://support.microsoft.com/en-us/top ... f26a218cc0

I'm not sure what to try next.

[ontrackp]

Thanks Richard and BJ for making so Mac Users can join the fun this month! How about commercial efx????

[Taron]

Sorry, Ranoka, I have no idea. I would assume that Bitwig might've some troubles with it?! ...not even a hickup in MuLab. There (and on Win7) it worked right away.

[RuediRena]

@RR have you re-scanned in Reaper Prefs? Note there's new options to the Scan button these days! Also, double check you have it in the right place and have the VST path correct.

Thanks, db, for writing once again.
I did all the above. Both dlls show in Reaper's new rescan dialogue as "plugins that failed to scan". So Reaper recognices them but can't read the files. Launching Reaper as admin doesn't help either. This might be the same error as Ranoka's with Bitwig.

[Aro]

So I downloaded the wrong folder. I'm a bit of a computard. It took like half an hour to download the zip. And I was like, 'this is ridiculous. do i have to assemble this myself?'. So I was about to give up. But then I thought about it for a minute.

This looks like a lot of fun. I've never seriously played with modular synths, but there are a lot of patches to learn from. So I think I'll give it a go.

[kvotchin]

@RR have you re-scanned in Reaper Prefs? Note there's new options to the Scan button these days! Also, double check you have it in the right place and have the VST path correct.

Thanks, db, for writing once again.
I did all the above. Both dlls show in Reaper's new rescan dialogue as "plugins that failed to scan". So Reaper recognices them but can't read the files. Launching Reaper as admin doesn't help either. This might be the same error as Ranoka's with Bitwig.

Precisely the same here.

[Aro]

Its not that I haven't tried or analyzed modular synthesis before. I just have trouble holding on to all the connections in my head to draw any valuable conclusions as to the logic of everything. I'm guessing my best bet is just to stick with the patches, and twist knobs from there.

I wish they had tutorial patches. Any suggestions as to how I could begin actually patching cable? How to make it graspable?

[MilksterX]

Double post

[MilksterX]

I installed the GitHub vst and updated dlls but was still getting crashes and bugs with many patches missing modules.

Then I discovered a way to use the latest standalone vcv rack & library and the old bridging dlls from v 0.6.2c.

The process of hooking these up is here as well as a way to sync the daw and the clock via clock pulse.

This is amazing compared to the GitHub vst.



Edit: Someone mentioned in the comments ableton has a m4l clock that can be used instead of the method for syncing suggested here. I've not tried that yet but his method should be applicable to most DAWs where you just sequence the pulse waves on an audio channel and use that audio to send to vcv's audio-8.

He also mentioned a bug with port 1 of the bridging dll so if you can't get the bridging dlls to work try using a different port.

[puresignal]

VCV Rack is acceptable, provided the modules used are freely available non-commercial.

Would it make sense to limit those using VCV Rack to the same modules as those available to the VST users? I don't think there is a way to add modules to the VST besides those included in the distribution (which apparently require code modification).

Also, the VST is monophonic, whereas VCV Rack now offers 16-voice polyphony, which would make a huge difference for efficiently tracking chords. Should VCV Rack users be excluded from using polyphonic cables?

https://vcvrack.com/manual/Polyphony