I can imagine such a system, but it would require a fair amount of user configuration, and I think the additional value of this would be pretty narrow (for a fairly large API cost). On Thu, May 3, 2012 at 9:55 AM, Alistair MacDonald <al@signedon.com> wrote: > >> 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 17:34:53 UTC