'trackschanged' event not fired correctly for multi-Period content #680
Labels
status: archived
Archived and locked; will not be updated
type: bug
Something isn't working correctly
Milestone
The
trackschanged
event from the Player doesn't fire at the correct time WRTplayer.getTracks()
. Currently, it fires when StreamingEngine handles a Period transition and starts buffering content from that Period. However,player.getTracks
will return tracks based on the current playhead position. This means that when the event fires, the tracks returned haven't actually changed and will change once the playhead moves. This also means that if you seek backwards into a different buffered Period, the event will not fire.Another side effect of this is that while the playhead is in the old Period and StreamingEngine is buffering from the new Period, the
tracks.active
field is not correct. Theactive
field is determined from the current streams in StreamingEngine; this means that while the playhead is in a different Period, there will be noactive
tracks. The demo app currently throws errors because of this.The text was updated successfully, but these errors were encountered: