[announce] VeeSeeVST Rack VST2 plugin

[bsp804]

I tried and it didnt work

works here, I just tried it (in Reason).

[Totolitoto]

Last version recognised as an effect inside FL, previous versions were ok though...

you have to rename "veeseevstrack_instr.dll__" to "veeseevstrack_instr.dll" if you really want to use the instrument version.
just keep in mind that only one of them (effect or instrument) can be used at the same time.

Nope this trick worked with previous versions but not with the last one.

[bsp804]

Nope this trick worked with previous versions but not with the last one.

I just unpacked veeseevstrack_0_6_1_win64_bin-06Jul2018.7z, pointed Reason to the extracted directory, renamed the "instr" DLL, instantiated the instrument, and it worked as expected.

Same thing in Reaper.

Besides, are you really sure that FLStudio can't send note events to effect plugins ? (that would have been a serious oversight on behalf of FLS!)

[Totolitoto]

Nope this trick worked with previous versions but not with the last one.

I just unpacked veeseevstrack_0_6_1_win64_bin-06Jul2018.7z, pointed Reason to the extracted directory, renamed the "instr" DLL, instantiated the instrument, and it worked as expected.

Same thing in Reaper.

Besides, are you really sure that FLStudio can't send note events to effect plugins ? (that would have been a serious oversight on behalf of FLS!)

Thanks, this one is working indeed!

Of course you can send midi to an effect inside FL :p

[xtreme sounds]

Nope this trick worked with previous versions but not with the last one.

I just unpacked veeseevstrack_0_6_1_win64_bin-06Jul2018.7z, pointed Reason to the extracted directory, renamed the "instr" DLL, instantiated the instrument, and it worked as expected.

Same thing in Reaper.

Besides, are you really sure that FLStudio can't send note events to effect plugins ? (that would have been a serious oversight on behalf of FLS!)

Thanks, this one is working indeed!

Of course you can send midi to an effect inside FL :p

HI can you please tell me what you use in FL studio to send midi to an effect track? is it the Midi out plugin? Or some other way? All that is missing for me is to use my keyboard to trigger notes. help!!! otherwise this thing is so awesome. One more thing I cant figure out is how to sync the vcv clocks with my DAW. maybe that was fixed in the more recent file which I havent downloaded. One more question is how to I preserve my favorites and stuff but use the newer file download?

I hope the creator of VCV rack works with this project. I think the biggest advantage is all the modules come installed and I dont have to install another software to use this.

[bsp804]

I cant figure out is how to sync the vcv clocks with my DAW. maybe that was fixed in the more recent file which I havent downloaded.

yes the clock feature was added in the previous release.

One more question is how to I preserve my favorites and stuff but use the newer file download?

The settings (which contain the favourite list) are never saved by the VST. You can use VCV Rack to create your favourites, then copy the "settings.json" file to the VeeSeeVSTRack folder.

I hope the creator of VCV rack works with this project. I think the biggest advantage is all the modules come installed and I dont have to install another software to use this.

This is an independent fork that is not associated with VCV Rack. A "proper" version of the VST would require an at least partial redesign of the engine and its UI framework. What you call an advantage is actually just a necessary side-effect. It would have been a lot easier if the modules could be loaded dynamically (i.e. as plugin DLLs).




Changelog:

Code: Select all

** July 7th, 2018
- add module Bidoo.DTROY
- add module Bidoo.BORDL
- add module Bidoo.MU
- add module Bidoo.TOCANTE
- add module Bidoo.CHUTE
- add module Bidoo.LATE
- add module Bidoo.LOURDE
- add module Bidoo.ACNE
- add module Bidoo.DUKE
- add module Bidoo.MOIRE
- add module Bidoo.FORK
- add module Bidoo.TIARE
- add module Bidoo.CLACOS
- add module Bidoo.ANTN
- add module Bidoo.LIMBO
- add module Bidoo.PERCO
- add module Bidoo.BAR
- add module Bidoo.ZINC
- add module Bidoo.VOID
- add module Bidoo.SIGMA
- add module LOGinstruments.constant
- add module LOGinstruments.constant2
- add module LOGinstruments.Speck
- add module LOGinstruments.Britix
- add module LOGinstruments.Compa
- add module LOGinstruments.LessMess
- add module LOGinstruments.Velvet
- add module LOGinstruments.Crystal
- add module modular80.Logistiker
- add module mtsch_plugins.Sum
- add module mtsch_plugins.Rationals
- add module mtsch_plugins.TriggerPanic
- add module NauModular.Tension
- add module NauModular.Function
- add module NauModular.Perlin
- add module NauModular.S_h_it
- add module NauModular.BitHammer
- add module NauModular.Osc
- add module Southpole-parasites.Annuli
- add module Southpole-parasites.Splash

