You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Stremio, shortcuts for moving ahead/behind are (and have been for years afaik) the following [1]:
Left arrow: Seek 20 seconds behind
Right arrow: Seek 20 seconds ahead
Shift + Left arrow: Seek 10 seconds behind
Shift + Right arrow: Seek 10 seconds ahead
However, in Stremio Web, these shortcuts have changed values:
Left arrow: Seek 10 seconds behind
Right arrow: Seek 10 seconds ahead
Shift + Left arrow: Seek 30 seconds behind
Shift + Right arrow: Seek 30 seconds ahead
This is very confusing to be honest. I would suggest normalizing the values between both would be the optimal solution, whatever version. Personally, I'd prefer to stick to those that we are already used to.
The text was updated successfully, but these errors were encountered:
I will make sure to discuss it with the rest of the team if this was intended or we should change at least the shortcuts to match the combinations on Desktop (i.e. w/ shift - finer grain seeking)
Hello, you can check out this PR in core and soon the changes should be also applied in stremio-web as not it uses a hardcoded ratio for seeking with the Shift key - Stremio/stremio-core#546
Because most player use a seeking time of 10 seconds we are keeping this value as the default and instead providing a finer seeking time of 3 seconds. You will be able to update your setting in stremio-web and make it consistent with stremio Desktop if you want.
In Stremio, shortcuts for moving ahead/behind are (and have been for years afaik) the following [1]:
However, in Stremio Web, these shortcuts have changed values:
This is very confusing to be honest. I would suggest normalizing the values between both would be the optimal solution, whatever version. Personally, I'd prefer to stick to those that we are already used to.
The text was updated successfully, but these errors were encountered: