Custom metadata in HDS stream bound for OSMF

Question

Can someone tell me which "BOX" (atom) type in a HDS stream I could use to embed custom timeline metadata?  I have access to, and can modify, the raw HDS stream.   MDAT, MOOF,etc....? The stream will be played back in OSMF, and presumably I can modify BoxParser and HHTPStreamingF4FFileHandler to parse the appropriate box.  Presumably this is how CuePoints and such are tunneled from AMS/FMS.
Thanks.
-- Brad

Answer 1

Another point to note is that once I start publishing to the
recording app, I get the metadata of the stream with
objMetadata = Stream.getOnMetaData("streamname");
and trace the properties of the objMetadata object every 1/2
second (this is purely for debugging purposes while I work out what
the hell is going on). But for around the first 30 seconds, nothing
is output! Then all of a sudden, the output starts tracing to
screen. IF my customduration metadata is there, it has its initial
value as indicated in my post above (for example 7), and never
increments. But more interestingly, the duration metadata that FMS
automatically inserts might say 39.076 once the traces start coming
through! So I would at least think that my customduration would be
around 39 give or take. Also the FMS duration says 39.076, but then
it stays at the same value for a while, even though it's being
traced every 1/2 a second, then it might say 71.200, then stays the
same for about 30 seconds, then 104.863 and so on.
This makes sense if this is only being updated in memory
every 30 seconds or so (the docs state that the 'data keyframe is a
special data message that can be added to a live stream and stored
in the memory of the server'), but then it also means that when
reading it, we will never know if this is actually correct! I mean
if I connect and get the metadata and the duration says 71, I'm
going to assume that I connected to the live stream 71 seconds in,
but it could have been saying 71 for the past 20 seconds, and I'm
really 91 seconds into the live stream!
K.