-
Notifications
You must be signed in to change notification settings - Fork 368
HW decoding ? #26
Comments
Yes, definitely planned. Afaik ffmpeg can already support some hardware decoding by itself, but it will also be good to skip the step of reading back the frame to the CPU and pushing it into OpenGL again. |
I just hacked this - lsiudut@38fe128 Pure PoC (dog science 100%, first time touching VAAPI hwaccel) but I want to test it a bit and make a good PR - with proper options entry to enable hw decoding. For now this is just VAAPI. I got frustrated as sw decoding at FHD + 60 fps was sometimes saturating my i7-8650U (during scenes with lots of details). This seem to be helping a lot. Most of CPU is now wasted on converting surfaces from NV12 to YUV420P. I'm pretty sure that there's a way to display image directy from VAAPI surface... |
So, CPU usage is still quite high: (1) solor space conversion - nv12->yuv420p Even though CPU load is predictable (pretty much the same all the time, no more peaks), definitely lower than w/o hw decoding and finally - I haven't experience any artifacts until now (~2h gameplay). I'll come up with more solid numbers once I clean the code up and put PR. |
Nice, looking forward to it! |
Yea I put up #205 , just to move things forward. Probably far from elegant, but let's start poking on this, sooner better :). |
Chiaki is an awesome projet, thank you for your work 👏
Do you plan to enable HW decoding acceleration using apis like vaapi ? I think this should greatly reduce latency.
The text was updated successfully, but these errors were encountered: