[announce] VeeSeeVST Rack VST2 plugin

[MFXxx]

 
Any chance of a 32-bit build, please?

(no clue how to do that myself)

Would jbridge work bridgin from 64 bit to 32bit as a solution?

[bsp804]

 Any chance of a 32-bit build, please?

geez, who on earth is still using 32 bit these days ?
I've included an x86/32bit version in the new release but please, if it's not working, I am not going to debug this. I loaded it in vsthostx86 and was able to see the UI but did not try anything beyond that.

Been testing this in buzz tracker, was having some cpu issues but your latest build seems to have fixed these, including the befaco Spring Reverb module. I can't get any midi messages (notes or cc's) from polac's vst loader to register in VeeSeeVST yet, but will keep trying.

hah, buzz tracker, I remember that one. good to know the denormals fix is working there, too. re: the MIDI events: you should probably ask polac then. should be simple to fix.


Here's a new release:

Code: Select all

- add module DHE-Modules.BoosterStage
- add module DHE-Modules.Cubic
- add module DHE-Modules.Hostage
- add module DHE-Modules.Stage
- add module DHE-Modules.Swave
- add module DHE-Modules.Upstage
- add module mscHack.MasterClockx4
- add module mscHack.Seq_3x16x16
- add module mscHack.SEQ_6x32x16
- add module mscHack.Seq_Triad2
- add module mscHack.SEQ_Envelope_8
- add module mscHack.Maude_221
- add module mscHack.ARP700
- add module mscHack.SynthDrums
- add module mscHack.XFade
- add module mscHack.Mix_1x4_Stereo
- add module mscHack.Mix_2x4_Stereo
- add module mscHack.Mix_4x4_Stereo
- add module mscHack.Mix_24_4_4
- add module mscHack.StepDelay
- add module mscHack.PingPong
- add module mscHack.Osc_3Ch
- add module mscHack.Compressor
- add x86/32bit build (you are completely on your own this this -- please upgrade to x64!)
- fix: load "settings.json" when plugin is initialized
   (note: the windowSize/windowPos and sampleRate are ignored)
- change: "allowCursorLock" is now enabled by default

veeseevstrack_0_6_1_win64_bin-08Jul2018.7z

• The settings.json file works now (will be loaded but never saved).
• The windowSize / windowPos settings had to be disabled since they led to some weird issues (the window became non-resizable until it was closed and opened again).
• The sampleRate setting is also ignored (the plugin build always uses the host sample-rate).
• While building some more patches, I noticed that not having the "CursorLock" feature was quite annoying. There were some issues with that in early builds (with mingw64) but apparently they've disappeared in the newer MSVC builds.

[lalo]

Thanks for the continuing work!
1. I wonder how VST parameter works. It seems to modulate a very little range. Maybe is interpreted by VCV as a 0-1 volt range?

2. I wonder if a VST3 version is planned.

3. GUI controls seems not to respond to VST parameter modulation

thanks and best!

[bsp804]

1. I wonder how VST parameter works. It seems to modulate a very little range. Maybe is interpreted by VCV as a 0-1 volt range?

2. I wonder if a VST3 version is planned.

3. GUI controls seems not to respond to VST parameter modulation

If you go back a few pages in this thread, you'll find some info on how the VST parameters are currently implemented.

The gist of it is

• Module parameters in the rack engine do not have ranges, they are arbitrary floats
• VST parameters have to be normalized to the 0..1 range
• The current "hack" supports a -1..1 modulation range that works with many parameters (but not all)

I've seen that module _widgets_ contain the missing parameter range info (see QuantityWidget class in widgets.hpp if you can read C++).

Now someone might think that when a VST parameter is changed by the host/sequencer and needs to be "de-normalized" to the actual value range, all that needs to be done is to traverse the widget tree in order to retrieve the missing min/max values (which is quite 'ugly' to begin with).
First problem with that is that you will probably have to (further) synchronize the access to the widgets (in the UI thread) with the audio thread and if you do that, you'll end up with something called "priority inversion" where the high priority audio thread suddenly needs to wait for the low priority UI thread, which can cause pops'n'crackles.
(if you don't synchronize, you'll end up with crashes when the audio thread tries to access a widget that the UI thread currently deletes / has just deleted).

