Subject: Re: [linux-audio-dev] Project: modular synth editor
From: Fons Adriaensen (fons.adriaensen_AT_skynet.be)
Date: Mon Jan 19 2004 - 17:09:14 EET
On Mon, Jan 19, 2004 at 02:56:52AM +0100, Fons Adriaensen wrote:
> The point is IMHO that JACK is great for making audio connections between
> independent Linux processes - that what it's designed for, and what it does
> extremely well (BTW congrats to Paul and the whole JACK team for the Open
> Source Award). But using JACK for internal connections is pure overkill,
> and I'm not even sure it will work as you expect.
Sorry to follow upp on my own ramblings, but I'm getting more and more
convinced that using JACK for internal connections in a modular synth will
not work as expected.
For example, take the patch
JACK -> A -> JACK -> B -> JACK
where A and B are two processing modules.
If A and B are inside the same JACK client, what will happen ?
Will jack use a single buffer for A-out and B-in (this is what you'd
expect in a modular synth), or will it copy the previous A-out to B-in
before calling your process callback, thereby introducing one cycle
delay ?
-- FA
This archive was generated by hypermail 2b28 : Mon Jan 19 2004 - 17:35:43 EET