- Newest
- Most votes
- Most comments
AWS Elemental MediaPackage will process SCTE35 markers from the input HLS playlists to provide the markers on HLS and DASH output endpoints. Please see this link to review how MediaPackage processes SCTE35 markers. https://docs.aws.amazon.com/mediapackage/latest/ug/scte.html
If some of the SCTE35 messages are being passed through and others do not, it may be helpful to determine which messages are having a problem. Perhaps there is a format inconsistency or some other variation that causes the message not to be recognized. Given that some messages are working properly, it indicates likely differences btwn the good and failing messages.
If a test can be created with different SCTE35 messages sent every 60 sec, for 30 sec ad break, that may help isolate the problem. Also you may consider testing with another encoder for comparison of MediaPackage outputs.
You seem to have a similar issue to us, splice insert signaling seems to be the keyword here.
https://docs.aws.amazon.com/medialive/latest/ug/getting-ready-set-the-ad-avail-mode.html
Reading the above you can see that if your signaling uses splice insert without any service descriptors it won't be treated as an ad avail. It could be that one of your signaling is picked up, either from the TS or from the playlist. In addition I did read somehere but can't seem to find it anymore that you're not supposed to mix between signaling on the input and just stick to one type.
You can interrogate the payload for your particular scte markers using this scte parser:
https://www.middleman.tv/scte35-parser
Good luck, hope this helps a bit :)
Relevant content
- asked 2 years ago
- asked 4 years ago
- asked a day ago
- asked 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 10 months ago