As for the specific request for ‘advanced’ library operations such as split /merge / move we will start with existing functionality but I could see how these would be a good addition once we get the current functions in place and polished up. I will add it to the list!
Gotcha. Thanks for the clarification. I don’t know if we can do this from a licensing standpoint. Therefore it is probably a no on this one. However, our user community is really smart and really crafty and sometimes solutions appear to problems like this (I know of none currently but would not be surprised to see one pop up!)
First @rwoffice I want to say thank you for joining us in the Fireside chat and I truly do appreciate the post. This is a really good post and I hope to do it justice by providing a solid answer here.
First, you are absolutely right that a lot of these look like super small and simple changes. And a lot of them are - for a single client. I also truly understand how from the outside it can feel really frustrating to see some of these issues be seemingly ignored or de-prioritized. The truth of the matter is, we hear you on these and for a lot of them it would be great to just knock them out. Unfortunately it generally isn’t that easy. We can take an example from this Fireside - the nerd stats. That one got done in 10 minutes. I know because I was the one talking to the engineering doing it and it actually took right at 10 minutes to complete - yet that is an outlier. It was on a single client and it was a simple change to something already developed and we just were able to get it over the line.
Let’s consider a different example - displaying the converted bitrate. Yup we have the data (since it is shown once you select the arrow to see more options/info) and so enabling it on one client isn’t tough. The challenge here is that we will want to make this change somewhat simultaneously across all clients. Now I have to make sure that this same change is occurring across 5+ clients (android, apple, roku, web, etc) meaning that I have to loop in 5+ different developers to effect these changes. With that many people involved it adds some overhead in making sure that this isn’t interrupting the flow on bigger projects and other work. The point here isn’t that we can’t do it - it is just that the complexity ramps up pretty quickly even for a “small change”.
Now if I left this answer here I am guessing it wouldn’t be very fulfilling. The good news is that we recognize all of this and there are efforts underway to: Just. Be. Better! We are freeing up more space in our work cycles to tackle backlog items and low hanging fruit. We are working on our codebases to standardize more across client platforms and reduce the number of people, and thus the complexity, needed for, not only changes like this, but bigger projects. I can also assure you that we aren’t tone-deaf here - these smaller QOL items actually provide us with quite a bit of energy and happiness knowing that we are being responsive and knocking stuff out. We are also users ourselves, so I can promise you we feel the same frustrations that you do on this stuff.
I know that this is a long response - but thank you again for the question and the opportunity to share that we do recognize the frustration and are working to be better here!
Another post @BanzaiInstitute ! Nice! I love the enthusiasm! We would like to do this one as well. Not sure if we would implement as you suggested within the context of a library, but it is definitely an idea that we are considering.
Thanks for the post @millercentral ! A couple of times a year we do hackathons and some of our most amazing features have grown into fully fleshed out features from these. Interestingly enough, someone did this exact idea as a hackathon! I like the idea. Not sure when we will be able to slot it into the roadmap, but backlog confirmed!
Hey @mlewellyn don’t fear! We plan to do everything we can to get to all posts in this thread! I am going to jump in on a few of your comments here
This is something that has been discussed internally. The current apps aren’t designed against or built for TV clients right now so we would have to do a little bit to get there, but the topic is definitely on our radar.
Thanks for these comments - the only response I have here is that Plexamp is one of our fastest client to see anything addressed and enhanced, so maybe I will disagree with the bit about it not getting much attention. This is all due to the always amazing Elan who really crushes it with Plexamp!
Yup - I am also looping in your response here - confirming read status: on!! As to the other points being brought up, I have commented on the TV status above and don’t have any context to provide on the possibility of proxy settings - but I would suggest you see if it is called out in the Feature Requests section of the forums and if it isn’t listed there then add it!
Thanks @yanle1 for the post! Unfortunately I don’t have a great answer for you here. We aren’t doing anything currently around this request. The good news/bad news is that it isn’t something we are saying no to - in face we really want to get back to adding more features like these to PMS but it would be a bit further down the backlog right now against other projects and it won’t be something we get to anytime soon.
Hey @db869 thanks for the comments here! I think my initial reaction would be to consider having your family members create their own accounts, then sharing libraries with them. This should prevent them from deleting media and allow you to control that from your account. If you are using the same devices in the house then you could add them to a Plex Home for easier access. You can check out more on these features in our Plex Home support articles.
As for some additional DVR settings, especially around deletion, I think that is a great idea and will be something we consider in the future while working to enhance the DVR functionality.
Thanks @tree2369 for the comments. I will be honest - I don’t know how the logic works around Apple’s Top Shelf but I know that a lot of devices are implementing something similar. I feel like I heard that we can only promote Plex streaming content here - but not 100% sure on this one - either way I can pass this feedback along to the appropriate team here at Plex!
Intended behavior - maybe not - was this a cast of downloaded content or content streamed from your server? I know that we were working on downloads recently and figured out that we weren’t updating watch state on downloaded content. Either way, I will get a ticket going on this one to take a look. Thanks for joining us at the Fireside @DonRaguzzi !
Thanks for the question @yukonzach ! I am definitely gong to ask the team about premature recording stoppage! At the minimum here we should be able to provide you with some more information as to why this is happening, so please consider it added to our list of things to take a look at!
For what it’s worth, this used to exist and was removed in Plex web version 4.56.4. I brought it up a few years ago when I noticed it. I’d very much appreciate its return as well :).