[announce] VeeSeeVST Rack VST2 plugin

[xtreme sounds]

Hi with regard to using mouse scroll wheel. Maybe Ctrl plus the scroll wheel could be used to move the windows as its less useful in programming sounds.

"Maybe in future releases I'll add a feature that displays the parameter number for the current mouse-over widget."

This would work well I guess. But I do like the finer control of the scroll wheel at times. Its your concept just throwing my 2 cents around. Your vst version made VCV something I can work with now. Thanks

[xtreme sounds]

Would it be possible for the plugin to display the value of the last touched knob/fader ?
Sometimes i want to set 2 parameters on 2 modules to identical values.
Or is there another way to do that (except duplicating the module) ?

If we had the scroll wheel knob control feature it would help

[LunarPierro]

Hi bsp! Thank you for making VCV a VST plugin, I absolutely love it. However, I stumbled on an issue.

Okay so bear with me on this one. I use Reaper and I want to map my midi to control some of the knobs in the VCV. I know that In Reaper you can click on Param tab on top of the vst window and it'll basically give you a list of vst fx parameters (which aren't named). I'm trying to map my midi knobs to some of the VCV knobs and it seems to be working fine. However for some of the vcv knobs it doesnt work. To illustrate,

 

Here I've chosen to show the VCO-1 "Freq" knob in the track control (it was named 9 in the FX parameters list). When I map my midi knob to it (on absolute) it doesn't do anything, further more when I try and change the value with left click and drag (from this window), it only changes from 0 to max in the VCV. For other knobs like "Level" in VCA-2, midi learn works fine and the value changes from the track.

Sо here,



you can see me using ReaLearn (a vst which remembers the last vst parameter that you changed, and then you can quickly map a midi control to this parameter). For knobs like "Level" on VCA-2, ReaLearn shows max Value of 100% and moving the slider changes it, but with knobs like "FREQ" in VCO-1 max Value is 5400%, when it's 0 it just shows blank. And when I try and move the slider it goes bonkers, jumps up and down, and goes from min to max in VCV, just like changing it from a track. I guess midi learn doesnt work because naturally the only allowed max value is 100%? Can we do anything to make it work?

And the small thing that's bugging me, I can't seem to resize the VCV vst window like I could in standalone, almost like it's not resizable. Resizing the window just gives you this white space.

[bsp804]

[..] 

Here I've chosen to show the VCO-1 "Freq" knob in the track control (it was named 9 in the FX parameters list). When I map my midi knob to it (on absolute) it doesn't do anything, further more when I try and change the value with left click and drag (from this window), it only changes from 0 to max in the VCV. For other knobs like "Level" in VCA-2, midi learn works fine and the value changes from the track.[..]

Hi LunarPierro,
I was not able to reproduce this issue in Reaper v5.941 (the latest version).
After creating an envelope for VCO-1 "Freq", setting the parameter value in Reaper via the small dial next to the parameter name (well, number) works fine here (apparently it edits the currently selected control point).
I also added some additional envelope points and replayed the sequence and the frequency knob moved as expected.
Is the song locator placed at the control point you're currently editing ?


Changelog:

Code: Select all

** September 3rd, 2018
- ui: remove email, password, and login widgets
- ui: add vst param id + param value fields
- ui: ctrl-w / ctrl-e over a param widget now copies / pastes param values
- ui: RMB click after param widget mouse drag now undoes last param change
       (undo works until the mouse pointer leaves the widget)
       (second RMB click will load param reset value)
- update precompiled plugin SDK