You might get away with synchronizing only the code paths where a parameter is added and a widget is removed, though.

There may be other obstacles I am currently not aware of (for example, will this work with modules that have different modes which change the meaning of certain knobs, e.g. the Clouds "Texture Synthesizer" ?).

Until the editor window issues have been resolved (which does not look so easy, see my earlier post(s)), there won't be proper VST parameter support anyway since many hosts expect their own editor window to be active (e.g. Reason) or it won't be possible to "learn" new parameters.

So, not sure if it's really worth the effort (but yeah, automating things like envelope amounts would sure be fun).
I may take a second look at this but if this involves any larger changes then it will stay the way it is right now.

p.s.: and no, they will be no VST3 version, unless someone else writes one (I have no use for it but it should not be too hard now)

[bsp804]

okay, here's an update (the entire changelog entry for today):

Code: Select all

** July 8th, 2018
- add module DHE-Modules.BoosterStage
- add module DHE-Modules.Cubic
- add module DHE-Modules.Hostage
- add module DHE-Modules.Stage
- add module DHE-Modules.Swave
- add module DHE-Modules.Upstage
- add module mscHack.MasterClockx4
- add module mscHack.Seq_3x16x16
- add module mscHack.SEQ_6x32x16
- add module mscHack.Seq_Triad2
- add module mscHack.SEQ_Envelope_8
- add module mscHack.Maude_221
- add module mscHack.ARP700
- add module mscHack.SynthDrums
- add module mscHack.XFade
- add module mscHack.Mix_1x4_Stereo
- add module mscHack.Mix_2x4_Stereo
- add module mscHack.Mix_4x4_Stereo
- add module mscHack.Mix_24_4_4
- add module mscHack.StepDelay
- add module mscHack.PingPong
- add module mscHack.Osc_3Ch
- add module mscHack.Compressor
- add x86/32bit build (you are completely on your own this this -- please upgrade to x64!)
- fix: load "settings.json" when plugin is initialized
   (note: the windowSize/windowPos and sampleRate are ignored)
- change: "allowCursorLock" is now enabled by default
- update VST parameter handling (now uses UI widget min/max info for VST parameter range translation)

The VST parameters are now translated between the engine params by using the UI widget min/max info.
Seems to be working, knobs are moving, too.

here's a short demo video:
https://vimeo.com/278941543
(basically my init patch, nothing fancy audio-wise)

veeseevstrack_0_6_1_win64_bin-08Jul2018b.7z

[Koshdukai]

I keep looking for the ThumbsUp button ~


PS: btw, has anyone using the veeseevstrack_instr.dll in Reason noticed a glitch where it's listed and considered as a rack Instrument but the proxy GUI shows up with a Off/On/Bypass (Enabled: 0..2) widget (like if it was a filter) and the functional Pitch/Mod wheels are gone but their place is still showing up?

PS2: oh ok, I updated the files while still on Reason, so it ended up trying to load the new version. Once I restarted Reason, it no longer recognizes this new _instr DLL as a valid VSTi

[newluc]

hi
cubase recognize this version as effect, not instrument (9.5 on Win 10)

[lalo]

Yep. Confirmed that the VSTi version is no more. No problem on Reaper wich is more flexible and can send MIDI message to VST fx too. But problem arises in hosts like Ableton Live.

[bsp804]

Changelog:

Code: Select all

