On Thu, Sep 11, 2014 at 11:02 AM, Radoslaw Szkodzinski astralstorm@gmail.com wrote:
On Thu, Sep 11, 2014 at 1:33 AM, Sergey sergemp@mail.ru wrote:
Sat, 6 Sep 2014 Radoslaw Szkodzinski wrote:
A recent change in alsa-plugins 1.0.28 alsa-jack has changed the poll semantics. This breaks audacious and mpv, perhaps more applications.
The regression is caused by: Commit: 9217377337cdceb62abeb5969112b738bb5cd551 jack: fix polling and recovering
I'm initial author of this commit and I'd love to fix the issue, but it never happens to me. I need your help to fix it.
Can you provide some steps to reproduce this bug? How much time it takes to reproduce it? Can you reproduce it with alsa 1.0.27 and alsa-jack plugin 1.0.28? You can download that plugin separately:
I'll test this during the weekend. 1.0.27.x was fine with alsa 1.0.27.
Sorry it took this long, the following version is fine: media-plugins/alsa-plugins-1.0.27-r3 was built with the following: USE="ffmpeg jack libsamplerate speex -debug -pulseaudio" ABI_X86="32 64 -x32"
It takes between 1 and 10 minutes to reproduce the bug with alsa-plugins-1.0.28.
Alsa-lib info is in both cases: media-libs/alsa-lib-1.0.28 was built with the following: USE="python -alisp -debug -doc" ABI_X86="32 64 -x32" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7"
I'm somewhat suspicious is it caused by a wrong Jack buffer size, and only masked by incorrect handling of buffer fill in the older version. Verbose log from aplay is attached (w/ alsa-jack 1.0.27.x). Note the discrepancy between JackClient period size (not divisible by actual period size) and ALSA min_avail.
Best regards,