29 Apr
2010
29 Apr
'10
12:07 p.m.
From my experience it's a question of client
design.
To loop a jack-client in a other jack-client there must be explicit
call's to the jack_buffer. Mean when I send out the data to the
jack_buffer, to a other client, I must make again a call (in the same
callback process) to the jack_buffer to recive the data.
port_1(get_buffer) -> outside_client -> port_2 (get_buffer)
Most jack applications be designed to receive the buffer for all ports
in one call.
for (int i = 0; i < 2; i++)
gInChannel[i] = (float
*)jack_port_get_buffer(input_ports[i], nframes);
process loop;
for (int i = 2; i < gNumInChans; i++)
gInChannel[i] = (float
*)jack_port_get_buffer(input_ports[i], nframes);
greats hermann
Am Donnerstag, den 29.04.2010, 13:44 +0400 schrieb Louigi Verona:
Well, from what Paul said it appears it is not
Qtractor, it is the
same with Ardour and basically just any loop connections setup.
Or am I getting it incorrectly? Let's wait for what Paul has to say %)
On Thu, Apr 29, 2010 at 1:32 PM, Ralf Mardorf
<ralf.mardorf(a)alice-dsl.net> wrote:
Louigi Verona wrote:
My version is 0.44, I think. pretty late one, I
compiled ot from git in February or January.
I can try another version or another app for that
matter. But let Paul tell us if it makes sense at all.
I guess Rui programmed buggy for Qtractor, it wasn't a fault
for JACK1 or JACK2. Perhaps 4.4.5+ is needed.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev