Hi The following is from "polyfony.ck": // device to open (see: chuck --probe) 0 => int device; // get from command line if( me.args() ) me.arg(0) => Std.atoi => device; MidiIn min; MidiMsg msg; // try to open MIDI port (see chuck --probe for available devices) if( !min.open( device ) ) me.exit(); I see and use this all the time; creating midi out/in ports by connecting to something. But how can I create a midi port that's not connected to anything? -- Atte http://atte.dk http://modlys.dk
I see and use this all the time; creating midi out/in ports by connecting to something. But how can I create a midi port that's not connected to anything?
Just omit the ".open()". I don't know why you'd want to do that though as those objects just abstract a port. What are you after here? Kas.
Kassen wrote:
Just omit the ".open()".
That doesn't create any ports...
I don't know why you'd want to do that though as those objects just abstract a port.
What are you after here?
I'm running under linux, normally with jack. Most other programs with midi connectivity create non-connected midi ports on startup, then you connect them to whatever you need afterwords. As to why I wanna do that: First I'd like to make the connections through jack and second I'd like to start my chuck script *before* the applications it should be connected to are started. Since it's just alsa seq ports, they should be possible to create. -- Atte http://atte.dk http://modlys.dk
Atte wrote:
That doesn't create any ports...
No, it doesn't. I didn't understand the question.
I'm running under linux, normally with jack. Most other programs with midi connectivity create non-connected midi ports on startup, then you connect them to whatever you need afterwords.
Got it. Then I don't know. I don't think that's possible right now. Kas.
participants (2)
-
Atte André Jensen -
Kassen