|--==> Eduardo Marcel writes: EM> On Tue, 2006-02-14 at 09:01 +0900, Junichi Uekawa wrote: >>Hi, EM> ... >>Here is a question: Do we want to start jack if it's not already >>started (always obey the symlinks that the sysadmin has set), or do we >>want to autodetect the current status ?
EM> I think it would be better if we detected the current status. I do agree. >>It might be nice to have a helper command that just detects what sound >>daemon is running and help applications to use. Currently individual >>applications are doing their own checks in their own ways, which may >>sometimes have problems. EM> That is precisely the point I want to address. Using the argv[0] trick EM> (diverting, let's say, hydrogen to hydrogen.real and EM> symlinking /usr/bin/hydrogen to this wrapper application) we would have EM> the advantage of being able to decide what CLI arguments to pass to the EM> real application so it connects to the detected running setup, and we EM> would not have to change anything in the menu system, which would keep EM> the user experience consistent. I think it's a good idea, at least till a consensus is reached in the Linux Audio community about how to manage the situation. If did something quite similar with the ALSA Modular Synth package (ams): http://svn.debian.org/wsvn/demudi/ams/trunk/debian/patches/11ams_launch_script.dpatch?op=file&rev=0&sc=0 the wrapper detects if jack is running and changes the actual command line accordingly. EM> Starting a sound daemon if none is already running could be a EM> configurable behaviour of this wrapper / helper application. EM> But I think in the general case, jack initialization would be better EM> handled by qjackctl since it presents lots of useful functionality EM> besides starting jackd. Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
