I updated from 5.3 to 5.5 yesterday. Instantly after the update i was not able to find a way to adjust the volume of my USB-Headset. Someone just removed the volume control in the call view. I thought "This cant be" ... but its true..
Searched the web ofc and found other people complaining about the same thing but there was at least a 3 click solution for those guys .. but on a Mac there is NONE!
On windows you are allowed to see the connection quality button.. on a Mac there is NONE!
And this is no Beta .. this is REAL.
To proof what i mean ...
I guess this will get fixed in about 12 month like the "Dial Pad Auto Popup" problem. So i will check out other clients in the time.
This is ridiculous!
Solved! Go to Solution.
I am actually using skype 6.0, and I hv found there isnt a button for your to increase/decrese volume, yet it could be adjust (skype only, not the system) by pressing alt+command+up/down. Hope that helps?
Apparently, the Skype for Mac dev team have removed the volume controls from the in-call control bar because the same functionality can be found by using the F11/F12 buttons on the Apple keyboard.
If that is the case, why haven't they removed the mute button as well?
I just want to say that I will not use Skype any more until this issue is fixed, and I've bought lots of minutes with Skype over the years. Whoever thought this was a good idea should be fired.
First off removing this kind of functionality is beyond believe! Who made this decision, why not use your blog and get some kind of feedback from the community first?
Plus who ever said the F11/F12 functionality on a Mac is just the same obviously a Windows users
For everyone else who wants to downgrade get the old version of Skype which also doesn't take up 25% of you screen realesate at http://www.skype.com/intl/en/get-skype/on-your-com
It's worse than that, not only is there no volume control to support the "Skype Certified FREETALK everyman Headset" which the previous build supported, however they also removed Video support for the FV Touchcam V1 HD camera which worked with build 184.108.40.2069 I will be reverting back to the previous build until both of these issues are resolved and strongly suggest others do the same.