Some current 2.8.2 feedback

[Urik]

It's really been a while since I've updated avidemux or really checked around here.
Probably because it just worked (works) and frankly I've been using it casually but regularly.
When I started using it, I was mostly using it to trim rather large gaming videos in copy/rewrap mode.
But since then I've been using it more with re-encoding, also utilizing filters like resize/crop and exporting with nvenc. It really became like a universal tool if I wanna quickly cut/compress something and send in a message, or in a chat or social.

I've been sitting on 230514, now recently I've tried 250407, 240128 and 241214. If it wasn't for messages here I didn't even notice first stuff like nvenc/opengl/fdk aac was broken in 2025 releases due to some git/MSVC issues eumagga has mentioned.

Some notes (all about VC++ on Win11/Intel/Nvidia):

• starting from 250101, it correctly selects dark mode in "default" setting (i.e. follows Windows mode)
• the "video is late by ... ms" desync alert in status bar is a nice addition
• I still use OpenGL + HW Accel because DXVA2 display is washed out (gamma shifted) and pixelated (windows hidpi scaling?) on my 4k monitor, and QT is just laggy. I often scale the preview to 1:4 for 4k to make it easier for playback
• unchecked GUI "limit refresh rate" because I like to see timecode update in real time
• I can confirm 241214 is the most recent one with working nvenc/opengl/fdk aac
• Maybe slightly offtopic, I have just recently installed new nvidia drivers (572.83) and both nvenc encoders work fine with 241214 (tho I only tested default VBR mode). The reason I updated was newer FFMPEG I also recently installed wouldn't work with an older 2024 nvidia driver citing old API so I had to. My old ffmpeg batch scripts also still work with newer drivers and new ffmpeg. And I do still have the old 1080 Ti.
• I was definitely grumpy noticing the generation of .idxb files, glad the mentioned solution works for now
• also left a reply here since I felt it was more relevant there

[eumagga0x2a]

"DXVA2" (DirectX) video display is oversaturated on my test Windows 11 installation, easily detectable by displaying a fullrange grayscale image. It looks there are settings in the graphics driver which can take precedence over whatever an application does.