cizekmilan

I am definitely in favor. I would like something like scale_npp or cuda_yadif (deinterlace). But if that's possible, I have no idea.

I have the same problem. The application of the patch shows some errors.

I used nv-jetson-nano-sd-card-image-r32.4.2.zip image, then I did apt upgrade/update and then compile nvmpi and ffmpeg. **Jetpack 4.4 DP [L4T 32.4.2]**

git apply seems OK ``` # git apply -v ffmpeg_nvmpi.patch Checking patch configure... Checking patch libavcodec/Makefile... Checking patch libavcodec/allcodecs.c... Checking patch libavcodec/nvmpi_dec.c... Checking patch libavcodec/nvmpi_enc.c... Applied patch configure cleanly. Applied...

yes, NVENC shows 384MHz (instead of OFF). One from CPU cores still utilized to 100% with -pix_fmt yuv420p. With real h264 mp4 as input... all cores 100% but with nvenc....

ffmpeg was compiled without errors with ./configure --enable-nvmpi?

Hello, > What specifically are you disappointed with, and what were you expecting? > framerate? encode quality? something else? you are right. I'm getting probably even higher performance at hevc...

I have one more question. It seems to me that the bitrate setting is ignored, compared to other codecs. I define e.g.: to HEVC: -profile:v main -level:v 4.1 -minrate 4000k...

Hi, here is my shared folder with all results: https://bit.ly/3k29qKg. Please check script for transcoding **DP_cpu-nvmpi-test.sh** (I deliberately do not use hw decoding here). In some cases I do deinterlace...

maybe, better - more universal is make -j$(nproc)