On Sun, May 4, 2008 at 11:52 PM, nescivi <
nescivi@...> wrote:
On Sunday 04 May 2008 09:44:58 felix wrote:
> what changed in that checkin is that it calls MIDIClient.list which is the
> correct way to find out how many ins/outs you have.
(on os x)
So the MIDI philosophy on Linux is slightly different then on Mac
right.
I wonder what the temporary solution should be to get MIDIIn.init working again for linux.
should we put a platform check directly into MIDIIn.init ? and then what can be done ? perhaps just skip the .list and go straight to connect initialize. this just means that on linux you have to specify how many ins and outs you want.
sorry, but I'm not in much of a position to suggest the best solution.
for those wondering:
the bug I was fixing was to make MIDIIn.init automatically connect to all possible os x ports.
A possible solution would be to add a primitive to initialize just the
connection with the sequencer without opening any ports. After that any other
methods can be used.
sincerely,
Marije
_______________________________________________
Sc-devel mailing list
Sc-devel@...
http://lists.create.ucsb.edu/mailman/listinfo/sc-devel
