Posts: 6,252
Joined: Jun 2009
Reputation:
115
da-anda
Team-Kodi Member
Posts: 6,252
2015-02-07, 17:33
(This post was last modified: 2015-02-07, 17:34 by da-anda.)
As I'm personally a fan of the additive/smart seeking (especially for 5button remotes) I'm fine with removing the old seek options, but I also know that many prefer the instant seeks, so it would be nice to get some feedback or maybe we can create a list with pros and cons for either side to see if we should keep all possibilities or do some cleanup.
As big con for the old instant seek approach I see the userexperience when seeking in online video streams. Depending on the connection speed it can take a few seconds to buffer after a seek operation. If you want to seek something like 3 mins on such a stream with old 30sec intervals it takes ages to get there (I know from experience). With smart seeking its basically just one seek and buffer process. The next obvious con for old approach is that you need 6 buttons instead of 2 to achieve the very same thing with the downside of a slight total delay of maybe 1000ms (or whatever you defined as delay value).
The con of smart seeking is that you seek blindly while with small subsequent steps in old behavior you could see the frame/scene of the intermediate step. But we might be able to give seek preview in some point in the future (like youtube does), so at least to me this wouldn't be a hard loss.
Posts: 3,077
Joined: Jun 2009
FYI I have lot's of mail from users of Yatse for 2 things :
The back button to do the 30 sec back that was changed in Gotham.
And a new button for instant back 15 or 7 seconds.
All saying the same I want a quick small back to listen to some words I missed.
So if this drop complete support for such possibility users will complains.
(By lots I mean really a lot)
Posts: 3,077
Joined: Jun 2009
My post was more informative of user requests
I did not checked how new system worked.
About 30s 3 key presses how does it work ? Since on rpi 1080p content if it tries to do 3 seeks to get to 30 secs it would be hardly usable.
Posts: 708
Joined: Jul 2012
Reputation:
30
xhaggi
Team-Kodi Developer
Posts: 708
There is a delay which defines the time to wait for subsequent key presses before performing the seek.
Configurable in GUI settings, with a value from 500ms - 3000ms, default: 1000ms, step size 250ms.
So for example if you press 3 times forward within the delay/timeout of 1000ms only one seek is performed.
Posts: 708
Joined: Jul 2012
Reputation:
30
xhaggi
Team-Kodi Developer
Posts: 708
2015-02-08, 14:17
(This post was last modified: 2015-02-08, 14:22 by xhaggi.)
As a hint I've tested the new smart seeking with your remote app and everything works fine.
The key-repeats + seeking work the same like with keyboard or remote control.
Posts: 3,077
Joined: Jun 2009
Ok so everything sounds good
Thanks for the test and explanation as users will ask me the same questions
Posts: 4,058
Joined: Oct 2007
Reputation:
89
zag
Team-Kodi Member
Posts: 4,058
Will I still be able to jump forward in 30 seconds gaps like now?
I use this all the time to skip the intro to a TVShow. Usually a click 3 times right on the remote and it is perfect.
Posts: 708
Joined: Jul 2012
Reputation:
30
xhaggi
Team-Kodi Developer
Posts: 708
Please take a look at the screenshot in the third post. You can enable/disable every step in the list of steps.
If you only activate one step per direction you'll end up on the same behavior as before, each keypress will skip XXX seconds e.g. 30 sec.
Posts: 6,252
Joined: Jun 2009
Reputation:
115
da-anda
Team-Kodi Member
Posts: 6,252
zag - you can still use old skipping behavior if you only select the 30 sec step f.e. - or if you need a little more flexibility and also smaller steps forward, select 15s and 30s. With this setup you can jump 15s, 30s, 60s, 90s, 120s, .. because the last skip step size will be repeated on subsequent key presses. Was this understandable?
Posts: 4,058
Joined: Oct 2007
Reputation:
89
zag
Team-Kodi Member
Posts: 4,058
Yep got it, if its configurable to work the same then great!
Posts: 515
Joined: Jul 2012
Reputation:
18
I've really missed this feature before. Tested and works great!
There's only one problem i see that wasn't noticeable with fixed skip steps:
The skin property "Player.SeekOffset" is exposed not before the action is performed and that is really too late!!!
Right now you have to know the skip steps that are active in the settings
and you have to count in your mind how often you press a button to get your desired jump in the timeline.
Posts: 3,571
Joined: Sep 2009
Reputation:
110
I *love* the instant nature of the current (now old) seek. I definitely don't want all seeking to have a delay waiting for more pushes before it seeks.
This read like a classic power user feature - great if you're used to it...but for new users it seems to me it's going to seem really non-responsive. I think I read on github if you have only one seek step defined it won't use the delay? Which is ok in principle - BUT I can currently - without any delay:
Seek Back 7
Seek Back 30
Seek Forward 30
Seek Back 10 mins
Seek Forward 10 mins
I'd really like to still be able to do ALL of that - and particularly the two seek backs - without ANY delay - as we use these a whole bunch of times every single day.
I get that this is wanted (and why), but I think having a delay on ALL seeks and variable seek length (with no obvious UI feedback?) is precisely the sort of thing that's going to confuse new users and that the instant, easy to understand seeks of the past were actually one of the majorly cool things I see new users liking about kodi.
It's of course always a balance between power features and default behaviour, but I think this is too far towards power users myself....
Addons I wrote &/or maintain:
OzWeather (Australian BOM weather) | Check Previous Episode | Playback Resumer | Unpause Jumpback | XSqueezeDisplay | (Legacy - XSqueeze & XZen)
Sorry, no help w/out a
*full debug log*.
