Originally posted by bug77
View Post
Announcement
Collapse
No announcement yet.
Firefox 80 To Support VA-API Acceleration On X11
Collapse
X
-
Originally posted by 240Hz View PostBut xOrG iS abAndoNEd
Comment
-
Originally posted by horizonbrave View PostWhat this brings to the table? Just a bit of power efficiency for laptop users??
- Likes 2
Comment
-
-
Originally posted by horizonbrave View PostSorry I missed the memo and I'm dumb as fuck. What this brings to the table? Just a bit of power efficiency for laptop users??
Thanks
Originally posted by Veto View Post
Well, let's have a look at your assertion: That is 15 floating point operations per pixel you show there. So you need 15*1920*1080*60 = 1 866 240 000 or approximately 2 GFLOPS just to do a simple YUV conversion on your CPU. For 4k video that will be 7½ GFLOPS...
Of course a real implementation will apply some tricks, but still... There is a reason why specialized hardware is a win when doing video conversions!
Of course, it's not just the transformation, so I'd accept a 5-10% CPU overhead. Anything on top of that, just screams of sloppy programming somewhere in the stack.
Comment
-
Originally posted by pal666 View Postit's the other way around. market share is a result of user choice. i.e. everyone already switched to chrome and improvements in firefox will not affect majority of users
Firefox has taken huge steps forward since Fx 75 and finally I can feel satisfied personally.
- Likes 1
Comment
-
Originally posted by bug77 View PostFreeing the CPU from some tasks usually yields a smoother experience. Also, when playing back several streams, without hardware acceleration even a modern CPU will choke. Fast.
That still works out to 15*1920*1080 or ~31MFLOPS every frame (~16ms). A CPU shouldn't even notice that, especially with SIMD.
Of course, it's not just the transformation, so I'd accept a 5-10% CPU overhead. Anything on top of that, just screams of sloppy programming somewhere in the stack.
- Likes 1
Comment
-
Originally posted by pal666 View Postyou are being silly. process node advancements apply to progress from 8 years old intel cpu to 14nm intel cpu.
but 8 year old intel cpu wasn't able to play video.
(and btw intel's 14nm is 6 years old)
it is better in many ways, but it is worse in hardware video decode way(especially when hardware video decoding parts of your laptop aren't used)Last edited by caligula; 05 July 2020, 10:03 AM.
Comment
-
Originally posted by treba View Post
That's assuming all the data is in L1 cache. But I think you are somewhat right - YUV - RGB translation apparently is not the main show stopper. It just adds to it and doing it on the GPU is more efficient. BTW, this motivated the the whole DMABUF implementation in the first place, see https://bugzilla.mozilla.org/show_bug.cgi?id=1580169
Decoding video id far from being my strong point, but it's pretty obvious something's amiss here.
And don;t get me started on Windows, where a fairly powerful laptop cannot output smooth video, no matter the amount of hardware decoding, because DPC woes...
Comment
Comment