In the process I came across a better example of the issue though, and am still not clear whether it falls under what you've described: With a GUI plugin, the settings panel tracks values perfectly when adjusted in the GUI, but not when adjusted by a fader (though like I said, the internal values are still correct).
hey, good find 
this case confirm what you supposed in your bug report,
sorry if it was closed shortly, but we tend to be very suspicious about the way some plugs follow the vst specifications and it's easy to loose precious time because of that.
but now it's more clear, it look like a problem on my side, i'll reopen the [report #31] to put my investigations result.
thanks again
Statistics: Posted by martignasse — 09 Oct 2013, 16:35
]]>
The main reason this came up for me was while adding controls to some non-GUI plugins I noticed inconsistencies between fader values and what's displayed in the settings (and as the only reference point, was pulling my hair out looking for ways to compensate!), but I eventually noticed the values were actually tracking correctly internally despite what was displayed.
In the process I came across a better example of the issue though, and am still not clear whether it falls under what you've described: With a GUI plugin, the settings panel tracks values perfectly when adjusted in the GUI, but not when adjusted by a fader (though like I said, the internal values are still correct).
Is it possible there's something buggy about how Usine is rendering the string, or is this still just the nature of the vst 2.4 'beast'?
Statistics: Posted by CREDO — 08 Oct 2013, 21:59
]]>
Too bad, I would love to have it as an input to the caption field on a usine fader. Few vsts have a touch friendly interface.....
I've created a bank of 8 faders that can be used to control any of the first 32 parameters of any of the vsts in my mixer. Since most are reaktor or kontakt instruments, I can choose to put all the params I'm interested in into the first 32 slots, but a lot of vsts put crucial parameters in early slots anyway..... And I'm hoping it's cheaper on cpu to send array[32]s around than array[1000]s.....
Then I can assign a param to a fader with a two mouse clicks while I'm playing (once HH is able to update the paramname output, that is....)
The text string to go with the value would be nice..... in a perfect world
c
Statistics: Posted by woodslanding — 08 Oct 2013, 21:34
]]>
Just to confirm though - there's no way to "read" or "extract" a parameter's display values directly from the plugin itself?
well, like i said above, it's what we do in the setting panel... if the plug provide some, and there is no guaranties at allthe choice made was to not expose it,
-because we can't make this behavior simple and generic enough
-because providing a string for each param in real time at patch level is just power killer
-because we have to deal with multi-platform too
-because use case are finally rather rare or specific
hope you understand our motivation
Statistics: Posted by martignasse — 08 Oct 2013, 10:24
]]>
Usine does indeed seem to know what the internal vst units are---right?
maybe it seems but in fact, no 
what you see in the settings for the params values is just a text string provided or not by the plugin
there is no rules about what the string should/must contain, so no guaranties off anything, this is literally the vst 2.4 spec
the actual behavior of usine for param value in the settings is :
if the plugin provide a string for the value param, we show it
if not, we show the 0 to 1 value
apart from comparing the settings param value (if the string provide some kind of scale or unit infos) and the real param value over time, i see no other way to deduce some extra info.
Statistics: Posted by martignasse — 08 Oct 2013, 10:11
]]>
http://www.sensomusic.com/forums/upload ... Detail.jpg
Usine does indeed seem to know what the internal vst units are---right?
So I would +1 for being able to display this info in usine somewhere besidesjust the module details panel.
Statistics: Posted by woodslanding — 08 Oct 2013, 04:48
]]>
So if it's not possible to display those internal plugin values outside of the setting panel, is there any ways to select them more accurately?
Statistics: Posted by CREDO — 30 Sep 2013, 20:13
]]>
You can recreate it, which I have done for important parameters on certain vsts.
Statistics: Posted by woodslanding — 30 Sep 2013, 19:43
]]>
Just to confirm though - there's no way to "read" or "extract" a parameter's display values directly from the plugin itself?
Statistics: Posted by CREDO — 29 Sep 2013, 20:22
]]>
@credo : here an example from the user percuson it's a layout for the piz midi delay plug-in
Download
Statistics: Posted by nay-seven — 29 Sep 2013, 19:44
]]>
]]>
]]>
there's many way to create plug-ins , so different answers possible, sometimes, it's possible to deal with array. Have you a precise example..?I guess there's no way to extract the non-numerical display values of a particular plugin though, huh? (the ones that only show up in the settings panel for non-GUI plugins.)
Statistics: Posted by nay-seven — 29 Sep 2013, 11:30
]]>
I guess there's no way to extract the non-numerical display values of a particular plugin though, huh? (the ones that only show up in the settings panel for non-GUI plugins.)
Thanks for the great tutorial BTW. I started using it the first day, and it's already saved me a lot of grief!
Statistics: Posted by CREDO — 29 Sep 2013, 00:56
]]>
for array you can use the get array value module and select the correct index
for vst you have to create your conversion, here i've 20 grains in my plugin, so i multiply by 20, you can also use the change scale ( from 0-1) sub patch
feel free to have a look also to the patching tutorial pdf in the download section
Statistics: Posted by nay-seven — 28 Sep 2013, 21:59
]]>
Thanks!
Statistics: Posted by CREDO — 28 Sep 2013, 21:39
]]>