Some EMSG events missing from version 4.11.3

[sobbe81]

Have you read the FAQ and checked for duplicate open issues?

If the problem is related to FairPlay, have you read the tutorial?

What version of Shaka Player are you using?

Can reproduce issue with versions 4.11.3 to 4.12.4
Can not reproduce issue with 4.11.2

Can you reproduce the issue with our latest release version?
Yes

Can you reproduce the issue with the latest code from main?

Are you using the demo app or your own custom app?
Custom app

If custom app, can you reproduce the issue using our demo app?
Tried to add listener for emsg event but was not able to do that.

What browser and OS are you using?
Chrome, Mac OS 14.7.1

For embedded devices (smart TVs, etc.), what model and firmware version are you using?

What are the manifest and license server URIs?

Will send this separately

What configuration are you using? What is the output of player.getNonDefaultConfiguration()?

abr
: 
advanced
: 
{minTotalBytes: 8000000}
defaultBandwidthEstimate
: 
10000000
[[Prototype]]
: 
Object
cmcd
: 
{enabled: true, sessionId: '5edd65db-650b-40c3-a3c1-58b9c3637197'}
drm
: 
{servers: {…}}
manifest
: 
{dash: {…}}
preferredAudioLanguage
: 
"sv"
streaming
: 
{bufferingGoal: 30}

What did you do?

Play linear stream over and ad break

What did you expect to happen?
Shaka Player to emit emsg events.

What actually happened?

emsg events are emitted but a lot of events missing

Are you planning send a PR to fix it?

[avelad]

I have tested your content for half an hour since it is live content and I have not seen that it has EMSG at any time

[shaka-bot]

Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including @shaka-bot reopen in a comment.

[sobbe81]

Hi,

Unfortunately, you have to wait for an ad break in the linear stream and the ad break needs to be replaced with personalised ads. I will share a new url via email that is at least more likely to have have ads replaced.

We have been testing this using https://shaka-player-demo.appspot.com/demo and registered a listener for emsg events.

(new shaka.util.EventManager()).listen(shakaDemoMain.player_, 'emsg', (event) => {
    console.log('shaka emsg', ID3Parser.ParseArray(event.detail.messageData));
})

The ID3Parser.ParseArray() will interpret the data and print it. We have also done the same in our service using old shaka version.

Here are two screenshots that show the difference:

If you look at YSEQ it will for example go from 1:4, 2:4, 3:4, 4:4 for the old shaka version but the new one will only show 1:4.

@shaka-bot reopen

[avelad]

@sobbe81 Can you review if #7839 solves your issue? Thanks!

[sobbe81]

Hi,

It does not fix the issue.

I figured out that it was possible to run the test-page with older versions of shaka player. Ran these

https://v4-11-2-dot-shaka-player-demo.appspot.com/
https://v4-11-3-dot-shaka-player-demo.appspot.com/

with the same url and 4.11.2 works as expected but 4.11.3 does not. I noticed that the 4.11.3 version buffers and then continues playback at another position. With 4.11.3 I see a lot of these in the logs

´Jumping forward 13.52268099784851 seconds because of gap starting at 1736275468.464999 and ending at 1736275481.945´

Each advert is a separate period and I'm guessing that the jump is to the next period and the gap in EMSG-data is a (correct) consequence of the jump rather than the actual EMSG-handling. Also, looking at the change log between 4.11.2 and 4.11.3 there are some changes to multi-period handling which makes more sense to have cause this regression compared to error in emsg-handling that seems untouched for a long time.

If you test this using the url I provided and do not get any EMSG at all you can try to restart the stream to get ads replaced and EMSG data.

@shaka-bot reopen

[sobbe81]

Hi,

Were you able to reproduce this? @avelad

[avelad]

No, sorry !

[sobbe81]

I just tested a multi-period stream from DASH-IF player and with that it's really easy to reproduce the jumping issue when there is a new period.

This url

https://d24rwxnt7vw9qb.cloudfront.net/v1/dash/e6d234965645b411ad572802b6c9d5a10799c9c1/All_Reference_Streams/ee565ea510cb4b4d8df5f48918c3d6dc/index.mpd

Works without any issues in 4.11.2 but with 4.11.3 I get a lot of "Jumping forward ...." and playback jumps.

@avelad

[avelad]

Yes I can reproduce the "gap" issue in the main branch