Re: [Jack-Devel] Proposal: JACK MIDI API extension for system exclusive messages

PrevNext  Index
DateFri, 01 Apr 2011 11:57:01 -0700
From Devin Anderson <[hidden] at charityfinders dot com>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
CcJack devel <[hidden] at lists dot jackaudio dot org>
In-Reply-ToPaul Davis Re: [Jack-Devel] Proposal: JACK MIDI API extension for system exclusive messages
Follow-UpPaul Davis Re: [Jack-Devel] Proposal: JACK MIDI API extension for system exclusive messages
On Fri, Apr 1, 2011 at 11:33 AM, Paul Davis <[hidden]> wrote:

> there are two rather significant issues here.
>
> 1) why would you structure a program like this when clearly the user
> knows where the BOSS GT-10 is connected?

It's just a simple example to illustrate the use of the proposed MIDI
blobs.  The example itself isn't all that practical, but I think it
serves its purpose.

A more practical and complex example (one I've been envisioning for
the past few months) would be a MIDI editor for a piece of external
hardware that uses the JACK session API to load and save patches.  I'd
love to open a JACK session, and have my Blofeld automatically load
the patches associated with the session. :)

> 2) is JACK MIDI an appropriate API for this sort of thing?

I think it could be very useful for this sort of thing.

> one can certainly make the argument that a relatively consistent API
> for all MIDI I/O is a good thing, and clearly you feel this way having
> put the work into this proposed API. but consider how much simpler
> this program would be with a simple blocking read/write API for MIDI
> when combined with the user knowing there the GT-10 is connected?

I'm not convinced it would be much simpler.

-- 
Devin Anderson
devin (at) charityfinders (dot) com

CharityFinders - http://www.charityfinders.com/
synthclone - http://synthclone.googlecode.com/
PrevNext  Index

1301684245.11868_0.ltw:2,a <AANLkTikKiHyeahLURLcKMvENB2bhHK6PN3UCwNp8Fypj at mail dot gmail dot com>