[announce] VeeSeeVST Rack VST plugin

[bsp]

Hi everyone,

I have ported VCV Rack 0.6.1 to the VST2 format.

Here's a video of it:

and here are the binaries for x64 Windows: vcvrack_0_6_1_vst2_bin_win64-29Jun2018.7z (removed).
EDIT: everything's now on GitHub (including the binaries), see here.

The plugin has been tested in my own host ("Eureka"), in Reaper, and in Reason 10.

The binary includes the "Fundamental", and the "AudibleInstruments" modules, which are ports of the Mutable Instruments Eurorack modules Braids, Elements, Tides, Clouds, Warps, Rings, Links, Kinks, Shades, Branches, Blinds, Veils, and Frames.

~bsp

[Despondo]

Will there be a Mac version of this as VST?

[bsp]

Will there be a Mac version of this as VST?

I can't do it myself since I don't have a Mac but if someone volunteers to compile one, then yes.

[Loque]

I have ported VCV Rack 0.6.1 to the VST2 format.

Dude...you make me horny...Try to collaborate with Andrew somehow. If it does not work, i will take your fork!

[jimmyklane]

Hi everyone,

I have ported VCV Rack 0.6.1 to the VST2 format.

Here's a video of it:

and here are the binaries for x64 Windows: vcvrack_0_6_1_vst2_bin_win64-29Jun2018.7z.

The plugin has been tested in my own host ("Eureka"), in Reaper, and in Reason 10.

The binary includes the "Fundamental", and the "AudibleInstruments" modules, which are ports of the Mutable Instruments Eurorack modules Braids, Elements, Tides, Clouds, Warps, Rings, Links, Kinks, Shades, Branches, Blinds, Veils, and Frames.

~bsp

Thank you so much for releasing this to the world! I’m super excited to download this and put it into Reason!!!

[Loque]

Well, it does not work on my side. Can help somehow to fix bugs?

[Ahornberg]

It works! Thank you!

I'm on Windows 8.1 and I scaled the screen display to 150% because my 4k monitor has a very high resolution.
The moment I put the VCV VST into the Reason rack, the resolution of Reason itself changes to 100% and I can barely read anything in the Reason window.

But sound is fine and DSP load is low!

One thing that doesn't work: When I save a Reason song with a VCV VST inside with some modules set up and then I close Reason and open the Reason song again, the VCV rack is empty

[kuhliloach]

game changer! As stated above if you save a Reason song that uses this the rack will be empty when you load it later. I'm curious -- how can we get our installed add-ons to appear? Since I made an account with VCV Rack I downloaded all the freebies, nearly 100 of them! It would be nice to see these appear in Reason.

[Re8et]

0.o
We should put the binaries in the usual vst2 folder or rewrite the original vcv files and then point reason there??
Thank you.

[mataya]

Works in Reason 10 here. I guess you have to save you patch first and load it trough vcv after you open a song again.

But it woks fine. I've routed the expanse into clouds and it's a dream come true.


tx man

M

[kuhliloach]

download link not working?

[bsp]

Well, it does not work on my side. Can help somehow to fix bugs?

please try the new version. if that fails, too, download "Dependency Walker", load the plugin DLL and check if there are any missing dependencies (but keep in my mind that the output is not exactly correct, it will show a lot of missing DLLs / false positives).

I'm on Windows 8.1 and I scaled the screen display to 150% because my 4k monitor has a very high resolution.
The moment I put the VCV VST into the Reason rack, the resolution of Reason itself changes to 100% and I can barely read anything in the Reason window.

hmm, that's probably not related to VCV itself but rather to the libraries it uses ("glfw" is used for creating the window).
I have no idea what could be causing this but I'll ask around (and take a closer look at glfw myself).

But sound is fine and DSP load is low!

that's a funny thing to say. it's quite a CPU hog, actually (the internal processing "buffer" size is 1 sample!)

One thing that doesn't work: When I save a Reason song with a VCV VST inside with some modules set up and then I close Reason and open the Reason song again, the VCV rack is empty

"program chunks" are implemented in the newer releases (see below)

how can we get our installed add-ons to appear? Since I made an account with VCV Rack I downloaded all the freebies, nearly 100 of them! It would be nice to see these appear in Reason.

