From the original SynthMaker forum (2004–2014), with its members’ names and dates.
tester ·
I'm confused a little bit with basic SM slider. Storing it's values in a preset, I'd like to get them not in (0-1) range but as a custom output (between min/max specified in the slider). For example if the slider outputs frequenccies (values in range 0-16000), then in preset file I'd like to have these frequencies. Thus, the preset file itself - would be more user friendy for manual edit as a text file. How to move/modify the preset module correctly to the output node?
DigitalWhiteByte ·
unfortunately can not, because the vst specific want that, the value is in range 0 to 1
trogluddite ·
DWB wrote: unfortunately can not,
Well, you sort of can - in fact I have done it a lot - but, yes, there are pretty strict rules...
It is possible to store any float value in a Preset Parameter - and it will appear in that form in the text file of saved presets. In the VST hosts that I have used (mostly Reaper and VSTHost), I've also had no problem storing and recalling such values. I've also not found (yet!) any limit to the min/max values allowed by the mouse drag primtives.
So you might think that all that scaling going on in the knob is for nothing?...
However, the 0-1 range is there for a reason - in the VST spec' it is the standard range for communicating automation and showing "controller lanes" in sequencers etc. Some hosts like Ableton Live, and Reaper also use this protocol to enable features like MIDI Learn, and showing proxy controls within the host interface. So, while it can be done, whether it is appropriate depends on the level of host communication you intend to use, and there is no guarantee that it will be bug free all with all hosts. If you are only interested in making an .exe, then you have no worries. None of the bugs reports I've had for my plugins have related to this issue. I have used "naughty" preset values quite a bit for simplicity - but crucially, I only use VST automation under duress, and generally use it purely for presets (not dynamic automation.) Always preferred MIDI control myself - unlike VST automation, it can be saved and transferred between different software, and is more amenable to messing creatively with the data - plus I'm an old fart that is comfortable with it!
There is another feature of the preset parameters that you may find handy if you prefer to work in literal values. There are two inputs labelled "Display Value" and "Display units", the strings here are for display by the VST host - for example if controls allow tootips to investigate the value, or for labelling axes an automation graphs. So you can feed these with a scaled version of the parameter for a more readable display.
tester ·
Good that you explain on the beginning, thanks 😉
I'm planning to make both, exes and vsts/vstis, but rather with no automation... Or maybe yes? I have in plans "timelines" inside some apps, but these are only a vague thoughts right now; on the other hand - host automations are rather for more advanced users. Making VST is motivated very simply. While EXE seem to have certain issues when exporting audio to wav, VST just mixes the plugin with any audio file (or with anylenght "null file"). Also - sometimes probably will be easier to use multiple instances of single unit. So - all options are under consideration. The only thing I probably focus on - are the hosts that will be supported by my apps; I'm not going to be compatible with everything if I can't.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker