> On 23.09.2015, at 15:09, amin...@gmail.com wrote:
>
> In SuperCollider for example, it's possible to identify which device a midi
> event came from. In SuperCollider it's called a "device ID" and searching the
> internet, a midi "device ID" is commonly referred to. The ID seems to be
> comin
On Wed, 23 Sep 2015, amin...@gmail.com wrote:
> It may not be called "device ID" in alsa-seq but my question is how
> to distinguish between midi events that came from different sources.
In Event.T there is a record field called 'source' that has the type
Address.T:
https://hackage.ha
In SuperCollider for example, it's possible to identify which device a midi
event came from. In SuperCollider it's called a "device ID" and searching the
internet, a midi "device ID" is commonly referred to. The ID seems to be coming
from the device itself (it's not e.g. a uuid assigned by SC),
On Mon, 21 Sep 2015, amin...@gmail.com wrote:
> I'm not seeing it. Can you point to the type itself, or the module it's
> in?
I still do not know what MIDI device ID you mean. Can you please tell me
the record type and field name you refer to? Is it in the Event module:
https://hackage.ha
> On Sep 21, 2015, at 15:44, Henning Thielemann
> wrote:
>
>
>> On Sat, 19 Sep 2015, amin...@gmail.com wrote:
>>
>>I've written a little thing with alsa-seq that listens out for
>> Sound.ALSA.Sequencer.Event.NoteOn messages and peforms actions based on
>> the message. Something I'm stuc
On Sat, 19 Sep 2015, amin...@gmail.com wrote:
> I've written a little thing with alsa-seq that listens out for
> Sound.ALSA.Sequencer.Event.NoteOn messages and peforms actions based on
> the message. Something I'm stuck on, though, is I can't find where the
> MIDI device id is.
What MIDI
Hey all -
I've written a little thing with alsa-seq that listens out for
Sound.ALSA.Sequencer.Event.NoteOn messages and peforms actions based on the
message. Something I'm stuck on, though, is I can't find where the MIDI device
id is. It doesn't seem to be in the "T" value for that module.
