Bug 110616 - vce module in h264 encode
Summary: vce module in h264 encode
Status: RESOLVED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-06 05:53 UTC by baopeng
Modified: 2019-05-24 07:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description baopeng 2019-05-06 05:53:00 UTC
We have a playback problem in the vce module of the amd graphics card, when using libva for h264 encoding, the field of pic_order_cnt_type in sps supports other options besides 0? Includes 1 or 2 and so on.
      Pic_order_cnt_type specifies the encoding method for poc (picture order count), and poc identifies the playback order of the images. The poc can be calculated from the frame-num through the mapping relationship, or it can be explicitly transmitted by the encoder.
      When pic_order_cnt_type = 2, the POC calculation method relies on the least extra parameters (can save the number of bits in the slice header), and it can only get the serial number of the top and bottom fields according to frame_num. We need to play it quickly in this way.
Comment 1 Michel Dänzer 2019-05-06 08:57:52 UTC
Please attach the corresponding output of dmesg and vainfo.
Comment 2 baopeng 2019-05-06 09:10:57 UTC
(In reply to Michel Dänzer from comment #1)
> Please attach the corresponding output of dmesg and vainfo.


It doesn't matter with dmesg and vainfo ? 
Dmesg and vainfo can't see anything
Comment 3 Michel Dänzer 2019-05-06 09:14:22 UTC
We need the information printed by dmesg and vainfo, otherwise we cannot help you.
Comment 4 Andre Klapper 2019-05-24 07:40:53 UTC
No reply by the reporter, hence closing.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.