DRKOSS

Hi - having trouble with virtual midi ports.

works great in Max 6 on OSX, using the message

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.

virtual-midi-ports

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.

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!

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?

maybe try to create the midi port a little later?

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

Just built standalones with your patcher and mine.

Your patcher don't work because the midiin object isn't set on AUX at startup.

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.
Cheers


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%;

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%;

this is basically the same thing he was doing

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


DRKOSS, thank you very much for your patch!

Because ports "from Max" didn't work (I don't know why, there were "disabled") I created a new MIDI port with your patch and transmit MIDI messages from Max to Ableton Live.

I didn't know that Max can create virtual MIDI ports!

Because ports "from Max" didn't work (I don't know why, there were "disabled") I created a new MIDI port with your patch and transmit MIDI messages from Max to Ableton Live.

I didn't know that Max can create virtual MIDI ports!

They make not much sense because they are available only

after app started and created them - that is useless.

On Mac one can create any number of IAC midi busses, which are then

permanently active and can be used in any app midi setup.

So why bother with that useless virtual midi ports ?

Virtual midi ports are Mac only.
They make not much sense because they are available only
after app started and created them - that is useless.
On Mac one can create any number of IAC midi busses, which are then
permanently active and can be used in any app midi setup.

So why bother with that useless virtual midi ports ?
