This is why I moved to Emby. I use a different player on all my devices and all my content is HEVC or H264 with AAC or DTS so never an issue playing. No need for premium either.
Jellyfin is on fumes. They made a call for help a couple of years ago but since then, haven’t had much of any. They found a critical bug last build I think and where supposed to disclose the details around the end of last year and it’s May now. No news.
There’s a ton broken and no one to really fix it. I remember posting about a bug and a long standing contributor just basically blamed the scraper and said well that scraper is shit.
I got the sense most of the older crew just gate keep but don’t actually work towards making the thing better.
They also said that they would divulge more about the huge critical fault they found “in a couple of weeks” which was like 6 months ago. Colour me skeptical.
Have you setup your home screen? You can do that on the dashboard, hiding, grouping, etc.
If what you’ve watched has nearly ended, it won’t show for continuing. I have the opposite issue, some shows has a long outro/preview of the next episode, so I have to either mark it as seen, or fast forward near the end for it not to show on the continuing watching section
Have you just installed jellyfin? The scraping for metadata for me took days literally. And the difficult time is that during the scraping, the interface is very slow.
You can monitor the scraping/parsing progress in settings > dashboard > libraries. The libraries have a sort of circular progress bar with a percentage symbol (only visible in this view) when parsing is ongoing.
Both. How quickly a server can send a webpage with images (even if they’re small) is directly proportional to the storage mediums seeks times. The worse the seek times, the less ‘responsive’ a website feels. Hard drives are a terrible location to keep your metadata.
The server scan will search for the files, look them up and grab metadata, and then store that metadata in the metadata location. If your metadata location is the same spot as your movie, it will cause some major thrashing, and will significantly increase the scan time for jellyfin. Essentially, it gets bogged down trying to read and write lots of tiny files on the same drive, the absolute worst case scenario for a hard drive to have.
If the movies are on a hard drive, and the metadata on an ssd (or even just a different hard drive) the pipeline will be a lot less problematic.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
removed by mod
This is not how you raise an issue on Github.
It would be nice to see a ui update. Part of what keeps me from using JF is the top bar. It takes up like 1/5th of the screen on my device.
This is why I moved to Emby. I use a different player on all my devices and all my content is HEVC or H264 with AAC or DTS so never an issue playing. No need for premium either.
Jellyfin is on fumes. They made a call for help a couple of years ago but since then, haven’t had much of any. They found a critical bug last build I think and where supposed to disclose the details around the end of last year and it’s May now. No news.
There’s a ton broken and no one to really fix it. I remember posting about a bug and a long standing contributor just basically blamed the scraper and said well that scraper is shit.
I got the sense most of the older crew just gate keep but don’t actually work towards making the thing better.
I just want to thank you and OP help me move on from this sinking ship that is Jellyfin. Been trying to like it enough for too long.
It sucks really. I would have preferred open source projects don’t shut down. I guess it is what it is.
The first major update in over a year is coming out in the next week or two.
Apparently their build pipeline was a major issue for a long time, now that it’s fixed they’re planning to do major releases a lot more regularly.
They also said that they would divulge more about the huge critical fault they found “in a couple of weeks” which was like 6 months ago. Colour me skeptical.
I’ve been following the development in their discord channel and tracking their general github issue progress.
This big release is coming, for sure.
They’ve been in feature freeze while testing it for over a month, now
I track their progress by seeing GitHub commits…
https://jellyfin.org/posts/jellyfin-release-10.9.0/
Maybe I am misunderstanding, but continue watching is only for resuming media. If you stop a show or movie in the middle.
If you want to go to the next episode in a series you want to look at “Next up” section.
Have you setup your home screen? You can do that on the dashboard, hiding, grouping, etc.
If what you’ve watched has nearly ended, it won’t show for continuing. I have the opposite issue, some shows has a long outro/preview of the next episode, so I have to either mark it as seen, or fast forward near the end for it not to show on the continuing watching section
You may want to change the following setting in that case: Settings > dashboard > playback > resume > Maximum resume percentage.
It will set the threshold of what is considered played (in percentage of video length). Default is 90%. Try lowering it?
I surely missed that setting. I am playing with it, it seems 85 is the sweet spot for me. Thanks!
Have you just installed jellyfin? The scraping for metadata for me took days literally. And the difficult time is that during the scraping, the interface is very slow.
You can monitor the scraping/parsing progress in settings > dashboard > libraries. The libraries have a sort of circular progress bar with a percentage symbol (only visible in this view) when parsing is ongoing.
You can significantly speed this process up by putting the cache folder on an ssd, instead of the same hard drive the videos are on.
Is that the limiting factor for the UI responsiveness? Or are you talking about the fact that the parsing and metadata querying takes days?
Both. How quickly a server can send a webpage with images (even if they’re small) is directly proportional to the storage mediums seeks times. The worse the seek times, the less ‘responsive’ a website feels. Hard drives are a terrible location to keep your metadata.
The server scan will search for the files, look them up and grab metadata, and then store that metadata in the metadata location. If your metadata location is the same spot as your movie, it will cause some major thrashing, and will significantly increase the scan time for jellyfin. Essentially, it gets bogged down trying to read and write lots of tiny files on the same drive, the absolute worst case scenario for a hard drive to have.
If the movies are on a hard drive, and the metadata on an ssd (or even just a different hard drive) the pipeline will be a lot less problematic.