MIDIResponder problem

[Martin Vognsen-3]

Hello

MIDIResponder only seems to repond to incoming midi from the first  
available midi device, and I need midi from the second device. I  
tried with the NoteOnResponder help test example where all args  
including src are set to nil, but I'm not getting any response when  
I'm feeding midi into the second port, which is also the second  
hardware device registered by the system. The device appears as it  
should in the source array when I do MIDIClient.sources. I'm using  
MIDIMonitor (very helpful little app) to check that the system is  
getting the incoming midi, so I'm wondering if something is not quite  
right with MIDIResponder? Does anybody have a clue? Oh, and the  
system is Leopard and it's SC 3.2.

And on a side note: According to the MIDIResponder help file I should  
be able to use the system uid (a minus followed by 10 digits) for the  
src argument. I get an error: Message 'uid' not understood. But if I  
use the index it works, meaning that I don't get errors - I'm still  
only getting input from the first port.

Thank you
Martin (without the dot)


_______________________________________________
sc-users mailing list


info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880
archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/

[Wouter Snoei-2]

Hi Martin,

In order to use multiple MIDI inputs you need to connect them by hand  
with MIDIIn.connect. When the MIDIClient initializes it shows the  
available MIDI sources and destinations in the post window. By  
default only the first one is connected. If you want to connect the  
other ones the easiest way is to first request the total number of  
sources (MIDIClient.sources.size) and then use that to connect them  
to the first destination port. Then you don't need the UID's etc. A  
bit like this:

(
MIDIClient.init;
x = MIDIClient.sources.size;
x.do({ arg i; MIDIIn.connect( i, 0 ) }); // connect all to port 0
)

This would always need to be the first thing you do, before  
activating NoteOnResponders etc.

In wslib there is also MIDIWindow, which does all this from a GUI.

hope that helps,

cheers,
Wouter

Op 26-jun-2008, om 23:31 heeft Martin Vognsen het volgende geschreven:

> Hello
>
> MIDIResponder only seems to repond to incoming midi from the first  
> available midi device, and I need midi from the second device. I  
> tried with the NoteOnResponder help test example where all args  
> including src are set to nil, but I'm not getting any response when  
> I'm feeding midi into the second port, which is also the second  
> hardware device registered by the system. The device appears as it  
> should in the source array when I do MIDIClient.sources. I'm using  
> MIDIMonitor (very helpful little app) to check that the system is  
> getting the incoming midi, so I'm wondering if something is not  
> quite right with MIDIResponder? Does anybody have a clue? Oh, and  
> the system is Leopard and it's SC 3.2.
>
> And on a side note: According to the MIDIResponder help file I  
> should be able to use the system uid (a minus followed by 10  
> digits) for the src argument. I get an error: Message 'uid' not  
> understood. But if I use the index it works, meaning that I don't  
> get errors - I'm still only getting input from the first port.
>
> Thank you
> Martin (without the dot)
>
>
> _______________________________________________
> sc-users mailing list
>
>
> info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/ 
> MusicTechnology/880
> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/

Wouter Snoei

info@...
http://www.woutersnoei.nl


_______________________________________________
sc-users mailing list


info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880
archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/

[Martin Vognsen-2]

Ah, ok great, I wasn't aware of that. Thank you, Wouter!

Den 27/06/2008 kl. 11.17 skrev Wouter Snoei:

> Hi Martin,
>
> In order to use multiple MIDI inputs you need to connect them by  
> hand with MIDIIn.connect. When the MIDIClient initializes it shows  
> the available MIDI sources and destinations in the post window. By  
> default only the first one is connected. If you want to connect the  
> other ones the easiest way is to first request the total number of  
> sources (MIDIClient.sources.size) and then use that to connect them  
> to the first destination port. Then you don't need the UID's etc. A  
> bit like this:
>
> (
> MIDIClient.init;
> x = MIDIClient.sources.size;
> x.do({ arg i; MIDIIn.connect( i, 0 ) }); // connect all to port 0
> )
>
> This would always need to be the first thing you do, before  
> activating NoteOnResponders etc.
>
> In wslib there is also MIDIWindow, which does all this from a GUI.
>
> hope that helps,
>
> cheers,
> Wouter
>
> Op 26-jun-2008, om 23:31 heeft Martin Vognsen het volgende geschreven:
>
>> Hello
>>
>> MIDIResponder only seems to repond to incoming midi from the first  
>> available midi device, and I need midi from the second device. I  
>> tried with the NoteOnResponder help test example where all args  
>> including src are set to nil, but I'm not getting any response  
>> when I'm feeding midi into the second port, which is also the  
>> second hardware device registered by the system. The device  
>> appears as it should in the source array when I do  
>> MIDIClient.sources. I'm using MIDIMonitor (very helpful little  
>> app) to check that the system is getting the incoming midi, so I'm  
>> wondering if something is not quite right with MIDIResponder? Does  
>> anybody have a clue? Oh, and the system is Leopard and it's SC 3.2.
>>
>> And on a side note: According to the MIDIResponder help file I  
>> should be able to use the system uid (a minus followed by 10  
>> digits) for the src argument. I get an error: Message 'uid' not  
>> understood. But if I use the index it works, meaning that I don't  
>> get errors - I'm still only getting input from the first port.
>>
>> Thank you
>> Martin (without the dot)
>>
>>
>> _______________________________________________
>> sc-users mailing list
>>
>>
>> info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de: 
>> 8888/MusicTechnology/880
>> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
>> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
>
> Wouter Snoei
>
> info@...
> http://www.woutersnoei.nl
>
>
> _______________________________________________
> sc-users mailing list
>
>
> info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/ 
> MusicTechnology/880
> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/

_______________________________________________
sc-users mailing list


info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880
archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/

[James Harkins-2]

MIDIPort in my library also automatically connects to multiple ports.

You can also reorder them, e.g. if your MIDI devices list as

MIDI Sources: 

MIDIEndPoint("IAC Driver", "Bus 1")

MIDIEndPoint("FastLane USB #3", "Port A")

MIDIEndPoint("FastLane USB #3", "Port B")

MIDI Destinations: 

MIDIEndPoint("IAC Driver", "Bus 1")

MIDIEndPoint("FastLane USB #3", "Port A")

MIDIEndPoint("FastLane USB #3", "Port B")

