[MPlayer-users] When I play some avi files with a locally compiled mplayer, it uses mpg123 to decode the audio, and it decodes it incorrectly.
kasp at vfemail.net
Sat Mar 26 17:42:03 EET 2022
On Fri, 25 Mar 2022 22:16:52 +0100
Reimar Döffinger <Reimar.Doeffinger at gmx.de> wrote:
> > On 25 Mar 2022, at 21:02, stan <kasp at vfemail.net> wrote:
> > I filed a bug at fedora's bugzilla, and it was closed as an mplayer
> > issue. I don't think it is, but I am asking here in case it is. I
> > have two workarounds, compiling without mpg123 support and using the
> > system mplayer, so not major. However, this used to work without
> > any issues.
> -ac ffmp3float or are probably workarounds as well.
Using -ac -mpg123 led to
Cannot find codec for audio format 0x55.
Audio: no sound
Using -ac ffmp3float led to
Forced audio codec: ffmp3float
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 48000 Hz, 1 ch, floatle, 62.6 kbit/4.08% (ratio: 7824->192000)
Selected audio codec: [ffmp3float] afm: ffmpeg (FFmpeg MPEG layer-3
[AO OSS] audio_setup: Can't open audio device /dev/dsp: No such file or
directory AO: [alsa] 48000Hz 1ch floatle (4 bytes per sample)
which seems like it should be OK, but this behaved just like when mpg123
is used. The movie froze each time the position was moved.
> > My question: Is it an mplayer issue?
> This uses libmpg123 from the RedHat repo?
From the fedora repo, but yes, the system mpg123
> Causes I suspect, most likely first:
> - A behaviour change in libmpg123. Matter of definition if that is a
> MPlayer or libmpg123 issue then
Possible, as the mpg123 package was updated on Feb 18, 2022, which
would be in the right time frame.
> - A libmpg123 issue. Not a MPlayer issue then
I could check the package change history to see if this is the reason.
> - Something weirder like libmpg123 not compiled right or such
I'm using rawhide (development version of fedora) and it has introduced
gcc12, and I noticed that there were other packages that had issues
caused by this change, so perhaps mpg123 had an issue that is less
visible, but still causes problems with the new compiler version.
> If it's the first point though that would have started to happen with
> an update to a newer libmpg123 and you could bisect when the issue
> started. Not sure it's really worth the effort though...
Yeah, given the options you recommended didn't work, I'll probably just
stop configuring the use of mpg123. But first, I'll try downloading
the src.rpm for the mpg123 package, and building it locally, to see if
it works when compiled on the local system.
Thanks for your help.
This free account was provided by VFEmail.net - report spam to abuse at vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
More information about the MPlayer-users