cosmin
commented
5 months ago From looking at the linked hls.js issue it seems that the problem is the underlying video decoder is failing to decode one of the segments. I'd recommend saving the input directly as a file and trying to play that directly with ffmpeg (since it was the selected video decoder) to see if it decodes successfully. If the input file can be decoded but the output of packager cannot be decoded then it might be a packager bug, and if so please reopen the issue and attach the input file.
System info
Operating System: Ubuntu 22.04 Shaka Packager Version: v2.6.1
Issue and steps to reproduce the problem
Packager Command: packager 'in=udp://127.0.0.1:{sink_port},stream_selector=0,init_segment={folder_path}/video_init.mp4,segment_template={folderpath}/video$Time$.m4s' --hls_playlist_type EVENT --hls_master_playlist_output {manifest_path} --fragment_duration 5 --strip_parameter_set_nalus=false"
Extra steps to reproduce the problem? (1) After the manifest been published, I've tried to play with many hls players (2) During passed some time, the player stops reproduce the segments and an error is through in the console (3) I've tested also with hls.js demo pages (https://hlsjs.video-dev.org/demo/ and https://hlsjs-dev.video-dev.org/demo/) and both of them has the same error:
What is the expected result? Play all the segments without any problem
What happens instead? The player stops the playback between the same segments (at 2'02")
Files examples:
Manifest (master.m3u8):
main.m3u8
<Please attach the input files or email to shaka-packager-issues@google.com.>
Additional information:
I had tried different players Shaka Player, Hls.js, Veeplay and react-hls and none of them pass though the problematic time (2'01"), but using the VLC app the content is reproduced from the beginning to the end without any problem or errors. For more details here is the hls.js issue.