[announce] VeeSeeVST Rack VST2 plugin

[bsp804]

Thank you! Now i can modular in my modular

Good to know. God speed and good luck !

[Clearscreen]

[..]Is there any chance of having param names passed over to the DAW? Or even assigning/organising params like reaktor does?[..]

The module parameters do not have names so this is not possible w/o some major changes.

A parameter editor (assign / label) is not something I am going to implement, mainly because I think that such a generic feature should be handled by the DAW.
In fact, the VST host / sequencer combo I am using allows you to do just that, and so does Reaper, for example ("Alias parameter").

Fair enough, I'll just carry on assigning macro's after I work out which dial is in use. Thanks for the reply!
Another thing I've noticed - been using veesee on my surface pro with Bitwig and the touch input is insanely sensitive. Works fine with mouse etc, but with touch a tiny movement results in a massive change in the param (even the basics like zoom, cord tension). Will the new refresh settings affect this by any chance?

[bsp804]

The only little issue that i also noticed initially - it's in Studio one, when you try write in upper "email" and "password" fields, this launches internal DAW hotkeys commands

The new release may fix this.

Another thing I've noticed - been using veesee on my surface pro with Bitwig and the touch input is insanely sensitive. Works fine with mouse etc, but with touch a tiny movement results in a massive change in the param (even the basics like zoom, cord tension). Will the new refresh settings affect this by any chance?

The refresh settings won't have an effect on this.

I can only guess that this is due to the way Windows emulates mouse input on touch devices. It will not send an LBUTTONDOWN message to a window until the touch point has moved a few pixels.
When it has not moved, it sends an RBUTTONDOWN message after a timeout.
The most annoying thing about this is that there is absolutely no way to turn this off.
Devs are forced to implement the Windows touch API to get around this.

