Avidemux Forum

If I recall correctly, the handling of files (not just MP4) with insanely high timebase denominator like those produced by VLC is still unchanged, i. e. Avidemux replaces it with 90 kHz and fails to export in copy mode due to decode timestamp collisions. Re-encoding such streams with "Resample FPS" filter inserted into the filter chain should work at the cost of quality loss.

Anyway, r241212 or the latest VC++ nightly (the latter for those who don't need AV1 decoding support without an AV1 hw decoder) is a better choice than 2.8.1 release by far.

Which version of AVD are you using?

The latest version (x64) is 2.8.2 r241212 (I'm assuming you're on Windows).
If you are using an older version, as per the confusing main Avidemux page download link, I would first advise to update from below.

https://www.avidemux.org/nightly/win64/

So I get the timestamp error when trying to export in copy mode some of my videos that I've edited as MP4. From what little I've read, it seems this issue is caused by VLC (which is how I trimmed videos prior to learning about Avidemux).

So what I do is export them as MKV instead. 95% of the videos that have issues exporting as MP4 export fine as MKV. But because I don't like working with non-MP4 if I can avoid it (MKVs have caused thumbnailing issues in the past), I just take that MKV and export it again as MP4. 90% of those cases export fine as well.

I don't really need to know why this workaround works (it would probably just confuse me to be honest), I just need to know that it really does work, isn't creating issues that I wouldn't notice at first glance, and won't cause problems down the road. And that's why I'm here.

This was a hilariously stupid snafu: packaging a stock, ancient libaom from Debian while building against a recent libaom in /usr/local. Should be fixed now, solving the problem with crashes. Please try a future nightly. I'm sorry for inconvenience.

However, the OpenGL breakage in appImage is real, please make sure OpenGL is disabled.

May be a long shot here, but I'll take a shot.

I am running portainer on a Synology 1823xs+

I have created a stack for avidemux and everything works fine as far as video playback but the audio does not playback. I get the error "Trouble initializing audio device" My compose looks like this:

version: "3"
services:
  avidemux:
    image: jlesage/avidemux
    ports:
      - 5700:5800
    volumes:
      - /volume1/docker:/config:rw
      - /volume1/docker/avidemux/test:/storage:rw
    environment:
      - DARK_MODE=1
When I try to add

- /dev/snd:/dev/snd
I get the error

Bind mount failed: '/dev/snd' does not exist
Can anyone tell me if there is different location for the sound device in my Synology or if there is another step I need to take to get the container use the sound device? Thank you

Hi, preview with the new 250521 nigthly works now but only after I disabled "Decode video using LIBVA (Intel)" in preferences -> HW Accel.
I don't remember why that was enabled..
Intel av1 encoding does not yet work on Core Ultra 7 tho.. just first frame and that's all.. audio is ok.

$./avidemuxLinux_GLIBC_2.36_amd64_250521_0739.app 2>&1 | tee avidemux.log

https://paste.debian.net/hidden/9d5ede72/

Did you include old or new libaom, @eumagga0x2a?

Edit: "Decode video using LIBVA (Intel)" does work either way on Core Ultra 7, only works as disabled on Core(TM) i7-1165G7. Don't know if that's relevant.

Sorry, I did not expect further questions from you and did not look into the forum.

I only uninstalled all the old ones and downloaded the VC++ nightly acc. to your advices and it works further on perfectly. Thanks again!

The reason for updating libaom were AV1 streams generated by desktop recording tools using NVIDIA hw encoder not supported by older versions (for decoding). Need to contemplate our options.

Thank you. Maybe you could use libaom version which was included in 241212 nigthly so that it won't crash when using resize filter? Just an idea..

Thank you, I completely missed that in course of struggle for fixing build with Microsoft Visual Studio the compilation of libaom AV1 decoder plugin was disabled, my apologies. The black screen is a result of the aforementioned plugin missing.

Will be fixed ASAP, alongside with an assert failure / a crash opening the plugins dialog in the "Help" menu (we have video encoders one too many than the dialog can handle).