2023-09-22, 04:12 AM
Like many of you I originally came from plex. One thing Plex has absolutely nailed (5 years ago when I was using it mind you) was the behaviour of the "next up" queue.
It showed a list of series, ordered by a combination of:
- in progress episodes (weighted by most recently watched)
- the next episode from recently watched series
- newly released episodes from series you hadn't watched in a while
The card showed the series banner, not the episode banner, and it had a fairly basic algorithmn to weight the order displayed by "date of last viewing" vs. "Broadcast date", so newly released seasons of a series you had previously watched would populate the list but be displayed further to the right of the screen.
Jellyfin's UI instead maintains 3 lists for this one purpose. It shows a "continue watching" of only in progress episodes, "next up" of only episodes sorted by last viewed date, as long as it isn't in progress, and "latest TV series", for newly added or updated shows.
A search here and on the repo doesn't come up with much, which leads me to think people are either happy with this behaviour (why!? It could be so much better!) Or there is a simple fix/mod I am unaware of.
It showed a list of series, ordered by a combination of:
- in progress episodes (weighted by most recently watched)
- the next episode from recently watched series
- newly released episodes from series you hadn't watched in a while
The card showed the series banner, not the episode banner, and it had a fairly basic algorithmn to weight the order displayed by "date of last viewing" vs. "Broadcast date", so newly released seasons of a series you had previously watched would populate the list but be displayed further to the right of the screen.
Jellyfin's UI instead maintains 3 lists for this one purpose. It shows a "continue watching" of only in progress episodes, "next up" of only episodes sorted by last viewed date, as long as it isn't in progress, and "latest TV series", for newly added or updated shows.
A search here and on the repo doesn't come up with much, which leads me to think people are either happy with this behaviour (why!? It could be so much better!) Or there is a simple fix/mod I am unaware of.