3 ms·
That's odd. I can't recall ever having a problem with browsers playing mp4s in a vanilla <video> tag, as long as I encode them in the main h264 profile, AAC aud
by anderspitman 6y ago
That's odd. I can't recall ever having a problem with browsers playing mp4s in a vanilla <video> tag, as long as I encode them in the main h264 profile, AAC audio, and MOOV atom at the front (see [0] for ffmpeg command). Obviously the server has to support Range: byte requests.
My impression is DASH/HLS are mostly useful for adjusting bitrate on the fly.
[0]: https://superuser.com/a/438471/402047 https://superuser.com/a/438471/402047
- sp332 6y agoWhen the parent talks about jumping to random byte offsets, they mean you don't have the first part of the file at all. You just have an arbitrary 512-MB chunk out of the middle.
- Dylan16807 6y agoBut they were claiming that a single monolithic file would break too, which is not the case. The browser does a range request to get the first part, then a range request to get the part you're playing, and it works.
- derefr 6y agoRight. Like tuning into a digital-cable signal "in the middle"†. You just get bytes of the stream starting from an arbitrary offset, without having seen/processed anything before that (and without even being able to request anything before that), and you need to resynchronize from what you've got. † I mean, a digital-cable video stream is always "in the middle" unless you're just starting a VOD stream, but still.