[Webkit-unassigned] [Bug 219634] New: Garbled audio from WebRTC remote stream that fixes itself after random period of time.

[bugzilla-daemon at webkit.org]

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

            Bug ID: 219634
           Summary: Garbled audio from WebRTC remote stream that fixes
                    itself after random period of time.
           Product: WebKit
           Version: Safari 14
          Hardware: All
                OS: macOS 10.15
            Status: NEW
          Severity: Major
          Priority: P2
         Component: WebRTC
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: szmydadam at gmail.com
                CC: youennf at gmail.com

Created attachment 415623

  --> https://bugs.webkit.org/attachment.cgi?id=415623&action=review

output-audio.m4a and source-audio.wav files

For some reason, Safari 14 seems to garble audio that came from remote stream during WebRTC connection. I'm able to easily see this every time on my setup:

- Safari Version 14.0.1 (15610.2.11.51.10, 15610)
- macOS Catalina 10.15.7 (19H15) running on MacBook Pro (Retina, Mid 2012)

Steps to reproduce (I used Jitsi Meet platform but I've seen the same on few others):
1. Establish WebRTC connection. I'm entering some jitsi room (https://meet.jit.si/SafariGarbledAudioTest) from Chrome and Safari. "Second" browser that'll produce sound (Chrome in my case) seems to have nothing to do here as I've used several with different operating systems even and the looks like the issue is just on Safari side as a receiver.
2. Make some sound (talk) so that Safari browser will receive it.

Expected result: Safari plays out audio just fine
Actual result: Sound in Safari is garbled/distorted. It fixes itself within few seconds or longer (its random period of time but averagely after around 10-15s all works correctly).

Additional info:
1. I recorded the output of this bug and I'm attaching it as "output-audio.m4a". You can see there that in ~15s audio clears out itself. No action is made on any side and this just fixes itself after random amount of seconds
2. To keep things reproducable and more predictable, I generate source audio from pre-recorder wav file and run it like "google-chrome-stable --use-file-for-fake-audio-capture="source-audio.wav" --use-fake-device-for-media-stream" using chrome. I wanted to attach it also.

-- 
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/20201208/6b17df82/attachment-0001.htm>