2 Replies Latest reply on Apr 12, 2012 5:32 AM by Silviu Vergoti

    OSMF 1.6: TimelineMetadataEvent.MARKER_TIME_REACHED not always fired for a certain cue point

    MicMic1234 Level 1

      Hi all,

      I'm working with TimelineMetadata markers for a while now and it always worked great for me.

       

      In the last few days I'm trying to figure how come a specific marker sometimes not trigering the Marker_Time_Reached event.

      What I found out is that sometimes the condition in checkTemporalMetadata function won't work:

      if ((temporalValueCollection[index].time >= (now - TOLERANCE)) && (temporalValueCollection[index].time <= (now + TOLERANCE))....

      My marker intime is at 227.185 and sometimes the TOLERANCE value is just not enough.

       

      I added traces right before this condition is checked. Here are the logs:

      Marker_Time_Reached sent:

      checkTemporalMetadata: currentTime: 226.6750999999997 marker time: 227.185

      checkTemporalMetadata: currentTime: 226.8100999999997 marker time: 227.185

      checkTemporalMetadata: currentTime: 227.3790999999997 marker time: 227.185

       

      Marker_Time_Reached not sent:

      checkTemporalMetadata: currentTime: 226.71479999999968 marker time: 227.185

      checkTemporalMetadata: currentTime: 226.8297999999997 marker time: 227.185

      checkTemporalMetadata: currentTime: 227.4357999999997 marker time: 227.185


      I know I can enlarge TOLERANCE value to a bit more than 0.25 and it will solve the issue, but how can I be sure it will be enough?

      Can you tell me what is special about this marker time that will cause it to be left out occasionally? Should I follow any recommendations before adding a timeline marker?

       

      Thanks,

      Michal