[announce] VeeSeeVST Rack VST2 plugin

[EvilDragon]

Yeah paid modules are probably off-limits.

Still, plenty of fun to be had for $0.

[lalo]

Yeah paid modules are probably off-limits.

Still, plenty of fun to be had for $0.

sure!

[Tj Shredder]

I hesitate to ask - would it be difficult to compile it for Mac? I do have all the dev tools, but zero experience to make a given source compile in xcode. Are the used libraries all cross platform...?

[perpetual3]

I hesitate to ask - would it be difficult to compile it for Mac? I do have all the dev tools, but zero experience to make a given source compile in xcode. Are the used libraries all cross platform...?

I would like to know this too.

[GaryG]

Nice. Worked ok first time in tried it (in Reaper) but then I lost audio when reloading the project, just says no device on the Audio module. I have trouble like this with the standalone too (losing the audio device) so maybe system specific...

But, whatever, thanks, yr efforts are much appreciated.

[bsp804]

Are the parameters visible to the host - for automation, link to controller, etc?

not yet but I think it's doable. I'll look into it tomorrow.

I hesitate to ask - would it be difficult to compile it for Mac? I do have all the dev tools, but zero experience to make a given source compile in xcode. Are the used libraries all cross platform...?

"difficult" is relative. It's much harder than a "hello, world" but much easier than building an X-Server for example.
If you don't have any experience with the dev tools better let someone else do the port.

I would like to know this too.

I'll upload the source code tomorrow (I'm done with coding for today!).

