On Sun, 13 Nov 2016 23:50:03 +0100
Carl Eugen Hoyos wrote:
> 2016-11-11 12:15 GMT+01:00 wm4 :
> > On Fri, 11 Nov 2016 10:19:08 +0100
> > Carl Eugen Hoyos wrote:
> >
> >> 2016-11-11 9:03 GMT+01:00 Hendrik Leppkes :
> >> > On Fri, Nov 11, 2016 at 6:34 AM, Yogender Gupta
> >> > wrote:
>
>
2016-11-11 12:15 GMT+01:00 wm4 :
> On Fri, 11 Nov 2016 10:19:08 +0100
> Carl Eugen Hoyos wrote:
>
>> 2016-11-11 9:03 GMT+01:00 Hendrik Leppkes :
>> > On Fri, Nov 11, 2016 at 6:34 AM, Yogender Gupta wrote:
>> >> The included patch should fix.
>> >>
>> >
>> > ffmpeg.c is in the middle of some chan
On Sun, Nov 13, 2016 at 4:46 PM, Yogender Gupta wrote:
>> I created a simpler patch that avoids modifying the external signature
>> of the function, and it still fixes it for me. Can you test and
>> confirm? Then we can apply this.
>
>
>> Just tested this patch, and I can confirm that at least a c
> I created a simpler patch that avoids modifying the external signature
> of the function, and it still fixes it for me. Can you test and
> confirm? Then we can apply this.
> Just tested this patch, and I can confirm that at least a cuvid hwaccel
> transcode works again.
I also verified the
> I created a simpler patch that avoids modifying the external signature
> of the function, and it still fixes it for me. Can you test and
> confirm? Then we can apply this.
Just tested this patch, and I can confirm that at least a cuvid hwaccel
transcode works again.
On Fri, Nov 11, 2016 at 12:47 PM, Yogender Gupta wrote:
>>>These are merges. Unless you volunteer to do the merges yourself (and
>>>properly please) you'll have to live with this.
>
> So were there merges that got left and broke the functionality. When do we
> get these merges in ? Please let me
2016-11-11 14:47 GMT+03:00 Yogender Gupta :
> >>These are merges. Unless you volunteer to do the merges yourself (and
> properly please) you'll have to live with this.
>
> So were there merges that got left and broke the functionality. When do we
> get these merges in ? Please let me know if I can
>>These are merges. Unless you volunteer to do the merges yourself (and
>>properly please) you'll have to live with this.
So were there merges that got left and broke the functionality. When do we get
these merges in ? Please let me know if I can help get this up and fixed. There
have been vari
On Fri, 11 Nov 2016 10:19:08 +0100
Carl Eugen Hoyos wrote:
> 2016-11-11 9:03 GMT+01:00 Hendrik Leppkes :
> > On Fri, Nov 11, 2016 at 6:34 AM, Yogender Gupta wrote:
> I was trying libnpp on Big Bunny video by below command:
> >>
> >>
> >>
> ./ffmpeg -loglevel debug -y -hwaccel cuvid
2016-11-11 9:03 GMT+01:00 Hendrik Leppkes :
> On Fri, Nov 11, 2016 at 6:34 AM, Yogender Gupta wrote:
I was trying libnpp on Big Bunny video by below command:
>>
>>
>>
./ffmpeg -loglevel debug -y -hwaccel cuvid -c:v h264_cuvid -vsync 0 -i
>>
/root/root/bunny.mp4 -vf scale_npp=1920:1072
>> ffmpeg.c is in the middle of some changes being merged, and once that is
>> done ffmpeg_cuvid.c will need to be adapted to a new system. Until then, it
>> would make everything easier if the code actively >> being modified by these
>> merges is not modified by hackish fixes.
When do we expec
On Fri, Nov 11, 2016 at 6:34 AM, Yogender Gupta wrote:
>>>I was trying libnpp on Big Bunny video by below command:
>
>
>
>>>./ffmpeg -loglevel debug -y -hwaccel cuvid -c:v h264_cuvid -vsync 0 -i
>
>>>/root/root/bunny.mp4 -vf scale_npp=1920:1072 -vcodec h264_nvenc
>
>>>/tmp/tmp0.264 -vf scale_npp=1
>>I was trying libnpp on Big Bunny video by below command:
>>./ffmpeg -loglevel debug -y -hwaccel cuvid -c:v h264_cuvid -vsync 0 -i
>>/root/root/bunny.mp4 -vf scale_npp=1920:1072 -vcodec h264_nvenc
>>/tmp/tmp0.264 -vf scale_npp=1280:720 -vcodec h264_nvenc /tmp/tmp1.264
>>This command is wor
13 matches
Mail list logo
