No it can’t be both and you’re clearly ignorant of the history of the project. He’s inferring because it was rebranded that Plex completely absolves itself of any responsibility. To this day it’s the only client that natively integrates with WMC. Therefore there isn’t a viable replacement. Plex Pass was marketed with this support and the PHT client is the only reason many people including myself paid for this software.
When Plex stopped support for PHT, the community took over the code and renamed it OpenPHT. Although it started with the same code as PHT, it is considered a different client and not supported by Plex. It’s like buying a new car and fixing it up. The car is the same but if there are problems, the manufacturer doesn’t provide support anymore.
No. Once a client is no-longer considered supported, there is zero support, even for backwards compatibility. That is the definition of “not supported”. If backwards compatibility was maintained, then it would be “supported”.
2 Likes
Sorry, I don’t have any more specifics to offer you on this topic. The numbers, %-wise, are very small.
1 Like
I strongly suggest, that you relax a bit here.
Plex forums is a place, where people are kind, and not attacking each other, and you tend to do that towards me, which is not nice!
Please see: https://forums.plex.tv/guidelines
It’s not an attack. You’re trying to play both sides. Bottom line is PHT was marketed heavily as a selling point for PlexPass subscriptions and a top reason why so many people paid PlexPass was to support development of PHT. It’s widely known why Plex suddenly dropped support for PHT and went to PMP but I’m not allowed to say it here or I’ll be banned. So, part of my argument can’t even be talked about here.
Good, cuz it felt like it 4 sure
I fail to see that, since I simply stated facts!
Huh…
PHT was always free. It was an open source based on Kodi
I’m not sure where you are getting this idea. A Plex Pass was not needed to use PHT and AFAIK, it was never marketed that way.
I’m not sure what reason you are thinking of, but PHT was dropped because it was based on XBMC (now Kodi). when their code changed, PHT had to change. PMP was created to use a different playback engine and no longer relied on XBMC.
Lots of lies in these last couple responses as well as selective memory as to where Plex came from and what it was just a short few years ago. PHT being dropped had nothing to do with Kodi’s code. The PHT code had already diverted quite a bit from Kodi’s that part was irrelevant.
This topic is no longer helpful and has transitioned into hurtful. It’s time to close.
Summary:
- OpenPHT and the other clients mentioned here are not supported clients.
- It doesn’t matter whether you are talking about PHT or OpenPHT, neither are supported.
- These clients have bugs which misreport the play progress to the server
- They report play progress of 0 (start of media) when playback ends when they shouldn’t.
- The server had an issue which ignored play progress in certain circumstances when it should not have been ignoring it
- The ignoring of play progress on the server has been fixed
- There is valid reason to reset the play progress back toward the beginning. I’ve personally been annoyed by not being able to do this and I know of others who have as well. In spite of this annoyance from myself and other users I personally know, I did not push for this change nor make the change myself. This means there are even more users than those I know who were also annoyed by this behavior enough to prompt a different developer to fix it.
- This change exposed the bug present in the unsupported clients
- No supported client has this bug
- We are adding a workaround to the server to alleviate this situation
- There is zero obligation on our part to do this as these clients, being unsupported clients, do not require we ensure support on our part.
On a side note: I find the point where users are focusing their anger in this thread interesting. I’ve used third-party clients in numerous circumstances and any time that client was broken by an update by the first-party, I never once turned to the first-party vendor to demand they fix it nor even accused them of intentionally breaking my third-party client. Whenever you run a third-party or unsupported client, you run the risk that someday it will cease working. This is the nature of such clients and should be clearly understood by all.
10 Likes
