Upgraded to OpenPHT ver. 1.6.1 after it has been released (1.6.1.dev-e452beab).
Removed the .plexht folder and started a new configuration.
Only issue so far is in Preferences - System - Advanced.
Under Video the first entry is “?0?” By moving the arrows value changes “?-1?” or “?0?”.
Tried on default and Black skin.
When cleaning up screen/video settings and fullscreen toggle it now enforces restrictions if the build supports fullscreen or not (embedded). This is possibly only an issue on linux, please report an issue on github to make it easier to keep track
I haven’t test it yet. Did the skip delay that destroys the picture quality while moving forward or backward at the 750ms been resolved? Or I still have to set it to none?
Sorry, no Roku support, ever, other devices are in the pipeline (which Plex Inc don’t have official clients for), don’t ask which at the moment, early days.
@Kwiboo said:
You can change the Playback → Advanced video → Skip delay option in Preferences to 0 ms to get back the old instant seeking behavior, default in 1.6 is to use adaptive seeking where if you repeatedly press skip forward/backwards within 750 ms the seek time will advance in steps of 30s, 1m, 2m, 3m, 5m+ until you finally stop
I made this change on my RasPlex install as I prefer the old behaviour. However it seems to have had the side-effect of disabling the preview images whilst seeking Is that by design, or is it a (known?) issue?
For me the perfect combo is non-adaptive seeking with preview images, since the usual behaviour in our house is to hold down the seek button until reaching the desired area. With the new adaptive seeking, that very quickly leads to seeking to the end of the episode!
This is still the case with 1.6.1. Can somebody confirm if this behaving as designed, or whether its a bug? Thanks!
@benadderson said:
Thanks @NedtheNerd. Do you know if there are plans to bring this feature to non-adaptive seeking in the future?
Preview images will always require some sort of delay before the seeking is actually performed.
Making the seek steps configurable (they are in Kodi) and only use -15,+30 should probably fit your usage pattern better. Please make a feature request on GitHub to make seek steps configurable (will most likely be implemented as an advancedsettings.xml setting) to help make it easier to track this.