Why is "accept-ranges" set to none on playback server?

[yelodevopsi]

Question

See that we have problems "seeking" when using the playback URL to the mp4-files.
Is there a reason for not using "Accept-Ranges"? @aler9
Anything with the segments etc?

Else I'll try to implement support for this, maybe on a new playback URL.

I'm looking at the on_get.gofile line:27

mediamtx/internal/playback/on_get.go

Line 27 in 7191c85

w.ctx.Header("Accept-Ranges", "none")

[aler9]

Hello @yelodevopsi, the reason is that playback streams are dynamically generated during each request, therefore it's impossible to seek something that does not exist yet. A caching system might be useful but it's not trivial to implement since it has to take into account the fact that recording segments might get added, deleted or even changed (in case of segments that are not finalized yet).

[cooperbrown9]

I had this same question today, thank you for your answer