Seeking in Chrome #1

New Issue

iou1name · 2018-09-14T10:55:34-04:00

iou1name commented

2018-09-14 10:55:34 -04:00

Chrome only allows seeking in HTML5 video/audio elements if the server serving the file responds to partial content requests correctly, even if the file is small enough to be retrieved in one go. The same applies to looping.
https://stackoverflow.com/questions/8088364/html5-video-will-not-loop

Possible way to fix would be translating the start and end positions of the Range header into arguments for the subprocess command. I don't think ffmpeg allows you to specify byte ranges directly though, so some magic might need to be worked with dd.

Alternatively, we could just play with the headers to trick Chrome into thinking we responded to the partial request properly when we didn't.

Chrome only allows seeking in HTML5 video/audio elements if the server serving the file responds to partial content requests correctly, even if the file is small enough to be retrieved in one go. The same applies to looping. <https://stackoverflow.com/questions/8088364/html5-video-will-not-loop> Possible way to fix would be translating the start and end positions of the `Range` header into arguments for the `subprocess` command. I don't think `ffmpeg` allows you to specify byte ranges directly though, so some magic might need to be worked with `dd`. Alternatively, we could just play with the headers to trick Chrome into thinking we responded to the partial request properly when we didn't.

iou1name added the

bug

label 2018-09-14 10:55:34 -04:00

Sign in to join this conversation.