This is mpg123 upstream here. I do not have a 16.04 system at hand currently, cannot confirm (and I suppose it should be a hardware machine, sound in a VM being possibly a different beast …). So, may I ask:
1. This is only with pulseaudio, right? Things are smooth when disabling it and playing directly via ALSA? 2. Does this persist with current mpg123 built from http://mpg123.org/current (it's 1.23.5)? Minimum receipe: apt-get install build-essentials apt-get libpulse-dev wget https://mpg123.org/current tar -xf mpg123-1.23.5.tar.bz2 cd mpg123-1.23.5 ./configure --disable-shared --with-audio=pulse make src/mpg123 $some_file (Naturally that's my guess, as I did not test on a ubuntu 16.04 system.) This should produce a self-contained mpg123 binary that does run without installing any modules. There was quite some work in the output code going from version 1.22 to 1.23. If the switch fixes things, we at least may have a hint at what fix might apply to the older version in Ubuntu. I am wondering about partial PCM frames being received by pulse, in particular. But that would cause output more like static noise, not what you describe … About the nature of the broken output … it is not just static noise; there is still the initial audio intelligible, just played fast with lots of skippyness? I may test this version of mpg123 on a ubuntu 14.04 box ... can someone tell me if something substantial in pulseaudio changed from that one (it was supposed to be stable now;-)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1585926 Title: mp3 files decode as crackly noise Status in mpg123 package in Ubuntu: Confirmed Bug description: MP3 files have started decoding as crackly noise instead of the intended sound (typically, music). Occasionally but not reliably, the crackly noise becomes music, as though it were a mere synchronisation error and mpg123 finds a sync signal. (I have no reason to believe that that is happening at a technical level, I offer it as an analogy for the occasional behaviour I've noticed.) While it's possible that this is only files on my disk that are corrupted, this would suggest that my backups have been similarly corrupted, so that hypothesis seems less likely. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mpg123 1.22.4-1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: i3 Date: Thu May 26 09:46:53 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-23 (215 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: mpg123 UpgradeStatus: Upgraded to xenial on 2016-05-16 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1585926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
