-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Photo slideshow: Sometimes image decoding has a hard time keeping up with the slideshow #203
Comments
Same problem here, with web interface. When the slideshow skips the the next pic, the original pic has not even finished loading so only half an image was showing when skipping happens. |
In fact, it is already doing this: https://github.com/jellyfin/jellyfin-web/blob/20ea6041a76bd1d6b2eee0b2ab3c16579a172984/src/components/slideshow/slideshow.js#L375-L376 I think the photos are really "high res" so the TV is not able to scale down them fast enough. |
Part of the issue with slideshow is default hide value of 3 seconds. It may be that this also causes that. |
Sometimes when the slideshow shows the next photo it takes the TV a couple moments to download and decode the image. This shows up as an initially black screen, and then photo either pops in a little later or it keeps showing up in chunks.
In my case the connection between the Jellyfin server and the TV is wired, to the limitation here is entirely just the interface speed of the TV. I also acknowledge that the processor in the TV might not be the fastest, so I should not expect it to be able to decode the larger photos super quickly.
However this is just as much of a problem on the regular web and people have come up with some solutions to mitigate the jank in these scenarios. In particular by trying to load and decode one or two photos ahead and before the photo currently displayed. That way, by the time user gets to the photo, the photo will be available for immediate presentation in pretty much every situation.
The text was updated successfully, but these errors were encountered: