Re: [LAD] Deciphering jack-smf-utils -- Jack MIDI stuff

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: M Donalies <ingeniousnebbish@...>
Cc: <linux-audio-dev@...>
Date: Monday, February 18, 2013 - 1:33 pm

--bcaec554dbba77abf804d5ffc4f9
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Feb 18, 2013 at 8:35 AM, M Donalies wrote:

> On Sunday 17 February 2013 08:21:51 Paul Coccoli wrote:

because the client may not want to get all the data at once.

ardour, for example, breaks up the process() cycle internally to deal with
"global" scheduled events. so it may ask for the first N frames, then
another M, then another P frames until everything is done.

there was another reason at one time too, but the internally engineering of
JACK has eliminated that one.

--bcaec554dbba77abf804d5ffc4f9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 18, 2013 at 8:35 AM, M Donal=
ies <ingeniousnebbish@cox.net> wrote:
On Sunday 17 February 2013 08:21:51 Paul Coccoli wrote:

wrote:
put(), wherein we find:
nframes);
ch

Yes, and that's the output_port arg, but what's with nframes?=
Why isn't the
function simply: =A0jack_port_get_buffer(output_port) ?because the client may not want to get all the data at once.a=
rdour, for example, breaks up the process() cycle internally to deal with &=
quot;global" scheduled events. so it may ask for the first N frames, t=
hen another M, then another P frames until everything is done.
there was another reason at one time too, but the internally engineerin=
g of JACK has eliminated that one.

--bcaec554dbba77abf804d5ffc4f9--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAD] Deciphering jack-smf-utils -- Jack MIDI stuff, M Donalies, (Sun Feb 17, 3:06 am)
Re: [LAD] Deciphering jack-smf-utils -- Jack MIDI stuff, Paul Coccoli, (Sun Feb 17, 1:21 pm)
Re: [LAD] Deciphering jack-smf-utils -- Jack MIDI stuff, Paul Davis, (Mon Feb 18, 1:33 pm)