[VDPAU] Support H264 Hi10 via vdpau
Peter Frühberger
peter.fruehberger at gmail.com
Mon Oct 28 19:40:52 CET 2013
Thx for your reply,
> ... although actually looking at the new fields you're adding, won't the
> values *always* be "10" if the new profile is in use? I think you only
> need to do one of adding a new profile value, or adding new fields to the
> picture info struct, not both?
this would be a an even more minimal approach to get those two fields
shipped. But as we have to decide if the target decoder can actually
do hi10p an new profile with a new extended struct would perhaps be
the better idea. So the actual vdpau decoder can tell itself if it
supports hi10p or not.
I don't know what happens when e.g. nvidia vdpau gets hi10p data in
the edited picture struct without a chance to distinguish it.
like
@@ -2821,6 +2821,12 @@ typedef struct {
/** See \ref VdpPictureInfoH264 for instructions regarding this field. */
VdpReferenceFrameH264 referenceFrames[16];
+
+ /* The following two fields are used for Hi10p */
+ /** Copy of the H.264 bitstream field. */
+ uint8_t bit_depth_luma_minus8;
+ /** Copy of the H.264 bitstream field. */
+ uint8_t bit_depth_chroma_minus8;
} VdpPictureInfoH264;
In that case the vdpauinfo patch would also not be needed.
Best Regards
Peter
--
Key-ID: 0x1A995A9B
keyserver: pgp.mit.edu
==============================================================
Fingerprint: 4606 DA19 EC2E 9A0B 0157 C81B DA07 CF63 1A99 5A9B
More information about the VDPAU
mailing list