3 ms·

Side note, this can also cause a bit of difficulty in some situations apparently as seen in a HN post from a few months ago that didn’t get much attention http

Side note, this can also cause a bit of difficulty in some situations apparently as seen in a HN post from a few months ago that didn’t get much attention https://news.ycombinator.com/item?id=39669626 https://news.ycombinator.com/item?id=39669626 > I've been working on an audio application for a little bit, and was shocked to find Chrome handles simultaneous recording & playback very poorly. Made this site to demo the issue as clearly as possible https://chrome-please-fix-your-audio.xyz/ https://chrome-please-fix-your-audio.xyz/

filleokus 2y ago
Not sure if it's the whole story, but the latest response in the linked Chrome ticket seems to indicate that the api's were used incorrectly by the author > <he...@google.com> > Status: Won't Fix (Intended Behavior) > Looking at the sample in https://chrome-please-fix-your-audio.xyz https://chrome-please-fix-your-audio.xyz, the issue seems to be that the constraints just aren't being passed correctly [...] > If you supply the constraints within the audio block of the constraints, then it seems to work [...] > See https://jsfiddle.net/40821ukc/4/ https://jsfiddle.net/40821ukc/4/ for an adapted version of https://chrome-please-fix-your-audio.xyz https://chrome-please-fix-your-audio.xyz. I can repro the issue on the original page, not on that jsfiddle. https://issues.chromium.org/issues/327472528#comment14 https://issues.chromium.org/issues/327472528#comment14