[MPlayer-users] Issue playing opus audio

[Илья Валеев]

Hello!
I'm trying to play opus audio with mplayer. When I open file, mplayer

Playing
file.webm.
[mkv] Unknown/unsupported audio codec ID 'A_OPUS' for track 1 or
missing/faulty
[mkv] private codec
data.
[mkv] Track ID 1: audio (A_OPUS), -aid 0, -alang
eng
[mkv] No video track
found/wanted.
Matroska
No stream found.
Exiting... (End of file)
mplayer file.webm -ac fflibopus
Playing file.webm.
[mkv] Unknown/unsupported audio codec ID 'A_OPUS' for track 1 or
missing/faulty
[mkv] private codec data.
[mkv] Track ID 1: audio (A_OPUS), -aid 0, -alang eng
[mkv] No video track found/wanted.
Detected file format: Matroska
No stream found.
Exiting... (End of file)
mplayer file.webm -demuxer lavf
MPlayer interrupted by signal 11 in module: demux_open
- MPlayer crashed by bad usage of CPU/FPU/RAM.
Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
disassembly. Details in
DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
gcc version. If you think it's MPlayer's fault, please read
DOCS/HTML/en/bugreports.html and follow the instructions there. We
can't and
won't help unless you provide this information when reporting a
possible bug.
audiocodec A_OPUS
status working
fourcc OPUS
driver ffmpeg
dll fflibopus
audiocodec A_OPUS
status working
driver ffmpeg
dll fflibopus
Option audiocodec needs a parameter at line 4

It does not matter for me how to open file: with libopus or with ffmpeg.
Can you tell me please, how to configure system to play opus encoded files?


Debian 8 x64
mplayer2 2.0-728-g2c378c7-4+b1 amd64 from debian repositories
libopus0 1.1-2 amd64 from debian repositories
libavcodec57 7:3.1.4-1~bpo8+1 amd64 from debian repositories
ffmpeg 7:3.1.4-1~bpo8+1 amd64 from debian repositories

[Dominik 'Rathann' Mierzejewski]

Dear Илья,

Post by Илья Валеев
Hello!
I'm trying to play opus audio with mplayer. When I open file, mplayer

[...]

Post by Илья Валеев
It does not matter for me how to open file: with libopus or with ffmpeg.
Can you tell me please, how to configure system to play opus encoded files?
Debian 8 x64
mplayer2 2.0-728-g2c378c7-4+b1 amd64 from debian repositories

This is not MPlayer, but a fork called mplayer2 and is not supported
here. You can open a bug report in Debian BTS for this package.

If you want the real MPlayer, please use either latest MPlayer SVN
snapshot or MPlayer-1.3.0 release.

Regards,
Dominik

[Nicola Sabbi]

Post by Dominik 'Rathann' Mierzejewski
This is not MPlayer, but a fork called mplayer2 and is not supported
here.

who ever dared to dare?!?

[wm4]

On Thu, 10 Nov 2016 20:48:26 +0100

Post by Dominik 'Rathann' Mierzejewski
Dear Илья,

Post by Илья Валеев
Hello!
I'm trying to play opus audio with mplayer. When I open file, mplayer

[...]

Post by Илья Валеев
It does not matter for me how to open file: with libopus or with ffmpeg.
Can you tell me please, how to configure system to play opus encoded files?
Debian 8 x64
mplayer2 2.0-728-g2c378c7-4+b1 amd64 from debian repositories

This is not MPlayer, but a fork called mplayer2 and is not supported
here. You can open a bug report in Debian BTS for this package.
If you want the real MPlayer, please use either latest MPlayer SVN
snapshot or MPlayer-1.3.0 release.
Regards,
Dominik

mplayer2 is dead. It seems at least in Debian unstable, mplayer2
redirects to mpv - which I'm not sure how much sense that makes,
because mpv is fully rebranded and has different binary name and
configuration location.

[Alexander Strasser]

Post by wm4
On Thu, 10 Nov 2016 20:48:26 +0100

Post by Dominik 'Rathann' Mierzejewski
Dear Илья,

Post by Илья Валеев
Hello!
I'm trying to play opus audio with mplayer. When I open file, mplayer

[...]

