appendBuffer() with overlapping audio segments not per spec.

Confirmed Issue #7979810 • Assigned to Rafael V.

Details

Author
Timothy D.
Created
Jun 23, 2016
Privacy
This issue is public.
Reports
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

The MSE spec requires user agents to support overlapping audio segments in one of two ways:

  1. remove the overlapping samples, and insert silence in their place; or
  2. cross fade the overlapping samples.

(See https://w3c.github.io/media-source/#sourcebuffer-audio-splice-frame-algorithm.)

Edge does not seem to do either and instead just removes the overlapping samples entirely, leaving a gap in the buffer (SourceBuffer). This does not seem consistent with the MSE spec.

Repro:

Rationale: the first segment has a duration of 10.005333… seconds and the second segment begins at 9.952 seconds. The second segment should be spliced in yielding a single buffered range of 19.957333… seconds.

Copied from Description when changed from Task to Bug

Copied from Repro Steps when changed from Bug to Task

The MSE spec requires user agents to support overlapping audio segments in one of two ways:

  1. remove the overlapping samples, and insert silence in their place; or
  2. cross fade the overlapping samples.

(See https://w3c.github.io/media-source/#sourcebuffer-audio-splice-frame-algorithm.)

Edge does not seem to do either and instead just removes the overlapping samples entirely, leaving a gap in the buffer (SourceBuffer). This does not seem consistent with the MSE spec.

Repro:

Rationale: the first segment has a duration of 10.005333… seconds and the second segment begins at 9.952 seconds. The second segment should be spliced in yielding a single buffered range of 19.957333… seconds.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Daniel T.”

      Changed Assigned To from “Daniel T.” to “Gurpreet V.”

      Changed Status to “Not reproducible”

    • Still reproducible with Edge/16.16299.

      @Gurpreet, can you be more specific when you set status to "not reproducible"? Not reproducible with which version of Edge? When can developers expect to see this fix?

    • Please reopen. This issue is still reproducible in Edge 16 with the steps detailed in the original report.

    • Microsoft Edge Team

      Changed Status from “Not reproducible”

      Changed Assigned To from “Gurpreet V.” to “Angelo L.”

      Changed Title from “appendBuffer() with overlapping audio segments not per spec.” to “appendBuffer() with overlapping audio segments not per spec.”

      Changed Steps to Reproduce

      Changed Assigned To from “Angelo L.” to “Rafael V.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed”

      Changed Status to “Confirmed”

    You need to sign in to your Microsoft account to add a comment.

    Sign in