Oh, come on! I know you’re joking, but some folks will take that seriously (besides, I thought doge was the hot thing now? 
). There is still some refinement to do, it’s still a prototype. 
Jokes aside
So you really did go of the forum and do more to make this go faster the other day?
That’s an interesting solution. Are you not worried that users will get pissed off by the (hopefully not) constant prompting that they turn the feature off?
No, we’re not going to be overly aggressive about it.
No, our pace or timing on this hasn’t really changed, was just coincidental
So you confirming now the pace is still going to be slow? 
Whats the hold up here? This issue is 2 years old. This is not a 2 year kinda problem.
Do you have an engineer working full time on this? If not, why not?
Is the other stuff you are doing higher priority so this gets like 1 hour a week worth of work? If so, why?
Playing videos properly is your core competency and you are failing at it, spectacularly.
Is this an issue that your engineering department is unable to do that in a sub 2 years timeframe because of lack of skills or is this a management issue that you guys don’t give that a higher priority. Either way you have a glaring personell issue which needs attention.
Other bugreports in the forum suffer a similar fate and don’t get fixed for months and months, some even years, like this one or the seeking issue.
You got a major issue here with your processes/workflows, not sure if you guys are aware of that.
Or you just don’t give a cr*p and your new streaming media/content/gaming/free tv/tidal ads etc is more important. Which would be a shame and ppl will leave over time, most ppl in this thread are plex pass users, do you think they have a plex pass for the plex content? Do you wanna keep these users or does it not matter because the ad business is more profitable by now? Or most have lifetime passes anyways?
This is infuriating by now Dave.
I am not sure what this is, but it’s really becoming super embarrassing for plex.
I am just so tired of this stupid, easy to fix issue, sosososo f… tired. sigh
(I know this is not your fault, sorry that you are bearing the brunt of it)
Well spoke
Can you ease up on the attitude a little here? I’m being as open and transparent as I can and giving you updates as regularly as I can, so getting told that things are infuriating, or embarrassing, and are easy to fix is not really appreciated when it’s super easy to make armchair criticism without actually knowing the engineering effort involved and the resourcing required. We don’t have infinite resources, we’re a fairly small team. We also haven’t been working on this for two years, that’s just when the request was made.
I mentioned further back, but there were also a lot of under-the-hood changes that were required to get us to a point where we could start to work on this, so things have been steadily progressing towards this for a while, even if you’re not seeing anything obvious (yet). Additionally, it’s not like someone just writes code and it’s all just magically finished then. Code is written, reviewed, tested, and then changes sometimes need to be made. Sometimes priorities need to be changed (“Hey, this thing over here is totally broken, and we need to fix it before the broken thing goes out to the public. Can you pause on this new thing you’re working on, so we don’t introduce a public regression?”), or there are things that need to be worked on that tie across multiple teams or features, and need to be prioritised a little higher. Sometimes staff change or move on or need some personal time (it’s been a pretty overwhelming time in the last 18 months for everyone), which can slow things down a bit too. Things get prototyped and maybe don’t work quite as well as initially hoped, so some tweaks are made to improve them.
I’ve addressed this before, but to say that we don’t care, or are not here is simply not true, and is frankly insulting. If we didn’t care, I wouldn’t be here listening and providing feedback both here, and internally, and continuing with the work on this. There is a balance to be struck between having staff work on things, and also be here helping folks (engineering folks tend to spend more time doing engineering and less time here, though I try to engage with the community as much as I can, even if that sometimes means being here on my own time). Ranting about things doesn’t mean they’ll get fixed any sooner, and things need time to be investigated, fixed/engineered, tested, and then released. We do releases for most things every 2-3 weeks, which means for things to make those releases, they need to be done at least a few weeks before that release to allow time for testing and app approval and all those sorts of things. We would love if we could get everything right the first time, and not have any bugs and be able to ship things perfectly the next day, but it’s just not possible (unfortunately).
I’ve personally been spending some of my time with helping to prioritise issues, and make things easier for our engineering teams to identify where major areas of concern are, so we can address things better, but like everything, it’s a work in progress, and there is always room for improvement. Some of these things are from public releases, or might be crashes that hit some people, but not others, other things are items that are identified during testing or beta periods, or by other employees, and are fixed before they’re ever seen by the general public (I guess you’d call that invisible work, if we fix something you never knew had an issue?), and others are refactors or changes needed in order to facilitate future work, as we have had to do with this feature (again, invisible work as far as the public is concerned).
We want to get this right, and not rush it, because we know how important it is, and that’s why we’re not doing a MVP and pushing it out the door. We’re working to get it right, make sure we’re happy with it internally, before we invite folks from here to help us with a closed beta, gather more feedback, and then make any changes required before opening it up more widely. So please, bear with me here as we continue towards a solution here that we think will not only reduce transcoding for server owners, but also improve the playback experience for clients, and not introduce any additional overhead for server owners 
I call bullsh*t
I would urge you to read our Forum Guidelines, as I mentioned to you previously. Responses like that are not helpful or appreciated, and may result in warnings or a suspension of your forum account.
I’m gonna give it some time as I just entered the topic a day or two ago although I had thought about it before. It’s not a dealbreaker. I do tend to agree they fix one thing and break two others sometimes (mainly with the Android client) but what he is saying doesn’t sount like BS to me.
So I’m not allowed to call something bs?
Dave you coming right out saying you haven’t looked at the problem for at least two years? I’m just like WHAT? there is forum threads tracking back to 2015 about the same issue. And that not you but some founding guy come out and said already back then its being looked at. And since then we got a new client for all systems. And we got DVR and Tilda and ads and free TV and movies. And some wierd arcade stuff. But a simple fix to this? That wasn’t in the work? And now you saying you taking a long way around because it has to be better and there need some re doing in the engineroom. Even tho this issue was brought up before we got a new client back in 16 or was it 17 I don’t remember. Are you kidding me
Everyone here needs to take a breath.
None of this is life or death.
Chill out, or be chilled.
Generally, no. We welcome constructive criticism, while that is just rude and dismissive. As mentioned in our guidelines:
You should be:
- Respecting others.
- Assuming good intentions.
- Offering constructive criticism or voicing a dissenting opinion, but don’t be mean or disrespectful.
And should avoid:
- Name-calling
- Personal attacks of users, employees, or Plex
- Responding to a post’s tone instead of its actual content
- Knee-jerk contradiction
- Ranting
- Trolling
We also ask that folks:
- Be civil : Don’t post anything that a reasonable person would consider offensive, abusive, or hate speech. Absolutely no personal attacks.
- Keep it clean : Don’t post anything obscene or sexually explicit. Keep profane language out of here.
- Respect each other : Don’t harass, intimidate, impersonate, or expose others’ private information without prior affirmative consent.
- Respect our community : Don’t post spam or otherwise vandalize the forum.
I don’t think these are a lot to ask.
Well I’m gonna take that bad excuse. As you guys knows you did a bad job
Honestly, the team at Plex know our outrage is justified. They’ll never admit it, but anyone who has been around for any length of time knows how it goes around here.
This isn’t the first or the last time that major issues will go unaddressed for a significant length of time.
I know I have been addressing a few the last couple of days. But this one needs to happen asap.
Not after 2 years, no.
We asked for more control for admins, not a super elaborate system you need 2 years plus to implement. That’s on you, not on us.
Yes you have explained why and most ppl here think the reasoning is wrong or suboptimal for what we want.
2 years is insulting. Don’t turn this around. This is how it looks to US, if it’s true or not.
Look what you guys released in the 2 years no one asked for. We don’t need you to stream us political propaganda tv channels that spread lies right into OUR users interface without our ok. Why, no stop, who thought that was a good idea to spend manhours on? That’s crazy.
Focus on what the pms is for. THIS is insulting.
You guys are having structural problems, this much is obvious to anyone working in IT.
Not just because of this, but you can see it all over the forum, bugs that got ignored for month and years, no way to report a bug and your management not knowing why people use plex.
2 years+ is not the time telling us we being impatience is insulting to you, i don’t care, sorry, it’s the time were you take stock of what went wrong and make drastic changes.
Is the solution around the cornor? Another year? another 2 years? Who knows! You leave us in the dark. THAT is insulting.
Not us saying thats wrong.
I am not asking you to move fast and break things, this isn’t about a MVP anymore and it has not been for a long time.
It has been 2 years man. 2 years. There is no way to sugar coat that.
2 years.
Two!
Years!
2 years
This is not particularly helpful, and is little more than a personal attack on Plex and its employees. I’m all for healthy debate and constructive criticism, but there is little here that is healthy or constructive.
