Issue with Audacious play mp3 on ac100

Bug #1072696 reported by saturn
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mpg123 (Debian)
Fix Released
Unknown
mpg123 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Attempt to open mp3 return "...mpg123: Error opening file a.mp3: Unable to set up output format! (code 1)."

This bug with solution discussed already here http://redmine.audacious-media-player.org/boards/2/topics/315

After recompiling and updating libmpg123 according to this discussion audacious now works fine.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libmpg123-0 1.14.2+svn20120622-1
Uname: Linux 3.1.10-6-ac100 armv7l
ApportVersion: 2.6.1-0ubuntu6
Architecture: armhf
Date: Mon Oct 29 16:03:47 2012
MarkForUpload: True
SourcePackage: mpg123
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
saturn (saturn-skb) wrote :
Revision history for this message
Thomas Orgis (thomas-forum) wrote : Re: [Bug 1072696] [NEW] Issue with Audacious play mp3 on ac100

Am Mon, 29 Oct 2012 12:19:50 -0000
schrieb saturn <email address hidden>:

> Attempt to open mp3 return "...mpg123: Error opening file a.mp3: Unable
> to set up output format! (code 1)."
>
> This bug with solution discussed already here http://redmine.audacious-
> media-player.org/boards/2/topics/315

Um, people want everything, eh? Well, there is some wrong and some
correct information there. The solution of using generic C code works
for getting all output formats, yes (John Lindgren got a wrong
impression there about float output being coupled to assembly
optimizations).

But there also is assembly-optimized decoding to floating point on ARM
platforms that feature the NEON instructions (Cortex A8). There is no
common build encompassing the different variants like x86 and it is not
likely that there will be, as the normal ARM does integer math. There
might be a build that combines ARM NEON with generic C fallback code,
using floating point math.

When audacious insists on floating point data, even on machines that do
not feature floating point hardware, you have some options:

a) build mpg123 with generic_fpu ... which makes it relatively slow for
normal 16-bit playback (or in ARM terms: consuming too much energy),
b) patch audacious mpg123 binding to convert 16 bit to float on-the-fly or
c) patch mpg123 (or motivate a release) to do that float conversion
after decoding, just like 24 bit or unsigned integer types are
handled right now.

I see a point for the latter one ... it would not be hard to do it.
Just a bit pointless in case this is running on a CPU that has working
floating point support, or NEON, even.

Thoughts from debian? I see this being a problem for packaging as you
have to decide for one mpg123 build for stand-alone operation and
linking to audacious. Compromises suck.

Alrighty then,

Thomas

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mpg123 (Ubuntu):
status: New → Confirmed
zuban (zuban)
information type: Public → Public Security
information type: Public Security → Public
Changed in mpg123 (Debian):
status: Unknown → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mpg123 - 1.18.0-1ubuntu1

---------------
mpg123 (1.18.0-1ubuntu1) utopic; urgency=low

  * Merge from Debian unstable. Remaining changes:
    - debian/libmpg123-0.symbols: Add arm64 and ppc64el as 64-bit arches.

mpg123 (1.18.0-1) unstable; urgency=low

  * New upstream release, Closes: #737243
    - libmpg123 version 39
    - Big version increase for clear distinction regarding the 1.14.x regression
      fixes in libmpg123.
    - Regression fix: Ensure decoder reinitialization on combination of seek and
      resync (buffer overflow bug 201, introduced in 1.14.1).
    - Regression fix: Make parsing really end on reaching of junk limit
      (introduced in 1.14.4).
    - Add check for bad bit allocation value in layer I decoder (removes audible
      glitch in bug 201 test file).
    - Avoid wrong error message about Frankenstein streams when gapless decoding
      disabled.
    - Be verbose about big header changes (Frankenstein streams). Note that
      changes in samples per frame will confuse the seeking code, but decoding
      can get through.
    - Actually use the full routine to close tracks. Avoids socket leak when
      playing multiple HTTP streams from a playlist (bug 203).
    - Send correct host header when connecting through HTTP proxy (bug 202,
      figured out by Rajeev V. Pillai).
    - The console application now informs about changed major stream properties
      (prints out another header line).
    - mpg123-id3dump --no-scan; for speedup
    - hide -C parameter from mpg123 --help when it is not supported
    - added tinyalsa Output (by Jarno Lehtinen)
    - build system tweaking
    - some care for fixing Cygwin builds
  * Update symbol table to work with mips64/mips64el.
    Thanks to YunQiang Su for the patch. (Closes: #729047)
  * Update symbol table to work with x32.
  * Bump Standards-Version.
    - Remove mp3-decoder from the Provides list.

  [ Riku Voipio ]
  * switch arm to use generic_fpu, Closes: #738981, LP: #1072696
 -- William Grant <email address hidden> Fri, 02 May 2014 11:54:24 +1000

Changed in mpg123 (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.