keep Nalu start code in VASliceDataBufferType data

keep Nalu start code in VASliceDataBufferType data

[Randy Li]

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.

P.S Thank you for the Intel guys help, I decided not to use the DRM 
framework to implement the interface in kernel after I talked to the 
kernel upstream. But the request API would be used.
-- 
Randy Li
The third produce department

_______________________________________________
Libva mailing list
Libva@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libva

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

[Xiang, Haihao]

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.

> 
> P.S Thank you for the Intel guys help, I decided not to use the DRM 
> framework to implement the interface in kernel after I talked to the 
> kernel upstream. But the request API would be used.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Randy Li]

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@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx