Avidemux Forum

I am not optimistic about a chance to get this implemented as FFmpeg libraries libavcodec and libavutil Avidemux uses to decode HEVC (and most other video codecs) don't pass the distinction keyframe vs IDR to decoded pictures.

The "non-IDR recovery points" warning is just a warning to reflect poor guesswork in libavcodec when dealing with POC discontinuities, i.e. if the target video player is not FFmpeg-based, the chances are high that it will play such streams just fine.

The presence of IDR frames in an open-GOP H.264 or HEVC stream is not guaranteed at all, and even if present, they may be very far apart (minutes or even hours apart).

Calling in the script console

ed = Editor()
for frame in range(0, 1000):
    ed.printFrameInfo(frame)
will dump raw info from the demuxer about the first 1000 (replace 0 and 1000 with different integer values if desired) frames to Avidemux log (admlog.txt in %localappdata%\avidemux on Windows). Search the log for occurences of the "Flags 0110" string that identifies an IDR frame and for "Flags 0010" that identifies merely a keyframe to get an impression of the frequency of IDR frames in the stream.

What a pity, thats bad news.

Oh well, hopefully oneday someone will bring the progressbar back somehow.

Thank you for the explanation eumagga

LG MiMau

Unfortunately, Qt has removed this functionality (QWinTaskbarButton class and friends) in Qt6 without replacement. Our bug is just that QT_HAS_WINEXTRA is never defined, even if we build against Qt5 with the required QtWinExtras module present.

As Avidemux has switched to Qt6 for Windows as well, this nice feature has been lost.

Hi all,

please would it be possible to add the progressbar on windows taskbar, it worked on older avidemux versions, but in 2.8.2 it is missing again, and its frustrating to see just black instead of progress

Wäre es bitte möglich, den Fortschrittsbalken in der Windows Taskbar in Avidemux 2.8.2 wiederherzustellen, es hat in älteren Versionen funktioniert.

Could it be done just like here maybe: https://avidemux.org/smif/index.php/topic,16490.msg72924.html

Thanks very much for your help
LG MiMau

However, I've been using Avidemux to edit HEVC (H.265) sources and ran into the "non-IDR recovery points" warning when cutting at what the keyframe navigation buttons identified as a keyframe. As I understand it, HEVC allows CRA/recovery-point frames that look like keyframes but aren't true IDR frames, and Avidemux's next/previous-keyframe navigation doesn't currently distinguish between the two — so it's easy to land on a non-IDR point without realizing it, risking corrupted frame reordering in copy-mode cuts.

It would be a great addition to have an option (even a toggle) for keyframe navigation to jump specifically to true IDR frames for HEVC sources, rather than any I-frame-type frame. This would make it much easier to choose safe, reliably cuttable points without needing to cross-reference external tools first.

Thanks for all the work on Avidemux — it's been a genuinely useful tool for years. Avidemux rules!

Quote from: eumagga0x2a on July 30, 2026, 02:44:12 PM

Quote from: Rainman74 on June 16, 2026, 10:50:05 AM@eumagga0x2a Why do the current nightly builds no longer support NVENC? This unfortunately renders them unusable for me.

Should be fixed in the 260729 build.

Thank you very much!

Quote from: eumagga0x2a on July 31, 2026, 08:23:22 PM

Quote from: Mew12 on July 31, 2026, 10:14:00 AMRegardless of the settings, it removes some black areas from the image.
So deep blacks are gone.

I would interpret the screenshots as the "original" being a result of the renderer ("DXVA2"?) incorrectly interpreting fullrange (0 - 255) input as limited (16 - 235) range one thus losing all the details. The second screenshot looks correct to me.

Thanks for the reply.
I know what you mean, but it's the other way around—exactly as I described it.
When i use VirtualDub for example and it uses Limited, it looks correct like the original with Avidemux as i posted.
And if i use Full Range, deep blacks are also gone and it looks like the Wavelet sharpener output.

Quote from: Mew12 on July 31, 2026, 10:14:00 AMRegardless of the settings, it removes some black areas from the image.
So deep blacks are gone.

I would interpret the screenshots as the "original" being a result of the renderer ("DXVA2"?) incorrectly interpreting fullrange (0 - 255) input as limited (16 - 235) range one thus losing all the details. The second screenshot looks correct to me.

Hi,
i want to report a bug with the Wavelet sharpener.
Regardless of the settings, it removes some black areas from the image.
So deep blacks are gone.

Original
You cannot view this attachment.

Filter preview:
You cannot view this attachment.

Quote from: Rainman74 on June 16, 2026, 10:50:05 AM@eumagga0x2a Why do the current nightly builds no longer support NVENC? This unfortunately renders them unusable for me.

Should be fixed in the 260729 build.