-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testing dGPU - ARC DG2 - decoding errors - edge cases - 4:4:4 12bit #100
Comments
Thank you for sharing decode isssues.
|
ok, I was testing 4K HDR P3 PQ 444 60fps material - perhaps that was too much for the hardware decoder - avsw working fine with all input files. source file is Prores 4444 xq working fine with avsw: but I think those are only edge cases for testing the hardware features - production workflow would not re-encode with libx265 or libaom-av1 444 12bit lossless before further processing |
just to really complete the decoder test, I also tested all (most combinations) of the other input formats (every format works with avsw, the following list is only for avhw/avqsv):
btw. I think I'm done decoder testing atm. - I'll keep those ffmpeg/generated test files to test them with all the future driver/qsvencc releases - perhaps I'll automate that step with a little script for windows/linux |
I was able to reproduce the HEVC 12bit 4:4:4 created myself using x265 lossless, running into "device operation failure". It seems like it might be hardware limitation (or driver issue?), as there were no problem found in the application side, the bitrate of the input file was 4317Mbps, way too high... |
thank you @rigaya for the confirmation - as you can see in my previous post I could make everything to work with hardware decoding except VP9 decode (tested profile 2+3) - either it is just my test files that go too far or there is still an error somewhere in the complete software stack. (btw. VP9 encoding works, slow but it works - but decoding no chance so far). btw. I would close that issue #100 at the current state and create a new one if something noteworthy would change to the better or worse in the future if that is ok with you. btw. one last technical question, perhaps you know the answer or can tell me where I can find some more info: --> crop/resize and vpp-deinterlace uses the the 1st or the 2nd "Video processing" engines ==> but why do some movies use "Video decode 1" engine and some others use both "Video Decode" engines? even if the first one is not saturated at all? |
Hello @rigaya
atm. I'm testing the Intel ARC dGPU (A380), everything working brilliantly using windows/current windows beta driver (31.0.101.3793) - but linux is a bit troublesome so far (intel devs: 6x kernel driver not ready, backport-i915 some errors, intel media-driver not en par with windows etc.)
linux --check-features output differs from windows:
btw. could you test the 4:4:4 decode so far?
I tried (high bitrate):
--> that works, but it looks like there are some bitrate limits, lossless HEVC produces some reproducible errors when bitrate gets too high
--> I could not get that working at all - did you?
==> everything else (low bitrate) is working fine, except VC1 decoding, that is painfully slow because of no hardware support in libvpl...and all those mem copy things
btw. if you need some samples/test material, I can provide you those - just tell me where to send those files/links
Kind regards
edit: we need a party in qsvenc - issue #100 now ;-) #100
The text was updated successfully, but these errors were encountered: