Paul Davis wrote: Is this issue documented anyway? Even just steps required to reproduce it. Anything anyone else can do to help? Cheers, Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

On 02/28/2016 03:04 AM, Paul Davis wrote: fwiw. have built, packaged and run jack-0.125.0rc1: http://www.rncbc.org/archive/#jack also on my OBS home project: https://build.opensuse.org/package/show/home:rncbc/jack example startup log head: ~~~ /usr/bin/jackd -P86 -t3000 -m -dalsa -dhw:DMX6Fire -r48000 -p128 -n2 -Xseq jackd 0.125.0rc1 Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. apparent rate = 48000 creating alsa driver ... hw:DMX6Fire|hw:DMX6Fire|128|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit integer little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 32bit integer little-endian ALSA: use 2 periods for playback creating alsa_midi driver ... using qjackctl for that matter where pretty_name metadata aliases are being used all the time btw. also doing all the usual things: development, testing, debugging, playing, streaming, browsing, etc. and with pulseaudio-sink and -source modules all along... all that on one desktop and two laptops, all rigged with latest 4.4 kernels (preempt w/threadirqs and preempt_rt_full; rtirq sets the primary snd card to rtprio=90 thus the jackd -P86 ... ;)) all to tell that 0.125.0rc1 is doing fine over here without any major hiccups, though the usual xruns specially due on video and possibly pulseaudio related but sure that was also happening before on jackd-0.124.x so it seems it's all as solid as ever before. however i have a complaint :) re. the git repo in particular: since 0.125.0rc1 announcement the submodules aren't pulling right... evidence follows: ~~~ ~/src/jack1/jack1-git> git pull --all Fetching origin Already up-to-date. ~/src/jack1/jack1-git> git submodule update fatal: reference is not a tree: e74323c535876abca9a2293bd2ca426a3b91ff8b fatal: reference is not a tree: a2536c8b348bbfb21ec53db901e7992d7ffef474 fatal: reference is not a tree: 8e140b72de0231d129c6006db969f1dba4f1486b Unable to checkout 'e74323c535876abca9a2293bd2ca426a3b91ff8b' in submodule path 'example-clients' Unable to checkout 'a2536c8b348bbfb21ec53db901e7992d7ffef474' in submodule path 'jack' Unable to checkout '8e140b72de0231d129c6006db969f1dba4f1486b' in submodule path 'tools' ~/src/jack1/jack1-git> git remote -v origin git://github.com/jackaudio/jack1.git (fetch) origin git://github.com/jackaudio/jack1.git (push) ~/src/jack1/jack1-git> git branch -a * master remotes/origin/HEAD -> origin/master remotes/origin/control_device_name_fixes remotes/origin/master remotes/origin/uuid byee -- rncbc aka. Rui Nuno Capela

On 28.02.2016 04:04, Paul Davis wrote: I have seen issues, too. I get heavily crackled sound on a first clients audio output upon loading of a second client into the graph. The crackling sometimes disappears when loading a third client. The server may also crash sometimes while crackling along. I have bisected it down to: 423931219dd3e3b669fde97786cadae92c066dc1 before that I do not seem to experience these crackles. .jackdrc -------- /usr/bin/jackd -M2048 -Xalsa_midi -P70 -t2000 -dalsa -dhw:Juli -r48000 -p128 -n3

On 03/02/2016 09:46 PM, Paul Davis wrote: i must say that i can also now definitely confirm that the issue below, that i've reported earlier as garbled sound on pulseaudio+alsa_midi driver, is introduced by this very same "Fons' topological sort" commit. only that the "crackling" does occur *always* on me (if not dead silence). funny enough, in my case at least, on all tests i've tried, and they were a lot during the past week, it only occurred deterministically speaking, when pulseaudio-jack-sink and -source modules were up and jackd had the alsa_midi slave driver loaded (via -Xalsa_midi or -Xseq). if the alsa_midi slave driver is not loaded, everything runs and sounds fine (apparently). also, using a2jmidid as a backup alsa_midi bridge, the problem didn't manifest. oh, and the new release has way more important fixes to me at least, like the fixes on the alsa_midi slave driver hotplug and freewheel handling and the metadata memory leaks and garbage/crash fixes. etc. On 02/28/2016 12:24 PM, Rui Nuno Capela wrote: hth. byee -- rncbc aka. Rui Nuno Capela

I didn't bother to read Fons' code in much detail ... I was more concerned with how to reformat it so as to get a "clean" commit. Perhaps somebody else will read that commit and be able to see what the issue(s) are. On Mon, Mar 7, 2016 at 1:55 AM, Erik de Castro Lopo <mle+la(a)mega-nerd.com> wrote: