PNS Feature Request: host one inst plugin

[Dewdman42]

Plug N Script Feature Request - add the ability to host one instrument plugin; post-script.

The primary need I have for PNS is to write midi manipulation scripts for midi that is intended to arrive at an instrument. its usually possible to route midi in the DAW, but adds a lot of user complexity...such as having to make extra tracks, etc. Or Patchworks can be used obviously but that still adds a level of complexity.

However, I wish to make some midi filter scripts which I plan to share with others..and what would make them supremely easier to use would be if it had a single instrument hosting slot added, so that basically the user could specify whatever instrument they want to host, and then my own PNS Gui would still be there for them to interact with the midi processing...and the midi would be filtered and sent to that hosted instrument, and they'd get all the audio outs, etc.. My PNS script would function like an AUinst or VSTinst. with my custom midi filtering built in...

If that seems like something you might consider adding, please contact me to also talk about multi-port midi for VST3 and AU3..which would also be extremely useful in PNS, but especially if it can host inside a multi-port VST3 plugin (example, VePro7.vst3).

regards

[Blue Cat Audio]

Thanks for the suggestion. I don't think this would really make sense for us to offer such a particular hosting feature in PnS. Many hosts (except Logic) make it indeed a bit cumbersome to use MIDI plug-ins. However you can use something like PatchWork to make it simpler and quickly connect MIDI plug-ins and VIs.

[Dewdman42]

Thanks for letting me know

I’ll still try to make a couple things with PNS at some point to see how it goes. It’s not bad for quick and dirty simple midi scripts. Would be a lot better if my midi scripts didn’t require patchworks.

I might be better off using JUCE in order to host the instrument together with my midi filters. PNS is convenient for prototyping though

[Dewdman42]

Also, patchworks does not currently provide vst3 multiport midi capability which makes it unsuitable for hosting the vepro plugin inside it, which is my primary need. What I didn’t elaborate on my first post, is that there is also a need for pns to be able to address multiple midi ports when filtering midi for vepro.vst3. Up to 48 ports. Both pns and patchworks are unsuited fir this. Yet.

Hypothetically, if pns could host a single vst3 plugin and allow the script to programmatically send midi to those 48 ports while also exposing up to 48 vst3 input midi ports to the daw, then it could work well.

Even if you added that feature to pstchworks it still would require to set up a complicated network inside patchworks to route to 48 ports and also pns would not have a way to programmatically route midi across different ports, which it theoretically COULD do if you built some vst3 hosting into PNS and enhanced the api to include port routing.

I can do all of that with logicpro scripter
Using AU3. Unfortunately my scripts only work in logicpro.

I am contemplating a move to cubase but this is the main impediment for me. I was hoping to convert these scripts to PNS and share them pubicAlly as well as I have been doing with logicpro scripts. However I just keep running into little roadblocks thst make pns not quite enough. I can of course convert my scripts to juce and do anything I want, which is the next step perhaps but they don’t provide vst3 multiport hosting either in their api as of yet. There might be some ways to program around it though but then I’m getting into the area of too much work and rather just stay in Logic Pro scripter for now

[Dewdman42]

Or I could face the music and try to use the vst3 sdk directly