W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Re: MIDI proposal implemented

From: Alistair MacDonald <al@signedon.com>
Date: Thu, 3 May 2012 12:55:07 -0400
Message-ID: <CAJX8r2nChDPcHoguy9sVsYmmOxTwXeDNEi5t4HECrP0WfEo4jA@mail.gmail.com>
To: Chris Wilson <cwilso@google.com>
Cc: robert@ocallahan.org, Jussi Kalliokoski <jussi.kalliokoski@gmail.com>, public-audio@w3.org
>
>
> A significant use case of the MIDI API is a software sequencer.  At the
> height of my basement studio, I had approximately sixteen MIDI I/O devices
> - that is, sixteen inputs plus sixteen outputs, with sixteen MIDI channels
> each.  My sequencer had to be able to independently address these and keep
> them organized - otherwise, every time I sat down at the computer and
> opened up a project, I would have had to spend a significant chunk of time
> selecting each device in the system UI.
>
>
This problem is exacerbated these days with more MIDI devices being
connected by USB hubs. Devices tend to get switched between ports a lot, so
you would not necessarily be able to rely on the devices being in the same
order as before, which (I think) would have been one way to minimize that
issue.

Can we have some way of the user "allowing" devices to be enumerable for
specific domains?

I could imagine a system where I allowed "http://awesome-synth.com" to
enumerate "MIDIKeyboard1 and MIDIKeyboard2", but neither of these devices
would be enumerable by "http://VideoDJ.net" - which I only allowed to see
my "Akai APC 40" controller for triggering video clips.
Received on Thursday, 3 May 2012 16:55:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 May 2012 16:55:37 GMT