News:

--

Main Menu

Avidemux 2.8.2 development

Started by eumagga0x2a, October 02, 2022, 01:42:10 PM

Previous topic - Next topic

eumagga0x2a

Quote from: Rainman74 on October 10, 2026, 12:43:03 PMWith the current nightly build, the error message no longer appears; instead, the app crashes and freezes.

This is https://avidemux.org/smif/index.php?msg=98711, related to the libavcodec-based AC3 encoder. NVENC-based video encoders are working for you now, aren't they?

Rainman74

Quote from: eumagga0x2a on October 10, 2026, 02:11:38 PM
Quote from: Rainman74 on October 10, 2026, 12:43:03 PMWith the current nightly build, the error message no longer appears; instead, the app crashes and freezes.

This is https://avidemux.org/smif/index.php?msg=98711, related to the libavcodec-based AC3 encoder. NVENC-based video encoders are working for you now, aren't they?


Yes, I can confirm, without AVX and AVX2 for AC3 audio, I can encode nvenc HEVC again with the current nightly build!

pierredpt

#92
Hello,

I found a bug in the AppRun script of the Linux AppImage (tested on Avidemux-x86_64_20261009.AppImage with debian 13 Trixie Cinammon desktop ) that prevents opening files via the command line or file manager context menus ("Open With...").

At the end of the AppRun script, the binaries are executed using the ${args} like this:

else "${HERE}/usr/bin/avidemux3_portable" "${args[@]}"

However, ${args} is never initialized or defined anywhere earlier in the script. As a result, ${args} is always empty and any arguments passed to the AppImage ($1, $2, etc.) are lost.

I fixed this by adding the missing initialization right at the beginning of the script (line 2):

args=("$@")

Could you please update the AppRun template in the build system to include this initialization so that arguments are properly forwarded to the Avidemux binaries?

Thank you for your time and for this great software ! I have been using it for a long time