On 05/28/2012 09:05 PM, David Adler wrote:
Since a few weeks I have issues with jack2 on Arch 1. It's gone pretty verbose, filling any terminal from where a jack application was started with lots of messages. These mingle with the client's output, rendering it more or less unreadable. Neither --silent nor the --verbose flag change the amount of jack's output. 2. It behaves as if the -T (--temporary) flag where given, i.e. exits once all clients have closed their connections. Some example output, which is the result of jack2 started with jackd -d alsa -d hw:0 -p 128 -n 3, then starting and quitting mplayer. http://sebsauvage.net/paste/?6fd645cc70f83404#8NHeh0ASRuLREkgFbPBNMRi4M8C35YAFN2NOQxZLBjk= Arch currently provides 1.9.8, but this seems unrelated to the version. Downgrading to older jack versions or package releases does not fix this, despite those having been perfectly fine at the time.
Hmmm. I have jackd2 v 1.9.8~dfsg.3+20120418gitf82ec715-6 from Sid running here on Aptosid (Debian Sid) without any problems.
Is there some hidden config or .desktop or .local file somewhere that could be effecting it?
-- David gnome@xxxxxxxxxxxxx authenticity, honesty, community http://clanjones.org/david/ http://dancing-treefrog.deviantart.com/ _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
[ALSA Users] [ALSA Devel] [Linux Media] [Kernel] [Online Dating] [Photo Sharing] [Gimp] [Yosemite News] [Video 4 Linux]