Open
Bug 1341228
Opened 8 years ago
Updated 2 years ago
[mse][youtube] unable to pass test case 92(AppendMultipleInitOpusAudio)
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
platform-rel | --- | ? |
People
(Reporter: vchang, Unassigned, NeedInfo)
Details
(Whiteboard: [platform-rel-youtube])
Attachments
(1 file)
116.75 KB,
image/png
|
Details |
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×tamp=1487670424161
Reporter | ||
Updated•8 years ago
|
Severity: normal → major
OS: Unspecified → Mac OS X
Priority: -- → P1
Version: unspecified → Trunk
Comment 1•8 years ago
|
||
Please, don't change priority, this is up to the triage team.
Severity: major → normal
Priority: P1 → P3
Updated•8 years ago
|
Assignee: nobody → jyavenard
Comment 2•8 years ago
|
||
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...
Updated•8 years ago
|
Component: Audio/Video → Audio/Video: Playback
Updated•7 years ago
|
platform-rel: --- → ?
Whiteboard: [platform-rel-youtube]
Updated•4 years ago
|
Assignee: jya-moz → nobody
Comment 3•4 years ago
|
||
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.
Flags: needinfo?(kinetik)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•