you could do "MIDIPort.init([1, 2])" and then the sources list like this (for my lib only, though... doesn't carry over to MIDIResponder in general):

MIDIPort.sources.do(_.postln)

MIDIEndPoint("FastLane USB #3", "Port A")

MIDIEndPoint("FastLane USB #3", "Port B")

MIDIEndPoint("IAC Driver", "Bus 1")

hjh

: H. James Harkins

: jamshark70@...

: http://www.dewdrop-world.net

.::!:.:.......:.::........:..!.::.::...:..:...:.:.:.:..:

"Come said the Muse,

Sing me a song no poet has yet chanted,

Sing me the universal."  -- Whitman

[nescivi]

Hiho,

to be complete: after 3.2 we fixed this and MIDIresponders automatically
connect to all ports.

sincerely,
Marije

On Friday 27 June 2008 05:17:36 Wouter Snoei wrote:

> Hi Martin,
>
> In order to use multiple MIDI inputs you need to connect them by hand
> with MIDIIn.connect. When the MIDIClient initializes it shows the
> available MIDI sources and destinations in the post window. By
> default only the first one is connected. If you want to connect the
> other ones the easiest way is to first request the total number of
> sources (MIDIClient.sources.size) and then use that to connect them
> to the first destination port. Then you don't need the UID's etc. A
> bit like this:
>
> (
> MIDIClient.init;
> x = MIDIClient.sources.size;
> x.do({ arg i; MIDIIn.connect( i, 0 ) }); // connect all to port 0
> )
>
> This would always need to be the first thing you do, before
> activating NoteOnResponders etc.
>
> In wslib there is also MIDIWindow, which does all this from a GUI.
>
> hope that helps,
>
> cheers,
> Wouter
>
> Op 26-jun-2008, om 23:31 heeft Martin Vognsen het volgende geschreven:
> > Hello
> >
> > MIDIResponder only seems to repond to incoming midi from the first
> > available midi device, and I need midi from the second device. I
> > tried with the NoteOnResponder help test example where all args
> > including src are set to nil, but I'm not getting any response when
> > I'm feeding midi into the second port, which is also the second
> > hardware device registered by the system. The device appears as it
> > should in the source array when I do MIDIClient.sources. I'm using
> > MIDIMonitor (very helpful little app) to check that the system is
> > getting the incoming midi, so I'm wondering if something is not
> > quite right with MIDIResponder? Does anybody have a clue? Oh, and
> > the system is Leopard and it's SC 3.2.
> >
> > And on a side note: According to the MIDIResponder help file I
> > should be able to use the system uid (a minus followed by 10
> > digits) for the src argument. I get an error: Message 'uid' not
> > understood. But if I use the index it works, meaning that I don't
> > get errors - I'm still only getting input from the first port.
> >
> > Thank you
> > Martin (without the dot)

_______________________________________________
sc-users mailing list


info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880
archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/

[Martin Vognsen-2]

Ok, confession: I haven't done SVN since February, and didn't see any  
explicit mention of NoteOnResponder in the ChangeLog, so I missed  
that. But indeed, it's fixed in the latest Wesleyan, and that makes  
me very happy! Thanks for the tip.

Den 27/06/2008 kl. 17.00 skrev nescivi:

> Hiho,
>
> to be complete: after 3.2 we fixed this and MIDIresponders  
> automatically
> connect to all ports.
>
> sincerely,
> Marije
>
> On Friday 27 June 2008 05:17:36 Wouter Snoei wrote:
>> Hi Martin,
>>
>> In order to use multiple MIDI inputs you need to connect them by hand
>> with MIDIIn.connect. When the MIDIClient initializes it shows the
>> available MIDI sources and destinations in the post window. By
>> default only the first one is connected. If you want to connect the
>> other ones the easiest way is to first request the total number of
>> sources (MIDIClient.sources.size) and then use that to connect them
>> to the first destination port. Then you don't need the UID's etc. A
>> bit like this:
>>
>> (
>> MIDIClient.init;
>> x = MIDIClient.sources.size;
>> x.do({ arg i; MIDIIn.connect( i, 0 ) }); // connect all to port 0
>> )
>>
>> This would always need to be the first thing you do, before
>> activating NoteOnResponders etc.
>>
>> In wslib there is also MIDIWindow, which does all this from a GUI.
>>
>> hope that helps,
>>
>> cheers,
>> Wouter
>>
>> Op 26-jun-2008, om 23:31 heeft Martin Vognsen het volgende  
>> geschreven:
>>> Hello
>>>
>>> MIDIResponder only seems to repond to incoming midi from the first
>>> available midi device, and I need midi from the second device. I
>>> tried with the NoteOnResponder help test example where all args
>>> including src are set to nil, but I'm not getting any response when
>>> I'm feeding midi into the second port, which is also the second
>>> hardware device registered by the system. The device appears as it
>>> should in the source array when I do MIDIClient.sources. I'm using
>>> MIDIMonitor (very helpful little app) to check that the system is
>>> getting the incoming midi, so I'm wondering if something is not
>>> quite right with MIDIResponder? Does anybody have a clue? Oh, and
>>> the system is Leopard and it's SC 3.2.
>>>
>>> And on a side note: According to the MIDIResponder help file I
>>> should be able to use the system uid (a minus followed by 10
>>> digits) for the src argument. I get an error: Message 'uid' not
>>> understood. But if I use the index it works, meaning that I don't
>>> get errors - I'm still only getting input from the first port.
>>>
>>> Thank you
>>> Martin (without the dot)
>
> _______________________________________________
> sc-users mailing list
>
>
> info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/ 
> MusicTechnology/880
> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/

_______________________________________________
sc-users mailing list


info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880
archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/

[nescivi]

On Friday 27 June 2008 17:24:00 Martin Vognsen wrote:
> Ok, confession: I haven't done SVN since February, and didn't see any
> explicit mention of NoteOnResponder in the ChangeLog, so I missed
> that. But indeed, it's fixed in the latest Wesleyan, and that makes
> me very happy! Thanks for the tip.


Actually, the change was in MIDIClient.init...
which now takes all available ports if no arguments are given to it.

mention of that should be in the svn log...

sincerely,
Marije

> Den 27/06/2008 kl. 17.00 skrev nescivi:
> > Hiho,
> >
> > to be complete: after 3.2 we fixed this and MIDIresponders
> > automatically
> > connect to all ports.

_______________________________________________
sc-users mailing list


info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880
archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/