Re: [Libva] keep Nalu start code in VASliceDataBufferType data

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 08/31/2016 09:52 AM, Xiang, Haihao wrote:
On Tue, 2016-08-30 at 08:59 +0800, Randy Li wrote:
Hi all:
   When I just doing the driver for us chip, we would request the
Nalu
header present in the data to be process. But I found the data be
Rendered to with type VASliceDataBufferType is removed the Nalu start
code. Is there any way to make the client send the data without
remove
the start code ? Thank you.

Do you mean the start code prefix 0x000001?  It depends on the codec,
VA-API has this requirement for HEVC, but no for AVC.

For AVC, I don't think the existing softwares using vaapi send the
prefix to driver, you have to workaround it in your driver. but if the
application is developed by yourself, you may send the prefix with
setting the right slice_data_offset, so other drivers can work well
with your application.
I see thank you. I think the Intel could handle the offset. So I think it could be regard as a bug for Gstreamer. I would report the Gstreamer.


--
Randy Li
The third produce department

_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx




[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux