[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mplayer changed behaviour in stretch



On 19/12/17 09:45 AM, Greg Wooledge wrote:

On Tue, Dec 19, 2017 at 09:36:11AM -0800, Charlie Gibbs wrote:
>
Follow-up: I've just come across MP3 files in my collection for which the
new mplayer _does_ display the tags.  Maybe it's just becoming more picky -
which isn't really a Good Thing.  Postel's Law says, "Be conservative in
what you do, be liberal in what you accept from others."

Could be id3v1 vs. id3v2 tags.  Try some of the command-line tools to
see which tags are present on which songs.

The files which display have both ID3V1 and ID3V2 tags. The ones which don't display only have ID3V2 tags. Could the latest mplayer have lost the ability to handle ID3V2 tags?

The old version on my Jessie machine reports:
Mplayer2 2.0-728-g2c378c7-4+b1

The new Stretch version (which can't see ID3V2 tags) reports:
MPlayer 1.3.0 (Debian), built with gcc-6.2.1

Hmmm, looks like the newer release rolled back to an older version of mplayer. There are no links, just the binary in /usr/bin. I think I'll just copy the version on my Jessie machine over to my Stretch machine... Arrgh! mplayer: error while loading shared libraries: libquvi.so.7: cannot open shared object file: No such file or directory

Rather than risk the Linux equivalent of DLL hell, I'll roll back to the installed version and see whether a newer one comes along.

$ sudo apt-get install mplayer
Reading package lists... Done
Building dependency tree
Reading state information... Done
mplayer is already the newest version (2:1.3.0-6).
0 upgraded, 0 newly installed, 0 to remove and 360 not upgraded.

$ sudo apt-get install mplayer2

Aha! That installed mpv and created a symbolic link to it from mplayer. Now I can see my ID3V2 tags again.

--
cgibbs@surfnaked.ca (Charlie Gibbs)


Reply to: