Using the per-revision bisect providing the bisect results,
Good build:55.0.2883.0 (Revision:423768)
Bad build: 56.0.2886.0 (Revision:424099)

You are probably looking for a change made after 423914 (known good), but no later than 423915 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.
  https://chromium.googlesource.com/chromium/src/+log/c70db2f7f0899c350ec8bb47bca750a3fbb87188..9848564877f0057f4dcbc98bce061dfa17a9202c

From the CL above, assigning the issue to the concern owner 

@rtoy - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Review-Url: https://codereview.chromium.org/2380183002

Thanks!

Adding RB label as this is a recent Regression. Please remove if not required.
Thank You.

Sorry, this is working as intended.  The WebAudio setVelocity function was removed in M56 as planned.  We had deprecation warnings about the removal for about 6 month prior to removal.

In addition, the actual Doppler effect that is associated with setVelocity was removed long before that.

This is in accordance to the WebAudio spec that removed the Doppler effect about two years ago.

Updating component. This is a WebAudio issue, not WebGL.

I've contacted Unity and hope that they'll update this content.

They've updated it. Closing as WontFix (not a Chrome bug).

Issue 698144 has been merged into this issue.