18 Feb
2013
18 Feb
'13
2:07 p.m.
On Sunday 17 February 2013 08:21:51 Paul Coccoli wrote:
Yes, and that's the output_port arg, but what's with nframes? Why isn't the
function simply: jack_port_get_buffer(output_port) ?
Oh, I get it. I was reading "last" as "previous" as in currentCycle -
1.
--
7:8
On Sat, Feb 16, 2013 at 10:33 PM, M Donalies
<ingeniousnebbish(a)cox.net>
wrote:
process_callback() calls process_midi_output(), wherein we find:
port_buffer = jack_port_get_buffer(output_port, nframes);
Why the nframes parameter? Is there a separate buffer area for each
frame?
There's a separate buffer for each port. A little later
in the same function we have:
last_frame_time = jack_last_frame_time(jack_client);
Is this the time of the end of the last process cycle?
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.