Does anyone know how midi works with pd~ instances?

The start message doesn't like it when I was in pass in alsamidi arguments and prints the pd help information on the console.

I want to have the pd~ create a separate alsa midi input from the main patch but I not sure how to do that.

It appears to be DSP-centric oversight or some unfinished functionality at work here. I noticed it is possible to go into the sub-process media menu and manually create midi ports for the sub-process after it is started, but as you say -- no way to do it with the sub-process startup flags.

I don't know if this helps (depends on what you are doing), but one reason I haven't had much use for [pd~] yet is because I usually just run multiple instances of PureData when I need different startup variables. The main issue you might have as using this method as a workaround for your problem is setting up the needed communication between the two instances.

@widdly How about this?

[#ctlin ...<

Cheers~

Thanks Eeight. That looks like a good work around for my situtation.