Does anyone have any other ideas on this? Maybe it is down to multiple restarts on the same stream? which affects time?
Also, this topic seems to be awaiting moderation? Curious as unable to see all replies when logged out. How long does it take to verify?
I don’t know what’s going on with this post, but it looks like it got caught in an super admin level moderation queue, sorry about that. We do moderate a number of posts due to spam, but this is not the normal experience.
On that note, I’ve asked our support team if they have any ideas on this one beyond Karel’s comment.
Engineering team wants to know if you are using this article to produce that tag. You can create the tag or they can be added with CMAF workflows, but the can’t really answer the question until they know how you are creating those tags.
With CMAF workflows, the program date time matches the time when we create the segment, so again, they are pointing to your system clock being incorrect (which you have mentioned many times is in fact correct!). If you are creating the tags, a code snippet would help further debug.
To answer your question about the impact of the value being off, it could be an issue with playback capabilities like seeking for low latency workflows and determining how close to the “live-edge” you are.