>Correction:
>
>./ffmpeg -init_hw_device cuda=0 -filter_hw_device 0 -i ../4k_normal.mp4 -vf
>format=nv12,hwupload,scale_npp=1280:720 -c:v h264_nvenc 720p1.mp4
OK that is good
$ time ./ffmpeg -init_hw_device cuda=0 -filter_hw_device 0 -i
../4k_normal.mp4 -vf format=nv12,hwupload,scale_npp=1280
On Sat, 2 Feb 2019 at 19:39, Mahmood Naderan wrote:
> >Using your sample above:
> >
> >./ffmpeg -init_hw_device cuda=0 -i ../4k_normal.mp4 -vf
> >format=nv12,hwupload,scale_npp=1280:720 -c:v h264_nvenc 720p1.mp4
> >
> >Try that and report back.
> >
> >
>
> It fails
>
>
> $ time ./ffmpeg -init_hw_
>Using your sample above:
>
>./ffmpeg -init_hw_device cuda=0 -i ../4k_normal.mp4 -vf
>format=nv12,hwupload,scale_npp=1280:720 -c:v h264_nvenc 720p1.mp4
>
>Try that and report back.
>
>
It fails
$ time ./ffmpeg -init_hw_device cuda=0 -i ../4k_normal.mp4 -vf
format=nv12,hwupload,scale_npp=1280:720
On Sat, 2 Feb 2019 at 18:47, Mahmood Naderan wrote:
> >Then don't use the cuda filter.
>
> So, my time measurements show that
>
> CPU: ./ffmpeg -i ../4k_normal.mp4 -vf scale=1280:720 720p1.mp4
> real0m23.748s
>
> GPU: ./ffmpeg -hwaccel cuvid -c:v h264_cuvid -i ../4k_normal.mp4 -vf
> scale_n
On Sat, 2 Feb 2019 at 19:09, Mahmood Naderan wrote:
> >Note that hardware accelerated
> >decode is targeted for real time PLAYBACK without using any CPU resources,
> >and does not necessarily imply to be faster than a software based decode.
>
> If I got the point, you are saying that GPU version
>Note that hardware accelerated
>decode is targeted for real time PLAYBACK without using any CPU resources,
>and does not necessarily imply to be faster than a software based decode.
If I got the point, you are saying that GPU version is somehow used to free
CPU cores, so that CPU cores are ready
On Thu, Jan 31, 2019, 22:45 Mahmood Naderan Hi,
> I want to run a multicore CPU job with ffmpeg and I think the command
> should be
>
> ./ffmpeg -i ../4k_normal.mp4 -vf scale_npp=1280:720 720p1.mp4
>
> but it fails
>
> ./ffmpeg -i ../4k_normal.mp4 -vf scale_npp=1280:720 720p1.mp4
> ffmpeg versio
>Then don't use the cuda filter.
So, my time measurements show that
CPU: ./ffmpeg -i ../4k_normal.mp4 -vf scale=1280:720 720p1.mp4
real0m23.748s
GPU: ./ffmpeg -hwaccel cuvid -c:v h264_cuvid -i ../4k_normal.mp4 -vf
scale_npp=1280:720 -c:v h264_nvenc 720p1.mp4
real0m20.889s
Do you thi
2019-01-31 21:06 GMT+01:00, Mahmood Naderan :
>>I believe if you want to use the cuda scaling filter you should also
>>use cuda decoding.
>
> The original cuda compatible run is
>
> ./ffmpeg -hwaccel cuvid -c:v h264_cuvid -i ../4k_normal.mp4 -vf
> scale_npp=1280:720 -c:v h264_nvenc 720p1.mp4
>
> I
>I believe if you want to use the cuda scaling filter you should also
>use cuda decoding.
The original cuda compatible run is
./ffmpeg -hwaccel cuvid -c:v h264_cuvid -i ../4k_normal.mp4 -vf
scale_npp=1280:720 -c:v h264_nvenc 720p1.mp4
I want to do that with multicore CPU. That command basically
2019-01-31 20:39 GMT+01:00, Mahmood Naderan :
> I want to run a multicore CPU job with ffmpeg and I think
> the command should be
>
> ./ffmpeg -i ../4k_normal.mp4 -vf scale_npp=1280:720 720p1.mp4
I believe if you want to use the cuda scaling filter you should also
use cuda decoding.
Carl Eugen
Hi,
I want to run a multicore CPU job with ffmpeg and I think the command
should be
./ffmpeg -i ../4k_normal.mp4 -vf scale_npp=1280:720 720p1.mp4
but it fails
./ffmpeg -i ../4k_normal.mp4 -vf scale_npp=1280:720 720p1.mp4
ffmpeg version N-93005-gd92f06eb66 Copyright (c) 2000-2019 the FFmpeg
dev
12 matches
Mail list logo
