That hot-plugging for jack is really a good idea. On Saturday 30 January 2010 19:00:17 Paul Davis wrote: > this all sounds great except for one little technical implementation > detail: JACK needs something to *drive* the graph. > this is why the driver "client" has a special place in JACK's heart. I don't think its a problem: The "clients" that are actually hardware, drive the jack-clock/-loop. No such client, no driving jack. Unless freewheeling gets activated. Will be a bit of a problem to represent that gui-wise. Thinking one step further, all available devices could then plug into jack when wanted/needed, from all kinds of hardware. This would mean mostly one pci/onboard alsa/oss soundcard will pop up and all usb/firewire devices too. While this reduces the chance of jack running without a device driving it, this highly enhances the chance of xruns when the clocks of the devices aren't synced. Maybe that can be "fixed" by selecting one device as the master and do resampling for the others... Have fun, Arnold
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
