Re: [Jack-Devel] C++ development of Jack enabled applications--particularly SysExec

On Fri, May 6, 2011 at 12:39 AM, Paul Davis <[hidden]>wrote:

> On Thu, May 5, 2011 at 11:34 AM, Sean Beeson <[hidden]> wrote:
>
> > Well, hmm, would that be coming and going from both ends? That is, will I
> > have that ability from the hardware, which has no way of controlling the
> > rate or size of data being sent? It just dumps it. Sorry for the very
> green
> > question, but how big of chuck is Jack going to handle before it discards
> > stuff in bytes? If you know?
>
> the input side is bad news: the existing bridges (a2jmidid, -Xseq and
> -Xraw) will either throw away or truncate long messages.
>
> on the output side, you can call jack_port_type_buffer_size (client,
> JACK_DEFAULT_MIDI_TYPE) to get the buffer size or you can just keep
> calling jack_midi_event_reserve() until it fails (which you should
> likely do anyway)
>

Thanks, I know what to look for now. Perhaps I just have to see if I can
help Devon move his proposal along. :-)

-S

1304610350.27430_0.ltw:2,a <BANLkTi=3Nq8DELo1Xim-H0LZKmjb9MUQ5g at mail dot gmail dot com>