![]() ![]() What is an issue? Always it’s work and from 2-3 months dosn’t work and I can’t work with hardware acceleration. |=|įfmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers | GPU GI CI PID Type Process name GPU Memory | Profile (-profile) The profile determines which features in the codec are supposed to be enabled, with each higher option requiring additional encoder work. Settings exclusive to H.264/AVC encoding. ![]() | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. Available with FFmpeg 4.4 and OBS Studio 27.2.x. | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ![]() dl_fn->cuda_dl->cuInit(0) failed → CUDA_ERROR_UNKNOWN: unknown errorĮrror initializing output stream 0:0 – Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or heightįew times I have error that device is not CUDA capable but how is it possible (I have newest LTS drivers). Sudo ffmpeg -i avengers.mp4 -c:v h264_nvenc -b:v 1M output.mp4 NVENC Preset Migration Guide This guide helps developers in knowing settings used in SDK v9.1 and their equivalents in SDK v10.0 and above. Firstly on Manjaro and then I reinstall it to Fedora. This guide provides a detailed discussion of the NVENC programming interface, describes setting up hardware for encoding and provides guidance on achieving maximum performance. From two months I can’t run ffmpeg encoding with hardware acceleration. The problem in UMS is that one parameter is hardcoded for ffmpeg and cant be changed -pixfmt yuv420p, the encoder h264nvenc not support this parameter. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |