Correction to pervious post: when I talk about audio, I mean MIDI.<div><br><br><div class="gmail_quote">On Sun, Oct 31, 2010 at 1:54 AM, Stefan Blixt <span dir="ltr">&lt;<a href="mailto:stefan.blixt@gmail.com">stefan.blixt@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I have been able to connect to the same device in the past, and send messages from two ChucK shreds to one MIDI thing. Have you tried if it works even if it just shows up as one device in Jack?<div>
<br></div><div><div>What you call &quot;port&quot; I usually call &quot;device&quot;. 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(&lt;number&gt;).</div>

<div><br></div><div>You probably know this, but don&#39;t confuse these with MIDI channels, which are 16 to a device (or port) and are specified inside each MIDI message that you send.</div><div><br></div><div>/Stefan<div>
<div></div><div class="h5"><br>
<br><div class="gmail_quote">On Sat, Oct 30, 2010 at 9:43 PM, Thomas Girod <span dir="ltr">&lt;<a href="mailto:girodt@gmail.com" target="_blank">girodt@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

hi<br>
<div><br>
&gt; That one will open port 0 twice. This should mean that ChucK will open it once,<br>
&gt; then have two internal shreds that both listen to the same port. I think this<br>
&gt; should help;<br>
&gt;<br>
&gt; %&gt; chuck-jack <a href="http://test.ck:0" target="_blank">test.ck:0</a> <a href="http://test.ck:1" target="_blank">test.ck:1</a><br>
&gt;<br>
&gt; That should make ChucK open two ports, one for each shred. The first shred gets<br>
&gt; port 0, then second gets port 1 That is, of course, assuming nothing is<br>
&gt; horribly wrong in ChucK or in Linux.<br>
&gt;<br>
&gt; How far does that get you?<br>
&gt; Kas.<br>
<br>
</div>That&#39;s what I thought too, as it seemed logical. but it doesn&#39;t work.<br>
Let&#39;s say I don&#39;t have any alsa-midi apps running. in qjackctl, I only<br>
have &quot;Midi Through&quot; (in and out)<br>
<br>
% chuck-jack <a href="http://test.ck:0" target="_blank">test.ck:0</a><br>
<br>
this will create a new MidiIn and connect it to &quot;Midi Through (out)&quot;.<br>
<br>
% chuck-jack <a href="http://test.ck:1" target="_blank">test.ck:1</a><br>
<br>
this won&#39;t work, with this message :<br>
<br>
&gt; [chuck]: MidiIn: couldn&#39;t open MIDI port 1...<br>
<br>
my conclusion: the port parameter to the MidiIn.open() function is not<br>
the number of the port you open, but the port number of the source or<br>
the target to which it is supposed to be connected.<br>
<br>
... which isn&#39;t that useful, in my opinion.<br>
<br>
tom<br>
<div><div></div><div>_______________________________________________<br>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu" target="_blank">chuck-users@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br></div></div>-- <br>Release me, insect, or I will destroy the Cosmos!<br>
</div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Release me, insect, or I will destroy the Cosmos!<br>
</div>