Avidemux Forum

Quote from: Cormy1 on July 03, 2025, 11:03:12 PMWould it be sufficient to grab runtime libraries?

If you are able to try and to report back, that would be great. I can test on Windows 11 only.

I receive an error when trying to run "Avidemux_2.8.2 VC++ 64bits 250526.exe" and of course Windows 8.1 does not support DX12... Natively.
Would it be sufficient to grab runtime libraries?

What do the strings mean after QT5 in the builds? They don't seem to be in any kind of order in relation to the build numbers.

avidemux_r241110_win64Qt5_35.zip
avidemux_r241110_win64Qt5_36.zip
avidemux_r241110_win64Qt5_8.zip

Either use an X11 session or lauch Avidemux with -platform xcb Qt command line option (losing hw accel related features). In any case, you are much better off using the latest 2.8.2 code. However, Wayland remains entirely unsupported (the GUI is totally broken in Qt6 on Wayland).

It's too long to post here and says it's spam, but I've pasted it here: https://pastebin.com/fMdrEHuf

Is this a Wayland problem again? I was using X11 before but got switched back to Wayland in the recent KDE Plasma 6.4 upgrade.

Avidemux was phasing out Qt5, transitioning to Qt6 for Windows builds as well. Support libraries, namely ICU (international components for unicode), pulled in by Qt6 are partially responsible for inflated installation size, libaom AV1 decoder and encoder components being a major factor too.

In official cross-compiled, ZIP-compressed builds, files needed for plugin development are not removed. Cross-compiled builds with NSIS installer allow to deselect installation of those header and lib files during installation.

Native Windows builds (MSVC-compiled VC++ builds) use Qt Installer Framework (QtIFW) as installer rather than NSIS, which includes a full static build of Qt, huge in size. Creating a custom build of QtIFW with all unused Qt features disabled could reduce installer size a lot – if the project maintainer find time to perform the extra work necessary. Honestly, I doubt that it is worth the effort, but I'm not the maintainer to decide.

ZIP-packaged cross-compiled builds use a fast but relatively weak ZIP compression, NSIS-packaged ones use a much stronger LZMA algo, resulting in a smaller package size.

All Avidemux builds are inherently portable, i.e. installers are for comfort and in order to match user expectations only. Once extracted, the program directory may be moved e.g. to a flash drive (at a cost of much lower launch speed compared to a fast internal drive, especially a SSD). "Portable mode" on Windows means that Avidemux stores user profile in the program directory instead of the default location in %appdata%\avidemux, i.e. the program directory must be writable for the user.

Regarding output format, I'd recommend to stick with the MP4 muxer.

Regarding video encoder, the choice depends on capabilities of the targeted hardware. A safe option would be to encode to H.264 with x264 ("Mpeg4 AVC (x264)") using default settings with the only exception of a shorter GOP (group of pictures) length for better seek granularity, like the source video that uses GOP length / size (the interval between keyframes) of 75 rather than the default value of 250. Reducing GOP size (on the "Frame" tab of the x264 plugin configuration dialog) comes at a cost of a worse compression, of course.

If your target hardware supports hw accelerated decoding of HEVC, you might want to choose HEVC as codec with x265 as encoder both for better compression rate as well as quality.

Please remember to switch away from "Copy" mode for video in order for video filters to become available.

Keep audio in copy mode.

I really liked Avidemux for how small an application it was, however I've been watching it grow drastically in size since I first started using it.
I don't know what happened in the ~2 weeks between release 241214 and 250101 but the fact that the executable grew nearly 67% between those two versions has alarmed me greatly. I think it's about 3X larger now than when I first started using avidemux.

I know I don't use the vast majority of avidemux features as it is and have no intention to, so I'd wager much of the new featureset will be just as wasted on me.
I'd like to be able to choose which components are installed/downloaded so I can keep the installation to a minimum.

I'm also a bit confused as to what it means to move back to "native" official VC++ builds vs the "regular" win64 builds I've been using up to now. I'll note that I am still using Windows 8.1 as my primary system.
What difference is there in practice between the installers and the ZIP downloads? The ZIP files are clearly much larger at the very least. I believe I started using them preferentially, assuming I can run them from a USB on "any" system just by copying the unpacked files/folders over to the USB.

