Avidemux Forum

Quote from: MC on August 25, 2026, 07:33:37 AMHi,

Do you intent to update the included ffmpeg to a newer version (latest is 9.0.1) ?

several CVE issues have been fixed since 7.0.2

https://ffmpeg.org/security.html

Christian

Hello,

Perhaps by using the newer MinGW64 versions that use Qt6...
But that's completely unverifiable...
It seems that adding features to AviDemux is more important than updating a version that's already running.

I am getting repeated warnings that Apple will be killing off support for Intel based Apps. Will be there be native downloadable build for Silcon based Macs?

I've seen people talking on other threads about building/compiling their own version of Avidemux. Unfortunately this is not something in my skillset. I haven't done any coding since using basic on a BBC micro in the 90s and even then I was crap at that.

Looking at other threads I have the feeling the answer is a definitive no. If that is the case does anyone know of any similar apps for Mac to Avidemux that would allow me to cut adverts out of .ts TV broadcasts. They don't need to be as good as Avidemux, but something poorer is better than nothing at all.

Hi,

Do you intent to update the included ffmpeg to a newer version (latest is 9.0.1) ?

several CVE issues have been fixed since 7.0.2

https://ffmpeg.org/security.html

Christian

Hello, I've been using Avidemux for years to cut and merge my videos. My process is that I encode the videos to same codecs with handbrake but keep the original framerate (25,30 etc) of each video intact and merge everything with Avidemux into a single variable framerate video. Later, I also edit it again with Avidemux if needed to add new clips or rearrange. Recently I discovered that Avidemux introduces jitter into the video when I was checking something in MPC-HC statistics (ctrl+4) ( see attachment, left is before editing and right after it the jitter went up to 5ms) and It seems it only happens if I cut a previously merged video into separate clips and merge again after either rearragement of adding new videos. Merging with ffmpeg concact or mkvtoolnix doesn't add the jitter.

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

Hey! With all the warnings my Mac OS has given me about how my avidemux binary is going to stop running when Apple deprecates x86 support, I figured I better build an ARM native version to head that off. Found and fixed some issues and it now builds.

The current master fails to build natively on Apple Silicon with Homebrew due to two new issues:

Linking:

The SDL3 link sites use the bare library name, and /opt/homebrew/lib  isn't in the default linker search path on Apple Silicon.

ld: library 'SDL3' not found
make[2]: *** [ADM_render_qt/libADM_render6_QT6.dylib] Error 1

Packaging:

fixup_bundle's search dirs hardcode /usr/local/lib, the Intel Homebrew prefix.

CMake Error at BundleUtilities.cmake:725 (message):
  error: otool-classic: can't open file:
  @rpath/QtCore.framework/Versions/A/QtCore (No such file or directory)
Here are the fixes for them

I've submitted both fixes as https://github.com/mean00/avidemux2/pull/555. Until it's merged, you can build today with:

git clone https://github.com/mean00/avidemux2.git
cd avidemux2
git fetch origin pull/555/head:pr555
git checkout pr555
bash bootStrapMacOS_Monterey.arm64.sh

Verified on macOS 26.5 (M-series), Homebrew Qt 6.11.1 / SDL3 3.4.14, CMake 4.4.2: clean bootstrap run through DMG creation and ad-hoc signing, all-arm64 bundle, app launches and a copy/copy cut saves and probes clean. No extra environment variables needed.

Above, I believe I meant to say, "PAR", Pixel Aspect Ratio.

so (something more along the lines of) ...

So lets say Media Info showed ...PAR... to be 1.3 (non-square pixels or whatnot).

Derived from display width, adjust by ...PAR...

Sorry, but I'm not good in this stuff, thats chinese to me, i can work with avidemux but not build my own avidemx
And i have no Linux, or VM, anyway

And in that respect, I was thinking of a setting in Avidemux, something like:

Derived from display width, adjust by DAR

That would go out, see that non-square pixels exist, & do the computation automatically...

Well you can do that, in a round about way - perhaps*.

*Perhaps, depending on Output Format.  Like mp4, mkv, but not flv...


Output Format
Configure -> Force aspect ratio --> Derived from display width


At that point, you need to set the Display Width to a number that "works".

In a recent video, output A/R was coming out wrong, & that had to do with the (oh, I'll probably get the terminology wrong, but...) DAR.
The DAR was weird.  So I took the expected Display Width, then divided that by the DAR (as reported by MediaInfo).

(I think that was the deal.)

So lets say Media Info showed DAR to be 1.3 (non-square pixels or whatnot).
So I took the expected Display Width, say 480, then divided that by 1.3, & used that value, 369, as the Display Width setting in Avidemux.

With that the output file A/R was as wanted (or at least close enough, given rounding).


(Again, I may have terminology wrong, or my numbers could be wrong, but the basic premise did work out.)