On 2018-02-28 23:54, James Girotti wrote:
What I believe is happening is that ffmpeg
is single-threading (as it must to reliable transcode), but the thread
migrates between CPU cores. On my system this leads to much lower CPU
clock
speeds, because the up_threshold is never met long enough on a
.
Garri
W dniu 28.02.2018 o 14:44, Garri Djavadyan pisze:
Hello FFmpeg community,
I faced a problem with NVDEC/NVENC resources underutilization while
running one ffmpeg instance.
We use ffmpeg to convert various format videos to MP4(h264/aac) and
applying logo overlay. Hardware decoding
Hello FFmpeg community,
I faced a problem with NVDEC/NVENC resources underutilization while
running one ffmpeg instance.
We use ffmpeg to convert various format videos to MP4(h264/aac) and
applying logo overlay. Hardware decoding and encoding process is
performed by NVDEC and NVENC chips. For
On 2018-02-13 23:56, James Girotti wrote:
Recently, I faced transcoding issues with fully hardware nvdec/nvenc
scheme. Particularly, my FFmpeg feed fails with the following error
after
30-60 minutes of live transcoding:
I have recently encountered this as well, but with DVD video material.
Hello FFmpeg community,
Recently, I faced transcoding issues with fully hardware nvdec/nvenc
scheme. Particularly, my FFmpeg feed fails with the following error
after 30-60 minutes of live transcoding:
---
[h264_cuvid @ 0x556e21e67e00] Initializing cuvid hwaccel
[h264_cuvid @