Looking at the video output settings, i can adopt many different formats. Which format is the most similar to the original in this video?

This might be a silly question, but I've only used 'copy' settings, so I'm not sure

Thank you, the source MP4 video has indeed both a broken timing

  11:28:18-070 [MP4Header::indexify] Build Track index, track timescale: 90000
  11:28:18-072 [MP4Header::indexify] Histogram map has 6 elements.
Frame duration 2070 count: 3
Frame duration 3599 count: 1
Frame duration 3600 count: 123538
Frame duration 5360 count: 1
Frame duration 7200 count: 5534
Frame duration 8821 count: 1
  11:28:18-072 [MP4Header::indexify] Video index done.
  11:28:18-072 [MP4Header::indexify] Setting video timebase to 1 / 90000
  11:28:18-072 [MP4Header::indexify] Variable frame rate, 41691 us per frame on average.
  11:28:18-072 [MP4Header::parseStbl] Movie duration = 5384546
  11:28:18-072 [MP4Header::parseStbl] # images = 129155
  11:28:18-072 [MP4Header::parseStbl] Avg fps 23986.238281

<snip>

<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:00:08,423 at 199 and 202
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:00:17,303 at 413 and 416
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:00:58,223 at 1394 and 1396
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:01:51,903 at 2682 and 2683
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:02:30,143 at 3598 and 3601
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:03:23,823 at 4885 and 4888
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:03:39,463 at 5260 and 5263
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:03:54,983 at 5630 and 5634
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:05:09,183 at 7411 and 7413
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:05:13,063 at 7504 and 7506
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:06:47,704 at 9800 and 9803
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:07:07,224 at 10268 and 10271
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:07:25,784 at 10713 and 10716
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:07:29,704 at 10807 and 10810
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:08:53,664 at 12820 and 12823
<!>11:28:18-853 [MP4Header::checkDuplicatedPts] Duplicate pts 00:10:07,784 at 14597 and 14599

<many more similar timing errors skipped>

  11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Original frame increment 00:00:00,041 = 41692 us
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:00:17,223 at frame 414
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:02:30,063 at frame 3599
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:03:23,743 at frame 4886
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:03:39,383 at frame 5261
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:06:47,624 at frame 9801
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:07:07,144 at frame 10269
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:07:25,704 at frame 10714
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:07:29,624 at frame 10808
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:08:53,584 at frame 12821
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:11:49,384 at frame 17036
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:13:14,344 at frame 19073
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:14:52,984 at frame 21438
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:15:01,784 at frame 21649
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:16:07,184 at frame 23217
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:18:02,424 at frame 25980
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:18:26,864 at frame 26566
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:19:47,904 at frame 28509
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:20:06,664 at frame 28959
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:23:37,584 at frame 34016
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:24:29,344 at frame 35257
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:25:03,544 at frame 36077
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:26:09,944 at frame 37669
<!>11:28:18-857 [ADM_EditorSegment::addReferenceVideo] Duplicate DTS 00:29:05,744 at frame 41884

<many more similar timing erros skipped>

and wrong frame rate info in the codec:

  11:28:18-054 [extractSPSInfo_mp4Header] Parser created
  11:28:18-055 [extractSPSInfo_mp4Header] Codec created
  11:28:18-055 [extractSPSInfo_mp4Header] Context created, ticks_per_frame = 2
Used bytes 0/41 (+5)
  11:28:18-055 [extractSPSInfo_mp4Header] Width2 : 1280
  11:28:18-055 [extractSPSInfo_mp4Header] Height2: 720
  11:28:18-055 [extractSPSInfo] width:1280
  11:28:18-055 [extractSPSInfo] height:720
  11:28:18-055 [extractSPSInfo] fps1000:25000
It is essentially a 24000/1001 fps video encoded as 25 fps with variable frame rate. IMHO, the best thing to do would be re-encoding it using "Resample FPS" video filter with "23.976 (Film)" as target FPS.

There is no (obsolete, unsupported) libmp4v2-based muxer in VC++ builds.