I have a TV episode encoded in a single video file that is 30 hours long. When I play it on PlexWeb or I play sync’ed one on iPhone Plex, it restarts from the beginning once the last played position goes beyond approximately at around 27 hours 40 minutes. This is approximately 100000 seconds.
**Is this due to some sort of overflow in arithmetic operation on the code?
**
If I sync it onto my iPhone using iTunes, iPhone’s inbox TV application has no problem resuming (so far I tested up to 70 hours).
There isn’t a way to disable this. It’s hard coded into PMS. The idea for using 90% is that, normally, this would allow you to skip ending credits and still have the file marked as watched. Otherwise you’d have to watch the entire video or manually mark each video as watched.
@“MovieFan.Plex” said:
There isn’t a way to disable this. It’s hard coded into PMS. The idea for using 90% is that, normally, this would allow you to skip ending credits and still have the file marked as watched. Otherwise you’d have to watch the entire video or manually mark each video as watched.
It makes sense but hard coded one doesn’t always work for everyone.
@“MovieFan.Plex” said:
There isn’t a way to disable this. It’s hard coded into PMS. The idea for using 90% is that, normally, this would allow you to skip ending credits and still have the file marked as watched. Otherwise you’d have to watch the entire video or manually mark each video as watched.
There should be a per library or, better, per each client setting that sets what “completed” means. Something like that is simple programming but possibly beyond Plex’s abilities or desires.
@“MovieFan.Plex” said:
I picked the thread that was in the feature request section, which is where it should be.
I don’t even read the “feature request” forum any more because it seems to get ignored and it is elitist because it ignores the non-Plex Pass users. While I can understand features only being available to paying customers all users can have valid ideas.
Having a feature request forum that is locked out for a large percentage of users makes that forum virtually worthless.
by no means am I a plex apologist, but I do understand that there are limited resources to understanding and resolving issues, and building out improvements, wishes and new features, along with competing priorities from directions both internal and external.
Yes I also think it would be nice to define your own completion percentage, but personally that is also much much lower on my personal priority list, and the 90% works well enough (but obviously not perfect) for the majority of use.
@TeknoJunky said:
Yes I also think it would be nice to define your own completion percentage, but personally that is also much much lower on my personal priority list, and the 90% works well enough (but obviously not perfect) for the majority of use.
I have seen something like this all the time in the modern softwares especially in the closed source products. The problem is that you design something based on a limited business analysis but you will rarely get a chance to revise it once the product ships because revising a shipped software isn’t necessary to proof of making money.
I think the solution would be: whenever you think you are smart enough and do something automatically, you always provide an option to override it. That automatic solution would work for 90% of normal users and the rest who complains about it can manually configure the solution. I think that would work for 99.9% users except for the users who have no knowledge about finding the manual solution but those users would never complain.
