Skip to content
This repository has been archived by the owner on Oct 14, 2022. It is now read-only.

Audio issues in safari browser in MacOS #135

Open
Surendhar95 opened this issue Apr 7, 2021 · 2 comments
Open

Audio issues in safari browser in MacOS #135

Surendhar95 opened this issue Apr 7, 2021 · 2 comments

Comments

@Surendhar95
Copy link

Surendhar95 commented Apr 7, 2021

Describe the bug

I'm currently experiencing the following audio issues in a group video call when joined using Safari browser in MacOS:

  • Not able to hear audio of remote audiences sometimes in the channel (this is happening only in safari version 13.x).
  • There is also echo in the channel when an user join from safari with headset connected. This works perfectly fine in other browsers - Chrome and Firefox.

SDK Logs

No error is thrown for these issues.

Platform and Browser:

MacOS 10.15.5
Safari 13.1.1

SDK Version:

"agora-rtc-sdk-ng": "^4.3.0",

To Reproduce

Steps to reproduce the behavior:

  1. Join a channel for a video call in safari v13.x
  2. Use a headphone for audio and publish the track in the channel with other users
  3. Other users in the channel must be hearing echo when any participant talks.
  4. Also if a remote client has published audio track and they talk something, it can't be heard in safari.

Additional context

The echo behaviour is only happening when a client joins using headphone, it doesn't happen otherwise.

Also when the remote audio track is played using remoteAudioTrack.play() agora returns no error but still no audio can be heard in safari v13.x.

Agora has mentioned that the new SDK (agora-rtc-sdk-ng) doesn't completely support Safari but it would be really helpful to know if these issues are consistent with the already observed behaviour in safari.

Thanks

@plutoless
Copy link
Contributor

could you pls provide a channel which you used to reproduce the channel? ideally a unique channel name would be helpful. i can help check out the backend quality data.

@Surendhar95
Copy link
Author

@plutoless Sure, the channel id I used to reproduce these issues are this: 6xXw9zGcPdXi80Qu5WwZ

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants