New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 624993 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Create a test for MSE init segment algorithm with multiple SourceBuffers

Project Member Reported by servolk@chromium.org, Jul 1 2016

Issue description

Current tests for the MSE init segment algorithm all use a single source buffer where bytestream track ids match the demuxer-assigned unique track ids. But many apps (notably YouTube) use multiple source buffers (one source buffer for audio and one for video). In that case bytestream ids might not be unique, but the demuxer-assigned track ids must be still unique. We need to have this important use case covered in our tests.
 
Components: Internals>Media>Source
Project Member

Comment 2 by bugdroid1@chromium.org, Jul 8 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ac29e2565ea5d0bb7891297b6160ae26fd6f6a00

commit ac29e2565ea5d0bb7891297b6160ae26fd6f6a00
Author: servolk <servolk@chromium.org>
Date: Fri Jul 08 01:09:35 2016

MSE test for two SourceBuffers with clashing bytestream track ids

BUG= 624993 

Review-Url: https://codereview.chromium.org/2118943002
Cr-Commit-Position: refs/heads/master@{#404292}

[modify] https://crrev.com/ac29e2565ea5d0bb7891297b6160ae26fd6f6a00/third_party/WebKit/LayoutTests/http/tests/media/media-source/mediasource-initsegmentreceived-alg.html

Status: Fixed (was: Available)

Sign in to add a comment