Re: [sc-users] [linux][quarks] VoicerMIDISocket problem

[krgn <k.gebbert@xxxxxxxxx>]

Odd. Let's check for a uid mismatch.

MIDIPort.ports.keys; // should be a list of uids

MIDIClient.sources.collect(_.uid); // should be the same uids (order doesn't matter)

returns:

 

Set[ 1310720, 0, 1, 8585216, 8519681, 917504 ]

[ 0, 1, 917504, 1310720, 8519681, 8585216 ]

so, although in a different order, these are of the same size and contain the same uid's

Also check these:

k.parent; // should be a MIDIChannel

k.parent.channel; // should display the device and channel number

k.parent.sockets; // should be [ a VoicerMIDISocket ]

 
this gives me:

a MIDIChannel

MIDIChannelIndex('System-Timer' : 'System-Timer', 0)

[ a VoicerMIDISocket ]

not sure if the 'System-Timer' is the correct one. Should this be set to the port sc will receive midi froM?

MIDIPort.ports[MIDIPort.sources[0].uid]; // should be a MIDIPort

MIDIPort.ports[MIDIPort.sources[0].uid][0]; // should be a MIDIChannel

MIDIPort.ports[MIDIPort.sources[0].uid][0].channel;  // should display the device and channel number

 a MIDIPort

a MIDIChannel

MIDIChannelIndex('System-Timer' : 'System-Timer', 0)

Strange one, I'd like to track it down.

 

me too, it looks like a very useful framework. In the meantime I've had quite some fun though using Voicer only and the responder classes - works quite well already, although its more work to setup CC's etc. 

best,

karsten