Status

()

defect
P1
normal
RESOLVED FIXED
4 years ago
2 years ago

People

(Reporter: jya, Assigned: jya)

Tracking

Trunk
mozilla46
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox43 wontfix, firefox44 affected, firefox45 affected, firefox46 fixed)

Details

Attachments

(4 attachments)

Let's get rid of it now that it's unused
It was now unused by default.
Attachment #8700440 - Flags: review?(ajones)
Attachment #8700441 - Flags: review?(mh+mozilla)
This is a reversal of commit b28d496da7bf48432cb3aac3d10e7a66a267421c
Attachment #8700443 - Flags: review?(n.nethercote)
Assignee: nobody → jyavenard
Summary: Remove gstreamer suppoert → Remove gstreamer support
Attachment #8700443 - Flags: review?(n.nethercote) → review+
Attachment #8700440 - Flags: review?(ajones) → review+
Attachment #8700442 - Flags: review?(mh+mozilla) → review+
Attachment #8700441 - Flags: review?(mh+mozilla) → review+
Isn't this required for support of various HD codecs on linux, which are needed, for example for 4k video on youtube? I've been using my own firefox build with gstreamer and the x264 and VPX codec since about FF 37 if I remember correctly, because the built-in codec wasn't working ...

See https://forums.gentoo.org/viewtopic-t-1013448-start-0-postdays-0-postorder-asc-highlight-libvpx%2Bfirefox.html
Gstreamer has never been compatible with MSE; only plain mp4.
YouTube has removed support for HD content without MSE in Firefox 41 unless you had MSE or Flash (and flash support was removed in 43).

So no, gstreamer wasn't required to support various HD codec with youtube, it has never supported HD streaming in youtube.
I wish this didn't happen, we've discovered this now and now this commit makes completely impossible for us to have any kind of usable video playback on embedded devices based on Freescale i.MX6. I would like to underline how gstreamer is important for embedded systems that are not android based, on those systems gstreamer is a de facto standard. So, please, revert this, and allow people to choose to use it when they need it.
You should enable the OMX decoder instead...
OMX is not an option on i.MX6 + Linux (not android). So the only available option is gstreamer-imx. Just to be clear: I'm not a big gstreamer fan, but I'm fine with it just because it works on that hardware.
OpenMax use isn't limited to Android.

Gstreamer won't come back, it's incompatible with html5.
OpenMax is not usable on Linux on i.MX6. And I think the same applies for other vendors such as TexasInstruments.
Gstreamer covers most of the use cases where <video> tag is involved so that's better than *nothing*.

If it may help this discussion I can spend some time to find official freescale documentation about OpenMAX support on not android i.MX systems.
by the way I would like to underline that i.MX6 is a big player on the embedded linux scene, and it is here to stay for a long time, it doesn't look like a good move to remove support to it.
then get them to provide an OpenMax SDK.
They are not going to support OpenMX, and they will keep providing users a patched chromium that has been updated just few times. I would like to underline how this is a poor technical choice: gstreamer would be the easy and good way to support video acceleration and despite your statements MSE if fully feasible with some additional work.
If you take a look to this: https://github.com/Samsung/ChromiumGStreamerBackend you will see that MSE can be implemented using gstreamer.
You need to log in before you can comment on or make changes to this bug.