Avidemux Forum

Thanks for the info.
A quick Google confirms Wayland is only an experimental option in Linux Mint (Cinnamon), not a default or requirement. X11 is the default, so should not be an issue.

Quote from: me444 on December 23, 2025, 09:25:59 PMis there really no chance to extract the installation executable from the VC distrib via any tool??

In principle, this is absolutely possible as the installer (which includes a full, statically linked Qt, making it huge) is just a set of concatenated 7z archives (open the installer in a hex editor and search for bytes "0x37 0x7A 0xBC 0xAF" marking the start of each archive). Someone from a Russian computer forum posted a (PowerShell?) script to automate extraction, can't find it ATM.

Quote from: me444 on December 23, 2025, 09:25:59 PMI don't really needed the internal player for working when doing cuts (stepping forwards or backwards when location the cut markers is sufficient), and once i'd set Audio: "Local playback downmixing" to "Stereo headphones" and "Andio device" to "Dummy".

Well, having a picture for a specific time offset is the whole purpose of using the graphical Avidemux app instead of the CLI one (or ffmpeg). Audio settings regarding playback affect only playback of the source video in Avidemux app(s) using the given Avidemux profile where this setting is stored. They bear no relation to output.

Quote from: me444 on December 23, 2025, 09:25:59 PMI'd read now in some threads here that "MP4v2" is old and obsolete and shouldn't be used any longer.
Q: is the anywhere some more information known that explains a bit more why MP4v2 is obsolete, and in how far it might have drawbacks to use?

For a prolonged period of time, the underlying libmp4v2 library was abandoned, i.e. no development whatever, not even security fixes. Recently, development has been resumed. However, the libmp4v2 version bundled with Avidemux is ancient even in comparison with libmp4v2 when it was abandoned. The muxer plugin in Avidemux has received no improvements, especially regarding more suitable time bases (MP4v2 uses just 1/90000 hardcoded) or codec support.

Configurable options for indexing will be added, sorry for dropping the ball for so long.

Quote from: sark on December 24, 2025, 04:45:15 PMI did try updating via the Linux route, mainly due to the frustration of Windows 10, but I would lose some important (to me) apps. However, I did like Mint enough to decide to install it on an older small form PC I have. I'll see how Avidemux performs on this setup.

Please be aware that Avidemux for Linux is unusable with Wayland. If you cannot use an X11 session, please make sure you set environment variable QT_QPA_PLATFORM for Avidemux to "xcb", e.g. call it like

QT_QPA_PLATFORM=xcb /full/path/to/avidemux3_qt6
to force XWayland. On PCs with NVIDIA graphics using recent NVIDIA drivers, even hardware acceleration (VDPAU, NVDEC and NVENC as well as OpenGL) works just fine with XWayland in a Wayland session. The experience with non-NVIDIA or older hw or oder drivers may be much worse.

I understand.

I did try updating via the Linux route, mainly due to the frustration of Windows 10, but I would lose some important (to me) apps. However, I did like Mint enough to decide to install it on an older small form PC I have. I'll see how Avidemux performs on this setup.

Thanks for clarifying.

It is somewhat complicated. There is no supply of official cross-compiled nightly builds, but whoever bothers to build it from source following the how-to, will find such builds as fully supported as Avidemux builds can be. On the other hand, while native, VC++-compiled official builds may be provided in the future, they are definitely worse supported as I cannot produce such builds myself.

I notice the cross compiled Windows Avidemux has not been updated since Dec 24. The VC++ version May 25.
Can I assume from this that cross compiled versions are no longer being supported. If so, is it now recommended Windows users switch to the VC++ version of Avidemux.
I appreciate it is a huge undertaking to maintain various flavours of the same application, so this is not a request. I'm in the process of updating my system and just seeking some clarity.

Thankyou and Merry Xmas to all

ohhh  Klasse 
Erstes mal ging das nicht bei mir, warum auch immer?
Ich hatte einige alte Advidemux noch drauf und die dann alle runter gemacht mit CCleaner.
Mit windows waren bei den Apps 2 dabei die konnten nicht gelöscht werden, die sind nun auch weg.
Dann das neueste 2.8 drauf gemacht, weis nicht ob das nötig war.
Anschließend das von deinen Link, und nun geht es.
Alerdings kam beim Installieren die Meldung dass ich in einen  bestehenden nicht leeren Ordner installiere
vermutlich war das zuvor installierte 2.8 damit gemeint, ich habe dann in meine spiele Platte installiert.

