Avidemux Forum

I see, I'll add a skeleton for NL and the corresponding qtbase_nl.ts file in near future. I need to regenerate all translation files anyway as they don't reflect the current state of the source tree anymore.

With the latest 2.8.2 nightly, adding compiled translation files to the qt6\i18n directory (we are not using Qt5 anymore) should work.

Please be aware of changes to translatable strings happening from time to time and also expected soon, e. g. when the pull request for indexing preferences gets merged.

Windows 10 might work, but is completely untested.

I want to make a Dutch translation.

There is a qtbase file here: https://github.com/qt/qttranslations/blob/dev/translations/qtbase_nl.ts, but there's no avidemux_nl.ts yet.

As for testing, can I just export a qm file with the translation to C:\Program Files\Avidemux\qt5\i18n? I can only test on Windows 10 (but I assume QT is robust enough to display untranslated strings in English without throwing errors).

For which language do you intend to create a translation? Does a matching Qt translation (qtbase_??.ts) exist for it?

If Qt translation exists upstream, but avidemux_??.ts does not, the best course of action would be to ask for both to be created in avidemux2_i18n repository which I'll do as soon as I am able to.

Having a build environment (preferably current Fedora or Ubuntu, Qt6 in Debian 12 is too old to work smoothly) simplifies things enormously as it allows comprehensive testing. It doesn't need to be bare-metal. Trying to avoid a minor hassle of setting up such an environment creates major complications, IMHO.

However, it should be entirely possible to do everything on GitHub website, downloading just the .ts file locally and editing it in Qt Linguist.

I'm still confused...
So the translations are in https://github.com/mean00/avidemux2_i18n/tree/ef89677a67de659918715cf8188080254f21b56e, but where can I find the source file to create a new translation? I'm on Windows and I don't know how to clone things with git, but surely it must be a file somewhere in that GitHub repository. Could someone point me to it?

The attached image explains how markers work.
The frame starting at marker B is not included into the selection.
If you set marker B to the last frame of the video, then the selection will be one frame sort.
To include the last frame, the marker B shall be set after the last frame, which is equivalent to "reset marker B".

There is no frame at the full duration of the video which is the presentation time of the last frame + non-zero frame durarion, therefore, of course, it is only logical that you cannot seek to full duration of the video. Use "reset marker B" (or "reset markers") menu action for this purpose.

Hi everyone,

I'm using Avidemux (Win64/VC++ 2.8.1) for an experiment to mark what users interpret as the start and end points of an event in short videos, using markers A (start) and B (end).

Each video is exactly 4 seconds long (100 frames). If I don't touch the playback bar at all when opening the video, and just check the default A and B markers, I get a clean selection from 0 to 4 seconds.

However, when I manually drag the playback bar with the arrow in the keyboard to set point B near the end, it stops at 3.96 and won't reach exactly 4.00. This makes it ambiguous whether the user meant to select the entire video (from 0 to 4 seconds) or just up to 3.96.

Is there any way to force Avidemux to snap to the exact end of the video (4.00) when setting B manually? Or is this a known issue with how time codes are displayed or handled?

Thanks in advance!

Der im Moment neueste offizielle VC++ build fur Avidemux 2.8.2 ist vom 30. Mai (frühere waren wegen unterschiedlicher Umbauarbeiten unvollständig). Der letzte Release (Version 2.8.1) wird bald drei Jahre alt – dazwischen liegen einige dutzend behobene Fehler. Die Angabe "2.8VC++64 Bit" passt auf beide und sagt daher herzlich wenig aus.

Auf jeden Fall wird Aktualisierung der Version nichts an der Ausrichtung des Videos ändern. Wenn dies eine effiziente Editierung des Videos verunmöglicht, muss es erst einmal mit dem Filter "Drehen" / Rotate" um 180° gedreht werden.

Thank you very much! Problem is solved!

Ich habe vorgestern die Version 2.8VC++64 Bit heruntergeladen. Es müsste die neueste Version sein.