3rob3 / ImmichFrame

GNU General Public License v3.0
262 stars 15 forks source link

Image transition skips an image #92

Closed crobibero closed 1 month ago

crobibero commented 1 month ago

Version

v1.0.5.0

Deployment Method

Chromecast with Google TV

Description

When the app loads the next image, it is skipped and a second image is shown after 1s instead of the configured duration (10s)

Reproduction

  1. Load album
  2. Configure duration
  3. See images skipped after 1s

Expectations

Images should not be skipped

Configuration

No response

Logs

No response

Pre-Submission Checklist

3rob3 commented 1 month ago

Just to clarify, you don't have TransitionDuration set to 10 seconds do you? Interval = time between images TransitionDuration = fade in/fade out duration. Should be a small number like 1 or two seconds

crobibero commented 1 month ago

Correct, the transition duration is 1s, and how long the image should be shown is 10s

3rob3 commented 1 month ago

I am unable to reproduce, works correctly for me. If I reverse the two I get the behavior your describing.

crobibero commented 1 month ago

After I restarted the device I was no longer able to reproduce the issue. I plan on looking into it when I get a chance

3rob3 commented 1 month ago

Any update here? Can this be closed?

crobibero commented 1 month ago

I haven't had a chance to see if I can reproduce the issue, likely won't for a week or two.

3rob3 commented 1 month ago

i just saw this behavior. Did you enable screensaver? I think what happens is the screensaver seems to launch another instance of the app when it kicks in (even if it was already running) and they conflict with each other.

crobibero commented 1 month ago

I left everything as default, I didn't see a place on the AndroidTV to disable the screensaver.

3rob3 commented 1 month ago

you don't have to disable it, you have to enable it (so you probably didn't). It still seems to being running multiple instances concurrently. I will keep investigating.

3rob3 commented 1 month ago

Pretty sure this was fixed in v1.0.6.0. If it is seen again I will create a new issue