- How does someone go about determining the Plugin ID and Manufacturer ID to use?
- If my exported VST will not be using any audio, how should I configure the audio ports field? Does it need to be configured as at least a stereo instrument type of plugin, even though it will be used only for midi purposes with no audio output?
- There is a midi FX type of plugin that can be created, but this is not clear to me what that is exactly.
- for Mac how do I go about exporting AUmfx version of it?
- Now the elephant int the room, do I need an actual Steinberg VST2 license in order to distribute a PNS script exported as a VST2 plugin? since I'm not compiling with the VST2 header, seems like I should not need it. Please clarify. Distributing the script this way is much cleaner then trying to distribute as a raw PNS script for those that want to buy PNS. Obviously, people don't have to buy PNS to buy it, but also there is always some concern about making sure the #include for Midi.hxx is right for the user, which makes it kind of a headache to use in raw PNS form.
PNS Export questions
-
- KVRAF
- 1985 posts since 14 Mar, 2006
I have made a midi filter script with PNS. I would like to share it. I have some questions about exported plugins from PNS:
MacPro 5,1 12core x 3.46ghz-96gb MacOS 12.2 (opencore), X32+AES16e-50
-
- KVRAF
- 9553 posts since 6 Jan, 2017 from Outer Space
I fear the VST2 export isn’t for distributing the plugin if you don’t have a license. I would not take the risk… For your own use, nobody cares…
-
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)
1. Plug-in ID and Manufacturer ID are supposed to be unique. Now that Steinberg has stopped their plug-in registration service, you will have to maintain your own list of unique plug-in IDs so that they do not clash with each other. At some point the manufacturer ID used to have to be registered at Apple or AVID, but it looks like you can now just choose your own, hoping noone else has the same...
2. There is a MIDI plug-in option in the plug-in type. It will produce the appropriate type of effect (only Audio Units actually have a specific type for MIDI effects, with no audio going thru). Choosing the mono/Stereo audio config for these is indeed the best way to have a plug-in that is compatible with most DAWs.
3. That's the type you want to use for plug-ins that only process MIDI.
4. Using the MIDI FX type
5. Yes you indeed need a license to distribute your VST or VST3 plug-ins (neither of these format is "free").
2. There is a MIDI plug-in option in the plug-in type. It will produce the appropriate type of effect (only Audio Units actually have a specific type for MIDI effects, with no audio going thru). Choosing the mono/Stereo audio config for these is indeed the best way to have a plug-in that is compatible with most DAWs.
3. That's the type you want to use for plug-ins that only process MIDI.
4. Using the MIDI FX type
5. Yes you indeed need a license to distribute your VST or VST3 plug-ins (neither of these format is "free").
-
- KVRAF
- 9553 posts since 6 Jan, 2017 from Outer Space
One possible license for VST3 is GPL, the other you have to sign with Steinberg… GPL is free in the best sense for the users (less free for the developer as she is forced to publish the source…)Blue Cat Audio wrote: Tue Mar 29, 2022 8:15 am 5. Yes you indeed need a license to distribute your VST or VST3 plug-ins (neither of these format is "free").