Sound Variants API in Plug 'n Script?
-
- KVRist
- 42 posts since 25 Aug, 2006
Any thoughts on allowing PnS scripts to support the Sound Variants API introduced in Studio One 5.2 and now supported by Digital Performer 11? This would enable scripts to auto-populate articulation maps in these and other DAWs that adopt this API.
-
- KVRAF
- 9560 posts since 6 Jan, 2017 from Outer Space
Is this a new standard? A google search reveals nothing. Do you have a link?
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981 - KVRAF
- 6345 posts since 8 Sep, 2004 from Paris (France)
That's something we have not heard about either... It seems indeed listed in the PreSonus VST3 extensions here:
https://www.presonussoftware.com/en_US/developer
https://www.presonussoftware.com/en_US/developer
-
- KVRAF
- 1985 posts since 14 Mar, 2006
Presonus introduced an additional API that is basically designed whereby the host can query a compatible plugin for keyswitching information. This same kind of stuff is part of VST3, but Presonus did something outside of that..it can be done with VST2 for VST3 no difference. Its a completely seperate API introduce by them. MOTU is now using it also.
I'm not sure what or how PNS would be used in conjunction with those two hosts and that particular feature. At the end of the day you mostly have to put PNS together with an instrument, inside some kind of sub hoster such as Patchworks..and then the SoundVariations API calls would need to be echoed out of Patchworks also... for example, so that the main host such as DP/S1 would interact indirectly through Patchworks and PNS...and if an instrument is Sound Variation capable, directly with that too. Seems complicated.
For the record I am not a fan of the Sound Variations feature. I feel that PreSonus overengineered a simple thing, which is how to get articulation map presets loaded into the DAW. I think creating a two way communication between plugin and DAW to load the preset was way over engineered and overly complicated...when most people will load the preset once and move on. It seemed neat to a lot of people that they could load a sample library and have the DAW know the keyswitches....ok...but the complication of the whole setup, IMHO, negates things.. not a fan. That's why also, IMHO, virtually nobody has embraced the same feature introduced in VST3 by Steinberg...other than Halion and perhaps some other Steinberg instruments that actually use it. Nobody else has even sniffed at it because the work involved and the complication involved isn't justified by the simple task of loading an articulation map preset.
Just my two cents..
I am curious what kinds of specific tasks people would try to use PNS to interact with Sound Variations though.
I'm not sure what or how PNS would be used in conjunction with those two hosts and that particular feature. At the end of the day you mostly have to put PNS together with an instrument, inside some kind of sub hoster such as Patchworks..and then the SoundVariations API calls would need to be echoed out of Patchworks also... for example, so that the main host such as DP/S1 would interact indirectly through Patchworks and PNS...and if an instrument is Sound Variation capable, directly with that too. Seems complicated.
For the record I am not a fan of the Sound Variations feature. I feel that PreSonus overengineered a simple thing, which is how to get articulation map presets loaded into the DAW. I think creating a two way communication between plugin and DAW to load the preset was way over engineered and overly complicated...when most people will load the preset once and move on. It seemed neat to a lot of people that they could load a sample library and have the DAW know the keyswitches....ok...but the complication of the whole setup, IMHO, negates things.. not a fan. That's why also, IMHO, virtually nobody has embraced the same feature introduced in VST3 by Steinberg...other than Halion and perhaps some other Steinberg instruments that actually use it. Nobody else has even sniffed at it because the work involved and the complication involved isn't justified by the simple task of loading an articulation map preset.
Just my two cents..
I am curious what kinds of specific tasks people would try to use PNS to interact with Sound Variations though.
MacPro 5,1 12core x 3.46ghz-96gb MacOS 12.2 (opencore), X32+AES16e-50