SCTE35 CUE_OUT CUE_IN

[Evgeny0420]

why the cue_out and cue_in tags don't come from the fragment? i'm using hls.js for playing m3u8 stream. I will make midroll logic, but i don't get this tags: SCTE35 CUE_OUT CUE_IN from manifest mono.m3u8. if i use videojs, then it works there, but i don't want use videojs

[robwalch]

Please provide an example of the Playlist so that we know what exactly what form of tag you are using.

DATERANGE tags are not directly associated with a fragment. Each DateRange describes a range of time on the playback program relative to the Program Date Time found in a Playlist. You can find all parsed, logical DateRanges in each levels' details (LevelDetails), as well as in cues on the HTMLMediaElement's metadata TextTrack. The start and end time of a DateRange are not bound to any EXTINF start and duration.

If what you are looking for is the Playlist content published above a segment, most raw tags (non-standard tags, comments starting with #, and some standard tags including PROGRAM-DATE-TIME and EXT-X-DATERANGE) listed above an EXTINF can be found on fragment.tagList.

https://hls-js-dev.netlify.app/api-docs/hls.js.level
https://hls-js-dev.netlify.app/api-docs/hls.js.leveldetails
https://hls-js-dev.netlify.app/api-docs/hls.js.fragment

[Evgeny0420]

Here I use video.js, at a certain moment such tags with links begin to come:
https://prnt.sc/rLxSpSw7h651,
but if I use hls.js it always comes like this,
https://prnt.sc/2eJQyXM2gjzG

and the tags that I selected on the last photo do not come, also in the video.js segment, the cue_in and cue_out element comes, in the hls.js fragment no such

[robwalch]

That is an issue between the page running the player and the server serving the HLS content. HLS.js is not responsible for what it is served.