Google has a philosophy of making everything idiot-proof. See https://code.google.com/p/chromium/i...tail?id=331072 They won't add local printing to Chrome OS, even as an advanced feature for highly qualified administrators. This looks a lot like more of the same.
I'd like to see Google reward manufacturers who ship validated implementations of open standards, even if it means users of some hardware are left disappointed.
[QUOTE=cynical;402696]I think the main issue is not video acceleration by itself, since that can be handed off to gstreamer like Firefox does on linux systems. The problem is more that Chrome is also using gpu acceleration for their UI and they can't guarantee it will work bug-free (imho) primarily due to FGLRX. I can't wait for the radeon driver to kill it so we can finally get decent third party support on Linux. If Nouveau could catch up and Intel would drop vaapi we would be in paradise >
It's good to have an evolution and in an ideal world all drivers would be open source so you can count on most of them to have adopted the latest patch made for Xorg or even the latest technology that replaces it. Unfortunately that's not the case and when you're a company making software that should run on Linux, you have to take into account the free drivers and the propietary ones and all the standards they support or not and all the bugs they have when supporting those standards. It's not an easy task. On the propietary side (Windows and OSX) there is a unified system, everything uses the latest technology or at least the old one in the transition time (which usually is much shorter than in Linux) so basically you don't have to fight with 20 implementations of the same, each one of them made by every vendor of graphic cards.
Originally Posted by robclark
That's just a very bad excuse.
Has anybody looked at the Android code where they handle video acceleration? They've pretty much worn out the if-else statements for the ten gazillion SoCs they have to support on that platform.
so, android standardizes on openmax for video accel (encode and decode). Going back a few years, it *used* to be that vendors would just hack up the stagefright layer to make it work with the quirks of their hardware / openmax implementation. I guess the rough equivalent in this scenario would be if nvidia/amd/etc had their own customized version of chromium.
Originally Posted by johnc
I've been further away from android development for the last years, so I could be wrong, but my understanding is that google was trying to get away from this and limit the ability of vendors to hack up the middleware.. although I'm sure there is plenty of 'if (vendor == FOO) ..' type stuff in stagefright. (Again, equivalent to having to put some 'if (vendor == NVIDIA) ..' workarounds in chromium.)
But yeah, it seems like a pretty poor excuse to me too. Android has more vendors with their own quirks to workaround, compared to different GPU vendors in the desktop space.
I think this is a great article: https://dolphin-emu.org/blog/2013/09...all-fameshame/ Kinda explains a lot. What I find most interesting is that adreno is (a) the most popular GPU, and (b) has some of the shittiest drivers. They should fix that.
Originally Posted by robclark
On Kubuntu 13.10 it looks like all acceleration is enabled on my Chrome Version 34.0.1847.116 running nVidia 650Ti Boost (great card for the money). VDPAU seems to be handling youtube decoding, as the CPU shows hardly any usage difference when viewing a full-screen HD video. I did go to chrome://flags and turn on all acceleration options (from "default" which tells me nothing, grrr). I don't see a difference in performance though - everything is still plain fast. Perhaps certain nVidia cards have been white-listed after all?
Right click on the video, "stats for nerds" and there it says if hardware decoding is working or not.
It should read something like:
VP8/9 videos (html5) are NOT decoded by hardware btw (no hardware decoding exists), only the h264 streams that come only via the flash player.
accelerated video rendering, hardware video decoding
At least on the Adobe version of flash VDPAU works even with the opensource radeon drivers IF its enabled in /etc/adobe/mms.cfg
, but it breaks the plugin on many other pages (crashes). Back when i had a 8200 nvidia it was exactly the same behavior btw.
BTW it seems that the Adobe plugin handles hardware accelerated playback just fine, only Google's version chokes (as in "uses 200-300% CPU and its laggy").
But 3d acceleration with webgl is crap too. It uses insane amounts of CPU to lag like hell.
So, in that link they say mesa is ok for them. Why their own plugin+webgl works like crap with it then (latest git kernel/mesa/xf86-ati version on Radeon HD 8570D)?
Once more: the same webgl demos work just perfect in Firefox/Seamonkey with very low CPU usage with the same hardware/d.