Closed Bug 1050083 Opened 10 years ago Closed 10 years ago

Changes to WebM buffered range handling.

Categories

(Core :: Audio/Video, defect)

Product:
Core
Component:
Audio/Video
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla34

People

(Reporter: kinetik, Assigned: kinetik)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 1 obsolete file)

Changes to WebM buffered range handling. v2
7.59 KB, patch
kinetik
: review+
Details | Diff | Splinter Review 
Include the frame duration in the range end.  Also handle (ignore) invalid
negative timestamps when parsing.  Include cluster offset in time/data
offset record.  Cluster offset will be used when calculating discard/resync
points in MSE.
Include the frame duration in the range end.  Also handle (ignore) invalid
negative timestamps when parsing.  Include cluster offset in time/data
offset record.  Cluster offset will be used when calculating discard/resync
points in MSE.
Attachment #8469044 - Flags: review?(cajbir.bugzilla)
Assignee: nobody → kinetik
Depends on: MSE
Attachment #8469044 - Flags: review?(cajbir.bugzilla) → review+
Include the frame duration in the range end.  Also handle (ignore) invalid
negative timestamps when parsing.  Include cluster offset in time/data
offset record.  Cluster offset will be used when calculating discard/resync
points in MSE.

Revert the changes to CalculateBufferedForRange and just add the frame
duration to aEnd.  Carrying forward r+
Attachment #8469044 - Attachment is obsolete: true
Attachment #8469867 - Flags: review+
https://hg.mozilla.org/mozilla-central/rev/1588a78a2feb
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
Blocks: MSE
No longer depends on: MSE
Blocks: 1031026
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: