Yeah, bingeMode is a user-related setting, so it needs the user ID - which it doesn’t have when offline. I can try and add a fallback in that case, to the last logged in user ID. I’ll check.
Edit: Sent you a test fix in DM
If you encounter this again, please DM me a log, thanks!
Does anyone have managed users in their Plex Home and can confirm with the latest PMS beta version, that managed users don’t see detected credits markers vs. non-managed users?
Please can you explain the technical process of the below addon options in detail? I read the descriptions but I’m not quite understanding how I can reduce the load to my PMS as much as possible?
“Library chunk size”
“round robin”
Also are any library updates done during media playback?
Libraries are queried in chunks (e.g. ranges of items) from the server, to reduce load on both the client and the server. Once you scroll down near the end of the current chunk, it loads the next one.
That’s generally the functionality of going to one of the ends of a list, going past that, and ending up at the opposite end. In case of lists of unknown length (home hubs), this can be very expensive and should be kept turned off.
Depends on what your situation is. Home gets updated right after playback, never during (to reduce the load on the client). When you play back from a library I’d have to check.
Thank you for the answers! So for library chunk size, is setting that option higher causing less or more load on the server?
I am curious if library caching is done during playback so if you could find out when you have some time that would be amazing. Ideally any caching is done when not playing back media I would hope…
That really depends. If you have a smaller size and you scroll through your entire list of movies that means more queries to the server but each one is returning a smaller set of data. And if it’s bigger then there’s less queries but a larger set of data each time. Depending on what’s going on in your network and/or server one may be better than the other but you’ll have to play with it to see if it makes any difference. Also remember that the chunk size affects your client as well. Bigger chunks could add a delay in scrolling if the client doesn’t process all of those media items fast enough. Or if it’s smaller and the network has issues then you would see more delays in scrolling because you have to do requests more often.
There shouldn’t be anything happening while playing back a video. The only thing we tell the server continuously is your playback progress. But I’ll check.
Very hard to properly answer. Depends on the use case and the hardware. Setting that value higher increases the load on the server for every library you open, initially, but reduces the load when you scroll your libraries often, as it has to do fewer chunk requests. It increases the memory usage of PM4K on the client, though, depending on the same parameters.
The server is pretty good at returning database stuff via the API. I’d put most of my focus on the client, and again, the defaults are sane for most combinations of client and server hardware.
Edit: if you rarely scroll your libraries, you can reduce the chunk size. But then, why even bother.
Edit 2: @bowlingbeeg do you remember whether we kill chunks that were scrolled past? If we don’t, I guess most of what I said about RAM on the client is moot.
So is there a “fully built” cache? ie does all the caching add up to a full cache that’s continually added to like on android tv? how does that part work here for pm4k?
If you hide a library, does that then mean it is not cached?
I’m not sure I totally understand your question but for the library view if you scroll through the entire library it will cache everything and then scrolling up through the list won’t require new requests to the PMS. There is also a setting to retrieve all of the media up front, meaning it will request everything right away when visiting a library, but I wouldn’t recommend it. And of course if you leave the library then the cache is discarded so it would be re-fetched if you go back into the library.
So I’m referring to a permanent cache so that PM4K doesn’t have to request data that has already been looked at.
Why is the cache discarded when you leave the view? This would mean continual requests to a PMS that cause extra load on the server each time you go in and out of the library view. Perhaps an alternative caching mechanism could be used to continually add to a permanently residing cache? I believe that is how the android tv client does it.
also if you hide a library, does that then mean it is not cached?
I’m not sure you want a permanent cache, how do you get updates then? I’m not understanding why you’re so concerned with the load on the PMS. These API requests aren’t that taxing. Do you have a severely underpowered PMS? Usually the client is more of a problem because they tend to have less ram and processing power. So having a giant cache of every library is going to be more of problem then re-requesting data when you’re switching library views.
Any chance there is a way to display multiple libraries on the home page? For example in the normal Plex app, it shows my continue watching, then recent movies 4k, recent movies 1080p, recent TV shows 4k, recent TV shows 1080p.
Not sure I understand that question, that is what PM4K does. In my Home page it shows multiple libraries from movies, tv, etc. That is a server side setting.