Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(164)

Issue 2464153002: Fixed track id remapping in MSE FrameProcessor (Closed)

Created:
4 years, 1 month ago by servolk
Modified:
4 years, 1 month ago
Reviewers:
CC:
chromium-reviews
Target Ref:
refs/pending/branch-heads/2883
Project:
chromium
Visibility:
Public.

Description

Fixed track id remapping in MSE FrameProcessor Previously FrameProcessor couldn't handle cases where audio and video track ids were swapped between the previous and current init segment, because we tried to do an in-place update, which is impossible to do correctly when track ids have been swapped. Consider the case where in the first init segment A=1,V=2 and in the second segment A=2,V=1. In such case we can't simply move let's say track A from 1 to 2, because track id 2 is occupied by V, and vice versa. This CL implements a more advanced logic, that will record how track ids have changed between segments and will then update all track buffer mappings in FrameProcessor::UpdateTrackIds at once. BUG=660247 Review-Url: https://codereview.chromium.org/2460763002 Cr-Commit-Position: refs/heads/master@{#428473} (cherry picked from commit b9233a906062fd461503fca84fa2223ee315bfaf) Committed: https://chromium.googlesource.com/chromium/src/+/0882ff112ce36167940baf57484de9e0c03d46d9

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+67 lines, -27 lines) Patch
M media/filters/frame_processor.h View 2 chunks +12 lines, -8 lines 0 comments Download
M media/filters/frame_processor.cc View 1 chunk +22 lines, -9 lines 0 comments Download
M media/filters/source_buffer_state.cc View 5 chunks +11 lines, -10 lines 0 comments Download
M media/filters/source_buffer_state_unittest.cc View 1 chunk +22 lines, -0 lines 0 comments Download

Messages

Total messages: 2 (1 generated)
servolk
4 years, 1 month ago (2016-11-01 18:12:33 UTC) #2
Message was sent while issue was closed.
Committed patchset #1 (id:1) manually as
0882ff112ce36167940baf57484de9e0c03d46d9.

Powered by Google App Engine
This is Rietveld 408576698