Wait with buffering when seeking

[brothom 177]

I couldn't find a request that matched this so here goes.

Currently, on any platform, when the user is seeking albeit via cursor click, remote control (tv) or double tap, the video player IMMEDIATELY seeks to the position. This causes the following behaviour:

1. Start video
2. Want to seek to 02:12
3. Seek forward
4. Wait for buffer, wait for playback
5. Seek forward
6. Wait for buffer, wait for playback
7. Seek forward
8. Wait for buffer, wait for playback
9. ... etc
10. Until reaching the desired timestamp

This doesn't seem to happen with the browser player and using touch controls / dragging.

1. Start video
2. Hold / drag the seeker to the designated time
3. Let go
4. Video is now buffering at desired timestamp

This DOES happen when using the "-10/+10" keys.

1. Start video
2. + 10
3. Wait for buffer, wait for playback
4. + 10
5. Wait for buffer, wait for playback
6. ... very annoying, especially when wanting to skip intros or just go to a certain timestamp

In my opionion it would be a significant QoL addition to wait (maybe a second or so) before requesting the buffered data from the server.
This way the interaction, especially on tv's becomes much more fluent:

1. Start video
2. Want to seek to 02:12
3. Seek, seek, seek, seek, seek, seek until reaching the desired timestamp
4. Stop seeking
5. Wait for a second or so
6. Buffer starts and so does playback

 

[ebr 16169]

Hi.  Exactly where are you having an issue with this?  I can jump multiple steps without any real lag.

[brothom 177]

7 minutes ago, ebr said:

Hi.  Exactly where are you having an issue with this?  I can jump multiple steps without any real lag.

Your source file probably requires little to no transcoding or the device you're using is rather "fast". When either the connection or the device isn't fast enough, you'll have to wait until that request is fulfilled. When that "10 second jump" is being fulfilled by the server, the entire device is unusable because it can't skip or seek.

An "easy" test is basically running any 4K video on a Samsung TV ór watch any content requiring heavy transcoding to make the issue more obvious.

When transcoding, click the +10 a couple of times and it will only seek once, regardless of how many times you clicked because the player is waiting for the server's request.

[Luke 42077]

OK we'll try to improve this. Thanks.