4 ms·
Yes, that's because Chrome includes proprietary codecs, while Chromium doesn't. I believe there are some ffmpeg bindings available on most distros to solve that
by icebraining 10y ago
Yes, that's because Chrome includes proprietary codecs, while Chromium doesn't. I believe there are some ffmpeg bindings available on most distros to solve that.
- amelius 10y agoOkay, thanks. I still think that Chromium needs better error reporting; it's difficult to figure out what is wrong when a video is not displaying (often, I think it is just not loading); and which codec is missing.
- majewsky 10y agoAFAIK that's sort of the website's fault. The HTML5 video support allows the website to query the browser's codec capabilities in order to determine which video file to show to the user (for those sites where videos are available in multiple codecs), so if the website's JS does not find any matching codec, they should show an appropriate error message. Now of course, to most users of the average video site, an error message involving the words "supported codecs" would just be gibberish, so I can see why many video sites just show a generic "Something went wrong" error (or nothing at all, since it's plainly obvious that something went wrong when the video's not playing).