Forums > MaxMSP

virtual midi ports

Jul 23 2012 | 7:45 pm

Hi – having trouble with virtual midi ports.

works great in Max 6 on OSX, using the message

#SM createoutport AUX1 coremidi

However, when i make a standalone application, they don’t seem to pass midi.

they show up as midi ports (in both pro tools and my standalone) but don’t actually pass midi.

any ideas?


Jul 24 2012 | 12:16 am

actually – is there a way to link virtual ports by name or create bidirectional virtual midi ports (a port with both an associated in and out)

as far as i know you can only make an out or an in

even if you give the port the same name – it seems max won’t route midi from one to the other.

Jul 24 2012 | 12:37 am

here’s an example. this patch works fine in max (using an external DAW to loop the midi back in) but doesn’t work when saved as a standalone application. Any ideas?

If I leave the original max patch open in the background – it works!

Close the max patch, and doesn’t work.


-- Pasted Max Patch, click to expand. --

Jul 25 2012 | 8:59 pm

did you try delaying the loadbang?
maybe try to create the midi port a little later?
something like this:


-- Pasted Max Patch, click to expand. --

Jul 25 2012 | 9:11 pm

Just built standalones with your patcher and mine.
Delay was the way to go.
Your patcher don’t work because the midiin object isn’t set on AUX at startup.
Delaying loadbang solves your issue.

Jul 26 2012 | 2:30 pm

the Create MIDI Port IN & Out function in Max 6 It's work very well.
Not sure this will solve your problems but if you need to use your virtual port with out any UI selection this work for me 100%;


  1. maxmidivrport.png


Jul 26 2012 | 2:37 pm

this is basically the same thing he was doing
what is your julynessi.midiparser ?

Viewing 7 posts - 1 through 7 (of 7 total)

Forums > MaxMSP