F
FallenPredatorI
Hi All,
this seems to be a very unique issue that I am struggling to find an answer to, I will try to be as clear as possible and have laid out below some facts to hopefully avoid red herrings.
I have a set of bluetooth headphones (SONY WH-1000XM3) they are connected to my laptop (ASUS SCAR STRIX II GL504GS)
the headphones have worked perfectly and as expected up until recently
i have made no hardware or driver changes prior to this issue occurring.
I believe this is an issue with windows rather than the headphones.
I know that the microphone for the headphones is functional as I will explain below.
The Issue:
Whenever i want to talk to someone, be it via Facebook messenger, or in voice chat on games, I get 1 of 2 problems.
either;
a) the audio quality my end is as expected, i can hear the call and if i am playing a game it is surround sound etc. but the computer is using the laptops microphone, this is terrible because the quality of the microphone is quite bad and it is right above the fans so sounds awful.
b) the computer uses my headsets microphone and the audio quality is great for the other person, but my headset goes into mono audio so it sounds tinny and awful, but on top of that, i cannot hear the other person...
now I have been able to control whether I get outcome A or B because windows seems to split headsets into "[headphone model name] Stereo" and "[headphone model name] Hands-Free AG Audio" selecting stereo gives outcome A, selecting AG Audio gives outcome B.
In sound settings I have changed Output device to Stereo, Input device to AG Audio, and have even done this for individual programs in advanced settings under "App volume device preferences" but this seems to cause outcome B suggesting that if the microphone is enabled, the computer will only output to the AG Audio?
It seems that I cannot have both the headset microphone being used, and good quality surround sound, however this has not been an issue since November 2019 until about 3 days ago. The issue may have occurred before this but that was the first voice call in a while.
Continue reading...
this seems to be a very unique issue that I am struggling to find an answer to, I will try to be as clear as possible and have laid out below some facts to hopefully avoid red herrings.
I have a set of bluetooth headphones (SONY WH-1000XM3) they are connected to my laptop (ASUS SCAR STRIX II GL504GS)
the headphones have worked perfectly and as expected up until recently
i have made no hardware or driver changes prior to this issue occurring.
I believe this is an issue with windows rather than the headphones.
I know that the microphone for the headphones is functional as I will explain below.
The Issue:
Whenever i want to talk to someone, be it via Facebook messenger, or in voice chat on games, I get 1 of 2 problems.
either;
a) the audio quality my end is as expected, i can hear the call and if i am playing a game it is surround sound etc. but the computer is using the laptops microphone, this is terrible because the quality of the microphone is quite bad and it is right above the fans so sounds awful.
b) the computer uses my headsets microphone and the audio quality is great for the other person, but my headset goes into mono audio so it sounds tinny and awful, but on top of that, i cannot hear the other person...
now I have been able to control whether I get outcome A or B because windows seems to split headsets into "[headphone model name] Stereo" and "[headphone model name] Hands-Free AG Audio" selecting stereo gives outcome A, selecting AG Audio gives outcome B.
In sound settings I have changed Output device to Stereo, Input device to AG Audio, and have even done this for individual programs in advanced settings under "App volume device preferences" but this seems to cause outcome B suggesting that if the microphone is enabled, the computer will only output to the AG Audio?
It seems that I cannot have both the headset microphone being used, and good quality surround sound, however this has not been an issue since November 2019 until about 3 days ago. The issue may have occurred before this but that was the first voice call in a while.
Continue reading...