Ticket #407 (closed defect: fixed)
HTTP Streaming generating extra onMetaData events
|Reported by:||paul||Owned by:||paul|
|Priority:||blocker||Milestone:||OVA for JW5 (v1.0.1)|
|Component:||OVA for JW Player 5||Version:||OVA for JW Player 5 (trunk)|
Sometimes, when skipping on the timeline with HTTP streamed show clips, extra onMetaData events seem to be generated and received by OVA where the time is less than the point at which the click occurred in the timeline.
This causes the player to halt playback.
Reported by Ben. See test case:
OVA doesn't set the duration on the show clip unless no duration is specified in the first place. The problem is that it sets the new duration correctly the first time, then on the second (rubbish) event resets the duration as per this log entry:
14:49:39 GMT+0100 Debuggable: Duration metadata received for active clip - metadata duration is 801.0419954648526
14:49:39 GMT+0100 Debuggable: Show stream duration requires adjustment - original duration: 0, metadata duration: 801.0419954648526 rounded: 801
14:49:39 GMT+0100 Debuggable: Active playlist clip duration updated to 801.0419954648526
14:49:43 GMT+0100 Debuggable: Duration metadata received for active clip - metadata duration is 310.9616326530612
14:49:43 GMT+0100 Debuggable: Show stream duration requires adjustment - original duration: 0, metadata duration: 310.9616326530612 rounded: 310
14:49:44 GMT+0100 Debuggable: Active playlist clip duration updated to 310.9616326530612
The first line is when the show stream starts - it receives metadata from your stream indicating that the stream is 801 seconds long and sets the duration accordingly.
When the user skips on the controls, OVA receives another metadata event from the stream changing the duration of the stream to 310 seconds (in this particular case) - in this case, where I clicked on the control bar is further along than 310 seconds so the player thinks the stream has ended and tells OVA that it has ended. Hence why it seems to end abruptly.