Post by Илья Валеев
It does not matter for me how to open file: with libopus or with ffmpeg.
Can you tell me please, how to configure system to play opus encoded files?
Debian 8 x64
mplayer2 2.0-728-g2c378c7-4+b1 amd64 from debian repositories

This is not MPlayer, but a fork called mplayer2 and is not supported
here. You can open a bug report in Debian BTS for this package.
If you want the real MPlayer, please use either latest MPlayer SVN
snapshot or MPlayer-1.3.0 release.
Regards,
Dominik

mplayer2 is dead. It seems at least in Debian unstable, mplayer2
redirects to mpv - which I'm not sure how much sense that makes,
because mpv is fully rebranded and has different binary name and
configuration location.

Talking about the Debian decision:

IIRC there is a symlink now addressing the binary name. Not sure if
it's such a good thing.

"Redirecting" to mpv was supposed to be a suggestion by uau himself.
I too thought it would make more sense to switch mplayer2 users to mpv,
as it probably contains more mplayer2 specific functionality than MPlayer.

On a second thought I am not sure it was truly a bright idea, because
it could as well be that most mplayer2 users just wanted to have the newest
version of MPlayer and so got mplayer2 on their systems as it sounds just
like that. I have no clue if that's the case, but I suspect a at least a
somewhat split audience along that lines.

Dunno what's best...


Alexander

[wm4]

On Sun, 13 Nov 2016 22:42:17 +0100

Post by Alexander Strasser

Post by wm4
On Thu, 10 Nov 2016 20:48:26 +0100

Post by Dominik 'Rathann' Mierzejewski
Dear Илья,

Post by Илья Валеев
Hello!
I'm trying to play opus audio with mplayer. When I open file, mplayer

[...]

Post by Илья Валеев
It does not matter for me how to open file: with libopus or with ffmpeg.
Can you tell me please, how to configure system to play opus encoded files?
Debian 8 x64
mplayer2 2.0-728-g2c378c7-4+b1 amd64 from debian repositories

This is not MPlayer, but a fork called mplayer2 and is not supported
here. You can open a bug report in Debian BTS for this package.
If you want the real MPlayer, please use either latest MPlayer SVN
snapshot or MPlayer-1.3.0 release.
Regards,
Dominik

mplayer2 is dead. It seems at least in Debian unstable, mplayer2
redirects to mpv - which I'm not sure how much sense that makes,
because mpv is fully rebranded and has different binary name and
configuration location.

IIRC there is a symlink now addressing the binary name. Not sure if
it's such a good thing.
"Redirecting" to mpv was supposed to be a suggestion by uau himself.
I too thought it would make more sense to switch mplayer2 users to mpv,
as it probably contains more mplayer2 specific functionality than MPlayer.
On a second thought I am not sure it was truly a bright idea, because
it could as well be that most mplayer2 users just wanted to have the newest
version of MPlayer and so got mplayer2 on their systems as it sounds just
like that. I have no clue if that's the case, but I suspect a at least a
somewhat split audience along that lines.
Dunno what's best...

Maybe they should just have made "mplayer" from the transition package
show an error message, with suggestions which packages can be installed
to get alternative players...

[Uoti Urpala]

Post by wm4
Maybe they should just have made "mplayer" from the transition package
show an error message, with suggestions which packages can be installed
to get alternative players...

Making a transitional package that only tells the user they need to
manually switch to something else could make sense for users who
manually installed that player specifically. However, that's quite
likely not even the majority of installs. Several other packages had at
least a "Recommends" dependency on mplayer2. Until all such packages
have been removed from the user's system or updated to versions which
have different dependencies, there needs to be a package that satisfies
those dependencies. Having the transitional package for that use just
show an error would make little sense - the most likely way the
depending packages will deal with the removal of the mplayer2 package
(or the way they already have dealt with that in newer package
versions) is switching the dependency to mpv, and the sane thing for
the transitional package to do is to create the same end result of
having mpv installed even if the depending-on packages haven't been
updated yet.

I think the main reason for the symlink is possible direct functional
dependencies (as opposed to just recommending that the system has a
player available so the user can start it by whatever means he
prefers). The symlink will likely work for most cases where a program
launches a player directly (at least I don't know of cases that would
use tricky options likely to have changed incompatibly outside of
something like SMPlayer, and trying to keep using old package versions
of that would likely not work anyway).