Flowplayer - Post-roll not firing tracking events correctly

[paul]

Look at this example (RC2 QA)

ad-formats/http/example05.html

Pre-roll tracking fires
Mid-roll tracking fires
Post-roll tracking only fires start, nothing else

[paul]

Bug does not occur for OVA for JW4 or JW5 - seems to just be OVA for Flowplayer.

[paul]

Doesn't occur for post-roll only. Seems to occur as the result of a pre, post combination...

[paul]

Ok, found the reason why this is happening.

When the post-roll is first obtained, the tracking table is setup for a duration of 29 seconds:

14:25:08 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 500 milliseconds with event label BA (child:false)
14:25:08 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 7300 milliseconds with event label 1Q (child:false)
14:25:08 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 14500 milliseconds with event label HW (child:false)
14:25:08 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 21800 milliseconds with event label 3Q (child:false)
14:25:08 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 500 milliseconds with event label SN (child:false)
14:25:08 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 28500 milliseconds with event label HN (child:false)
14:25:08 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 28500 milliseconds with event label EA (child:false)

When the ad is fired up, the metadata duration resets the tracking table based on 30 seconds:

14:26:34 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 500 milliseconds with event label BA (child:false)
14:26:34 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 7500 milliseconds with event label 1Q (child:false)
14:26:34 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 15000 milliseconds with event label HW (child:false)
14:26:34 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 22500 milliseconds with event label 3Q (child:false)
14:26:34 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 500 milliseconds with event label SN (child:false)
14:26:34 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 29500 milliseconds with event label HN (child:false)
14:26:34 GMT+0000: Tracking point recorded in table (2:0, post-roll2) at 29500 milliseconds with event label EA (child:false)

But for some reason, when Flowplayer fires the timing events, it is still firing them based on the 29 second duration.

So an event comes in at 14500 milliseconds, but 15000 milliseconds is in the table. As a result, no match is found resulting in no tracking event firing.

The question is - why?

[paul]

Ok, found it.

This bug was introduced with the rewrite of the onMetaData duration reset code.

The following method was missed out when the duration is reset:

setupTrackingCuepoints(_player.currentClip, theScheduledStream.getTrackingTable(), getActiveStreamIndex());

Added back in. Problem fixed.