Alle Achtung das ist gute Arbeit von dir   

To set default muxer (output format) to MP4, choose it in Avidemux GUI and press CTRL+ALT+D ("Save current setting as default").

Number of audio tracks is meaningless as long as no video is loaded, therefore the original request is flawed. However, you can create a file e.g. as "clear-all-audio-tracks.py" in %appdata%\avidemux\custom directory with the following content

adm = Avidemux()
adm.audioClearTracks()
and manually call it from the "Custom" menu after you have loaded a video. There is no way to do it automatically when a video is loaded though (adding adm.audioClearTracks() command to defaultSettings.py file won't update the GUI to reflect the new count of audio tracks and won't survive the next press of CTRL+ALT+D).

Since times i'd been using Avidemux (on Windows 10 x64) especially for cutting videos, mostly in "copy" mode to MP4, sometimes converting (then audio codec AAC (lav), video codec MPEG4 AVC x264).
In most cases without any problems. So my big thanks and big respect for this wonderful software at this place!

'Historically' i'd been using the "win64" nighlys. I noticed this had not been updated since ages, the last one is from Dec. 2024:  avidemux_r241212_win64Qt5_9.zip.
Meanwhile i doubt there will be an update next time, but i'd be interested in, because i don't like
the manner to avoid the leftover index files, actually via environment variables, eg. ADM_NOINDEX_MP4, ADM_NOINDEX_WEBM etc.
I'd like to see finally the setting/option for this which had been announced once.
So now for the first time i tried the VC version (vsWin64\Avidemux_2.8.2 VC++ 64bits 250526.exe).
Why the first time? Because i'd been using my own .vbs scripts to unzip, copy and integrate my settings into a fresh distribution, rename the avidemux.exe to avidemux_portable.exe etc. -  with one click.
So i had ignored the install exe based VC version, which anyhow appears to require an installation process.
I tried some measures to extract the install exe (via 7zip, winrar, universal extractor), but no chance.
Why i don't like an installation? Because a) it leaves entries within the start menu and registry, which i don't want to have (portable instead), and b) it hinders to use a script for to integrate existing settings into any new distribution 'automated'. Having a chance to extract the VC install exe, then one could do such.

So my first question: is there really no chance to extract the installation executable from the VC distrib via any tool??

By that occasion i'd noticed a few minor things i wasn't really aware of since ages, so i'd like to ask (very noob quests i belieave):
I don't really needed the internal player for working when doing cuts (stepping forwards or backwards when location the cut markers is sufficient), and once i'd set Audio: "Local playback downmixing" to "Stereo headphones" and "Andio device" to "Dummy".
So, for to go really sure, the noob question: this really applies to the ADM's builtin player only and has absolutely nothing to do with the resulting file, right?
(It would be nice to see a short sentence within the preferences's audio page explaining the scope for what it applies).

Similar "historical" i'd be still using the MP4v2 container codec for the copy operations (needed MP4 instead mostly only when the input file had "AV1" format).
I'd read now in some threads here that "MP4v2" is old and obsolete and shouldn't be used any longer.
Q: is the anywhere some more information known that explains a bit more why MP4v2 is obsolete, and in how far it might have drawbacks to use?

Was heißt warten? Es funktioniert schon jetzt, nur eben nur mittels eines HW-Decoders. Wenn eine NVIDIA-Grafikkarte in der Lage ist, AV1 zu generieren, ist sie definitiv auch in der Lage, AV1 in Hardware zu dekodieren.

Was das Dekodieren von AV1 in Software angeht, wurde die libaom für die offiziellen, nativen Nightly Builds offensichtlich ohne Unterstützung für AV1 Levels 7.x und 8.x kompiliert. Die cross-kompilierten (also unter Linux für Windows kompilierten) Avidemux Builds dürften solche AV1 Streams seit Februar 2025 abspielen können – nur muss man sie selbst kompilieren.

Es sind keine Änderungen an Avidemux notwendig, man muss "nur" die libaom in der Build-Umgebung zum Kompilieren von Avidemux mit entsprechenden Optionen kompilieren – eine organisatorische und logistische Frage, bei der ich im Falle von offiziellen Builds nicht helfen kann. Wer sich zu helfen weiß und ein Linux-System mit 8 GiB oder mehr Arbeitsspeicher (gerne auch als eine VM) hat, kann jederzeit Avidemux mit diesen Fähigkeiten bauen.