Re: [Jack-Devel] C++ development of Jack enabled applications--particularly SysExec
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)
1304610067.27235_0.ltw:2,a <BANLkTimH6DEid8W5D4q2JM6JyHFfBzB4ew at mail dot gmail dot com>