KVR Audio

Taika-Kim · Post by **Taika-Kim** » Fri Jul 06, 2018 8:14 am

Wow, this is good news! I hope this would become official

KennyG5000 · Post by **KennyG5000** » Fri Jul 06, 2018 9:14 am

Thanks very much for the response and taking the time to convert those modules, really appreciate it. I tested OSC out on the Trowasoft modules and it is working as expected, which is great.

In case anyone is interested (and has a copy of Reaktor), you can quite easily achieve working MIDI out. I currently have this set up to trigger drum samples in Battery (but you could trigger anything else with MIDI out). Just use the Trowasoft 'cvOSCcv' module. You need to find your computer's IP address (via ipconfig) and put this in the address on the config page of 'cvOSCcv'. Pick an out port (eg 9000) and enable OSC in Reaktor (getting it to listen on port 9000 in this case). I have added a link to a very simple Reaktor ensemble that will listen for the first 4 'val' ports on the 'cvOSCcv' module and convert them to MIDI notes for triggering (you can choose the MIDI note and channel in the ensemble window).

I think this is pretty useful to open up VCV further (I am also finishing an ensemble that will also take pitch into account to drive external instruments etc).

Here is the link in case anyone else wants to try it:

https://www.dropbox.com/s/rprffj0efw4lb ... 2.ens?dl=0

StudioDave · Post by **StudioDave** » Fri Jul 06, 2018 10:37 am

klinik wrote: Also, some request:
...
-NYSTHI, because those are wonderful modules!

Probably won't happen unless Antonio opens his source code.

And they are indeed wonderful modules.

Best,

dp

xtreme sounds · Post by **xtreme sounds** » Fri Jul 06, 2018 12:49 pm

Thank you. This made VCV Rack quite useable in my DAW (ableton and FL studio) no problems. I hope that the official VCV Rack gets it set up this way. BUt as it stands with what is available in this vst format plenty to work with as it is.

I noticed one thing that is different. The mixers and volume controls do not do anything while in VCV as a vst. You have to use the DAW mixer volume to control. Am I missing something?

Does anyone have any preset setup templates to share?

MFXxx · Post by **MFXxx** » Fri Jul 06, 2018 1:35 pm

Star work.Thank you

bsp804 · Post by **bsp804** » Fri Jul 06, 2018 2:53 pm

