Video settings not restored in next session

[RocketJet]

The "Save Current Settings as Default" menu option no longer seems to be honoured for Video settings. In the next session Video resets to Copy, and the Config reverts to default values.

I am running Avidemux 2.8.2 260516_46963d075c1-fflibs 7.0.2  mingw 64bit
under Windows 11 on an Intel PC, with a local account.

I also have an old version that works fine in this regard,
on a Windows 10 AMD PC, with a Microsoft account.
Avidemux 2.8.2 250526_b008a4d098-fflibs 7.0.2-VC++

[eumagga0x2a]

At least the current git master works fine (on Linux, testing on Windows is not possible for me ATM) in this regard. From 2026-04-08 to and including 2026-05-29 is a very unfortunate time range as opening MPEG-TS streams with MPEG-2 video was broken.

If you don't need MPEG-2, it should be more or less fine function-wise. Can it be that you access the same Avidemux profile from different Avidemux versions? As configuration was changed on April 8, returning to an earlier build may be problematic. In doubt, please rename %appdata%\avidemux directory and retry with 260516.

[eumagga0x2a]

I've updated MXE setup scripts and was able to test my own build off the latest git on Windows 11: "Save Current Settings as Default" works for me as it should.

If you have access to a somewhat powerful PC with a current Linux distribution (e.g. Fedora 44) and 10 GiB or more free storage space, I would recommend to cross-compile from source as described here (the description itself has not been updated but should work as-is).

[RocketJet]

I do have multiple versions of Avidemux installed,
so I renamed the Avidemux folder in %appdata%.
I also uninstalled all versions of Avidemux,
downloaded the latest current nightly of the ming64 version,
and reinstalled from that, and rebooted.

It did not fix the problem,
but I should now have a clean Avidemux install,
which is good.

TT don't use Mpeg-2 TS files anymore,
though I sometimes use AviDemux to
extract Mpeg-2 from MKV into an Mpeg-2 PS file.
I have not noticed any problems with that.

I have very little experience with Linux,
it is rather beyond me to do a cross-compile.
I can wait for the next nightly windows build, thanks.

[eumagga0x2a]

A new cross-compiled official Avidemux nightly has been generated and uploaded. Upon a quick look at the ZIP-packaged variant (didn't try the installer-packaged one), I understand what might have posed a problem: please make sure the Avidemux executable is not named "avidemux_portable.exe" but simply "avidemux.exe" else it will try to save its configuration to install directory rather than to %appdata%. If the install directory is not user-writable, this will fail causing the problem you describe.

Alternatively, make the install directory read-write for your user.

I have very little experience with Linux,
it is rather beyond me to do a cross-compile.

Which is a pity as e.g. this official nightly lacks NVENC-based video encoders (which is a build environment configuration issue) which would be available in your own, local build.

[RocketJet]

I uninstalled the 2605 version ans installed the new nightly.
Windows, of course, tried to stop me running it,
but I found the "run anyway" button.

The new version did not fix the problem,
but I have found a work around:

Running AviDemux as an Administrator allowed it to set the new default settings.
Subsequent runs of Avidemux were able to pick up the new defaults,
without running as Administrator.

I just have to remember that if I want to change them again in the future, then I will need to run as Administrator for that session.

This is good enough for me. Thank you for your help.

[eumagga0x2a]

Running AviDemux as an Administrator

You should absolutely never do that, especially without a solid reason :-( Please re-read the explanation why the problem with current official nightly builds exists in the first place and follow the solution given in my previous reply.

[RocketJet]

Oops, sorry, I forgot to mention that I gave myself full authority,
but it didn't help.

Also, I have never used the portable zip files,
but the desktop shortcut points to
"C:\Program Files\Avidemux64\avidemux_portable.exe".
I looked for a file just called avidemux.exe,
but I did not find one.

I have not looked at the code,
but I suspect the setting save
is not checking for an error code.
Windows will sometimes provide an error code
if a request does not work.
No guarantee though.

[RocketJet]

I found a better work around:
installing into a different folder
avoided the need to access the Program Files folder,
so now it works fine.

I must have done something wrong when trying to authorize myself
to the Avidemux folder in Program Files. Sorry again.

I am quite happy now, since I do not need to run as Administrator
for it anymore.