From: Sheikh Afnan via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Sheikh Afnan <sheikh15520011@gmail.com>
Subject: [FFmpeg-devel] NVENC regression in newer FFmpeg builds; CPU encoding works correctly and fixes MPEG artifacts
Date: Sat, 27 Dec 2025 18:26:13 +0530
Message-ID: <CALaz=br3i=MK+37ipoEMAdXzsMoJtmApaiCwSbKvqbdpUXagVw@mail.gmail.com> (raw)
Hello FFmpeg Team,
I would like to report observations comparing older FFmpeg builds with
newer releases (latest from gyan), specifically regarding NVENC support and
MPEG handling.
Behavior with older FFmpeg builds:
- NVENC (h264_nvenc) works correctly on NVIDIA GTX 1660 Super and RTX 3050
systems.
- Using explicit colorspace and range settings (BT.709, limited/TV range)
produces correct colors.
- However, when processing MPG/MPEG files, visible horizontal line
artifacts (interlacing/combing on faces) appear, even though these
artifacts are not present in the original source files.
Behavior with newer FFmpeg builds (latest gyan):
- CPU-based encoding (libx264, CRF 25) produces correct output:
- Colors appear correct without forcing colorspace parameters.
- MPG/MPEG files no longer show the face-line/interlacing artifacts seen
in older builds.
- NVENC, however, does not function correctly:
- NVENC is unavailable or fails to initialize on systems where it
previously worked.
- This affects both NVIDIA GTX 1660 Super (driver 12.4) and RTX 3050
systems (driver 12.x).
- As a result, applications are forced to use CPU encoding in newer
builds.
In summary:
- Newer FFmpeg builds improve CPU-side decoding and MPEG handling.
- NVENC support that worked reliably in older builds appears to regress or
become incompatible in newer builds for the same hardware and driver
environments.
I would appreciate clarification on:
- Whether there have been intentional changes or increased requirements for
NVENC initialization in FFmpeg 6.x.
- Any recommended steps to restore NVENC functionality on supported GTX and
RTX GPUs.
- Whether this NVENC behavior is expected or considered a regression
compared to older builds.
Thank you for your continued work on FFmpeg. Any guidance would be greatly
appreciated.
Best regards,
Sheikh Afnan
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2025-12-27 12:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALaz=br3i=MK+37ipoEMAdXzsMoJtmApaiCwSbKvqbdpUXagVw@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=sheikh15520011@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git