-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The timelineregionenter event is not being fired in certain scenarios #6711
Labels
priority: P1
Big impact or workaround impractical; resolve before feature release
status: archived
Archived and locked; will not be updated
type: bug
Something isn't working correctly
Milestone
Comments
littlespex
added a commit
to cbsinteractive/shaka-player
that referenced
this issue
May 30, 2024
…egionenter events are fired see: shaka-project#6711
avelad
added
the
priority: P1
Big impact or workaround impractical; resolve before feature release
label
May 31, 2024
avelad
pushed a commit
that referenced
this issue
May 31, 2024
joeyparrish
pushed a commit
that referenced
this issue
May 31, 2024
joeyparrish
pushed a commit
that referenced
this issue
May 31, 2024
joeyparrish
pushed a commit
that referenced
this issue
May 31, 2024
joeyparrish
pushed a commit
that referenced
this issue
May 31, 2024
tykus160
pushed a commit
to sky-hugolima/shaka-player-contrib
that referenced
this issue
Jun 3, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
priority: P1
Big impact or workaround impractical; resolve before feature release
status: archived
Archived and locked; will not be updated
type: bug
Something isn't working correctly
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from
main
?Yes
Are you using the demo app or your own custom app?
Both
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
Also occurs in all embedded devices we've tests
What are the manifest and license server URIs?
Needs a DASH manifest with an
<EventStream />
element containing an<Event />
element that has apresentationTime
attribute with a value less than 1 second (event.presentationTime / eventStream.timeScale
). We are using a sample DAI asset which can be retrieved using the following (this call must be made manually using the DAI API, the DAI SDK does not return manifests withEventStream
):Using this code, a manifest is returned with the following event stream:
What configuration are you using? What is the output of
player.getConfiguration()
?Default configuration. The setup code we are using is:
What did you do?
timelineregionenter
event before loading the manifest.What did you expect to happen?
A
timelineregionenter
event is dispatched for every<Event />
element in the manifest.What actually happened?
The first
timelineregionenter
event does not fire.Are you planning send a PR to fix it?
Maybe. We aren't sure of the best path forward. Using
git bisect
we tracked the issue to commit4425dca2836d4820e7d1b7315d52b67b465cc8ec
. Before this commit, the call tocreatePlayheadObserversForMSE_
inplayer.js
was passedNaN
for thestartTimeOfLoad
argument. After this commit, the argument comes through asDate.now() / 1000
. This results in theRegionObserver
missing the first event. The trouble we are having is that this change seems to make the following line of code irrelevant, becausestartTimeOfLoad
is now always greater than0
:shaka-player/lib/player.js
Line 3254 in 30ac8c0
We don't have a comprehensive understanding of
startTimeOfLoad
and why it's being used in VOD scenarios. Is it safe to simply alter this line to only check forthis.isLive()
? Perhaps use thestartTime
value passed toload()
instead ofstartTimeOfLoad
?The text was updated successfully, but these errors were encountered: