Avidemux 2.8.2 development

[Mew12]

Regardless 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.

[Rainman74]

@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!

[efa]

I think it's very important Avidemux should give a warn when sees an unsupported stream in MKV (like soft subtitles), that will be removed on conversion/copy of audio/video streams.
I'm quite advanced user but converted many video before realizing it removed all of that. Fortunately of some I kept the original, extracted subtitles and re-added, but some I lost the subs.
I Imagine many users fall on this, and it is a subtle dataloss bug/rfe.

Currently 2.8.2 nightly 260516 on Debian 13