Open jamesburrow23 opened 1 year ago
The parsing of remote files and the parsing of local files have lot of code in common but not yet the part which is able to parse multiple files, so parsing stops after the parsing of the first .ts
file.
Definitely a big issue as the reported duration is wrong but it is also long to fix so we won't fix that in priority with free support (our sponsors either use HLS on local storage or referenced files with only 1 file per track), contact us if you wish to accelerate the fix of this issue.
Context
Version of MediaInfo: v23.09 (CLI) Command:
mediainfo https://sr-video-output.s3.amazonaws.com/media-info-test/hls/index.m3u8
Expected Duration:35s
Returned Duration:20s
Issue
Hello! I'm attempting to use MediaInfo to determine the duration of an HLS video that is hosted in AWS. It seems that mediainfo is using the first
.ts
file as the source of the duration and is not accurately evaluating the other chunks to return the correct duration.What's especially strange about this is when I download the files from S3 and run the same command but against the local index.m3u8 it does return the correct duration.
Am I missing some kind of flag or option that is causing mediainfo to behave differently for a remote index.m3u8 path?
I've attached the 480p version of the files as well as the url to the remote m3u8 for reference, any help is much appreciated!
testFiles.zip
https://sr-video-output.s3.amazonaws.com/media-info-test/hls/index.m3u8