Well, the new release now supports the Win8 touch API.
I'm not sure if it has to be enabled explicitly on a touch-capable device like your Surface tablet. The new release may work out of the box but if it does not, try enabling "touchInput" in settings.json (set it to true).
(and don't edit the file with the Windows notepad! When the favorite list disappears, you know the file is broken)

Changelog:

Code: Select all

** August 8th, 2018
- support Windows 8 touch API and add settings.json:"touchInput" option
   - RMB is emulated via ctrl-LMB or LMB-hold
- don't forward keyboard events to next listener when 
   they have been consumed by the plugin UI

veeseevstrack_0_6_1_win64_bin-08Aug2018.7z

[c_voltage]

bsp804
Thank you, yes now focus inside plugin, but not works entering symbols with shift like @ yet.

[lalo]

Next stop: A proper plugin interface. This will take a while.

thanks bsp404!
what do you mean with "a proper plugin interface"? are you talkin' about the VST itself or the dynamic modules loading?

[bsp804]

bsp804
Thank you, yes now focus inside plugin, but not works entering symbols with shift like @ yet.

Good point The last release broke it. I've fixed it and uploaded a new version (same link / filename). Please give it a try.
veeseevstrack_0_6_1_win64_bin-08Aug2018.7z

what do you mean with "a proper plugin interface"? are you talkin' about the VST itself or the dynamic modules loading?

Maybe I should not have mentioned it since at the moment it's just an idea.

What I'm thinking of is some kind of lightweight plugin interface that

• is suitable for virtual modulars
• is not tied to a specific host
• is not tied to a specific programming language
• is stable (i.e. does not require all plugins to be recompiled when the host changes)

like I said, this is going to take some time and thought.

[c_voltage]

Please give it a try.

Yes, now symbols works, thank you.

[lalo]

bsp804
Thank you, yes now focus inside plugin, but not works entering symbols with shift like @ yet.

Good point The last release broke it. I've fixed it and uploaded a new version (same link / filename). Please give it a try.
veeseevstrack_0_6_1_win64_bin-08Aug2018.7z

what do you mean with "a proper plugin interface"? are you talkin' about the VST itself or the dynamic modules loading?

Maybe I should not have mentioned it since at the moment it's just an idea.

What I'm thinking of is some kind of lightweight plugin interface that

• is suitable for virtual modulars
• is not tied to a specific host
• is not tied to a specific programming language
• is stable (i.e. does not require all plugins to be recompiled when the host changes)

like I said, this is going to take some time and thought.

thanks for the info.
Are the SDK documented in some way. I'd like to try do compile some open source module and see if i can do the modifications needed by VeeSeeVST and then try to code some module for VeeSeeVST.

[VariKusBrainZ]

Great to see patch compatability

[bsp804]

Are the SDK documented in some way. I'd like to try do compile some open source module and see if i can do the modifications needed by VeeSeeVST and then try to code some module for VeeSeeVST.

The current plugin interface is almost the same as in the standalone Rack application. The main difference is that the VST version uses a couple of macros (some of which do some "magic" behind the scenes), and the VST and the plugins have to be built with Microsoft Visual Studio (their Community edition is free as-in-beer).

The plugin SDK contains an example plugin (a "port" of the "Template" example plugin).
It should be self-explanatory.
In the VSVR repo you can also find a more complex plugin (dBiz).
In case you get stuck, just go ahead and ask.

[Clearscreen]

Another thing I've noticed - been using veesee on my surface pro with Bitwig and the touch input is insanely sensitive. Works fine with mouse etc, but with touch a tiny movement results in a massive change in the param (even the basics like zoom, cord tension). Will the new refresh settings affect this by any chance?

The refresh settings won't have an effect on this.

I can only guess that this is due to the way Windows emulates mouse input on touch devices. It will not send an LBUTTONDOWN message to a window until the touch point has moved a few pixels.
When it has not moved, it sends an RBUTTONDOWN message after a timeout.
The most annoying thing about this is that there is absolutely no way to turn this off.
Devs are forced to implement the Windows touch API to get around this.

Well, the new release now supports the Win8 touch API.
I'm not sure if it has to be enabled explicitly on a touch-capable device like your Surface tablet. The new release may work out of the box but if it does not, try enabling "touchInput" in settings.json (set it to true).
(and don't edit the file with the Windows notepad! When the favorite list disappears, you know the file is broken)

THANKS - Touch is working great now!! Really appreciate your responsiveness and effort here!
Just the touch keyboard doesn't work into the search bar - Sorry, hope I'm not annoying you too much...

And some minor things - it possible for the favourites to be a collapsed group item instead of a long list before the other makers? It'd make scrolling down a little easier. I've been deleting the favourites using brackets to make getting to the modules a little easier, but there's useful stuff there so keeping it collapsed wouldn't hurt.
The scroll bars a little tricky to grab with touch, but it works now, so I'll take it as is if it's too much hassle for you to mess with.
Thanks again!

[Mutant]

I can confirm the "not seeing the knob movement in REAPER until i release the left mouse button" bug that was reported earlier.
Setting the "false" flag in the properly named .json file doesn't solve the problem.

[lalo]

I can confirm the "not seeing the knob movement in REAPER until i release the left mouse button" bug that was reported earlier.
Setting the "false" flag in the properly named .json file doesn't solve the problem.

Latest version of August 8 doesn't suffer of it anymore just download the latest version

[Mutant]

I can confirm the "not seeing the knob movement in REAPER until i release the left mouse button" bug that was reported earlier.
Setting the "false" flag in the properly named .json file doesn't solve the problem.

Latest version of August 8 doesn't suffer of it anymore just download the latest version

Correct.
THX for info and THX bsp804 for the quick fix.

[bsp804]

[..]Just the touch keyboard doesn't work into the search bar[..]

The new release now supports touch keyboard input but I can tell you one thing: The internals for this are _horrible_, mainly b/c Microsoft does not have proper (C) APIs for this.
The touch keyboard support is disabled by default, i.e. you have to set "touchKbd" to true in "settings.json".

And some minor things - it possible for the favourites to be a collapsed group item instead of a long list before the other makers? It'd make scrolling down a little easier. I've been deleting the favourites using brackets to make getting to the modules a little easier, but there's useful stuff there so keeping it collapsed wouldn't hurt.

I can imagine that using the tiny scrollbars on a a touch device is not very comfortable but the whole point of the favourites list is that you don't have to scroll (much).
You could edit the list and add your own favourites, or you can now use the filter text field to narrow down the module list (e.g. type "vcf" for a list of all filters).

Changelog:

Code: Select all

** August 9th, 2018
- add settings.json:"touchKbd" option
   - show / hide virtual keyboard when textfield is clicked
   - support virtual keyboard input via effEditKeyDown

veeseevstrack_0_6_1_win64_bin-09Aug2018.7z