Server Version#:1.15.3.858
Player Version#: open plex home theater 1.8
Hi I understand you don’t support plex home theater any more which is why open plex home theater was created but thought I would ask for help anyway. Basically the latest updates have broken the resume feature in OPHT it will not save the point you were at. The last version this worked on was Version#:1.15.3.793 so I rolled back. I run Windows 7 32 bit so can’t use the new plex client and I find the kodi one is unreliable it resumes 20% of the time after trying to resume about 5 or 6 times. It’s only used for TV so not paying to upgrade to Windows 10. I use a remote control so don’t want to plug in a mouse and open a browser either.
What you are experiencing is actually a bug in OPHT where it is reporting play progress incorrectly during the process of resuming. In certain circumstances this play progress was ignored by the server but the cases where it is ignored have been lessened. Now OPHT’s broken behavior is being exposed. There is at least one other bug in OPHT’s play progress reporting that I have seen before.
Unfortunately, OPHT is not being developed futher - is there a way to make an exception for this ? I know about 8 other people using similar setups that are now experiencing this…
I’m having the same problem.
OpenPHT is my family’s player of choice . For them it is the simple layout, and for me, it is the superior configurability that allows me to create a simple layout.
Now I have a rebellion on my hands as their favourite player is broken…and of course, in their eyes, it’s all my fault
@gbooker02 so if the new modifications have not fixed anything regarding the player are they nessesary? why can they not get reverted? Can you just help us out I can’t upgrade until this is fixed its my main source for plex.
Where did you get the idea that the modifications didn’t fix anything? I never said anything of the sort. They are necessary because they do fix behavior and it works correctly with clients that report their play progress correctly.
As @gbooker02 mentioned above, the change in behavior addresses buggy behavior; specifically, when you are seeking around in a video, and then seek back to the beginning to make sure it’s not saved at that offset, that beginning offset was being ignored.
The change in behavior does make it more susceptible to buggy clients, and that’s unfortunate, but ultimately we made the decision to help the majority of clients.
@elan well I never had any issues on the 1.4 version of Plex server and no issues on 1.5.793 on Android client, PHT, OPHT. So be interested to see some posts about seeking and issues before your modification. If you were trying to fix the Kodi client resume and seeking it has not worked it’s still terrible for resume and seeking etc. So if you have proof the changes have done more harm than good I would be interested to see some positive posts on the forum because I can’t find any. @gbooker02 you didn’t say that it did not fix anything it’s my observation. I was just saying as above, no issues for any of my clients before you fixed it.
So only hope is we get a developer to pick back up OPHT is what you are saying. So anyone on here who got the skills to pick up OPHT please do ! I am sure you would get some donations for your time.
Put simply, this is the risk you run when you use a client that’s no longer supported/updated. If it is using the API incorrectly, then that behavior will eventually be exposed. The API implementation is free to change implementation details and any client relying on undocumented behavior is at fault when it experience breakage. If OPHT were reporting play progress correctly, then this would have never been an issue. Personally I noticed OPHT’s incorrect behavior in play progress reporting long ago which is why I immediately knew it was at fault when I first read this topic.
To be explicit: this change fixed incorrect behavior in spite of your observation.
@gbooker02 what do you suggest for a Windows 7 32 bit user ?
You stopped PMT which was one of the worst decisions you made IMO so my options are the Kodi client which won’t resume either unless you click it 50 times, on my LAN can’t play a high bit rate blue ray rip via direct play. or web site which you need a mouse for?
I am intending on upgrading to Windows 10 when windows 7 goes out of support next year but the windows 10 app is also a smoke and mirrors web site so IMO best front end ever for a computer was PMT which is why someone started OPHT it’s a real shame it’s not continued any longer or you guys pick up PMT. I would be interested to see a poll of prefered Plex client to see what majority of the users think. And on a different note how come the iPhone application shows a full grid TV guide and the android one does not ?
I assume this is what “fixed” the bug as per the release notes:
" * When playing in the middle and returning to start, view offset is properly saved."
Cannot be edit this behavior by identify the client?
The problem is that from our point of view Plex put their hands in the air and say “we don’t support that app and replace your TV if yoyu want to use our product”. This is really not a customer friendly behavior and to be honest thats why I will never pay for PlexPass.
I would love to see how many people are affected by this fix. Sometimes a bug is a feature and need to step back or rethink the fix.
Retrive the fix and leave the bug which is a feature
@darcilicious can you kindly point me to a 32 bit download of PMP because when I go to download it says 64 Bit only hence my post. I am also not a fan but would try it out if there is no other option available.
@darcilicious I have tried the Kodi Plex client and I have 2 issues.
It can’t direct stream a high bit rate blue ray rip it says server is not powerful enough when I have direct play selected I play the same movie in OPHT and it plays perfectly.
If I play a TV episode on another device like my android phone or my tablet and I then want to resume on the Kodi Plex client I hit resume it fails I can click it about 10 - 20 times and it will some times work or I give up and go back to OPHT.
That’s why I keep using OPHT because it does everything I need it too until you added the fix for the clients which no one seems to complain was broken in the first place or has acknowledged it’s been fixed. I am talking about actual user acknowledgement not Plex employees or mods saying oh yeah massive bug it’s fixed. Not one user has jumped on this thread to back you guys up, so that must count for something. I know you are able to identify the OS and player used so it’s easy to put a routine in that says if OPHT then ignore incorrect flags or whatever is at fault then else statement apply the fix.
And for the record I have used Plex for like 8 years or more with your old PMT client and then OPHT because I love it, I recently bought the pass to check out the PVR and support Plex. I can easily say stuff it and go with Kodi but I like Plex, so keep up the good work and listen to your users or you will lose them.
- is there a way to make an exception for this ? I know about 8 other people using similar setups that are now experiencing this…
