Plex Server 1.15.3.858 and above broke save resume on OPHT, Orca and Other Plex players

OK, please suggest a path that works for you then?

and whilst I am here, please can you at least tell us just how many non-Tizen Samsungs are running Plex?

@Mini_Server_1
Just to make things clear, I never said that, even though you made it look like it :wink:

Yeah, I have a 2014 4k 65" Curved, 3D UHD Samsung… I got it when it came out… REALLY expensive, like &*($# expensive, I’m probably never going to get a new TV in 10 years LOL there just isnt a reason when you buy the best at the time, 4k content is barely used and certainly not mainstream.

I hope someone can pickup the samsung development app, usually there are a fe stragglers that know how to do it and we can jump on them to update it :slight_smile:

Any takers :wink:

1 Like

Thank you thank you thank you!

Can’t wait for this fix – it’ll keep the great OpenPHT with Plex Black Edition alive for me a little longer :slight_smile:

(Also still looking forward to UNO for the macOS version of Plex Media Player.)

1 Like

Well, actually I am, and I perfectly understand how this works and how hard it is. This is why I also noted that it is commendable how well supported older devices generally are - Plex just continues to work nicely on them. That said, there are ways to cope with such problems, API versioning for example, but I’m not here to tell Plex devs how to do their job! I’m here to provide feedback on a situation and that’s why I said “try (translate: please, do your best) not to completely break the experience on old apps.”

It is not a LOL matter to ask for “the app to not break” on a TV that is 3-4 years old and was bought under the premise that it runs Plex (and direct plays everything btw, no cheap tv dongle matches that)

But…

It’s an unsupported 3.Party App!

Plex never ever developed it!

And as said multiple times, you can’t expect Plex to keep devices, and test for every 3.party app ever launched!

You can however expect Plex to check their own players!

And to make things clear here, I’m also an IT Pro (+35 years) as well as a dev

This has been well established this far in the discussion.

Thanks for the continued support!

Hi guys

Thanks for this thread great to hear there’s a fix coming.

We have a mixture of openPHT on 32bit players, rasplex on TVs in cabins and rooms, 55-65 inch Samsung TVs that are only a few years old and mounted on motorised guerneys (and working perfectly otherwise) and all have started showing this bug. iPads are unaffected as is latest pmp official (not a fan of pmp but hey it works).

Whilst totally understand that things evolve and the original bug laid in the ecosphere not plex itself , Itd be a great shame to suddenly have to go ripping out TVs from saloons, loungerooms, overhauling raspberry pi clients and various other openPHT clients - when it’s all working perfectly.

Almost everyone I know uses openPHT and rasplex - from 100-200ft superyacht bedrooms and deck saloons, to good old homes with grandma’s (all are fee paying plex pass holders).

1 Like

Plex should continue to test OpenPHT though since it was the official Plex Client for years and still the only client that isn’t terrible.

PHT was an official client once.
OpenPHT has never ever been an official Plex client

OpenPHT is PHT… They just changed the name because it was no longer maintained by the official Plex Devs. Its the same client.

Not so.

It was based on PHT yes, but 3.Party added/changed code in it, since Plex stopped developing/supporting it, due to they switched to PMP

Would be nice to get an answer to this please?

@elan would you consider reactivating PMT ? I still think this an OPHT are the best Plex clients. Just wondering if you could just get PMT to same feature set as OPHT then leave it at that so when your releases come out you test the basic play back and current features no more no less. Just an idea, I am still really happy that you decided to fix PMS for the OPHT users. I am looking forward to the release that fixes it any idea when that is ? This week …next week :grinning:

Yeah, enhancement and fixes were added after renaming it to OpenPHT. Doesn’t take away from the fact that it was the exact same code as PHT. You have no idea what you’re talking about so I’m not sure why you’re arguing the point. The fact that you think OpenPHT started as something new or different is beyond ignorant.

Keyword here is was

With all due respect, I kinda do :wink:

Newer said so.
I said that Plex abandoned PHT, and then community took over, rebranded as OpenPHT, and started to develop on it.

Notice that Plex stopped developing and supporting it, due to they switched focus to PMP instead

3 Likes

So which is it? The community took it over, or it was NEVER an official client because it can’t be both. You’re good at talking out both sides of your mouth though.

Even if OpenPHT didn’t exist I would expect Plex to maintain compatibility for PHT. At least until they come up with a viable successor. If OpenPHT didn’t exist I sure wouldn’t be a Plex user.

You’re being rude as well as ignorant. He stated quite clearly that PHT ‘was’ an official client. Then, Plex abandoned the project in favor of PMP. At this point, the community took over development and it was re-branded OpenPHT. So yes, it can, and is, BOTH.

2 Likes

What is PMT? I don’t know of a Plex client with that abbreviation.

1 Like