VST 3 is comming

exonerate · 17 Dec 2007

Yeah VST3 is looking good 😉

Logical Parameter Organization

I think this enhancement will make working with presets a lot more flexible, I don't think you would be limited to one preset manager. I currently have a slow solution for saving and loading banks of waveforms, i tried loading and saving only certain parameters in some areas while still being able to save all parameters. But that is currently not possible, i think with this enhancement it should be.

Improved Performance

I think this is a good one as well,(no processing when audio is not present) it should mean that the 'mono' streams in SM wouldn't be processed all the time like they are now, although I'm not sure if this would be the case of a synth, because it says when theres no audio at the input, should be the case though if it works for the audio output as well.

Well they are all good and very useful enhancements, i hope SM can be updated to VST3 sooner rather than later. I could do with the 'Logical Parameter Organization', of course though then most likely we'll have to wait for hosts to upgrade.

cheers 😉

Exo

Acrobat · 18 Dec 2007

Audio Inputs for VST Instruments

? - there's not AUDIOIN in already - ?

EDIT: oh they mean for DIRECT connection via busses from anywhere to the instrument. Cool.. 😀

Acrobat · 19 Dec 2007

Logical Parameter Organization

Nice, this probably mean you can have folders and categories by default.. actually on plugins with folders for presets (like, i.e. Vember Audio Surge) locations of patches are not recognized and don't work well because the host doesn't records the plugin folder where the sound is actually stored....

exonerate · 19 Dec 2007

Acrobat wrote: Logical Parameter Organization

Nice, this probably mean you can have folders and categories by default.. actually on plugins with folders for presets (like, i.e. Vember Audio Surge) locations of patches are not recognized and don't work well because the host doesn't records the plugin folder where the sound is actually stored....

You can set this up your self, the 'file dialog' primitive has a 'start folder' option, you can set this to your preset folder. The 'plugin folder' primitive will give you the location of your dll, then you can add the name of your preset folder to the output of the plugin folder primitive,

like "C:\vst plugins\my synth" would be the output of the 'plugin folder' primitive and then add "\presets" to the end and feed this to the 'start folder' input on the file dialog inside your preset manager.

Now no matter what computer your synth is run on saving or loading presets will alway default to this folder.

cheers 😉

Exo

Acrobat · 19 Dec 2007

exonerate wrote: Acrobat wrote: Logical Parameter Organization

Nice, this probably mean you can have folders and categories by default.. actually on plugins with folders for presets (like, i.e. Vember Audio Surge) locations of patches are not recognized and don't work well because the host doesn't records the plugin folder where the sound is actually stored....

You can set this up your self, the 'file dialog' primitive has a 'start folder' option, you can set this to your preset folder. The 'plugin folder' primitive will give you the location of your dll, then you can add the name of your preset folder to the output of the plugin folder primitive,

like "C:\vst plugins\my synth" would be the output of the 'plugin folder' primitive and then add "\presets" to the end and feed this to the 'start folder' input on the file dialog inside your preset manager.

Now no matter what computer your synth is run on saving or loading presets will alway default to this folder.

cheers 😉

Exo

yes I did use that primitive just some weeks ago implementing the general settings for Alieno. (I must admit that saving and loading to disk gave me a strange sense of power - now I understand what programmers feel when they work...) Anyway that trick works inside a plug, hosts have their own patching mechanism that doeasn't have folders so how can you browse between folders created from a plugin DIRECTLY from the patch browser of a host? I see it impossible..... 😕

exonerate · 19 Dec 2007

Acrobat wrote: exonerate wrote: Acrobat wrote: Logical Parameter Organization

Nice, this probably mean you can have folders and categories by default.. actually on plugins with folders for presets (like, i.e. Vember Audio Surge) locations of patches are not recognized and don't work well because the host doesn't records the plugin folder where the sound is actually stored....

You can set this up your self, the 'file dialog' primitive has a 'start folder' option, you can set this to your preset folder. The 'plugin folder' primitive will give you the location of your dll, then you can add the name of your preset folder to the output of the plugin folder primitive,

like "C:\vst plugins\my synth" would be the output of the 'plugin folder' primitive and then add "\presets" to the end and feed this to the 'start folder' input on the file dialog inside your preset manager.

Now no matter what computer your synth is run on saving or loading presets will alway default to this folder.

cheers 😉

Exo

yes I did use that primitive just some weeks ago implementing the general settings for Alieno. (I must admit that saving and loading to disk gave me a strange sense of power - now I understand what programmers feel when they work...) Anyway that trick works inside a plug, hosts have their own patching mechanism that doeasn't have folders so how can you browse between folders created from a plugin DIRECTLY from the patch browser of a host? I see it impossible..... 😕

Ahh.... yes well that is not possible for any VST, i guess though with the VST3 update this could be possible, but it would be down to the host to add support for such a thing.

cheers 😉

Exo

MyCo · 21 Dec 2007

rl wrote: 64 Bit processing

that's nothing new. It has been introduced in VST 2.4

infuzion · 21 Jul 2008

A few comments on VST3.0.1: http://www.kvraudio.com/forum/viewtopic.php?t=221988

obiwanjacobi wrote: Chris Walton wrote: Take a look at how Steinberg defines true in VST3. I'll save you the trouble and tell you. 0.Yes, zero. No further comments needed

Yes, that seems odd. But it isn't. Its also used on COM. Zero as a return value means 'all is fine' (OK or True) in COM. Negative values indicate an error. Positive values are 'OK with info'. Like False.

Unfortunately they've missed it with their enum. It doesn't allow for extension or customization very well.

arne wrote: Leslie Sanford wrote: At this point, I really only have two problems with VST 3:

1) If I adopt it, I'll need to support two formats for my plugins. v2.4 (as ugly as it may be) isn't going any where for a long time to come. Supporting two formats will be a pain.

With regards to 1, there may be a way to write a library that lets you target either v3.0 or v2.4 with a flip of a compiler switch. I haven't looked deeply enough to know what's involved.

There will be a wrapper in the upcoming VST3 SDK which will wrap a VST3 plug-in to a VST2.4 plug-in. {after December}