Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No audio output in Google Meet (blocked by autoplay) #4621

Closed
jameshalsall opened this issue May 28, 2019 · 18 comments · Fixed by brave/brave-core#4741
Closed

No audio output in Google Meet (blocked by autoplay) #4621

jameshalsall opened this issue May 28, 2019 · 18 comments · Fixed by brave/brave-core#4741

Comments

@jameshalsall
Copy link

jameshalsall commented May 28, 2019

Description

When joining Google Meet there is no audio output. If I join using Google Chrome then I hear audio no problem. I have compared Google Meet settings between Brave and Chrome and they are identical, so this points to a problem with Brave itself.

It has always worked for me in the past but the recent updates to Google Meet that were released may have caused this issue to occur.

Test plan / Steps to Reproduce

  1. Open up https://meet.google.com/_meet in Brave
  2. Click the settings cog in the top right
  3. Press "Test" next to the Speakers setting and you should hear no output

Actual result:

Audio should work in Google Meet.

Expected result:

No audio is output in the speakers when using Google Meet.

Reproduces how often:

Always.

Brave version (brave://version info)

Brave    | 0.64.77 Chromium: 74.0.3729.169 (Official Build) (64-bit)
Revision | 78e4f8db3ce38f6c26cf56eed7ae9b331fc67ada-refs/branch-heads/3729@{#1013}
OS       | Mac OS X

Version/Channel Information:

I have not tried.
I can reproduce this issue in the Beta version too.

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields? No.
  • Does the issue resolve itself when disabling Brave Rewards? No.
  • Is the issue reproducible on the latest version of Chrome? No.
@YvanDaSilva
Copy link

YvanDaSilva commented Jun 6, 2019

I had the same problem, and by switching default sound cards now I have the opposite problem.
I have audio output but not audio input.

I can hear everyone clearly.
People are not able to hear me. The input icon shows the microphone line as active (the little spectrum moves up and down) (Sound reaches Brave, but does not leave Brave browser for the web).

I also disabled every "Brave" feature to see if it changes anything, it ends with the same result.

This is not reproducible on the latest version of chrome with the same exact settings and accounts.
Note: I can switch inputs as much as I want on Chrome it doesn't effect my ability to have output and input sound. However on Brave, even after a full restart the outcome is always uncertain.

Brave | 0.64.77 Chromium: 74.0.3729.169 (Official Build) (64-bit)
Revision | 78e4f8db3ce38f6c26cf56eed7ae9b331fc67ada-refs/branch-heads/3729@{#1013}
OS | Linux

@Aracki
Copy link

Aracki commented Jun 6, 2019

Same problem here with:
Brave | 0.64.77
OS | MacOS Mojave

@rebron
Copy link
Collaborator

rebron commented Jun 7, 2019

@rebron to reproduce.

@rebron rebron added the needs-more-info The report requires more detail before we can decide what to do with this issue. label Jun 7, 2019
@YvanDaSilva
Copy link

What more info do you need ?

@mdczaplicki
Copy link

Same here
Version 0.69.132 Chromium: 77.0.3865.90 (Official Build) (64-bit)
Linux Mint 19

@JacobMuchow
Copy link

Got it figured out after some tweaking. I think the main thing was enabling auto-play for meet.google.com.

  • Disabled Brave Shield
  • Updated to latest version
  • Saw a warning in the corner that auto-play was disabled for meet.google.com, I enabled it. That fixed it.
  • Re-enabled Brave Shield. Still works.

Why Google Meet needs auto-play on for the audio to work is beyond me.

Brave Version 0.70.121 Chromium: 78.0.3904.70 (Official Build) (64-bit)
macOS Mojave 10.14.6

@cmer
Copy link

cmer commented Oct 30, 2019

Thanks @JacobMuchow, confirmed working for me too!

@bsclifton bsclifton added workaround/allow-autoplay and removed needs-more-info The report requires more detail before we can decide what to do with this issue. labels Oct 31, 2019
@bsclifton bsclifton changed the title No audio output in Google Meet No audio output in Google Meet (blocked by autoplay) Oct 31, 2019
@fmarier
Copy link
Member

fmarier commented Nov 19, 2019

meet.google.com is already whitelisted so there might be another hostname/domain that needs to be whitelisted.

@GeetaSarvadnya
Copy link

GeetaSarvadnya commented Mar 4, 2020

Verification passed on

Brave 1.4.96 Chromium: 80.0.3987.132 (Official Build) (64-bit)
Revision fcea73228632975e052eb90fcf6cd1752d3b42b4-refs/branch-heads/3987@{#974}
OS Windows 10 OS Version 1803 (Build 17134.1006)
  • Reproduced the issue in 1.4.95
  • Verified STR from the description
  • Verified that click on "Test" output the audio in 1.4.96
    image

Verification passed on

Brave 1.4.96 Chromium: 80.0.3987.132 (Official Build) (64-bit)
Revision fcea73228632975e052eb90fcf6cd1752d3b42b4-refs/branch-heads/3987@{#974}
OS Ubuntu 18.04 LTS
  • Reproduced the issue in 1.4.95 - auto play blocks the sound
  • Verified the test plan from the description. The sound is played

Verified passed with

Brave 1.4.96 Chromium: 80.0.3987.132 (Official Build) (64-bit)
Revision fcea73228632975e052eb90fcf6cd1752d3b42b4-refs/branch-heads/3987@{#974}
OS macOS Version 10.14.6 (Build 18G3020)
  • Reproduced the issue in 1.4.95 - auto play blocks the sound
  • Verified the test plan from the description. The sound is played in 1.4.96.

@Tectract
Copy link

Bump / reopen please. I'm experiencing this issue with the latest Brave and autoplay / shields settings is having no effect for me. Google meet will NOT play any sound, other sites play sound just fine.

@bsclifton
Copy link
Member

bsclifton commented Nov 19, 2020

@Tectract you might visit brave://settings/socialBlocking and then enable Allow Google login buttons on third party sites and also Allow Google login for extensions under extensions. There's also an option for Hangouts. Let us know if toggling any of those helps

@sp
Copy link

sp commented Dec 7, 2020

Same problem here, just started in the last couple weeks.

Version 1.17.75 Chromium: 87.0.4280.88 (Official Build) (x86_64)
macOS Mojave 10.14.6

@Hansie020
Copy link

Hansie020 commented Dec 18, 2020

On macOS Catalina 10.15.7 and Version 1.18.70 Chromium: 87.0.4280.101 (Official Build) (x86_64) I have the same issue. Setting the Allow Google login buttons on third party sites and also Allow Google login for extensions dit not work

@posita
Copy link

posita commented Apr 1, 2021

I'm also seeing this with Catalina 10.15.7 and Version 1.22.70 Chromium: 89.0.4389.105 (Official Build) (x86_64) with autoplay allowed globally (no site-specific settings).

@Tectract
Copy link

Tectract commented Apr 1, 2021

Allow Google login for extensions

Hmmmmm this seems to be weakening my security to try and route around a bug?

Can we just get the issue fixed for this one site somehow without me needing to do that? Can we make it so google login can only access extensions published by google?

@zigojacko
Copy link

Experiencing this issue in Jan 2022 still !!

Couldn't figure it out so switched to a different browser just to use Google Meet which worked fine. It's definitely something to do with the Brave Shields tracking but nothing I tried resolved it.

@fmarier
Copy link
Member

fmarier commented Jan 6, 2022

I used Google Meet in Brave (beta) yesterday and it worked fine. Are you sure you gave it all of the permissions it needs?
Screenshot from 2022-01-06 13-38-57

@ccollova
Copy link

ccollova commented Sep 6, 2023

I have the same problem but - strange enough - it happens on all chromium-based browsers where i am logged in, not only on one computer, but cross-devices... ¯_(ツ)_/¯ I mean: I have a MacBook Pro, three Chromebooks, one Windows machine. Wherever (i.e. from any device using a chromium-based browser) I access Google Meet, I get no sound output. It works on Firefox though. Which leads me to think that (1) being Firefox not based on Chromium that makes it work (2) the problem should lie in some chromium-based extension or setting that is synched cross platform whenever I access my account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment