Presets being meddled with

[TrueTenacity]

I'm 100% sure it isn't filebot's problem or filebot's fault...

Every time I restart my machine, the filebot presets revert to how they were a few edits ago... and I have to re-edit them to how they are supposed to be now.

Is there something I can check to stop them getting messed with?

[rednoah]

Please run filebot -script fn:sysinfo and post the output.

Are you using the normal edition or the Windows Store edition of FileBot?

Does the log file say anything interesting?

[TrueTenacity]

Code: Select all

Current application revision (r6224) does not match cache revision (r5829): reset cache
FileBot 4.8.5 (r6224)
JNA Native: 5.2.2
MediaInfo: 18.12
7-Zip-JBinding: 9.20
Chromaprint: fpcalc version 1.4.2
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2019-05-15 (r565)
Groovy: 2.5.6
JRE: OpenJDK Runtime Environment 11.0.2
JVM: 64-bit OpenJDK 64-Bit Server VM
CPU/MEM: 2 Core / 1 GB Max Memory / 23 MB Used Memory
OS: Windows 10 (amd64)
Package: APPX
License: Microsoft Store License
Done ?(?????)?

[TrueTenacity]

Windows Store Edition
Can't find a log file...

[rednoah]

FileBot stores your settings in this file:

Code: Select all

settings.properties

FileBot will also periodically backup your settings to this file, and restore your settings from this file if settings.properties is empty or deleted:

Code: Select all

preferences.backup.xml

The FileBot application folder for the Windows Store edition can be found here:

Code: Select all

%USERPROFILE%\AppData\Local\Packages\PointPlanck.FileBot_*\LocalCache\Roaming\FileBot

You can track these files and see what's happening.


Make sure you don't have multiple versions of FileBot installed and randomly use different versions with different settings (e.g. Store and non-Store edition at the same time)

[TrueTenacity]

Ha!

The backup file is from march and the settings file is from today.

It won't cause trouble if I just delete the backup?

[rednoah]

That would be normal behaviour. The settings file is written each and every time FileBot is closed. The backup file is only written to once per month, and generally never read.

The behaviour described in your OP indicates that the *.json file is deleted at some point when FileBot isn't running, which means FileBot will restore settings via the *.xml file next time it's starting up.

[TrueTenacity]

Yeah, it probably happened when filebot was open when the machine restarted itself and didn't get the opportunity to close clean...

I just closed it clean and now the setting and backup file have today's date

[rednoah]

Windows should close all applications normally on shutdown. But I guess if you cut power suddenly, right after creating a new format, then those new settings will likely be lost.

[TrueTenacity]

Happened in march, when we were having random power cuts because stable power is a western thing...

Thanks Rednoah