Avidemux Forum

Quote from: MC on September 30, 2026, 06:21:45 AMAlso, as ffmpeg already support faac audio, that's a good idea to have two aac encoder/decoder ?

We have three and the only one which really matters feature-wise is fdk_aac (non-free). Absolutely no objections at least on my part when duplicate functionality like faac AAC encoder and faad2 AAC decoder are left out. Regarding having multiple tools to do the same job, I personally don't see a problem with that, may be useful for testing.

Mister Developer, could it be possible for you in Avidemux to add a separate default folder for audio that is used for selecting the track from and save a track to, please? I keep both video and audio separated, this feature would make my workflow more comfortable. Thanks a lot in advance.
Kind regards from Litze.

Up to at least version 2.5.6, the x264 codec was much more configurable:

- the three *qcomp* (curve compression) values ��are now fixed and cannot be modified
- *zones* can no longer be set

(ver. 2.5.6)
You cannot view this attachment.You cannot view this attachment. 



Now (ver. 2.8.x)

You cannot view this attachment.You cannot view this attachment.

Why were they disabled? 

It would be great if at least these two options were made functional and user-adjustable again, as they were in older versions.

Xvid is also much less configurable than before: at the very least, AQ and PB-ratio should be adjustable, as these are important parameters.

Thanks.

Since avidemux_mingw64_20260912 & 20260922, the nvenc encoders no longer work and throw an error.

The Sep 22 nightly has given multiple freeze-ups when using x264.
First last week after updating from the Sep 12 nightly and again this week after doing a clean install.
Last week and this week I rolled back to the Aug 6 nightly, same files, same workflows, no problems.
The Sep 12 also was problem free for the week I used it.

Maybe you can see something in the attached crash.py and admlog.

https://drive.google.com/file/d/1g133aSIetKL17zO4V37gcR_6IPZeC5qc/view?usp=sharing

https://drive.google.com/file/d/1XtiTp0Q1WO-njB70BDyNhYfh1kj44Irs/view?usp=sharing

Hi,

avidemux fail to build with faac 2.x
2.1 introduced soname libflac1
2.2 introduced soname libflac2

Also, as ffmpeg already support faac audio, that's a good idea to have two aac encoder/decoder ?

Christian

Hi. I'm posting here to report a strange behaviour in the "Save" window. I'm using a MacBook Pro 2023 16" with M3 Pro with MacOS Tahoe, version 2.8.1 compiled by Kadiwa and available here.
When I'm in the "Save" window the four arrow keys don't move the cursor in the name tab, but they continue to move the position bar by frames or cut points.
UPDATE: on another build available here the arrow keys work correctly.
By the way, in every Avidemux release I tried - as fas as I remember - text can't be pasted in the name tab. That would be an useful feature.

Quote from: eumagga0x2a on September 17, 2026, 08:59:07 PMHi Christian,

do you mean the Dockerfiles for containerized build and create*FromSource*.bash convenience scripts? FFmpeg

Hi,

No, I build Debian packages with cmake and the build fail from the ffmpeg side.

CMake Error at cmake/admFFmpegBuild_helpers.cmake:323 (MESSAGE):
  configure output is <nasm not found or too old.  Please install/update nasm
  or use --disable-x86asm for a build without hand-optimized assembly.
But before trying to build ffmpeg, cmake only check for yasm.

-- Checking for YASM
-- *****************
-- Found as /usr/bin/yasm
Christian

Hi Christian,

do you mean the Dockerfiles for containerized build and create*FromSource*.bash convenience scripts? FFmpeg build uses nasm on my system (as I have both). The check in avidemux_core/cmake/admFFmpegBuild_helpers.cmake:329 ensures that we don't try to proceed with the build if FFmpeg configure has failed to find any assembler at all. Avidemux asking for yasm for its own assembly doesn't interfere with FFmpeg build system.

I'll have a look regarding devpod / Docker scripts, thanks.

Hi,

May be you didn't notice, but now ffmpeg 9.x use nasm instead of yasm.

Not really important for Debian packaging though.

Could you fix that ?


Thanks in advance,
Christian