veeseevstrack_0_6_1_win64_bin-07Jul2018.7z

I tried porting the (P)arableInstruments modules (which contain alternative versions of e.g. Mutable Instruments' Clouds) but the resulting binary crashed when the module was instantiated.
The Southpole-parasites version of it did not work either.

Some of the Bidoo modules are missing (OUAIVE and CANARD use GPL sources, DFUZE clashes with the freeverb symbols already defined in the Reverb and ReverbStereo modules by AS. By the way: you cannot mix BSD and GPL code, then use the BSD license for the resulting work -- it has to be GPL!)

This VST2 plugin now comes with 352 modules. That's quite a collection !

[xtreme sounds]

Very cool. What more does anyone need here? Am I able to remove modules I dont wish to use by deleting certain files or is it built into the dll?

[mystran]

Nope this trick worked with previous versions but not with the last one.

I just unpacked veeseevstrack_0_6_1_win64_bin-06Jul2018.7z, pointed Reason to the extracted directory, renamed the "instr" DLL, instantiated the instrument, and it worked as expected.

Same thing in Reaper.

Besides, are you really sure that FLStudio can't send note events to effect plugins ?

Create a "MIDI out" device and pick some random output port number (preferably one that's not assigned to any hardware). Then open the effect plugin's "wrapper" settings (ie. the FL specific one you open from the top of the plugin window) and pick that same port number as the "MIDI input port." Now anything you write in the "MIDI out" device's piano roll goes to the effect plugin. Similarly if you want a given plugin (eg. an arpeggiator or whatever you might have that produces MIDI) to send midi to another plugin, you would assign a "MIDI output port" to another random number in the same place in the wrapper properties (and then choose the same port as the input port on another plugin.. and so on).

[xtreme sounds]

Thanks Ill try it.

I also wanted to mention that the settings.json file is not saving my favorites with newest version download. I opened a new template and started selecting all my favorites. thats fine but then when I opened an older save project it erased all my favorites and they do not come back.

[bsp804]

I also wanted to mention that the settings.json file is not saving my favorites with newest version download.

Please (re-)read my previous reply. The previous version(s) didn't do that, either.

I disabled the settings (auto-)saving since it would not have worked properly when there are multiple instances of the plugin running at the same time.

[sonicstrav]

I've never managed to get the GUI to work with VCV - always comes up with an issue with OpenGL. Great to see this finally working using the VST version in Ableton Live 8
Not working in Tracktion Waveform....can see the rack, but right click and no modules in the list, nothing there
Is problem with veeseevstrack_instr.dll showing up as effect in Ableton Live 8 ... I'll try an older version

[bsp804]

Not working in Tracktion Waveform....can see the rack, but right click and no modules in the list

Sounds like a (DAW-specific?? or graphics driver related?) OpenGL issue (a GL context problem that leads to missing font textures).


Here's a new release:

Code: Select all

- fix denormalized float performance issue
- add (optional) AVX2-optimized binaries

Now that I finally found some time to create some patches, I noticed severe CPU load spikes. These typically happened after a note off.
The new release should fix that (it did with my patches).

In case you have an i9 CPU, you can also try the new AVX2 optimized binaries.

veeseevstrack_0_6_1_win64_bin-07Jul2018b.7z

[ZeePok]

 
Any chance of a 32-bit build, please?

(no clue how to do that myself)

[Koshdukai]

I hope the creator of VCV rack works with this project. I think the biggest advantage is all the modules come installed and I dont have to install another software to use this.

This is an independent fork that is not associated with VCV Rack. A "proper" version of the VST would require an at least partial redesign of the engine and its UI framework. What you call an advantage is actually just a necessary side-effect. It would have been a lot easier if the modules could be loaded dynamically (i.e. as plugin DLLs).

I really hope Andrew Belt is willing to redesign the engine at this stage and prepare VCV for multi-instancing.

A (properly) redesigned version of VCV would allow VST/AU/etc formats while still allowing the main (standalone) version to evolve, but the main thing would be compatible modules across those different use formats.

Sure, it would break (again) all modules, forcing all module devs to also retweak their code (basically what you did already for the open sourced ones) but the earlier this happens, the easier and fewer devs need to be involved.

Edit: oh, and btw, thanks for doing this, actually proving this could/can be done

[mantratronic]

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.

Thanks a lot for doing this!