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

PrevNext  Index
DateFri, 01 Apr 2011 14:33:04 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToDevin Anderson <[hidden] at charityfinders dot com>
CcJack devel <[hidden] at lists dot jackaudio dot org>
In-Reply-ToDevin Anderson Re: [Jack-Devel] Proposal: JACK MIDI API extension for system exclusive messages
Follow-UpDevin Anderson Re: [Jack-Devel] Proposal: JACK MIDI API extension for system exclusive messages
On Fri, Apr 1, 2011 at 2:13 PM, Devin Anderson <[hidden]> wrote:
> On Fri, Apr 1, 2011 at 1:00 AM, Stéphane Letz <[hidden]> wrote:
>
>> I guess I would help to understand the new API if you provide some
>> "pseudo" example of a JACK client using it.
>
> Good idea. :)
>
> Here's an example that sends out an identify request message to a BOSS
> GT-10, and waits for an identity reply containing the software
> revision level on the GT-10.  I've omitted error checking to simplify
> the code.

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?
2) is JACK MIDI an appropriate API 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?
PrevNext  Index

1301682805.10567_0.ltw:2,a <AANLkTi=adLXh+t1hM4OoL72iPw=cZBOUhuzWir5akgEK at mail dot gmail dot com>