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

PrevNext  Index
DateFri, 06 May 2011 00:34:04 +0900
From Sean Beeson <[hidden] at gmail dot com>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
Cc[hidden] at jackaudio dot org
In-Reply-ToPaul Davis Re: [Jack-Devel] C++ development of Jack enabled applications--particularly SysExec
Follow-UpPaul Davis Re: [Jack-Devel] C++ development of Jack enabled applications--particularly SysExec
On Fri, May 6, 2011 at 12:17 AM, Paul Davis <[hidden]>wrote:

> On Thu, May 5, 2011 at 10:34 AM, Paul Davis <[hidden]>
> wrote:
> > On Thu, May 5, 2011 at 10:31 AM, Sean Beeson <[hidden]>
> wrote:
> >
> > The key point is that you cannot currently do what you want to do with
> > the JACK MIDI API. Its that simple. Devan has made some reasonable
> > looking proposals on extending the API to make this sort of thing
> > possible, but they are not currently implemented and as far as I know,
> > nobody is working on even a test implementation.
>
> I should probably be a little clearer too.
>
> It *is* possible to deliver large sysex (or other) messages via JACK
> MIDI, but the API does not provide you any help doing so. You will
> have to break the message into chunks and send a bit out at every
> process() callback. Most people would view this as "cannot be done" -
> others might see it as a way to spend a glorious spring weekend having
> fun :)
>
> --p
>

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?

-S
PrevNext  Index

1304609775.26852_0.ltw:2,a <BANLkTinoWH7xHA1=w=wFcKRE-hpfPkW6fg at mail dot gmail dot com>