On Sat, 2009-04-18 at 16:45 +0200, Lennart Poettering wrote: > On Fri, 17.04.09 19:22, Callum Lerwick (seg haxxed com) wrote: > > If the user hasn't set a preference, such as on the first run, use Jack > > if it's running, otherwise fall back on Pulse, otherwise fall back on > > ALSA. Easy. There should be a simple obvious UI (Not hidden in the ! # > > $ing preferences) that clearly indicates the current output and allows > > you to dynamically change the output if it chooses wrong, with a sticky > > preference for the next time. > > It's not that easy. There's autospawning of both PA and Jack. Hence > checking 'if it is running' doesn't really work. Why is Jack autospawning now? Bletch. Autospawn is mostly irrelevant. If Pulse is autospawning properly, presumably the user wants to use it. Jack is a bit different, presumably we'd want some kind of global (to the user session) "I want to use Jack" preference. If it's not enabled, don't touch Jack. And like I said, let the easy obvious UI allow the user to sort things out. Jack isn't dynamic last I checked, it likes to lock on to one and *only* one device for it's lifetime. Making it a not so great candidate for autospawning without being configured first. Its design goal of super-low latency doesn't allow for multiple devices, as they aren't going to be perfectly in sync unless they're specialized pro-gear. So basically, Jack should not be used until a user checks an "Use Jack" checkbox somewhere and picks a device to use.
Description: This is a digitally signed message part