Hello Laza,
Here is some kind of a vicious regression related to the slideshow time : it is "reset" automatically to 3 seconds, when you re-edit a project

• If you modify the slideshow time to e.g. 5 seconds, save the album, generate the album and upload it to the server : everything is fine.
• If you switch to another project and go back to your original project, the slideshow time is reset to 3 seconds (although you save it before).
• If you exit JAlbum, launch it again and reopen this project, than the slideshow time is also reset to 3 seconds.

Aaarrrggghhh

I did reproduce it, but only once, and now I can't reconstruct the sequence that produced it. It seems to happen if you switch from a Projector project to a Tiger project, then back again. In short, I'm guessing that it's some kind of cross-skin problem - maybe a skin-loading issue.

I'll keep tinkering to see if I can figure out how to reproduce it reliably.

Is this the only setting that gets reset? It's jAlbum, not the skin that saves and loads the settings, so if this happens it must affect other settings, and other skins too.

No problem, I will try the uninstall/re-install and let you know.
So far, I didn't noticed any issue with other data savings (but I am using lot of default settings).

One more thing: my last update of jAlbum was version 32.1.3 on August 28th. I saw this issue only after this upgrade, and it is very easy for me to notice this bug as I am using a slideshow time of 5 seconds since years (quite visible difference with the default time of 3 seconds).

Btw, question for Laza: has this default slideshow time of 3 seconds been changed in Projector in the last year or so?

Interresting: if the default slideshow time has always been 4 sec ... where does this 3 sec come from ???

I made 2 tests before trying your recommendations above:
1) Basic upgrade to the latest jAlbum version:

• Uninstall jAlbum 32.1.3.
• Cleanup the Windows registry.
• Install jAlbum 33.0.4

The problem is still there.

2) Check what is happening with one of my old album from e.g. 2015:

• The file "jalbum-settings.jap" contains the following line: skin.slideshowDelay=5.0
• This should be where the slideshow time is saved, right?
• When opening this album, the settings HMI tells 3.0 sec
• If I exit the album without saving, the jap file is kept unchanged: normal.

A nice idea, but I tried Save as skin default with 3s selected, but it still doesn't cross-contaminate a saved project. I've tried various other things, like telling jAlbum not to use hints, not to restore settings, etc., etc., all to no avail. I can't replicate this problem.

PhilippeCharles, please attach the jalbum-settings.jap file to a post here. Maybe there's some stray value lurking in there, from elsewhere.

In short, I'm running out of bright ideas!

Besides default.japs, is there also a Projector-defaults.jap?

And I'd still like to see the jalbum-settings.jap file from a project that is showing this problem.

These three files all serve different functions.

I also tried the following menu commands:

• File > Save as default album
• File > Save as default skin

The problem is still there, but what is really weird is that I made some other changes in 2 other projector skin parameter for test purpose ... and they were saved and restored properly when creating a new album from scratch, but not the slide show delay; this is really getting strange!

After using the command "Save as default skin", I have now a "Projector-defaults.jap" file saved in the config directory (I has never used this command before, thus no such file, this makes sense):

• I have checked the content of the newly created "Projector-defaults.jap" file and indeed the delay has been properly saved to 5 seconds.

So it looks like:

• The parameter "skin.slideshowDelay" is properly saved in the 3 possible jap files ("defaults.jap", "Projector-defaults.jap" and "jalbum-settings.jap").
• The parameter "skin.slideshowDelay" is overriden when opening a project file (i.e. even though the parameter was set correctly in this file), with the value "3" which we have no idea where it comes from?!