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

On Fri, Apr 1, 2011 at 11:50 AM, Paul Davis <[hidden]> wrote:
> On Fri, Apr 1, 2011 at 2:42 PM, Pedro Alves <[hidden]> wrote:
>
>> I still think that it's a fundamental design bug
>> to assume where the sysex's size is known in advance, and hence
>> that the blob can and should be created in one go.  Unless you were
>> planning on making that `size' be a hint and allowing
>> jack_midi_blob_write to grow the blob?
>
> isn't that what blobstream is for?

No.  The 'jack_midi_blobstream_t' type would allow file-like
operations on blobs.

I don't envision blobs growing dynamically.  A client knows the size
of sysex messages it's going to send, and should be able to deal with
received sysex messages in another thread if memory allocation is
necessary.

The only exception would be MIDI drivers, which have no idea about the
size of sysex messages they might receive.  In this case, I think
command-line arguments should be used to specify the number of blobs
and the size of the blobs that a MIDI driver should create before
starting.

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

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

1301684671.12286_0.ltw:2,a <AANLkTikAN-=WAqNP8=W6y3DQfDpYrErzjM21haBXoYSz at mail dot gmail dot com>