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

PrevNext  Index
DateFri, 01 Apr 2011 10:00:04 +0200
From Stéphane Letz <[hidden] at grame dot fr>
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-Uptorbenh 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
Le 1 avr. 2011 à 09:34, Devin Anderson a écrit :

> On Thu, Mar 31, 2011 at 1:13 AM, Devin Anderson
> <[hidden]> wrote:
> 
>>    typedef struct _jack_midi_event {
>>        jack_nframes_t time;
>>        size_t size;
>>        union {
>>            jack_midi_data_t *buffer;
>>            const jack_midi_stream_t *stream;
>>        };
>>    } jack_midi_event_t;
> 
> I forgot to mention that while my message in August suggested the
> above, the proposal I'm making would actually have the definition of
> 'jack_midi_event_t' changed to:
> 
> typedef struct _jack_midi_event {
>    jack_nframes_t time;
>    size_t size;
>    union {
>        jack_midi_data_t *buffer;
>        const jack_midi_blob_t *blob;
>    };
> } jack_midi_event_t;
> 
> ... where it's still the case that (size == 0) to indicate that the
> event contains a blob object.
> 
> Just clarifying in case that confused anyone.
> 
> -- 
> Devin Anderson
> devin (at) charityfinders (dot) com

I guess I would help to understand the new API if you provide some "pseudo" example of a JACK client using it.

Stéphane
PrevNext  Index

1301644819.27203_0.ltw:2,a <DC50D283-3319-41EA-9969-76856E0FF726 at grame dot fr>