- add module Alikins.IdleSwitch
- add module Alikins.MomentaryOnButtons
- add module Alikins.BigMuteButton
- add module Alikins.ColorPanel
- add module Alikins.GateLength
- add module Alikins.SpecificValue
- add module BaconMusic.Glissinator
- add module BaconMusic.PolyGnome
- add module BaconMusic.QuantEyes
- add module BaconMusic.SampleDelay
- add module BaconMusic.SortaChorus
- add module BaconMusic.ChipNoise
- add module BaconMusic.ChipWaves
- add module BaconMusic.ChipYourWave
- add module BaconMusic.KarplusStrongPoly
- add module BaconMusic.ALingADing
- add module BaconMusic.Bitulator

The instrument issue should also be resolved for good now (a bug in the build system).

Even though I mentioned it several times already:
**WARNING: DON'T TRY TO USE THE INSTRUMENT AND EFFECT PLUGINS IN THE SAME PROJECT OR YOUR DAW _WILL_ CRASH.**

veeseevstrack_0_6_1_win64_bin-09Jul2018.7z

[lalo]

Changelog:

Code: Select all

- add module Alikins.IdleSwitch
- add module Alikins.MomentaryOnButtons
- add module Alikins.BigMuteButton
- add module Alikins.ColorPanel
- add module Alikins.GateLength
- add module Alikins.SpecificValue
- add module BaconMusic.Glissinator
- add module BaconMusic.PolyGnome
- add module BaconMusic.QuantEyes
- add module BaconMusic.SampleDelay
- add module BaconMusic.SortaChorus
- add module BaconMusic.ChipNoise
- add module BaconMusic.ChipWaves
- add module BaconMusic.ChipYourWave
- add module BaconMusic.KarplusStrongPoly
- add module BaconMusic.ALingADing
- add module BaconMusic.Bitulator

The instrument issue should also be resolved for good now (a bug in the build system).

Even though I mentioned it several times already:
**WARNING: DON'T TRY TO USE THE INSTRUMENT AND EFFECT PLUGINS IN THE SAME PROJECT OR YOUR DAW _WILL_ CRASH.**

veeseevstrack_0_6_1_win64_bin-09Jul2018.7z

Thanks! Luckily enough in Reaper i can use the FX version as an Instrument!

PS. Should be possible to have a 16 in/out version?

[bsp804]

PS. Should be possible to have a 16 in/out version?

The Core.Audio module supports "only" 8 ins and outs.
Can't you just use another plugin instance and split your patch ?

[lalo]

PS. Should be possible to have a 16 in/out version?

The Core.Audio module supports "only" 8 ins and outs.
Can't you just use another plugin instance and split your patch ?

sure. thanks.

[ZeePok]

 
The VeeSeeVSTRack Legacy-32 Version overall is running fine on most of my hosts/DAW's (tried VSTHost (no midi), Mulab, Reaper, Bidule (crashes b/c the OpenGL thingy), Cantabile 2 and Ableton Live 9 Intro. Rest of them are all running fine )

Some modules crash, but most of them are running fine

Overall I'm quit happy

Thank you very very much for making this fine software available for me.

(Very old computer. Unable to upgrade due to increasing medical costs due to serious health issues . Also no strenght for a new reinstall to 64-bit ..)

So thanks again once more!

[Clearscreen]

Thanks again for this bsp804 - it's very addictive!
Not sure if I've noticed an issue, I can't get midi notes directly into VeeSeeVST - anyone out there able to confirm this, or let me know what I'm stuffing up?
CLK/STRT/STOP/CONT all seem to work ok, and bitwig usually passes all midi to anything. I've worked around it with a bitwig keytrack modulator, but working out which control to modulate can be a trick - after playing around adding and deleting modules for a while I found I had about 500 controls!

I tested it with the instr version and it received midi perfectly, but it doesn't work right as an effect, passing the unaffected audio through all the time - again, if anyone can confirm this it'd be appreciated.

Either way, this is great work!! Thanks again bsp804!!!

[Edit - just tried the instr version again and it seems fine. DOH!! I'll use that in bitwig in future...]

[xtreme sounds]

Hi I tried selecting favorites form VCV Rack main and then copying the settings.json file over to the VST version. It did not save favorites. so I guess this feature doesnt work.