| |||||||||||||
Interview with Lennart Poettering (LinuxFR.org)Interview with Lennart Poettering (LinuxFR.org)Posted Jul 6, 2011 22:45 UTC (Wed) by tialaramex (subscriber, #21167)In reply to: Interview with Lennart Poettering (LinuxFR.org) by drag Parent article: Interview with Lennart Poettering (LinuxFR.org)
Yes, pro-hardware is capable of using an external clock. So you pick one reference clock and all your gear keeps time with that.
Most consumer hardware does not offer this capability, you will need to investigate nasty hacks if you want to try to strap three cheap PCI soundcards together as an alternative to buying one six channel pro card.
(Log in to post comments)
JACK Posted Jul 6, 2011 22:53 UTC (Wed) by tialaramex (subscriber, #21167) [Link]
Oh, I forgot to address the actual point you made. No, JACK only works with one device.
If you have several physical devices which are genuinely sync'd you can just use ALSA to weave them together. If they aren't synchronised bad stuff may happen.
The reason for working with one device is that JACK's graph execution goes like this:
1. Interrupt from hardware indicates that, say, 128 frames are ready
If JACK was willing to work with more than one device, which interrupt does it wait for? What does it do with parts of the graph which require data from more than one input device? Or send data to more than one output device?
Lots of complexity, for a corner case no professional audio people care about (they either have only one device, or their devices can be clock-locked and woven into a single virtual device) and no consumers have the gear to test.
|
|||||||||||||