[Webkit-unassigned] [Bug 218261] NotSupportedError thrown assigning ConvolverNode buffer

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=218261

--- Comment #15 from Chris Dumez <cdumez at apple.com> ---
(In reply to Ashley Gullen from comment #5)
> I think it's the first reason (different sample rate). In Chrome, Firefox
> and Safari I get an AudioContext running at 44.1KHz (the default, we don't
> specify a sample rate). In Chrome and Firefox the audio buffer we assign to
> the convolver node is also 44.1KHz, presumably because it came from the
> AudioContext's decodeAudioData which knew to resample it. However our audio
> files are all WebM Opus - it's nearly supported in all browsers, but Safari
> is the last browser that does not support this format. So we have to ship a
> WebAssembly WebM Opus decoder just for Safari. But this decoder outputs
> audio buffers at a fixed sample rate of 48 KHz, hence the mismatch. (I guess
> your system's sample rate defaulted to 48 KHz so it matched?)
> 
> Does the spec say the sample rate has to match? It doesn't seem to be a
> problem anywhere else in the Web Audio API, just with this specific case.
> 
> While I'm here, please, please add support for WebM Opus. I first asked for
> this back in 2018 in issue 183852. It would save us so, so much trouble if
> we didn't have to bundle a decoder just for Safari. And it looks like Safari
> has been shipping an Opus codec for WebRTC since 2017 anyway. It doesn't
> seem like such a big jump to hook that up to the Web Audio API.

Bug 221745 may be of interest to you.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210211/141f2ff1/attachment-0001.htm>