klinik wrote:Tried the VST effect version in studione 3.5 andcan´t work... the "inputs" from tthe core audio module are working (I can send a VCO and it sound thru the Studioone track where Veeseee is inserted, but the audio from the track can´t reach core audio "outputs" tried even bridging ins to outs
Tried in reaper (not my daw but for testing) and worked fone.

hmm, unless this is just a setup/routing issue, maybe some other dev can take a look at the plugin source to see if there is anything that would prevent the audio inputs from working ?

klinik wrote:it really opnen a new world for quick prrocessing tracks thru the VCV modules inside the DAW. Thanks!!

I've only scratched the surface myself but from what I've seen so far, this could be a real desert island synth/effect ! (so many interesting and great sounding modules !)

klinik wrote: -Arable&Parable instruments please!! I the parasite firmaware for the Clouds, and also a better interface having all parameters in dedicated knobs so great for automation all of them inside the DAW
-Aepelzens, also some parasites firmwares for warps and others
-NYSTHI, because those are wonderful modules!

I've put these on my TODO list but I really have to be careful not to burn the candle from both sides for too long (this is all done in my spare time).
Believe it or not, I haven't even had time to create patches / make music with what's already there.
But as they say, Rome wasn't built in one day and eventually those modules will be added, too.

Taika-Kim wrote:Wow, this is good news! I hope this would become official

I wrote an email to Andrew the other day and suggested the same thing. Maybe he'll look into it when he's not so busy anymore (?).

KennyG5000 wrote:I tested OSC out on the Trowasoft modules and it is working as expected

cool, thanks for testing !

melodyz wrote:The mixers and volume controls do not do anything while in VCV as a vst

There are mixer and volume controls ?? (..where ?)

Regarding the VST host timing issue (no clock out) that KennyG5000 reported:
Here's an update that implements the clocks and the start / stop signals.
I've tested them in my own host and in Reason.

Changelog:

Code: Select all

** July 6th, 2018
- Core.MIDI-1: support clock and start, stop signals
   (host must implement audioMasterGetTime and
    support kVstTempoValid + kVstTransportPlaying)

veeseevstrack_0_6_1_win64_bin-06Jul2018.7z

RCJacH · Post by **RCJacH** » Fri Jul 06, 2018 3:57 pm

Awesome work! I am grateful for your generosity.

Just a little inquiry and request, currently VeeSeeVST Rack, like VCV, check for opengl 2.0 upon startup, and if detected opengl version is lower, the whole plugin shuts down along with the DAW.
Is the GUI necessary for the sound engine to work? If not, is it possible to include a checkup at activation so that if the detected opengl version is lower than 2.0, the GUI does not start, only the sound engine?

The situation is that I am using RDP to control my production desktop, and RDP has only opengl 1.1...that would start this plugin at all. So I have to use VNC to connect with single monitor (because bandwidth issue that causes a lot of lag if I go vnc with multiple monitors) to use this plugin. If the sound engine works without the GUI, then I can dial the VeeSeeVST Rack vst2 with VNC, then do post-production with RDP on multiple monitors.

bsp804 · Post by **bsp804** » Fri Jul 06, 2018 4:26 pm

RCJacH wrote:Is the GUI necessary for the sound engine to work? If not, is it possible to include a checkup at activation so that if the detected opengl version is lower than 2.0, the GUI does not start, only the sound engine?

The patch state in the rack engine seems to be tied to the UI (patch states are loaded by "ModuleWidget"s, not "Module"s).

Therefore, the OpenGL context needs to be created before a patch can be loaded (=> the VST plugin has to delegate any load requests to the UI thread, then wait for it).

Like everything "good and binary", this could be changed, but it would take a considerable effort (I won't do it).

xtreme sounds · Post by **xtreme sounds** » Fri Jul 06, 2018 4:31 pm

How do we connect a midi controller to it to trigger notes? also I see in FL studio this has to be loaded as an effect only which may affect using a midi controller to trigger it

RCJacH · Post by **RCJacH** » Fri Jul 06, 2018 4:40 pm

bsp804 wrote:
RCJacH wrote:Is the GUI necessary for the sound engine to work? If not, is it possible to include a checkup at activation so that if the detected opengl version is lower than 2.0, the GUI does not start, only the sound engine?
The patch state in the rack engine seems to be tied to the UI (patch states are loaded by "ModuleWidget"s, not "Module"s).

Therefore, the OpenGL context needs to be created before a patch can be loaded (=> the VST plugin has to delegate any load requests to the UI thread, then wait for it).

Like everything "good and binary", this could be changed, but it would take a considerable effort (I won't do it).

Thank you for the quick reply, I'll find some other way to work it out.

bsp804 · Post by **bsp804** » Fri Jul 06, 2018 4:42 pm

melodyz wrote:How do we connect a midi controller to it to trigger notes? also I see in FL studio this has to be loaded as an effect only which may affect using a midi controller to trigger it

Don't know about FLStudio but In Reason for example you instantiate the effect, choose "Combine" in the context menu, enable "Receive Notes" in the combinator programmer, and voilà.

Totolitoto · Post by **Totolitoto** » Fri Jul 06, 2018 5:10 pm

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

xtreme sounds · Post by **xtreme sounds** » Fri Jul 06, 2018 5:34 pm

How about ableton can we use our midi controller to trigger notes that way? I like what you did - more than trying to use bridge. - especially having all modules straight away did but we need a way to trigger notes in any daw.

bsp804 · Post by **bsp804** » Fri Jul 06, 2018 5:35 pm

Totolitoto wrote: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.

melodyz wrote:How about ableton can we use our midi controller to trigger notes that way? I like what you did - more than trying to use bridge. - especially having all modules straight away did but we need a way to trigger notes in any daw.

If your DAW does not support note input for effects, please direct your complaints to the DAW vendor.

In any DAW, you will have to set this effect plugin up like a harmonizer / pitch shift effect that also expects MIDI note input.

xtreme sounds · Post by **xtreme sounds** » Fri Jul 06, 2018 5:36 pm

bsp804 wrote:
Totolitoto wrote: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.

I tried and it didnt work. It wants even the intru version to be loaded as an effect. I wonder if I can do it in patcher

[announce] VeeSeeVST Rack VST2 plugin