[x264-devel] Passing custom data through the encoder. (Kieran Kunhya)

[Jason Garrett-Glaser]

On Sat, Aug 13, 2011 at 4:36 AM, Dan Rosen <drosen at drdsystems.com> wrote:
>
>
> -----Original Message-----
> From: x264-devel-bounces at videolan.org
> [mailto:x264-devel-bounces at videolan.org] On Behalf Of
> x264-devel-request at videolan.org
> Sent: Saturday, August 13, 2011 6:00 AM
> To: x264-devel at videolan.org
> Subject: x264-devel Digest, Vol 51, Issue 8
>
> Send x264-devel mailing list submissions to
>        x264-devel at videolan.org
>
> On Fri, Aug 12, 2011 at 1:37 PM, Dan Rosen <drosen at drdsystems.com> wrote:
>>> When using the API, is there any way to pass data arbitrary frame data
>>> through the encoder so that we can relate information from the source
>>> YUV frame to the encoded frame? ?We could create a custom unregistered
>>> user data SEI, but then we would need to manually remove this SEI from
>>> the list of encoded NALs. ?Was hoping there would be an easier and
>>> lower overhead technique.
>>
>> Thanks, Dan Rosen
>
>>You mean something like this existing feature:
>  > /* private user data. libx264 doesn't touch this,
>  >      not even copy it from input to output frames. */
>  >  void *opaque;
>>Except that x264 copies the pointer through?
>>Jason
>
> Problem is, our developers say the pointer isn't copied.

That's why I said "except that x264 copies the pointer through".

Jason