why is ogg in firefox SO MUCH slower than standalone player?

[her34]

for example:
http://www.mozilla.com/en-US/firefox/video/firefox-3.5.html

if you watch that video in browser, it maxes out one of my cpu cores (c2d 1.6ghz), 50% in task manager

yet if you download and watch with player like vlc, it barely uses any cpu, less than 5% in task manager

can someone explain why this is?

[MatMaul]

:search:
http://forum.doom9.org/showthread.php?p=1292991#post1292991

[Keiyakusha]

By the way. Does anyone knows if it is possible to write FFMPEG-based plugin for Firefox to add new formats support and maybe even replace built-in Theora decoder? Or this is impossible/too complicated?

[Dark Shikari]

Because Firefox developers, being complete idiots, compiled ffmpeg without assembly optimizations.

It's as if they're intentionally trying to sabotage HTML5 video.

[Reimar]

Because Firefox developers, being complete idiots, compiled ffmpeg without assembly optimizations.

Originally they used libtheora and I'd think they still do. Which is not an excuse since libtheora normally is faster than FFmpeg...

[neoufo51]

My question is, how come VLC can play these new HTML5 videos but MPC-HC can't?

[clsid]

Disable the internal Ogg splitter and use Haali instead. The splitter in MPC-HC does not yet have good Theora support.

[cdouble]

Originally they used libtheora and I'd think they still do. Which is not an excuse since libtheora normally is faster than FFmpeg...You are correct. Firefox uses libtheora, not ffmpeg. The decoding performance is mainly hampered by inefficiencies in going through the HTML rendering pipelline so that HTML can be overlaid on top and the video can be styled/affected by CSS, SVG, etc.

There other other issues related to the libraries we're using and the way we're using them that are being addressed to improve performance.

[RNiK]

Because Firefox developers, being complete idiots, compiled ffmpeg without assembly optimizations.

It's as if they're intentionally trying to sabotage HTML5 video.
Enable optimized Theora code in Windows builds (FIXED!) (https://bugzilla.mozilla.org/show_bug.cgi?id=498770) ;)

[Keiyakusha]

This is sounds good, now we still need some plugin for h264 decoding ^_^

[CruNcher]

Keiyakusha Silverlight 3 or Adobe Flash Player both can playback H.264 soon you could also use DivX WebPlayer or CoreCodecs old TCPMP Firefox plugin (not sure if that still works though) :)

Btw i told some firefox guys in #theora that it would be a disaster to release 3.5 with this bug under Windows the answer back then was clear it wont be fixed for 3.5 so Theora started on Windows with this impression of being extremely CPU utilizing :( sad thing really sad (especially for Netbook Atom users it feels far away from being low complexity) though Video was skipped anyway from HTML5 thx to Google :(

[Keiyakusha]

Well, I know, but we need special firefox plugin to be able to watch h264 videos in html5 video tags, because as firefox devs stated somewhere, there will not be native h264 support ever.
And things that you listed IMHO must die. Well, maybe except Adobe Flash Player.

EDIT: oops, did not notice your update.

[Dark Shikari]

though Video was skipped anyway from HTML5 thx to Google :(No, <video> is still part of HTML5.

[pirlouy]

Well, I know, but we need special firefox plugin to be able to watch h264 videos in html5 video tags, because as firefox devs stated somewhere, there will not be native h264 support ever.
And things that you listed IMHO must die. Well, maybe except Adobe Flash Player.
I completely agree with this statement. One advantage of this balise is the fact than we should be able to avoid these dangerous plugins (security and other problems).

Adobe Flash or Silverlight could be used as a fallback for H.264, but an extension/plugin just for this balise could be great (based on MPC-HC for example).

[cdouble]

Btw i told some firefox guys in #theora that it would be a disaster to release 3.5 with this bug under Windows the answer back then was clear it wont be fixed for 3.5 so Theora started on Windows with this impression of being extremely CPU utilizing :(Unfortunately the bug wasn't fixed in time for the FF 3.5 release. We had originally enabled the MSVC assembly a while back and it caused issues on some machines and worked on others. A fix for it wasn't available until FF 3.5 was due for release and it was too late to run it through a beta test cycle to see if it had similar issues to the last time it was enabled.

In actual fact it doesn't make that big a difference to CPU usage - this is another reason why it wasn't a high priority. There are other reasons for why Firefox has a high CPU usage when decoding video and fixing that is really needed first.

[her34]

In actual fact it doesn't make that big a difference to CPU usage - this is another reason why it wasn't a high priority. There are other reasons for why Firefox has a high CPU usage when decoding video and fixing that is really needed first.

What are the other reasons?