[x264-devel] avoiding copying x264_picture_t
Loren Merritt
lorenm at u.washington.edu
Tue Aug 31 10:54:37 CEST 2010
On Mon, 30 Aug 2010, Jason Garrett-Glaser wrote:
> On Mon, Aug 30, 2010 at 1:40 PM, Dennis Munsie <dmunsie at gmail.com> wrote:
>
>> that would be less than ideal in my case -- I am currently receiving the
>> pictures to encode over shared memory, so if I had to copy the picture into
>> x264s buffer, I wouldn't gain anything. Another strike against me is that
>> my pictures are coming in as YV12, not NV12.
>> it sounds as though I wouldn't be able to get this working easily, so I'll
>> have to live with the overhead of copying.
>> Thanks!
>> dennis
>
> The passing a buffer is feasible, just harder to implement than x264
> giving you a buffer.
x264 still has to be able to choose the stride.
> The NV12 part is mandatory, as that's how x264 stores its data
> internally.
We could copy chroma and passthrough luma.
--Loren Merritt
More information about the x264-devel
mailing list