Audio processing: ScriptProcessorNode.onaudioprocess sending duplicate audio input buffers

Confirmed Issue #14476692 • Assigned to Gurpreet V.


Jet F.
Nov 1, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

we’re trying to process a microphone input and convert it into raw pcm data for processing
out current implementation follows the guidelines on this demo:

for a simple standalone script, the ScriptProcessorNode.onaudioprocess works correctly and we’re able to create the correct audio buffer from microphone input

However, once the script is implemented on a processing-heavy page like a React/Angular single page application, the onaudioprocess event stutters, the observation is that:

  • would send duplicated input buffers
  • it would also drop some of the input buffers

causing the resulting audio to have duplicated and missing segments.

we’ve tried changing the audio recorder script processing node to a larger buffer size, but the issue still persists.

Tried also the fall preview for Edge 16, and the issue is still reproducible.

issue not reproducible in Firefox, Chrome, and Safari. they are able to produce to correct audio input buffers

here’s the sample raw PCM data that has been created that demonstrates the issue.
32-bit float

you’ll notice that a lot of the recorded audio segments get duplicated, while some of the recording audio data is lost.


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

    Changed Assigned To to “Venkat K.”

    Changed Assigned To from “Venkat K.” to “Steve B.”

    Changed Assigned To from “Steve B.” to “Venkat K.”

    Changed Assigned To from “Venkat K.” to “Shawn P.”

    Changed Assigned To from “Shawn P.” to “Gurpreet V.”

    Changed Status to “Confirmed”

    Changed Status from “Confirmed”

    Changed Assigned To to “Stephen E.”

    Changed Assigned To to “Firoz D.”

    Changed Assigned To to “Gurpreet V.”

    Changed Status to “Confirmed”

    Changed Status from “Confirmed” to “Won’t fix”

    Changed Assigned To to “Gurpreet V.”

    Changed Status from “Won’t fix”

    Changed Status to “Confirmed”

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

Sign in