On 6/5/22 15:08, Michael Catanzaro wrote:
On Sat, Jun 4 2022 at 01:05:58 AM +0300, Otto Urpelainen <oturpe@xxxxxx>
wrote:
It seems clear that there is a bug somewhere, but I cannot decide,
where, hence this post to devel. Should Fedora's Firefox actually have
media.ffmpeg.enabled set to false by default, because Fedora's variant
of ffmpeg has this problem? Should upstream Firefox be smarted about
which decoder library it attempts to use? Or should ffmpeg-free package
do something to avoid this from happening. Any opinions are welcome!
Only the developers will be able to tell you for sure, but I would start
with a Firefox bug report. That's the place where code changes are most
likely to be required, and the Firefox developers can always punt the
bug to ffmpeg if they think it is doing something wrong.
Our ffmpeg-free is supposed to support H264 via OpenH264.
From my understanding ffmpeg-free should work with Firefox regardless
of actual codec name.
Firefox uses avcodec_find_decoder() to query supported formats and it
uses AVCodecID. So as far as openh264 ffmpeg module claims support of
AV_CODEC_ID_H264 it's supported (unless the decoder crashes later and
it's disabled or so).
You can get exact info by running Firefox with
MOZ_LOG="PlatformDecoderModule:5"
env variable.
Firefox without ffmpeg-free package uses GMP interface to use OpenH264
and you can find its status at about:plugins page.
--
Martin Stransky
Software Engineer / Red Hat, Inc
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
