> I'm trying to put together a patch, but I'm struggling a bit setting up to
> build.
I just pushed the neccesary changes.
Works slightly diffrent than on x264, as the option it has seems a bit
broken, seeing that both 0 and 1 force IDR frames:
x4->forced_idr >= 0 ? X264_TYPE_IDR : X264_TYPE_KEY
Hello,
I've been experimenting with encoding with a cuda card, and I noticed
that setting the pict_type member of the AVFrame structure to
AV_PICTURE_TYPE_I >does not trigger it to encode the next frame as an IDR
frame as libx264 does. I looked at the nvidia docs a
On 10/12/2016 7:45 PM, Grant Brownewell wrote:
>>> Hello,
>>>
>>> I've been experimenting with encoding with a cuda card, and I noticed that
>>> setting the pict_type member of the AVFrame structure to AV_PICTURE_TYPE_I
>>> >does not trigger it to encode the next frame as an IDR frame as libx2
>> Hello,
>>
>> I've been experimenting with encoding with a cuda card, and I noticed that
>> setting the pict_type member of the AVFrame structure to AV_PICTURE_TYPE_I
>> >does not trigger it to encode the next frame as an IDR frame as libx264
>> does. I looked at the nvidia docs and it appea
On 10/12/2016 4:15 PM, Grant Brownewell wrote:
> Hello,
>
> I've been experimenting with encoding with a cuda card, and I noticed that
> setting the pict_type member of the AVFrame structure to AV_PICTURE_TYPE_I
> does not trigger it to encode the next frame as an IDR frame as libx264 does.
>
Hello,
I've been experimenting with encoding with a cuda card, and I noticed that
setting the pict_type member of the AVFrame structure to AV_PICTURE_TYPE_I does
not trigger it to encode the next frame as an IDR frame as libx264 does. I
looked at the nvidia docs and it appears there is a mecha
