This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28234 - [MSE] "highest presentation timestamp" is ambiguous/misleading
Summary: [MSE] "highest presentation timestamp" is ambiguous/misleading
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: CR
Assignee: Matt Wolenetz
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-19 00:17 UTC by Chris Cunningham
Modified: 2015-04-09 18:53 UTC (History)
3 users (show)

See Also:

Attachments

Description Chris Cunningham 2015-03-19 00:17:22 UTC 
"set highest presentation timestamp for track buffer to frame end timestamp."

To me, the name "highest presentation timestamp" implies a definition as the presentation timestamp set on the frame which is furthest into the timeline for the coded frame group. You see in the quote above that it actually the presentation timestamp + the duration for that frame... 

I think this would be more easily understood if we called it "highest frame end timestamp".
Comment 1 Aaron Colwell 2015-03-19 16:28:20 UTC 
How about the following changes?

1. Change "highest presentation timestamp" to "highest end timestamp"
2. Change the definition of the variable to say "stores the highest coded frame end timestamp across all coded frames in the current coded frame group that were appended to this track buffer."

This makes the definition more consistent with the "group end timestamp" name and definition.
Comment 2 Chris Cunningham 2015-03-19 17:30:13 UTC 
Aaron, that sounds great to me.
Comment 3 Matt Wolenetz 2015-04-07 19:54:17 UTC 
Pull request for the fix recommended in Comment 1 is pending at https://github.com/w3c/media-source/pull/4