From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110616] vce module in h264 encode
Date: Mon, 06 May 2019 05:53:00 +0000 [thread overview]
Message-ID: <bug-110616-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1294 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110616
Bug ID: 110616
Summary: vce module in h264 encode
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: baopeng88_com@163.com
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2567 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-05-06 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 5:53 bugzilla-daemon [this message]
2019-05-06 8:57 ` [Bug 110616] vce module in h264 encode bugzilla-daemon
2019-05-06 9:10 ` bugzilla-daemon
2019-05-06 9:14 ` bugzilla-daemon
2019-05-24 7:40 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-110616-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.