Launchpad has imported 24 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1210727.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2015-10-02T10:01:00+00:00 Jyavenard-9 wrote: This would do decoding only ; not rendering (yet) Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/7 ------------------------------------------------------------------------ On 2015-10-02T10:33:11+00:00 RussianNeuroMancer wrote: Hardware decoding on Intel Ironlake should be used only for 720p and lower. Hardware 1080p decoding on Intel Ironlake is slower than software decoding on CPU: https://bugs.freedesktop.org/show_bug.cgi?id=47858 GPU model from about:support Intel Open Source Technology Center -- Mesa DRI Intel(R) Ironlake Mobile I need to fill separate issue about VA-API on Ironlake or drop this info here is fine? Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/8 ------------------------------------------------------------------------ On 2015-10-02T12:42:52+00:00 Jyavenard-9 wrote: (In reply to russianneuromancer from comment #1) > Hardware decoding on Intel Ironlake should be used only for 720p and lower. > Hardware 1080p decoding on Intel Ironlake is slower than software decoding > on CPU: https://bugs.freedesktop.org/show_bug.cgi?id=47858 > > GPU model from about:support > Intel Open Source Technology Center -- Mesa DRI Intel(R) Ironlake Mobile > > I need to fill separate issue about VA-API on Ironlake or drop this info > here is fine? We have a generic preference to disable hardware acceleration, I'll hook it up to vaapi, but I have no intention at this stage to make specific cases for particular chipset. Would have to be in a separate bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/9 ------------------------------------------------------------------------ On 2016-07-06T04:29:09+00:00 Ajones-m wrote: Mass change P2 -> P3 Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/52 ------------------------------------------------------------------------ On 2016-07-06T09:06:19+00:00 sheepdestro...@gmail.com wrote: Is there a reason the priority would go from P2 to P3? Lack of hardware acceleration is the worse offender on Linux right now. Some youtube videos can not even play at a decent framerate because of that, especially the 4K / 360 ones. And that's without speaking of the heat generated by those poor CPUs... I do not get why it would not even go the other way, right to P1 ? Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/53 ------------------------------------------------------------------------ On 2016-07-11T06:18:47+00:00 Ajones-m wrote: See bug 1210726. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/54 ------------------------------------------------------------------------ On 2016-08-11T18:00:44+00:00 agm97 wrote: linux had have the firefox browser by default in all distros I think much users of firefox are from linux and the only thing we get from mozilla a long waiting for a feature that is very needed.. between google with chromium and the denied featured requests and firefox not to working on features for firefox, linux in browser category is very late and the battery for laptops is damaged with linux and video viewing with browsers, I feel really annoying Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/58 ------------------------------------------------------------------------ On 2016-09-23T23:46:01+00:00 Melroy van den Berg wrote: I fully agree, video acceleration is a must have feature now a days. Please solve it! Don't force me to move to Chrome.... Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/75 ------------------------------------------------------------------------ On 2016-11-14T12:45:36+00:00 Waz wrote: I still have hope too to see full VDPAU/VAAVI support in order to have hardware video acceleration. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/77 ------------------------------------------------------------------------ On 2016-11-18T21:41:36+00:00 Ehumphries wrote: Gentle reminder: * Our guidelines ask you don't argue about priority setting on bugs. Triage leads and Mozillians working on the bug set the priority. See: https://bugzilla.mozilla.org/page.cgi?id=etiquette.html * "Me too" or "Fix this or I'm moving to Chrome/Lynx/Gopher/Edge/Webkit" comments are off topic and just add noise. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/78 ------------------------------------------------------------------------ On 2017-03-04T08:59:00+00:00 Laurent Bonnaud wrote: Hi, in firefox release/51 and beta/52 in about:support one can see "Hardware H264 Decoding" status. However in firefox aurora/53 and nigthly/54, this line is no longer visible. Was this done on purpose or is this an omission? BTW, how about adding a line about "Hardware VP9 Decoding" since recent Intel GPU do support hardware VP9 decoding? Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/82 ------------------------------------------------------------------------ On 2017-05-05T14:57:23+00:00 Pmenzel+bugzilla-mozilla-org wrote: (In reply to Laurent Bonnaud from comment #10) > in firefox release/51 and beta/52 in about:support one can see "Hardware > H264 Decoding" status. > > However in firefox aurora/53 and nigthly/54, this line is no longer visible. > > Was this done on purpose or is this an omission? > > BTW, how about adding a line about "Hardware VP9 Decoding" since recent > Intel GPU do support hardware VP9 decoding? Laurent, if this is still reproducible – I only have 45.9.0 here –, could you please create a separate report for this issue? That’d be great. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/83 ------------------------------------------------------------------------ On 2017-05-05T15:18:02+00:00 Pmenzel+bugzilla-mozilla-org wrote: @ehumphries, if I interpret the bug comments correctly, you flagged this report with *NEEDINFO*. Could you please tell us, what information is needed to get the feature implemented? Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/84 ------------------------------------------------------------------------ On 2017-05-05T15:20:23+00:00 Mhoye-4 wrote: "needinfo" is intended to call the attention of a specific person to the bug - I need information from X, to answer question Y. It's not intended as a nonspecific "we need more information to figure this out" thing, but it's true the term is a bit opaque. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/85 ------------------------------------------------------------------------ On 2017-06-22T07:22:11+00:00 Lordxraven wrote: (In reply to Paul Menzel from comment #11) > Laurent, if this is still reproducible – I only have 45.9.0 here –, could > you please create a separate report for this issue? That’d be great. Is there already a separate report for this issue? There are also some other useful informations gone (i can't remember exactly, but e.g. regarding OpenGL acceleration). Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/87 ------------------------------------------------------------------------ On 2017-06-22T07:39:30+00:00 Jyavenard-9 wrote: Yes, we also need accelerated layers to be able to render the frames. And right now, this has taken a set back and the feature has been disabled for now. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/88 ------------------------------------------------------------------------ On 2017-07-13T21:08:27+00:00 89c51 wrote: (In reply to Jean-Yves Avenard [:jya] from comment #15) > Yes, we also need accelerated layers to be able to render the frames. And > right now, this has taken a set back and the feature has been disabled for > now. Have you started doing work on this and you wait for accelerated layers to land in order to merge it or you will start after the layers? Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/89 ------------------------------------------------------------------------ On 2017-07-23T15:40:15+00:00 ojab wrote: Just FYI: https://chromium-review.googlesource.com/c/532294 this will be [chrome-parity] soon Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/90 ------------------------------------------------------------------------ On 2017-08-16T01:04:33+00:00 W-jan-k wrote: "The Quantum Flow (QF) initiative is a cross-component effort to improve user perceived responsiveness and performance." Could you please triage this if it would meet your demands for 57 or 58? Video hardware decoding is very desirable for Linux devices that: * do not have a powerful CPU * should be energy-efficient (laptops) * want to fluently play 4K videos on YouTube while using the CPU for compiling Nightly. ;-) There is new code from Chromium in comment 17 providing VAAPI hardware video decoding that could and should be shared, or not? If Mozilla and Google both would fix bugs it would result in far better stability for all users. Would it be possible? At least we have example code now. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/94 ------------------------------------------------------------------------ On 2017-08-16T02:02:42+00:00 W-jan-k wrote: (In reply to Jean-Yves Avenard [:jya] from comment #15) > Yes, we also need accelerated layers to be able to render the frames. Could we say we have a dependency to WebRender (instead of the current painting code) here, to prevent double work? Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/95 ------------------------------------------------------------------------ On 2017-09-19T01:04:23+00:00 Erdem U. Altinyurt wrote: Personally, I do NOT care about accelerated layers for rendering frames. Who cares? I just want to use "accelerated video decoding via HW" because solving the video codec exhaust many CPUs, not rendering frames after. Yes rendering via OGL will probably give much better results but who cares? We need accelerated youtube videos ASAP. Also, read the first reply of :jya at the topic, "for just decoding, not rendering (yet)." I believe, after 2 years, devs need to complete first step using current painting stack. Because this gonna hurt firefox project much more than other bugs. Since linux users cannot watch simple videos with FF, they gonna switch to Chrome soon. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/96 ------------------------------------------------------------------------ On 2018-03-18T11:41:42+00:00 sam tygier wrote: There is a bounty for this issue at https://www.bountysource.com/issues/55506502-add-va-api-hardware- decoding-support-on-linux Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/102 ------------------------------------------------------------------------ On 2018-05-02T18:18:00+00:00 Jonathan Watt wrote: Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.) Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/103 ------------------------------------------------------------------------ On 2019-06-03T16:52:04+00:00 Robert Mader wrote: The dependency of this bug could probably changed from ogl-linux-beta to bug 1491303, as webrender will replace all the old rendering architecture and is already enabled on linux + intel in nightly. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1424201/comments/120 ** Changed in: firefox Status: Unknown => Confirmed ** Changed in: firefox Importance: Unknown => Medium ** Bug watch added: freedesktop.org Bugzilla #47858 https://bugs.freedesktop.org/show_bug.cgi?id=47858 -- You received this bug notification because you are a member of UBUNTU - AL - BR, which is subscribed to Chromium Browser. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: The chromium team has done a great job to totally disable hardware decoding on Linux. Even ignoring the GPU blacklist does not enable GPU decoding. How ever the patch is quite simple and it's already working using this PPA ( using libVA ) : https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev the corresponding patch is here : http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff that would be great if we could have this patch indefault Ubuntu chromium build, this situation is really sad right now, google use linux to make chromeOS so chromebook are really good at playing videos but GNU/Linux chromium is slow at doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- Mailing list: https://launchpad.net/~linux-traipu Post to : linux-traipu@lists.launchpad.net Unsubscribe : https://launchpad.net/~linux-traipu More help : https://help.launchpad.net/ListHelp
