RE: [MSE] MPEG audio byte stream format spec.

Aaron:

We’ve reviewed this document at Microsoft and think it’s very useful.  Thanks.

We do have one topic to discuss:  On other formats, timestampOffset is not modified internally when the sourceBuffer is set to “segments” append mode.   It seems that timestampOffset shouldn’t get updated for one format and not for others.  The website using MSE is not likely to care as much about which format is being used, but does need to care about timestampOffset as it is part of the API.

We suggest that sourceBuffer be restricted to operate in “sequence” append mode only for these byte stream formats.   Sequence append mode already handles updating the timestampOffset (although there may need to be some edits to state that the coded frame duration should be used rather than the presentation timestamp if the byte stream format does not carry timestamp information).

Regards,

Jerry

From: Aaron Colwell [mailto:acolwell@google.com]
Sent: Monday, March 31, 2014 2:36 PM
To: <public-html-media@w3.org>
Subject: [MSE] MPEG audio byte stream format spec.

I just wanted to let people know that I just posted a draft of the MPEG audio byte stream format spec<https://dvcs.w3.org/hg/html-media/raw-file/default/media-source/mpeg-audio-byte-stream-format.html> that Chrome has been experimenting with for a while. It allows MP3 & ADTS streams to be used with MSE.

Assuming that there are no major objections, I'd like to add it to the byte stream format registry<https://dvcs.w3.org/hg/html-media/raw-file/default/media-source/byte-stream-format-registry.html> in the next week or two.

Aaron