Regarding a Mac (or Linux) port in general: There already are some Linux/Mac specific codepaths in there but they are completely untested.
On the other hand, the source was originally meant to be compiled with GCC in a POSIX environment so it should be much easier to compile to for Mac than for Windows (I had to add a couple of WIN32 specific codepaths after moving from mingw64 to MSVC. On a Mac you'll be using the original versions of these codepaths.)

Nice. Worked ok first time in tried it (in Reaper) but then I lost audio when reloading the project, just says no device on the Audio module. I have trouble like this with the standalone too (losing the audio device) so maybe system specific...

I haven't seen this happen but if you have a patch file that reproduces the issue I could have a look (or better send it to the VCV Rack devs if it also happens in the original standalone app).



Last but not least: Here's a new version: vcvrack_0_6_1_vst2_bin_win64-30Jun2018.7z

Changelog:

Code: Select all

- add module AS.ADSR
- add module AS.AtNuVrTr
- add module AS.BPMCalc
- add module AS.BPMClock
- add module AS.BlankPanel4
- add module AS.BlankPanel6
- add module AS.BlankPanel8
- add module AS.BlankPanelSpecial
- add module AS.Cv2T
- add module AS.DelayPlusFx
- add module AS.DelayPlusStereoFx
- add module AS.Flow
- add module AS.KillGate
- add module AS.LaunchGate
- add module AS.Merge2.5
- add module AS.Mixer8ch
- add module AS.MonoVUmeter
- add module AS.Multiple2.5
- add module AS.PhaserFx
- add module AS.QuadVCA
- add module AS.ReverbFx
- add module AS.ReverbStereoFx
- add module AS.SEQ16
- add module AS.SawOsc
- add module AS.SignalDelay
- add module AS.SineOsc
- add module AS.Steps
- add module AS.SuperDriveFx
- add module AS.TremoloFx
- add module AS.TremoloStereoFx
- add module AS.TriLFO
- add module AS.TriggersMKI
- add module AS.TriggersMKII
- add module AS.VCA
- add module AS.WaveShaper
- add module AS.StereoVUmeter
- add module Befaco.ABC
- add module Befaco.DualAtenuverter
- add module Befaco.EvenVCO
- add module Befaco.Mixer
- add module Befaco.Rampage
- add module Befaco.SlewLimiter
- add module Befaco.SpringReverb
- add module ESeries.E340
- add module ErraticInstruments.MPEToCV
- add module ErraticInstruments.QuadMPEToCV
- add module HetrickCV.TwoToFour
- add module HetrickCV.AnalogToDigital
- add module HetrickCV.ASR
- add module HetrickCV.Bitshift
- add module HetrickCV.BlankPanel
- add module HetrickCV.Boolean3
- add module HetrickCV.Comparator
- add module HetrickCV.Contrast
- add module HetrickCV.Crackle
- add module HetrickCV.Delta
- add module HetrickCV.DigitalToAnalog
- add module HetrickCV.Dust
- add module HetrickCV.Exponent
- add module HetrickCV.FlipFlop
- add module HetrickCV.FlipPan
- add module HetrickCV.GateJunction
- add module HetrickCV.LogicCombine
- add module HetrickCV.RandomGates
- add module HetrickCV.Rotator
- add module HetrickCV.Scanner
- add module HetrickCV.Waveshape
- add module SonusModular.Addiction
- add module SonusModular.Bitter
- add module SonusModular.Bymidside
- add module SonusModular.Campione
- add module SonusModular.Chainsaw
- add module SonusModular.Ctrl
- add module SonusModular.Deathcrush
- add module SonusModular.Harmony
- add module SonusModular.Ladrone
- add module SonusModular.Luppolo
- add module SonusModular.Luppolo3
- add module SonusModular.Micromacro
- add module SonusModular.Multimulti
- add module SonusModular.Oktagon
- add module SonusModular.Osculum
- add module SonusModular.Paramath
- add module SonusModular.Piconoise
- add module SonusModular.Pusher
- add module SonusModular.Ringo
- add module SonusModular.Scramblase
- add module SonusModular.Twoff
- add module SonusModular.Yabp
- add module Valley.Topograph
- add module Valley.UGraph
- add module Valley.Dexter
- add module Valley.Plateau

Thanks to EvilDragon and SLiC (on GS) for the module suggestions.

Most important of all, big thanks to the creator(s) of VCV Rack and all the people who have contributed (open source) modules to it !

[caecos]

Crash in Cubase...I'll try again...

[starflakeprj]

What a shocker, crash in Cubase. Are there any plugins working at all in Cubase? I mean, everyday I see people mentioning plugins crashing in Cubase, but reports say there are no problems in other DAW's (well, a few problems in FL Studio every now and then).

[experimental.crow]

a walk-through on a typical win10 installation would be useful ...

[bsp804]

Unpack the 7zip archive and add the unpacked folder to your DAW's plugin path.
Alternatively, move the folder to an existing plugin directory, e.g. "c:\Program Files\Steinberg\VstPlugins\".

[thecontrolcentre]

Thanks for your work on this bsp804

[chk071]

What a shocker, crash in Cubase. Are there any plugins working at all in Cubase? I mean, everyday I see people mentioning plugins crashing in Cubase, but reports say there are no problems in other DAW's (well, a few problems in FL Studio every now and then).

None of my 200 plugins ever caused Cubase to crash.

[experimental.crow]

Unpack the 7zip archive and add the unpacked folder to your DAW's plugin path.
Alternatively, move the folder to an existing plugin directory, e.g. "c:\Program Files\Steinberg\VstPlugins\".

a double thank you , to you ...

[starflakeprj]

What a shocker, crash in Cubase. Are there any plugins working at all in Cubase? I mean, everyday I see people mentioning plugins crashing in Cubase, but reports say there are no problems in other DAW's (well, a few problems in FL Studio every now and then).

None of my 200 plugins ever caused Cubase to crash.

So mostly user related then? I'm not surprised to be honest.

[chk071]

Could be plugin related as well. After all, it's mostly the plugins which crash DAW's, not vice versa, isn't it?

OK, now that i think about it, there was a plugin which crashed Cubase. Waldorf Largo. It crashed any DAW though, if you installed it with normal user rights, and executed your DAW with normal user rights as well, because the developers missed to install some files in the installing users Documents folder. Apart from that, i really can't recall one plugin crashing Cubase. I recall a few getting blacklisted though, for no apparent reason.