Dear TeamViewer community,
I've been using TeamViewer for a couple of years now and I mostly use it on my MacBook Pro, currently running osSierra 10.12.5, to remote access my Dell laptop, currently running Windows 10 Enterprise. I always carry my MacBook Pro with me and leave the Dell laptop at home. When I need to access the latter, I use TeamViewer and I've been very happy with this setup during the past years.
Before upgrading to TeamViewer 12.0.78517 on both my MacBook Pro and Dell laptops no later than yesterday, I could listen to music or watch a YouTube video on my Mac even while a remote control session was open to access my Dell laptop.
Since the upgrade, however, as soon as I begin a session, the sound volume on my Mac turns down to a level which almost makes it imperceivable (at first I thought there was no sound at all coming from my Mac). I tried increasing the volume on my Mac, applications and YouTube in all possible ways I could think of, but even with all the sliders set to the maximum, the sound remains way too low... Connecting headphones doesn't resolve the problem either.
As soon as I close the remote session, the volume on my Mac is automagically restored to a normal level.
Anyone else experienced this issue ? Any advice on what I could possibly try, besides uninstalling TeamViewer on both computers and re-install the previous 12.x version ?
Thank you in advance for your kind replies !
Solved! Go to Solution.
We published a new version with a fix. Please install the new version and post your feedback here.
Thank you in advanced
Same problem here. It occurs because for whatever reason, TV is now turning on our webcams/microphones when we make remote control connection. When the webcam/mic is enabled, local media playback volume is automatically lowered. I don't know why TV is now doing this but I am really concerned by this behavior and have filed a ticket with support to try to get to the bottom of it.
Same here (Mac OS X Sierra with TV 12.0.78517) ! It doesn't simply mess up with audio output but with input as well so I can't use Teamspeak or discord and teamviewer at the same time.
I don't even use any of TV sound feature...
Thanks for sharing this with us, @pplaisance
When you say that TV is "turning on" (or initializing them without actually turning them on, possibly?) our webcams and microphones when launching a remote control connection, do you mean those that belong to the remote computer (e.g. the Dell laptop in my example), the local computer (Ex: MacBook Pro) or both?
I'll investigate further at my end. Thanks for pointing this out and let me know if I can be of any assistance (e.g. provide my own settings to the support team) to help you get that ticket resolved quickly.
All the best !
Thanks for sharing this, @RoxTeddy.
Wow, that's quite inconvenient. I haven't tried making a Skype call or similar using my Mac while remote controlling my Dell laptop with TeamViewer. There's a great chance that I'll experience the same symptoms when I'll do...
Let's hope TV's support and maintenance teams will find a solution to this very quickly.
All the best !
Ah, found something interesting.
There's no need to establish a remote connection in order to reproduce the issue.
Right after launching the TeamViewer app on my MacBook Pro, without establishing a remote connection to any computer, if I open up the Preferences window (TeamViewer > Preferences.... from the top menu) and then click on the Audio icon, the sound level is affected immediately. Clicking on any other icon (General, Security, Remote Control, etc., even Video) in this same window restores the sound to its normal level, and vice-versa.
Tried changing all the possible settings under the Audio section, even saving and closing the Preferences window in between each of these changes. Problem persists...
Can any of you guys reproduce this behavior as well ?
Thanks in advance !
This is caused by "Audio Ducking". Baiscally, this is caused if you have the VoIP Feature inside the connection turned on. Like many other VoIP services, this lowers the sound of all other output devices during a conversation to allow the Voice to be raised higher than the volume of other programs (As the audio cannot go above max).
If you aren't using TeamViewer VoIP, the only way I can find to stop the audio from lowering is to change the default audio device output for TeamViewer before making a connection as only the audio device it is trying to play through should get ducked.
This can be done under "Audio Confrencing" in the options of TeamViewer
I have tested this and the audio does play at the correct volume during the connection (It does dip just as the connection is being established)
I hope this helps!
No, this does not help. :smileysad:
Change it back to how it was before, please!
There is no "audio conferencing" setting in TeamViewer for Mac preferences that I can find. There is an Audio tab, which will duck the audio when you open, but I've tried every combination of settings imaginable and nothing stops it from activating my webcam's microphone and ducking the audio when making remote connections.
When I make a remote connection from my Mac Mini to any other computer, windows or Mac, TV 11 or 12, the light on my MS Lifecam on my Mac turns on, likely because it has activated its microphone. Audio on my Mac is ducked for the duration of the connection.
Thanks for joining this thread !
Is this audio ducking feature new on the latest Mac version of TeamViewer (12.0.78517) ? I've never experienced this problem in earlier 12.x versions, but I might have skipped one or two. I didn't write down the version I was using before updating it to 12.0.78517, unfortunately...
You wrote :
«[...] the only way I can find to stop the audio from lowering is to change the default audio device output for TeamViewer before making a connection as only the audio device it is trying to play through should get ducked.
This can be done under "Audio Conferencing" in the options of TeamViewer.»
As @pplaisance already pointed out, the "Audio Conferencing" settings are simply called "Audio" in the Mac version of TeamViewer :
Most of the time, the only audio devices that I use on my MacBook Pro are the built-in microphone and speakes. So I don't have many options regarding the selection of a different audio device, as you suggested, to use for VoIP in TeamViewer. Even if I try to change the devices above from "Built-in In/Out" to "Standard recording/palyback device" and apply the changes :
I also tried clicking on the "Configure" button to change the "Conference Call" settings :
Still no luck, only "duck".... :smileywink:
The ONLY way I was able to circumvent this problem was to attach an external audio device to my Mac and then, after selecting this device for "audio conferencing", I was able to hear sound loud and clear from my built-in speakers (no audio ducking) :
I swear something's changed, as I didn't need to do this in earlier versions. Also, maybe it would be a good idea to add a checkbox allowing users to enable or disable "Audio Conferencing" altogether in TeamViewer, or add an item to the Speakers and Microphone dropdown list named "Disabled" so as to not initialize and apply audio ducking to any audio devices. Just my two cents...
Thank you in advance for considering this as an annoying side-effect, if not a bug, of an otherwise useful feature (for some other users and customers, I guess) you tried to introduce in TeamViewer.
That's actually kind of scary too, isn't it @pplaisance ?
I mean, how can we be sure someone isn't actually hearing audio through the built-in or webcam's microphone or, even worse, accessing the webcam's video feed ?
An unexperienced user may think he's being spied or something while using TeamViewer. **bleep**, had I seen my webcam's led lighting up (which I don't, as the built-in microphone on a MacBookPro isn't linked to the webcam), I would have been quite worried even if I don't consider myself being too paranoid about these things...
Thanks again @pplaisance for your input !!
I fixed the problem by downgrading to a previous v12 build.
I can still reproduce the bug by going into settings > audio. If I had a session opened, I have to close it to get back the sound. If I hadn't, I just have to go the another setting panel or close the settings.
That audio ducking story is weird. I see the interest in limiting other programs sound output to hear the voice over but why would it duck the microphone input too ?
I don't even use any sound feature of TV. No Meeting or Voip. Only remote control with the remote sound disabled.
Obviously, something has changed in the last build that triggers some conference/voip functions that aren't really needed.
Thanks for your input, @RoxTeddy !
I'm thinking about taking that path as well (downgrading TeamViewer to its previous version), although I wasn't sure if it would actually solve the problem. Your post gives me hope that it will.
Thank you !!
This has always been the problem with Teamviewer since I started using it from somewhere around v5. The TeamViewer staff doesn't use Macs themselves and painfully obvious bugs like these keeps coming up every year.
Just look at the moderator answering this thread, he/she gave a direct advice from their PC, in a thread about a Mac problem... :smileysad:
Thanks for joining the conversation !
I wouldn't know if what you say regarding the TeamViewer staff not using Macs is accurate or not, but one thing is certain, they've done an incredible job with this application so far.
It's fast, has a small footprint on data usage, works beautifully across platforms and it's completely free for personnal use. Yes, I'm totally addicted to it ! :smileywink:
No software is absolutely bug-free. IMHO, the important thing is to see how quickly and diligently the support and development teams react when this type of bugs are reported to them by us, the end users. Let's hope for the best ! :smileyvery-happy:
All the best,
Oh well, I guess I should have posted my message here... I'm sure both reports are related, anyway.
Same problem here (I think). I'm using version 12.0.78517 on OS X Yosemite 10.10.5. I started having this issue yesterday. I was playing some music on Spotify and suddenly the volume was VERY low, I had to increase the system volume to maximum to barely hear anything on the speakers connected to my Mac Mini computer. I first thought that the speakers were broken because I couldn't find anything on the system to change the output mixing/master volume, etc.
But as soon as I closed Teamviewer I got the normal volume again. So it turns out that every time I open a new Teamviewer session with a remote computer, the system volume is barely audible. As soon as you close the remote session, volume goes back to normal (no need to actually exit Teamviewer). I tried to disable the remote audio option while in a session, but it doesn't fix the issue.
Another weird issue, if you go to Preferences > Audio when you have anything playing in the background (Spotify, for example) Teamviewer will either crash or volume will almost mute (until you leave the preferences panel).
If you mess with the volume controls it somehow gets better. You can slide the volume of the Speakers up to the top and the master system volume will increase almost back to normal (not really). But as soon as you close the audio preferences the volume will just boost up to the maximum.
My guess? The volume scale on Teamviewer doesn't match the system's volume. A 100% volume on Teamviewer's audio preferences is about 60-75% of the real system volume. Meaning that if your system volume is at about 25-40%, when you launch a Teamviewer remote session, it will get a -25%-40% "increase", leaving it to almost 0% (mute).
Screenshots of system volume level and Teamviewer's audio preferences (sound barely audible in that scenario, but will go back to normal if I just close the audio preferences or simply switch to another preferences' section). The slider on Teamviewer's audio preferences should be way lower (first/second mark) but it's in the middle:
I'm not sure I can edit my post, so I'm replying to myself (haha). I've played a bit more with the audio preferences and since I've used Soundflower in the past, I thought I should give it a try. By setting the output to Soundflower, everything works fine (this is, of course, related to SkyLukeQc's solution of attaching an external audio device to the computer but without the need to actually have a "physical" device).
I still have a brief "fade-out, fade-in" effect every time I start the first remote session (or I play with the audio preferences) after I have got a remote session active, opening new sessions won't disturb the sound. I also obviously have no sound from the remote sessions.
I'm curious of what would happen if you attach an external USB soundcard and set it as the output device for Teamviewer. I'm sure the system volume would work like a charm while being able to play the remote session's audio through the external soundcard (at what volume, that I don't know). So, again, I'd say there's some bug here with the mixing of Teamviewer and system audio (Teamviewer's volume messing with the system's "master volume" level).
Your solution of changing output might work but most of us have only a single ouput.
I insist that before the last update, if we weren't using Teamviewer voip/conferene part, it was not affecting our experience. I can remember now it always hapenned in conference and thats why I stopped using it but at least the remote control wasnt messing with other programs' sound.
In my opinion, TeamViewer developpers should rollback the code to a previous commit when it was not affecting the remote control.
Which v12 older build? 12.0.75813? I can't seem to find it anywhere to download it... :( My issue is similar, in a way that TeamViewer crashes completely, but the error message points to audio issues:
Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler  /Applications/TeamViewer.app/Contents/MacOS/TeamViewer Application Specific Information: dyld: in dlopen() /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
Later edit: I uninstalled Boom 2 from www.globaldelight.com, everything is back to normal for me. :)
Thank you so much for your very useful contribution to this thread !! Using Soundflower was a brillant idea to diagnose the issue and run your tests !
To answer your comment below :
"I'm curious of what would happen if you attach an external USB soundcard and set it as the output device for Teamviewer. I'm sure the system volume would work like a charm while being able to play the remote session's audio through the external soundcard (at what volume, that I don't know)."
Since I do have an external USB sound card available that I can use on my Mac, I'll try to run a few tests later today to see how that works. I'll post my results here as soon as I can.
Thank you for joining this thread and sharing your issues and workarounds with us !!
I can't answer your question about the specific earlier version @RoxTeddy used to "fix" the issue.
In my case, TeamViewer never crashed, at least not in relation to the issue at hand (audio related issue). @Devotee mentioned that TeamViewer would sometime crash in his case. Don't know if the cause and error message were the same for him, however.
Thanks for pointing out the "Boom 2" application, I din't know this app. From my understanding, it allows you (among other things) to "boost" the audio volume coming out of your audio devices beyond their normal max levels, is that correct ? So I can imagine that after installing this app, you're able to boost back up the sound that was ducked by TeamViewer's audio conferencing feature. Does it also add virtual sound devices in a similar way of what Soundflower does ?
I have a few questions that came to mind :
Thank you in advance for your valuable input. I'm sure that with all this info, TeamViewer's team will be able to nail the problem down and correct the issue in the next release.
Actually, it was the other way around. Boom 2 boost audio level by adding a virtual output device and rerouting audio to be boosted. So by UNinstalling it removed said device and now TeamViewer no longer crashes. I was able to make it crash just by visiting Preferences -> Audio tab. It is my understanding that Boom 2 takes control of the audio output device and said device was no longer matching the manually selected TeamViewer audio output device in Preferences. Trying to connect to a remote computer also made it crash.
I have a few questions that came to mind :
Oh, sorry. I misread the edit you wrote on your first post.
Uninstalling "Boom 2", not installing it, fixed your problem !!
So now you're basically at the same level as all of us : no more crashes, but sound ducking when starting a remote connection or accessing the Audio settings.
Thank you once again for your valuable input and taking the time to answer all my questions, I appreciate it !!
All the best,
for the version, I rolled back to 12.0.72647 . I have found a page on the official website to get previous major versions (v11, v10..) but not previous v12 builds so google gave me this site instead : http://teamviewer.fr.uptodown.com/mac/old
But I cannot garantee the file are leggit, that's the first time I use this website.
Edit : Oh and for newcomers, as I said the audio ducking happens in this version too but only if you trigger audio/voip functionnalities, not just using remote control. That's pretty much all I need from TeamViewer.
Hi again everyone.
@ apologise, I say audio/confrencing as there is both settings in here. But on Mac the title was shortened due to the lateral layout of options, although we still refer to it as Audio Confrencing internally I apologise for any confusion.
I have tested this on a MacBook Air running Sierra 10.12.1
In my testing, if you change the default audio output in here, the audio still ducks at the beginning of a connection, but then returns to normal. But I can confirm that this behaviour has been occuring well before V12.
@SkyLukeQc Thank you for your calm help on this page, it's fantasic to have users like you :)
@Ducam I am sorry if it seems like we don't care. However I did not test this on a windows device. There would have been no point and if I cared so little, I simply would have let this post be rather than respond.
I do have support looking at this as well and we will monitor for any updates here and I will respond if I can make any headway from our side.
How is it that there is no ability to disable audio conferencing altogether? I have a single audio in source and that is my Skype polycom phone. It starts an audio session when I log into one of my computers via teamviewer. As mentioned above it ducks audio from other sources. It also blocks incoming calls since the phone thinks it is in another call. Since I cant turn the stupid thing off as there is no settings to do so in Teamviewer, this is not sustainable. This is aboslutely rediculous and you guys need to change it back or I will find other option.
Thank you @RoxTeddy !!
"Oh and for newcomers, as I said the audio ducking happens in this version [12.0.72647] too but only if you trigger audio/voip functionnalities, not just using remote control. That's pretty much all I need from TeamViewer."
I agree with you, same here. Rolling back TeamViewer to this pre-12.0.78517 behavior would be ideal for me too as well as many others, IMHO. Even better would be to have a way to disable Audio Conferencing altogether in the Audio preferences panel, at least for those of us that do not need or use this functionality or who'd rather use an external audio conferencing solution, such as Skype or similar for example.
A huge thank you to everyone who has contributed to this thread so far !! I believe we've caught the support team's attention. :smileywink:
Also, thank you very much @Scotty for your very nice words. I appreciate it ! :smileyvery-happy:
All the best,
Thanks for your contribution on the subject at hand.
IMHO, using words such as "stupid" and "ridiculous", or threatening to look for a different solution if a bug isn't solved as quickly as you'd like, isn't very constructive.
The part that is constructive, though, is your description on how you use TeamViewer in conjuction with other software and/or hardware. I believe we all use it a bit differently depending on our own needs. So I'm glad you shared that with us.
Let's keep this thread "clean" by remaining calm. I'm sure something good will come out of it ! :smileywink:
Thank you for your contribution.
I would like to share an update with you which I got from our development.
We got the confirmation that this is a bug in the current version – we are already working on a fix and I will inform you when we published it.
We want to say a big THANK YOU for your feedback because also the input from this thread helped us to identify the problem.
Thank you for sharing this information with us ! These are excellent news !!!
Looking forward to the next release of TeamViewer ! :smileyvery-happy:
All the best,
@RoxTeddy How were you able to get your hands on a previous version? I am having the same problem and want to roll my version back.
Any advice is appreciated
However I don't know at all if this site is reliable.
Maybe our staff friends @Julia @Scotty have a more leggit way to download earlier versions ? On the official website I see only links to V10 & v11 but no way to get earlier version of v12. I understand you may want to keep most client the most updated as you can but in those case it could be useful to let us rollback. (Before that solution I was about to uninstall TV and find other remote control solution. It would have been a shame ^^)
Cheers from Paris
teamviewer.app restored from TimeMachine fixed for me.
Sound was crashing app at login on remote host
Thanks for the tip. I'm fairly new to the mac and never heard of Time Machine before. Unfortunately I hadn't configured it yet. I was able to downgrade with the link @RoxTeddy gave me and it fixed the issue.
Thanks for the link. I downgraded to version 12.0.72647 and it did the trick. What was interesting was I did your test of going to the audio settings in preferences and regardless of the version (12) everytime I click audio in preferences it would start "ducking". So I decided to try connecting remotely and the problem was solved.
Thanks for the info it was a big help. This was driving me crazy!
Cheers for Canton Connecticut U.S.
Please us the following link to download the previous TeamViewer 12 release:
We always recommend to download TeamViewer directly from our homepage or our links.
Thank you very much for this official download link. It's wonderful to see how much you guys at TeamViewer care about your users ! :smileyvery-happy:
I'll downgrade to this version too while waiting for the next version of TeamViewer to be released, in which hopefully the issue reported in this thread will be a thing of the past. :smileywink:
All the best and cheers from Quebec City, Quebec, Canada ! :smileywink:
I found a way not to uninstall Boom2 and still get the right voice.
I installed DPS reflector. And just used that as the audio device in the DPS reflector
Works like a charm
I have the very exact problem as well, quite irritating. Start TeamViewer Preferences, go to Audio tab, and the sound is suddenly 'gone'.....
So I tried it with the teamviewer version for which a download link was provided earlier on in this thread. That however appears to be an even newer version, namely 12.0.75813 (well, assuming a higher number means a more recent version)
So, not surprisingly, that version does not fix the problem for me.
Hi @Jakob !
Thanks for joining the conversation !
Actually, the link posted by @Julia allows you to download TeamViewer 12.0.75813, which is the version that came right before the one in which the audio ducking issue was introduced : 12.0.78517 (and of course 75813 < 78517... :smileywink:)
I downgraded to version 12.0.75813 and the issue no longer occurs on my MBP, unless I go to Preferences and click on the Audio icon... But otherwise, simply starting a remote session won't cause the audio to be ducked as it happens in version 12.0.78517.
If this doesn't work as expected at your end, make sure you completely uninstall TeamViewer from your Mac by going to TeamViewer's Preferences > Advanced, scroll down completely to the bottom and click Uninstall. Then, reinstall TeamViewer 12.0.75813 and give it a second try.
Do not try to open or change the Audio settings unless you really need to (e.g. if you have access to multiple audio devices on your Mac), otherwise the audio ducking issue may be triggered even in this version.
Hope this helps ! :smileyhappy:
same here , only solution is to downgrade, so try mostly everything without success, audio is ducked all the time, as soon as a session is established.
I hope that new update will arrive soon !
I'm glad to see that I'm not the only one experiencing this problem. I scoured the internet for over an hour attempting to solve this problem. I'll be using Julia's link to rollback to the previous version as this sound issue was driving me crazy! I'm a graduate student and I live in an apartment with paper thin walls unfortunately. So, I need my headphones and my volume to drown out the noise when I remote log in to my lab computer(s) and work from home. Thanks for posting this problem and I look forward to the new update.
Same issue here.
I run a program that alerts me whenever an application hijacks the mic ( https://obdev.at/products/microsnitch/index.html )
As of the most recent build I get alerted any time I open Team Viewer that it is taking over the mic. This is when all other sounds get near-muted until I completely exit TeamViewer.
Let me know if there's any info I can provide to help you guys diagnose.
Hi @panckreous !
Thanks for joining the discussion !! :smileyhappy:
Wow, this community really rocks ! Each and everyone who contributed to this thread added useful information that surely helped others as well as TeamViewer's support team isolating the problem. It's really a refreshing experience !! :smileyvery-happy:
Keep up the good work everyone !
I solved this problem by changing the output audio setting to Airplay.
Nice workaround !! Thanks for sharing this with us ! :smileyhappy:
FWIW, I downgraded to version 12.0.72647 (file dated Feb. 6 2017) that was still in my trash and the issue went away. Thanks all for great input and helping resolve via a simple workaround.
after using my Airplay workaround, i updated to Sierra and now Airplay is no longet an option in the dropdown. Not sure if anyone knows why it is gone in Sierra.