Properly identify Random Access Point in streams

RESOLVED WONTFIX

Status

()

Product:
Core
Component:
Audio/Video: Playback
Type:
defect
Importance:
P2
normal
Status:
RESOLVED WONTFIX
Opened:
5 years ago
Updated:
4 years ago

People

(Reporter: jya, Unassigned)

Tracking

Version:
Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Bug is a sub-task of bug 1118126.

To properly implement the range removal algorithm we need to be able to identify where the random access points in a track buffer are located.

In fragmented mp4, those are:
Stream Access Point of type 1 or 2 as defined in Annex I of ISO/IEC 14496-12.
(ref http://www.w3.org/2013/12/byte-stream-format-registry/isobmff-byte-stream-format.html#iso-random-access-points)

In webm, this is the start of a Cluster (e.g last resync point).

WebM parser provides an API to retrieve those (GetOffsetForTime), mp4 MoofParser doesn't.

API needs to be added to ContainerParser.
See Also: → 1061007
Priority: -- → P2
Component: Audio/Video → Audio/Video: Playback
this is no longer required with the new MSE
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.