On Mon, Dec 31, 2012 at 9:47 AM, Len Ovens <len@xxxxxxxxxxxxx> wrote:
this is not true, if they are clock-synced.
if they are not clock synced, then yes.
Quite honestly, it does not seem to be something that _should_ be done by
On Sun, December 30, 2012 7:12 pm, Devin Anderson wrote:
>
> JACK *could* deal with this issue, but:
>
> 1.) It would be better if the functionality was independent of JACK.
> 2.) I don't think the issue is JACK's responsibility.
ALSA either, because properly joining two devices would mean an extra
buffer (and latency).
this is not true, if they are clock-synced.
It seems that the reality is that each device needs
to be dealt with as a separate device. So if it is not Jack's problem then
a second jacklike server that exposes the ports as jack clients is needed
and expected. So using something like zita-a2j would be the "correct" way
of doing things.
if they are not clock synced, then yes.
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