• It is now possible to edit parameter values numerically
• The UI now displays the VST parameter id for the widget under the mouse cursor
• Right-click after editing a parameter via mouse-drag now undoes the last parameter change (a poor man's undo so to speak)
• Parameters can now be copied with ctrl-w and pasted with ctrl-e
• Any additional module plugins have to be recompiled with the updated plugin SDK

veeseevstrack_0_6_1_win64_bin-03Sep2018.7z
veeseevstrack_0_6_1_win32_bin-03Sep2018.7z

[Mutant]

• It is now possible to edit parameter values numerically
• The UI now displays the VST parameter id for the widget under the mouse cursor
• Right-click after editing a parameter via mouse-drag now undoes the last parameter change (a poor man's undo so to speak)
• Parameters can now be copied with ctrl-w and pasted with ctrl-e
• Any additional module plugins have to be recompiled with the updated plugin SDK

Thank you very much.

[bsp804]

Yeah no problem, these are definitely some very useful features.

Regarding the "tuned delay line" module I added yesterday:
Check out this rather untypical application of it:

https://vimeo.com/288076107

To be honest, I was not expecting it to be that useful for ambient pad drones !

At the beginning of the video I'm turning down the wet amount for a moment so you can hear what it sounds like w/o the tuned delay line.

[LunarPierro]

Hi LunarPierro,
I was not able to reproduce this issue in Reaper v5.941 (the latest version).
After creating an envelope for VCO-1 "Freq", setting the parameter value in Reaper via the small dial next to the parameter name (well, number) works fine here (apparently it edits the currently selected control point).
I also added some additional envelope points and replayed the sequence and the frequency knob moved as expected.
Is the song locator placed at the control point you're currently editing ?

Envelope itself strangely enough was working as intended. But I fixed it! There was a checkbox in ReaLearn for values, "slowly approach if jump is too big (scale mod)". Apparently the value of 5400% (54 in the VeeSee ui display though) was too much for midi to handle, I don't know. Thank you for your work :) Do you know if anything can be done to resize the window, or it's just coded that way?

[bsp804]

[..]Do you know if anything can be done to resize the window, or it's just coded that way?

ah yes, about that: you can change the window size in the config file ("settings.json").

[..]Apparently the value of 5400% (54 in the VeeSee ui display though) was too much for midi to handle, I don't know.[..]

from the DAW's perspective, all parameter values are normalized (0..1 as floats, 0..127 as 7bit MIDI bytes, 0..16383 as 14bit MIDI shorts). When a plugin parameter is set, it will be scaled to the actual parameter range (-54..54 in case of the VCO-1 frequency parameter, i.e. "0.5" becomes "0").

[Funkybot's Evil Twin]

[*]It is now possible to edit parameter values numerically
[*]The UI now displays the VST parameter id for the widget under the mouse cursor

Hi,

First off, these two features are fantastic and greatly expand the usability. One request though: can you make the UI display the VST parameter ID for the last clicked parameter? Here's what I'm running into:

1. Click on parameter, make some changes
2. Now I want to edit the value via text entry
3. Move my mouse cursor to the top of the GUI to click on the text box

Result: very often, in the process of moving my mouse cursor, it will pass over another parameter and therefore the parameter shown in the text box will immediately update. Sometimes it happens so fast that I end up entering a text value for a parameter I didn't mean to edit.

Suggestion: only update the VST Parameter ID and Value for the last clicked parameter. This way, if someone accidentally moves their mouse over a parameter, the displayed value doesn't change. If I need to see what the VST Parameter ID is for automation, clicking to see that isn't hard at all and still very intuitive.

[bsp804]

Any chance of adding the Gratrix MIDI-C1 and MIDI-G1 modules?

The github repo for these modules is not up-to-date and the modules are commented out (the module sources look like they were written for an earlier version of VCVR). You could ask the author to update them (/release the current source).

[..]very often, in the process of moving my mouse cursor, it will pass over another parameter and therefore the parameter shown in the text box will immediately update. Sometimes it happens so fast that I end up entering a text value for a parameter I didn't mean to edit.[..]

there's a simple solution for that:
left-click the parameter value textfield so it gets the keyboard focus, then move the mouse over the parameter(s) you want to edit. The textfield remains focused even when you move the mouse to the next parameter.

[Funkybot's Evil Twin]

there's a simple solution for that:
left-click the parameter value textfield so it gets the keyboard focus, then move the mouse over the parameter(s) you want to edit. The textfield remains focused even when you move the mouse to the next parameter.

Sweet! I would never have guessed to do it in reverse, but I can see some benefit to this approach if I'm going to be entering text values on multiple parameters.

Now that direct text entry exists, how hard would it be to make a parameter return to zero when double-clicking or Ctrl-clicking? Right-click to return to the last value is great, but sometimes the last value wasn't zero, so double or control-clicking would be a fast way to reset some knobs. [Waiting for you to tell me there's already a trick to do this I haven't discovered yet.]

[bsp804]

how hard would it be to make a parameter return to zero when double-clicking or Ctrl-clicking? Right-click to return to the last value is great, but sometimes the last value wasn't zero, so double or control-clicking would be a fast way to reset some knobs. [Waiting for you to tell me there's already a trick to do this I haven't discovered yet.]

Actually, double-clicking (the right mouse button) resets the value (single-click when there's nothing to undo)

[Funkybot's Evil Twin]

how hard would it be to make a parameter return to zero when double-clicking or Ctrl-clicking? Right-click to return to the last value is great, but sometimes the last value wasn't zero, so double or control-clicking would be a fast way to reset some knobs. [Waiting for you to tell me there's already a trick to do this I haven't discovered yet.]

Actually, double-clicking (the right mouse button) resets the value (single-click when there's nothing to undo)

Ha! I told you you were going to tell me that!

[bsp804]

Changelog:

Code: Select all

** September 5th, 2018
- ui: add global settings toolbar menu
   - select window size preset
   - change refresh rate
   - toggle vsync
   - save settings.json (including favourites)
- ui: fix MsDisplayWidget namespace issue 
   - affects e.g. AS.SignalDelay module
- update module AS.Flow (v0.6.9)
- update module AS.SignalDelay
- update module AS.Phaser
- add module AS.TriggersMKIII
- add module AS.ReScale
- remove module BogAudio.RM
- add module BogAudio.AD
- add module BogAudio.AMRM
- add module BogAudio.Matrix88
- add module BogAudio.UMix
- update module LindenbergResearch.QuickMix
- update module LindenbergResearch.MS20VCF
- add module LindenbergResearch.BlankPanelWood

• The window size can now be changed via the new settings menu
• The favourite module list can now (finally) be edited (+saved) via the UI (Toolbar->Global Settings->Save Settings)

veeseevstrack_0_6_1_win64_bin-05Sep2018.7z
veeseevstrack_0_6_1_win32_bin-05Sep2018.7z

[ZeePok]

 
Stellar! Thank you!