Regarding the problem of http 206 Content-Range error when the recorded file (fmp4) is played in the browser

[klk2]

Question

Using the record attribute to record fmp4 file, there seems to be a file size problem, which causes the wrong file size to be obtained when playing it in the browser. When playing it using the http Content-Range breakpoint, the entire file is obtained at once.

I use gin StaticFS and Static to play mp4 files

This problem does not exist when using the browser to play the new MP4 file after conversion through ffmpeg.
It seems that the problem points to the mp4 itself and the recording

[0ip]

Can you ffprobe your affected recordings and see if the duration is correctly set for them?

[aler9]

Hello, as @0ip already suggested, this may have been caused by #2477, that was fixed by #2715. Please try again with the latest server version and let me know if recordings generated with it cause the same browser error.

[fbotp]

Today, this question still exists.😟

[aler9]

@fbotp false. Use the embedded playback server to serve recording segments (do not serve them with a plain HTTP server) and append the format=mp4 parameter as written in the README:
https://github.com/bluenviron/mediamtx?tab=readme-ov-file#playback-recorded-streams