Avidemux Forum

Avidemux is a great tool, it would be even better with 4:2:2 YUV ability.
Will Avidemux ever make the leap to 4:2:2 and if not, why?

Well, to run at least recent Avidemux appImages on Trixie, you need to install libfuse2t64 and libpcre2-16-0:

sudo apt update
sudo apt install libfuse2t64 libpcre2-16-0
Thank you for reporting the problem --> on my todo list with priority.

Didn't have time to try to compile Avidemux on Debian 13.2 yet, but will do it soon.

Quote from: Kohlhaas on November 30, 2025, 06:43:53 PMWhen I start the app image in the terminal, I get several error messages.

Using the latest available (from May 30 2025) appImage from https://avidemux.org/nightly/appImage4Buster/, please reproduce the issue and post the error messages. I didn't have time to setup a VM with Debian 13 to test myself yet, unfortunately.

Quote from: Kohlhaas on November 30, 2025, 06:43:53 PMCompiling with the downloaded sources also did not work; the compiler issued various error messages that I did not understand.

No problem with not understanding the errors, but, obviously, with not providing any directly usable information. If you are not comfortable with providing build or CMake logs as attachments publicly (rename them to add extension ".txt" to be accepted by the forum software) or via pastebin web service, you may send them in a personal message (PM).

I discovered what is causing my HEVC-to-AVC conversions to screw up, resulting in a file with less than 15fps...

It seems that "good" HEVC files that convert to AVC flawlessly have a framerate of 23·976023, whereas the "bad" HEVC files have a framerate of 23·9876215.

Through some experimenting, it seems that if I use Avidemux's Video filter to Resample the FPS (retaining speed & duration) at 23·976 (film) and resave as HEVC, it indeed corrects the framerate to 23·976023. However, the playback is stuttery and jerky.

Apparently, that difference of 192fps makes a noticeable difference.

I think I also used the Constant Bitrate (1-pass) filter @ 2500kbits/sec - perhaps I will try the Constant Rate Factor (1-pass), Constant Quantiser (1-pass), and Video Size (2-pass) options in combination with the Resample FPS filter, though I have my doubts it will affect anything (but who knows).

Assuming these adjustments to the filters do not help keep the modified FPS smooth and stutter-free, my question is : HOW DO I FIX THIS stutter problem?

How do I get the HEVC framerate modified FROM the crappy 23·9762015 fps, TO the proper 23·976023 fps, so that it will play back smoothly, and thereby convert to AVC flawlessly?

(*sigh* Why can't these things just be encoded ONE way, the right way, in the first place?) 

When I accidentally closed the avidemux_jobs window the list comes up as empty even though the progress window and  the window batch file are still running.

Is there a way to restore the list?

Thanks

I am a fairly inexperienced user of Avidemux, which I have been using with great satisfaction for years.

However, I have now switched from a mini PC with an AMD processor to a mini PC with the latest Intel processor (Intel Core Ultra 9 255H) and at the same time upgraded my Linux system from MX-Linux 23 to MX-Linux 25 (Debian Trixie based).

Unfortunately, Avidemux no longer works after this action.
When I start the app image in the terminal, I get several error messages.
Compiling with the downloaded sources also did not work; the compiler issued various error messages that I did not understand.

There is only one thing I can do: ask the 'experts' here in this forum for help.
Thank you in advance.

Looking at the code, the issue should persist in the current pre-2.8.2 codebase. It is a general issue with case-insensitive filesystems, not just on Windows.

Thank you for your report.

I am using the Windows version 2.8.1.  When saving a *.mp4 or *.mkv file, the program adds "_edit" to the filename when saving into the source folder.  It does not add "_edit" when saving a *.MP4 or *.MKV file.  It does detect that a file already exists and prompts to either overwrite or change the filename.  In Windows, filenames are not case sensitive, so saving a file named aaa.mp4 will overwrite an existing aaa.MP4 file.  Suggest that in Windows "_edit" should be appended to the saved filename regardless of the case of the file extension.

Thank you, so it was apparently related to VP9 decoding in hardware via DXVA2. If crashes resume, please try disabling hw accelerated decoding first.

Having different versions of Avidemux present on the system should not matter as long as none share an install directory and none run simultaneously. However, unless they are run in portable mode (requires write permissions to program folder), they all would share the same profile (%appdata%\avidemux) which may result in problems due to incompatible changes to configuration.

Except for the installer, Avidemux doesn't enact Windows registry at all. It uses %appdata%\avidemux for user data like Avidemux settings and custom scripts and %localappdata%\avidemux for logging.

The crashes appear random for all files, if one file crashes on closing (Ctrl+W) I can reload the same file & close it without a crash, I haven't been able to find a pattern other than the crashes are pretty spread apart, there's usually a long break and sometimes it wont crash all day (very odd).

Completely forgot the last stable version of Avidemux 2.8.1 was installed (havent used in awhile) and have been using Nightly builds from another directory, not sure if there was any conflicts there but after posting here I did a Revo uninstall on avidemux and let it delete all traces / folders, I then deleted my nightly folder and unzipped a fresh copy of same nightly build ive been using, so far I haven't had any crashes so fingers crossed.

I'll be sure to try your other suggestions if it crashes again I'm curious what the admlog file might show.

also not sure if this helps but when it started crashing I had made a crude screenshot from a previous nightly build and it shows the full text from error popup window.

You cannot view this attachment.