Avidemux Forum

So cool! Thank you.

I just noticed! Awesome, thank you. I hope future nightly builds won't be delayed by two months

Please provide a sample preferably via WeTransfer, Mega, Dropbox or Google Drive. Alternatively, please post the ffmpeg command line used to generate the sample.

Thank you.

Fresh nightlies (at least for Linux, macOS Monterey and later (x86_64) and the cross-compiled one for 64-bit Windows) have been generated and uploaded.

Just in case, I provided it in Russian, due to the fact that I don't speak English

на всякий случай привёл на русском языке, в связи с тем, что не владею английским языком


ошибка длительности нулевого кадра происходит при создании слайдшоу при помощи ffmpeg используя метод setpts для точной установки длительности кадра

то есть при fps 50 Я установил длительность 6 секунд для всех кадров

0 кадр обязан длится 6 секунд, но он длится 20 миллисекунд, а все остальные 6 секунд

так происходит в avidemux и в mpc(media player classic K-Lite Mega Codec), но на YouTube всё нормально воспроизводится

если Я в avidemux редактирую слайдшоу и нажимаю кнопу воспроизвести на произвольном кадре, то сразу переключается на следующий кадр, то есть не показывает текущий кадр на 6 секунд, а перескакивает на следующий кадр

если Я в avidemux редактирую слайдшоу и копирую из произвольной области два кадра из слайдшоу куда-нибудь в добавленное видео с таким же fps, то потом при воспроизведении показывается второй кадр из слайдшоу на 6 секунд, далее показывается кадр из видео на 6 секунд, далее воспроизводится видео
    а если после редактирования это сохранить методом copy, то на кадрах могут появится артефакты при воспроизведении в mpc


(google translate)
zero frame duration error occurs when creating a slideshow using ffmpeg using the setpts method to precisely set the frame duration

that is at fps 50 I set the duration to 6 seconds for all frames

Frame 0 is supposed to last 6 seconds, but it lasts 20 milliseconds, and all the rest are 6 seconds

this happens in avidemux and mpc (media player classic K-Lite Mega Codec), but on YouTube everything plays fine

if I edit a slideshow in avidemux and press the play button on an arbitrary frame, it immediately switches to the next frame, that is, it does not show the current frame for 6 seconds, but jumps to the next frame

if I edit a slideshow in avidemux and copy two frames from the slideshow from an arbitrary area somewhere into an added video with the same fps, then during playback the second frame from the slideshow is shown for 6 seconds, then a frame from the video is shown for 6 seconds, then played video
    and if after editing it is saved using the copy method, then artifacts may appear on the frames when played back in mpc

I forgot an important detail: at least on Windows 10 (didn't test job queue on Windows 11 yet), you must allow all three Avidemux executables to bypass the Windows firewall in order to be able to use Avidemux Jobs.

Avidemux doesn't accept connections from outside the system, Windows throws a drama for no reason here, acting silly, IMHO.

Quote from: eumagga0x2a on May 19, 2024, 08:10:30 PMPlease note that Avidemux Jobs cannot be switched to portable mode by renaming the executable, this utility really needs the option --portable to be passed to avidemux_jobs.exe for that purpose. I believe this should be made consistent with the main application.

Should be fixed now, please try a future nightly.

When avidemux_jobs.exe is launched in portable mode (e.g. by renaming it to "avidemux_jobs_portable.exe"), it will try to launch "avidemux_cli_portable.exe" and "avidemux_portable.exe" if avidemux_cli.exe or avidemux.exe haven't been found in the current directory when processing the queue.

The 2024-03-16 nightly contains the patch for that empty job list bug. Could it be that you queue jobs while in portable mode, but then launch avidemux_jobs.exe in the normal mode?

Please note that Avidemux Jobs cannot be switched to portable mode by renaming the executable, this utility really needs the option --portable to be passed to avidemux_jobs.exe for that purpose. I believe this should be made consistent with the main application.

Maybe you misunderstand the meaning of "portable mode" in case of Avidemux on Windows: Avidemux itself is always a portable application in the sense that it doesn't need to be installed to run. The portable mode on Windows just tells Avidemux to store its configuration in the program directory (which must be writable for this purpose) rather than in %appData%\avidemux. This helps to avoid conflicts when different Avidemux versions are used on one and the same computer.

Quote from: thoste on May 19, 2024, 06:19:52 AMThere I can find as version for avidemux.exe = 2.8.2.24076
and NOT 2.8.2 240316 as expected.

This a form of numbering using the day-of-year. DOY076 is the 16th of March in 2024.

Quote from: eumagga0x2a on May 18, 2024, 08:25:01 PMThis bug was fixed on February 11, your Avidemux build is too old.

I am using v2.8.2 240316 see this snapshot:

https://snipboard.io/t0xeou.jpg

The avidemux.exe file timestamp "created" is of 19.May 2024
Is there a newer?