Avidemux Forum

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?

I go to Avidemux download webpage:

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

and download either package
- avidemux_2.8.2 r240316_win64.exe
or
- avidemux_r240316_win64Qt5_26.zip

The package name pattern shows as version "r240316"

Now I install (resp. extract) the download version, then right-click on "avidemux.exe", select "Properties" from context menu and the "Details" tab.

There I can find as version for avidemux.exe = 2.8.2.24076
and NOT 2.8.2 240316 as expected.

Is the wrong file Avidemux.exe put into Download package?
Or is the version number in source code resp. compilation process not correctly updated?

Quote from: thoste on May 18, 2024, 11:41:46 AMHowever I started the other program avidemux_jobs.exe from Avidemux installation directory and though the job would be listed there.

But there is no job here. the list is empty.

This bug was fixed on February 11, your Avidemux build is too old.

Please ignore Avidemux Wiki alltogether. It is hopelessly outdated.

Quote from: thoste on May 18, 2024, 11:41:46 AMOne more idea: The job files *.py are  created but not in the default directory C:\Users\<username>\AppData\Roaming\avidemux\
but in the new directory

D:\tools\Avidemux\settings\jobs\

since I setup a portable Avidemux installation.

Works as intended.

The issue with this method (with any software) is the fact that the three clips you join (concatenate) must have the same encoding parameters. There are many parameters other than basic resolution, framerate etc that will differ between the encoded clip and the non encoded clips. This will cause issues when concatenating. Even if the clips do concatenate, you will likely discover playback issues on some devices/players.

After loading a *.mp4 video into (portable) Avidemux v2.8.2 on Windows10 I setup all parameters "as usual" and clicked then menu file--->queue to add the job to joblist. I guess "Queue" means "Add to joblist" because there is no menu "File--->Add to joblist"

According to https://www.avidemux.org/admWiki/doku.php?id=using:joblist
I can view the current joblist by clicking on menu

File--->joblist

But there is no such menu (have a look at the attached snapshot).

However I started the other program avidemux_jobs.exe from Avidemux installation directory and though the job would be listed there.

But there is no job here. the list is empty.

Why is no job created and added to joblist?
How can I view joblist otherwise?

If I don't assign the current encoding to joblist but just click File--->Save the video is encoded successfully.

But I want to setup multiple video encodings and then perform one run for all.
How can I achieve this otherwise?

One more idea: The job files *.py are  created but not in the default directory C:\Users\<username>\AppData\Roaming\avidemux\
but in the new directory

D:\tools\Avidemux\settings\jobs\

since I setup a portable Avidemux installation. So I guess Avidemux_portable.exe and avidemux_jobs.exe do not know where to search for the *.py job files.
Any chance to tell them the folder?

Something like a command line parameter

avidemus_jobs.exe -dir="D:\tools\Avidemux\settings\jobs\"

?

Or entering the jobs folder path somewhere else in settings?

If not: This option should be added to next release


You cannot view this attachment.