Closed jxu closed 2 years ago
https://github.com/yt-dlp/yt-dlp/issues/2001 might be related
I can reproduce this too, even on git master. I'll see if I can find a public video
That seems to be a bit different issue than #2001, as it happens on initialization fragment. (2001 is at media fragments without initialization ones)
Here's first 10 lines of segment playlist in question:
#EXTM3U
#EXT-X-VERSION:7
#EXT-X-TARGETDURATION:10
#EXT-X-MEDIA-SEQUENCE:0
#EXT-X-PLAYLIST-TYPE:VOD
#EXT-X-INDEPENDENT-SEGMENTS
#EXT-X-MAP:URI="fragmented.mp4",BYTERANGE="1300@0"
#EXTINF:9.000111,
#EXT-X-BYTERANGE:516680@1300
fragmented.mp4
I noticed also GNOME Files / Nautilus reports the wrong duration in their Audio/Video properties tab (not sure where they get this metadata), reporting the duration of one fragment of just 9 seconds, and ffprobe reports double the bitrate (maybe calculated from the large fragment 1). For the video that was interrupted, ffprobe reports
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x560d108ca9c0] Found duplicated MOOV Atom. Skipped it
e4fa34a13e9f94f27f0fccae6bcadc8dd1ea1415 ?
remainder: was it fixed?
Did some testing, seems like it is fixed. Doesn't get stuck on fragment 1 anymore and seems to detect the correct size of it.
Checklist
Region
US
Description
This is a bug report on the abnormal behavior I observed in the comments of the original site request #1946 @coletdjnz
When downloading, fragment 1 is huge. For example, of a 1.9 GB video, I recorded fragment 1 as 633 MB.
The reason I suspect it is a bug is because if I interrupt downloading at say fragment 300 and then resume, yt-dlp will start writing to video.mp4.part-Frag1.part which again swells to a massive size instead of the leftover fragment videomp4.part-Frag300.part. This causes the final video to be much larger than needed.
Also attached is m3u8 files I saw used in firefox network dev tools, renamed for clarity.
m3u8s.zip
Verbose log