2024-05-22, 01:34 PM
(2024-05-22, 01:14 PM)Efficient_Good_5784 Wrote:(2024-05-20, 06:24 PM)34626 Wrote: Lets say the cached data should be stored for like 10 hours or untill it has been played over 90%?What's the purpose of this? The cache is normally designed to stay for the duration of the viewing session. Once the player closes, the cache is released. The media player doesn't have an offline mode as it always needs to stay connected to the Jellyfin server, so the preserved cache would be useless when your server is offline.
Also, if this was how it worked, you'd have to keep the media player always open (at least in the background) so that it knows when 10 hours went by so that it can delete the cache.
Wouldn't this use case be better served by just direct downloading the entire file and playing it locally?
The purpose is to get the media that is being played sent to the client, not for offline mode, but to ensure a clean playback - An example, if you watch a movie while traveling in train, or are a place with unstable Wi-Fi or mobile network, it would try and get the entire movie down, as fast as possibleble, but not for offline mode, and the time period for i to keep the data, could just be based on date and or time the data is cached/downloaded, but after 10 hours, it should be cleared (Maby the 10 hour thing, should be a thing users at client side can customize).
So it's not a download feature that requires user interaction, but how aggressive the media can be sent to the client, for best possible playback experience.
I dont know how cache function, if that only in the RAM or on the disk? But its on the disk that could have interest, but just as tempoerary storage to ensure the user experience.
Debian 12 | Jellyfin 10.10.7 docker | Intel N5105 | RAM 32 GB | 26 TB storage