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: Sunday, February 17, 2013 - 1:21 pm

On Sat, Feb 16, 2013 at 10:33 PM, M Donalies wrote:

IIRC, a "frame" in JACK parlance is one sample, so 1/44100 in your
example. The process callback is called regardless of transport
state. You call a function (jack_transport_query I think? I don't
have any of my code in front of me right now) to get transport state
and timing/tempo information (including bar:beat:tick).

> process_callback() calls process_midi_output(), wherein we find:

There's a separate buffer for each port.

> A little later in the same function we have:

Not sure about this one. The docs say: "the precise time at the start
of the current process cycle" which should be the same time as the
start of the current process cycle, I would think.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev

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)