The plugin does not support dynamically loaded VCV plugins (due to technical limitations of Windows and b/c of VCV Rack's architecture).
However, I've added a huge number of statically linked add-ons (the plugin comes with 321 modules to be precise).

We should put the binaries in the usual vst2 folder or rewrite the original vcv files and then point reason there??

Put the "vst2_bin/" folder in your usual plugin directory or add it to Reason's VST search path.

But it woks fine. I've routed the expanse into clouds and it's a dream come true.

here's the latest version: veeseevstrack_0_6_1_vst2_bin_win64-01Jul2018.7z

The VCV Rack author asked me to change the name and remove the logo(s), which I did.
(that's also the reason why the old download link does not work anymore)

Here's the complete module list:

Code: Select all

    - AS.ADSR
     - AS.AtNuVrTr
     - AS.BPMCalc
     - AS.BPMClock
     - AS.BlankPanel4
     - AS.BlankPanel6
     - AS.BlankPanel8
     - AS.BlankPanelSpecial
     - AS.Cv2T
     - AS.DelayPlusFx
     - AS.DelayPlusStereoFx
     - AS.Flow
     - AS.KillGate
     - AS.LaunchGate
     - AS.Merge2.5
     - AS.Mixer8ch
     - AS.MonoVUmeter
     - AS.Multiple2.5
     - AS.PhaserFx
     - AS.QuadVCA
     - AS.ReverbFx
     - AS.ReverbStereoFx
     - AS.SEQ16
     - AS.SawOsc
     - AS.SignalDelay
     - AS.SineOsc
     - AS.Steps
     - AS.SuperDriveFx
     - AS.TremoloFx
     - AS.TremoloStereoFx
     - AS.TriLFO
     - AS.TriggersMKI
     - AS.TriggersMKII
     - AS.VCA
     - AS.WaveShaper
     - AS.StereoVUmeter
     - AudibleInstruments.Braids
     - AudibleInstruments.Elements
     - AudibleInstruments.Tides
     - AudibleInstruments.Clouds
     - AudibleInstruments.Warps
     - AudibleInstruments.Rings
     - AudibleInstruments.Links
     - AudibleInstruments.Kinks
     - AudibleInstruments.Shades
     - AudibleInstruments.Branches
     - AudibleInstruments.Blinds
     - AudibleInstruments.Veils
     - AudibleInstruments.Frames
     - Befaco.ABC
     - Befaco.DualAtenuverter
     - Befaco.EvenVCO
     - Befaco.Mixer
     - Befaco.Rampage
     - Befaco.SlewLimiter
     - Befaco.SpringReverb
     - Bogaudio.VCO
     - Bogaudio.XCO
     - Bogaudio.Additator
     - Bogaudio.FMOp
     - Bogaudio.LFO
     - Bogaudio.EightFO
     - Bogaudio.DADSRH
     - Bogaudio.DADSRHPlus
     - Bogaudio.DGate
     - Bogaudio.Shaper
     - Bogaudio.ShaperPlus
     - Bogaudio.ADSR
     - Bogaudio.Follow
     - Bogaudio.Mix4
     - Bogaudio.Mix8
     - Bogaudio.VCM
     - Bogaudio.Pan
     - Bogaudio.XFade
     - Bogaudio.VCA
     - Bogaudio.VCAmp
     - Bogaudio.Analyzer
     - Bogaudio.VU
     - Bogaudio.Detune
     - Bogaudio.Stack
     - Bogaudio.Reftone
     - Bogaudio.Bool
     - Bogaudio.CVD
     - Bogaudio.FlipFlop
     - Bogaudio.Manual
     - Bogaudio.Mult
     - Bogaudio.Noise
     - Bogaudio.Offset
     - Bogaudio.SampleHold
     - Bogaudio.Sums
     - Bogaudio.Switch
     - Bogaudio.Lag
     - Bogaudio.RM
     - Bogaudio.Test
     - Bogaudio.Test2
     - Bogaudio.ThreeHP
     - Bogaudio.SixHP
     - Bogaudio.EightHP
     - Bogaudio.TenHP
     - Bogaudio.TwelveHP
     - Bogaudio.ThirteenHP
     - Bogaudio.FifteenHP
     - Bogaudio.EighteenHP
     - Bogaudio.TwentyHP
     - Bogaudio.TwentyTwoHP
     - Bogaudio.TwentyFiveHP
     - Bogaudio.ThirtyHP
     - cf.trSEQ
     - cf.LEDSEQ
     - cf.L3DS3Q
     - cf.SLIDERSEQ
     - cf.PLAYER
     - cf.STEPS
     - cf.METRO
     - cf.EACH
     - cf.FOUR
     - cf.PEAK
     - cf.MONO
     - cf.STEREO
     - cf.MASTER
     - cf.SUB
     - cf.CUBE
     - cf.PATCH
     - cf.LEDS
     - cf.DAVE
     - ESeries.E340
     - ErraticInstruments.MPEToCV
     - ErraticInstruments.QuadMPEToCV
     - Fundamentals.8vert
     - Fundamentals.ADSR
     - Fundamentals.Delay
     - Fundamentals.LFO
     - Fundamentals.LFO2
     - Fundamentals.Mutes
     - Fundamentals.SEQ3
     - Fundamentals.SequentialSwitch1
     - Fundamentals.SequentialSwitch2
     - Fundamentals.Scope
     - Fundamentals.Unity
     - Fundamentals.VCA
     - Fundamentals.VCF
     - Fundamentals.VCMixer
     - Fundamentals.VCO
     - Fundamentals.VCO2
     - HetrickCV.TwoToFour
     - HetrickCV.AnalogToDigital
     - HetrickCV.ASR
     - HetrickCV.Bitshift
     - HetrickCV.BlankPanel
     - HetrickCV.Boolean3
     - HetrickCV.Comparator
     - HetrickCV.Contrast
     - HetrickCV.Crackle
     - HetrickCV.Delta
     - HetrickCV.DigitalToAnalog
     - HetrickCV.Dust
     - HetrickCV.Exponent
     - HetrickCV.FlipFlop
     - HetrickCV.FlipPan
     - HetrickCV.GateJunction
     - HetrickCV.LogicCombine
     - HetrickCV.RandomGates
     - HetrickCV.Rotator
     - HetrickCV.Scanner
     - HetrickCV.Waveshape
     - Koralfx.Beatovnik
     - Koralfx.Mixovnik
     - Koralfx.Nullovnik4
     - Koralfx.Nullovnik6
     - Koralfx.Presetovnik
     - Koralfx.Quantovnik
     - Koralfx.Scorovnik
     - LindenbergResearch.SimpleFilter
     - LindenbergResearch.MS20Filter
     - LindenbergResearch.AlmaFilter
     - LindenbergResearch.ReShaper
     - LindenbergResearch.BlankPanel
     - LindenbergResearch.BlankPanelM1
     - Qwelk.Automaton
     - Qwelk.Byte
     - Qwelk.Chaos
     - Qwelk.Column
     - Qwelk.Gate
     - Qwelk.Or
     - Qwelk.Not
     - Qwelk.Xor
     - Qwelk.Mix
     - Qwelk.News
     - Qwelk.Scaler
     - Qwelk.Wrap
     - Qwelk.XFade
     - SonusModular.Addiction
     - SonusModular.Bitter
     - SonusModular.Bymidside
     - SonusModular.Campione
     - SonusModular.Chainsaw
     - SonusModular.Ctrl
     - SonusModular.Deathcrush
     - SonusModular.Harmony
     - SonusModular.Ladrone
     - SonusModular.Luppolo
     - SonusModular.Luppolo3
     - SonusModular.Micromacro
     - SonusModular.Multimulti
     - SonusModular.Oktagon
     - SonusModular.Osculum
     - SonusModular.Paramath
     - SonusModular.Piconoise
     - SonusModular.Pusher
     - SonusModular.Ringo
     - SonusModular.Scramblase
     - SonusModular.Twoff
     - SonusModular.Yabp
     - SubmarineFree.AG106
     - SubmarineFree.BB120
     - SubmarineFree.FF110
     - SubmarineFree.FF120
     - SubmarineFree.FF212
     - SubmarineFree.LA108
     - SubmarineFree.LD106
     - SubmarineFree.NG112
     - SubmarineFree.OG106
     - SubmarineFree.PG112
     - SubmarineFree.PO101
     - SubmarineFree.PO102
     - SubmarineFree.PO204
     - SubmarineFree.WK101
     - SubmarineFree.WK205
     - SubmarineFree.XF101
     - SubmarineFree.XF102
     - SubmarineFree.XF104
     - SubmarineFree.XF201
     - SubmarineFree.XF202
     - SubmarineFree.XG106
     - SubmarineFree.BP101
     - SubmarineFree.BP102
     - SubmarineFree.BP104
     - SubmarineFree.BP108
     - SubmarineFree.BP110
     - SubmarineFree.BP112
     - SubmarineFree.BP116
     - SubmarineFree.BP120
     - SubmarineFree.BP124
     - SubmarineFree.BP132
     - Valley.Topograph
     - Valley.UGraph
     - Valley.Dexter
     - Valley.Plateau

last but not least, the plugin now supports VST parameter automation.

The bad news is that it does not work in Reason.
Reason shows no parameters at all. I think someone here once mentioned that there is a 128 parameter limit.
Only Propellerhead can fix this.

here's a short video that demos the VST parameters in my own host (Reaper recognizes the params, too):

I'll try to keep you posted but you may also want to read the thread at KVRaudio.

[bsp]

I'm on Windows 8.1 and I scaled the screen display to 150% because my 4k monitor has a very high resolution.
The moment I put the VCV VST into the Reason rack, the resolution of Reason itself changes to 100% and I can barely read anything in the Reason window.

could you please try this test version ?

[Ahornberg]

I'm on Windows 8.1 and I scaled the screen display to 150% because my 4k monitor has a very high resolution.
The moment I put the VCV VST into the Reason rack, the resolution of Reason itself changes to 100% and I can barely read anything in the Reason window.

could you please try this test version ?

I did. It's the same weird screen resolution change in the Reason window.

[bsp]

I did. It's the same weird screen resolution change in the Reason window.

"hmm."
I just changed the Windows display scaling to 150% and that resolution change does not happen here (tested with the original release) (I'm on Windows 10 with an NVidia graphics card).
Could you please check if there is an updated driver for yours ?

(on a side note: I'm currently playing with the Dexter (FM) module. It's really really good!!)

[Ahornberg]

I did. It's the same weird screen resolution change in the Reason window.

"hmm."
I just changed the Windows display scaling to 150% and that resolution change does not happen here (tested with the original release) (I'm on Windows 10 with an NVidia graphics card).
Could you please check if there is an updated driver for yours ?

(on a side note: I'm currently playing with the Dexter (FM) module. It's really really good!!)

I think it's a Windows 8 specific behaviour. It happens in Reason and in Live but not in Bitwig.

Comparing your VST solution with thw VCV Bridge there's is a measurabel improvement in DSP performance.

[bsp]

I think it's a Windows 8 specific behaviour. It happens in Reason and in Live but not in Bitwig.

very strange. IIRC you have forked the VCV Rack repo yourself so it's probably safe to assume that you are a dev. You could have a look at the VeeSeeVSTRack repo (see below), maybe you can find a solution for this issue yourself (the glfw library source is located in the dep/dep.7z archive).

Comparing your VST solution with thw VCV Bridge there's is a measurabel improvement in DSP performance.

That's very interesting. The VST binary is built with MSVC, while the standalone app is built with MINGW64 (GCC).
I'm quite sure that it has never been built with MSVC before since there were a lot of issues I had to fix.
Maybe the generated code is better, or the whole-program optimization (which is not possible with plugin DLLs) has an effect on this.


Here's the link to the GitHub repo (see vst2_bin/ for latest binaries).

It won't compile for MacOSX out-of-the-box but it should not be very difficult either.

[Ahornberg]

I think it's a Windows 8 specific behaviour. It happens in Reason and in Live but not in Bitwig.

very strange. IIRC you have forked the VCV Rack repo yourself so it's probably safe to assume that you are a dev. You could have a look at the VeeSeeVSTRack repo (see below), maybe you can find a solution for this issue yourself (the glfw library source is located in the dep/dep.7z archive).

Yes, I made a module for VCV 0.5 and I think I should take a look at the source.

Comparing your VST solution with thw VCV Bridge there's is a measurabel improvement in DSP performance.

That's very interesting. The VST binary is built with MSVC, while the standalone app is built with MINGW64 (GCC).
I'm quite sure that it has never been built with MSVC before since there were a lot of issues I had to fix.
Maybe the generated code is better, or the whole-program optimization (which is not possible with plugin DLLs) has an effect on this.


Here's the link to the GitHub repo (see vst2_bin/ for latest binaries).

It won't compile for MacOSX out-of-the-box but it should not be very difficult either.

My assumtion is, when VCV is running over VST bridge there's an extra overhead in process-to-process communication.

[johnnyhagopian]

Hi,Do you know of anyone who wants to sell their Reason 8.1 License?
I'm working on Pro Tools 10 HD and I need the ReWire.
Regards
John

[bsp]

My assumtion is, when VCV is running over VST bridge there's an extra overhead in process-to-process communication.

ah, of course. when you mentioned DSP performance I thought of CPU performance.
since the DSP bars show the ellapsed time, not the CPU usage, a plugin that will stall and wait for network packets will most certainly increase the "DSP load".
(makes me wonder btw why the bridge plugin even has to wait, and why they used networking instead of zero-copy shared memory. plus there should be a ringbuffer that, when large enough, ensures that the plugin never has to wait! this definitely explains why people were complaining about crackling sound..)

Anyways, I came here to say that you were absolutely right, the plugin's rack state load+save feature was definitely broken in Reason (and most other hosts).
The fix was very easy, though (support bank chunks, not only program chunks).

Here's the update.