What you call "port" I usually call "device". A device is either Jack, or an audio interface or some other sound thing. You see these listed when you run chuck --probe, along with their respective device number, which is what you give to min.open(<number>).

You probably know this, but don't confuse these with MIDI channels, which are 16 to a device (or port) and are specified inside each MIDI message that you send.

/Stefan

On Sat, Oct 30, 2010 at 9:43 PM, Thomas Girod <girodt@gmail.com> wrote:

hi

> That one will open port 0 twice. This should mean that ChucK will open it once,
> then have two internal shreds that both listen to the same port. I think this
> should help;
>
> %> chuck-jack test.ck:0 test.ck:1
>
> That should make ChucK open two ports, one for each shred. The first shred gets
> port 0, then second gets port 1 That is, of course, assuming nothing is
> horribly wrong in ChucK or in Linux.
>
> How far does that get you?
> Kas.

That's what I thought too, as it seemed logical. but it doesn't work.
Let's say I don't have any alsa-midi apps running. in qjackctl, I only
have "Midi Through" (in and out)

% chuck-jack test.ck:0

this will create a new MidiIn and connect it to "Midi Through (out)".

% chuck-jack test.ck:1

this won't work, with this message :

> [chuck]: MidiIn: couldn't open MIDI port 1...

my conclusion: the port parameter to the MidiIn.open() function is not
the number of the port you open, but the port number of the source or
the target to which it is supposed to be connected.

... which isn't that useful, in my opinion.

tom

_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

--
Release me, insect, or I will destroy the Cosmos!