Announcement
Collapse
No announcement yet.
Hi10P Support Proposed For VDPAU
Collapse
X
-
(forgot to mention: my hw list was for accelerated decoding in general. I don't know if all that hw is 10-bit capable.)
-
Originally posted by AdamW View PostSo help me out here - gotta admit I'm not really au fait with all this 'state tracker' stuff. Executive summary: does this mean we'll get trouble-free HW-accelerated decoding of hi10p in XBMC running on top of...open drivers? Proprietary drivers? In the fairly near term? What would be the oldest HW that would support this decoding? Thanks!
Most of hd4000, everything of hd5000 and up.
Leave a comment:
-
Originally posted by ryszardzonk View PostThanks. Compiled fine with trivial fix of placing ":" instead of ";" in second part of first patch. However does not seem to get picked up by XBMC where it still is using "ff-h264" for decoding at least in my case
But yeah, I can't believe I'm writing this, but if it works fine I might end trading the nvidia gpu on my media center pc with an amd one, as right now I need a very heavy overclock (+1GHz) to play 10-bit 1080p content perfectly (not a very recent CPU).
Leave a comment:
-
Originally posted by fritsch View PostFor those playing with it, i missed to squash a commit before posting, which resulted in a build error. Should work now: http://sprunge.us/WacV
Leave a comment:
-
Some features I'd like to see in the VDPAU state tracker:
High quality deinterlacing: DEINTERLACE_TEMPORAL and DEINTERLACE_TEMPORAL_SPATIAL
High quality scaling: HIGH QUALITY SCALING - L1 (even this would be enough which is all my nvidia card supports)
Not sure if these are strictly nvidia hardware based or if it can be done on Radeon hardware as well.
On a somewhat related note, I'd like to see triple buffered vsync for all of the Mesa drivers. Yeah, it takes more memory but it's superior to regular vsync when performance is needed (and tends to lower input lag a bit as well)
Leave a comment:
-
For those playing with it, i missed to squash a commit before posting, which resulted in a build error. Should work now: http://sprunge.us/WacV
Leave a comment:
-
Originally posted by AdamW View PostSo help me out here - gotta admit I'm not really au fait with all this 'state tracker' stuff. Executive summary: does this mean we'll get trouble-free HW-accelerated decoding of hi10p in XBMC running on top of...open drivers? Proprietary drivers? In the fairly near term? What would be the oldest HW that would support this decoding? Thanks!
2) This is acheaved by common API entry points (classic + gallium) and some common helper code (classic + gallium) and with State Trackers (gallium).
3) State trackers try to implement given API (OpenGL, OpenGL ES, OpenMAX, etc.) in general terms. Leaving blank spaces for dealing with actuall hardware.
4) Drivers fill in that blanks with actuall code.
5) This way, repeatable code IS NOT repeated in all those drivers.
(And obviously, if someone advance or create State tracker, other gallium drivers can build on that code -> Nouveau theam is usually fast to add any needed code if AMD crew add something to OpenGL State tracker. Which benefit them greatly due to small HR pool)
So:
State tracker means possibility of supporting something. GPU drivers must support it too thoug to make it work.
Leave a comment:
-
Originally posted by johnc View PostI don't know much about UVD... Is this a dedicated DSP for decoding and if not, is it any better than just using software?
Leave a comment:
Leave a comment: