1341228 - [mse][youtube] unable to pass test case 92(AppendMultipleInitOpusAudio)

Status: NEW

(Core :: Audio/Video: Playback, defect, P3)

Description

[Vincent Chang[:vchang][changyihsin]]

STR,
1. Using the firefox nightly(trunk) built by myself.
2. Turn on media.mediasource.webm.enabled to true
3. click test case 92. 

It's failed in below line when calling SourceBuffer.buffered.end(0) API. 
var end = src.buffered.end(0);


[1]http://yt-dash-mse-test.commondatastorage.googleapis.com/unit-tests/2017.html?&test_type=conformance-test&timestamp=1487670424161

Comment 1

[Jean-Yves Avenard [:jya]]

Please, don't change priority, this is up to the triage team.

Comment 2

[Jean-Yves Avenard [:jya]]

https://w3c.github.io/media-source/webm-byte-stream-format.html#webm-media-segments

"The user agent MUST accept and ignore Cues or Chapters elements that follow a Cluster element."

But here the Cues are placed *prior* the cluster element.

https://w3c.github.io/media-source/webm-byte-stream-format.html#webm-init-segments
states:
"The user agent MUST accept and ignore any elements other than an EBML Header or a Cluster that occur before, in between, or after the Segment Information and Tracks elements."

so I guess we shouldn't error on cues.

The WebM container parser really, was only designed to accept what YouTube typically feeds...

Comment 3

[Alastor Wu [:alwu][PTO 8/28-9/6]]

Attachment: cues.png

I checked this bug today, but I still not did not really understand how to fix this. I did see the last element Id in the init segment is Cues, because we didn't handle that in WebMBufferedParser, so it seems being skipped and not affecting our parsing for the init segment. Then, the error happened in nestegg, see here, because the id is ID_Cues(0x1c53bb6b), not ID_EBML. But by looking closer to the ne_peek_element, it seems reading the last element, which I don't understand why. Because ID_EBML should be the first element, not the last.

Kinetik, would you mind to give me some suggestion for this issue? I would like to help on this issue.
Thank you so much.