Jump to content

Imbalanced sound at low volume

empleat
Go to solution Solved by Spuriae,

Cheap potentiometers, like those often used in headphones, tend to have large channel imbalance at low levels since mechanical inaccuracies in the construction have a magnified effect in those sections.

 

The recommendation that you not use digital volume control generally only applies if you have a good powered analog volume control like the potentiometer on a heapdhone amplifier (and even then, isn't always valid). The impedance mismatch and reduced damping from lowering the volume using an unbuffered series potentiometer like those used on passive headphones are massive compared to any noise contribution that digital volume control could ever produce.

 

Why digital volume control doesn't matter for anyone who's just plugging their headphones into their computers:

Spoiler

The issue with digital volume control is that you lose the least significant bits of the digital signal when you attenuate it. There are methods to mitigate this error, but I will ignore these and instead focus on a simplified worst-case scenario to show why concerns about digital volume control for the end listener are in most cases overblown.

 

If a 4-bit signal for instance is represented as [0,1,0,1], then to reduce its level 50% it would become [0,0,1,0] and noise would be introduced due to the error caused by losing the information contained in the last position. In this case, the 4-bit representation of 5 changed to 2 when reduced by 50%; however, 2 is obviously not 50% of 5! Because the odds of this error are functionally random with most signals of interest (corresponding to whether or not the smallest bit is a 0 or 1) they can be treated like white noise.

 

Furthermore, changing level by something other than a factor of 2 would introduce additional error: in our example, for instance, attempting to reduce the volume by 10% is impossible without introducing error since there are only 16 valid levels in a 4-bit signal to begin with.

 

However, note that these errors are only introduced at the level of the least significant (smallest) bit. On a 4-bit signal this error can be no greater than 1 part in 16 relative to a full-scale signal. On a 24-bit signal like those used for volume control in most modern devices, this error is limited to 1 part in 16 million. Note that a 16 bit signal (CD-quality) has an inherent digital noise level 8 bits greater than this; volume on a standard end-consumer audio track may be reduced by up to 48dB, or a factor of 8, before the noise from the volume control begins to overtake the minimum amount of noise already guaranteed to be present in the recording. Windows volume set to 2/100 on default settings (the lowest that can be achieved on most computers) is only roughly -33dB; in other words, as long as you are using a 24 or 32 bit output device setting, it is impossible for Windows volume control alone to appreciably reduce the dynamic range of 16-bit audio playback on most computers. For a signal chain containing higher bit depth files or multiple stages of amplification/attenuation the outcome might be different, but for the normal end-user already using default Windows settings, it doesn't matter.

 

TL;DR: If you're just plugging your headphones into your computer, set your Windows output device to 32 bits and don't worry about volume control.

 

 

This happens to me on 2 computers and 2 different models of headphones. When i lower sound to a certain level on headphones, one side is playing more loudly. This is annoying, because than sound is overall too loud...

So i need to lower sound in windows, but i heard contradictory things about that. Either you are supposed to keep it on 100% always, because than some frequencies won't be played, or be distorted. Or you are suppose set same level of sound approximately in windows as in headphones, otherwise you can even damage your headphones. I used always 100% and never had problem tbh.

Link to comment
Share on other sites

Link to post
Share on other sites

It could be hearing damage...

I think you should get your hearing checked.

A PC Enthusiast since 2011
AMD Ryzen 7 5700X@4.65GHz | GIGABYTE GTX 1660 GAMING OC @ Core 2085MHz Memory 5000MHz
Cinebench R23: 15669cb | Unigine Superposition 1080p Extreme: 3566
Link to comment
Share on other sites

Link to post
Share on other sites

9 minutes ago, Vishera said:

It could be hearing damage...

I think you should get your hearing checked.

LMAO, when it is fine at higher levels? I thought it is was my older mobo, it had already worn out audio output, but it happens even on new one with another headphones. I am not using anything expensive, but not the most cheaper ones. Logitech g203 and razer kraken.

Link to comment
Share on other sites

Link to post
Share on other sites

2 minutes ago, empleat said:

LMAO, when it is fine at higher levels?

Yep,it could be hearing damage or hearing loss.

Hearing damage is measured by the lowest volume you can hear.

0.1 dB is perfect hearing (often written as 0dB),while 20dB~30dB and above is considered hearing damage.

Also there could be variations between ears,which could also do that effect as well.

A PC Enthusiast since 2011
AMD Ryzen 7 5700X@4.65GHz | GIGABYTE GTX 1660 GAMING OC @ Core 2085MHz Memory 5000MHz
Cinebench R23: 15669cb | Unigine Superposition 1080p Extreme: 3566
Link to comment
Share on other sites

Link to post
Share on other sites

4 minutes ago, Vishera said:

Yep,it could be hearing damage or hearing loss.

Hearing damage is measured by the lowest volume you can hear.

0.1 dB is perfect hearing (often written as 0dB),while 20dB~30dB and above is considered hearing damage.

Also there could be variations between ears,which could also do that effect as well.

Problem in your theory, i can't hear that one side, even if i switch sides. Also i can hear one side fine always, which is loud and second very quiet. But thanks for concern :D

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, empleat said:

Problem in your theory, i can't hear that one side, even if i switch sides. Also i can hear one side fine always, which is load and second very quiet.

I don't understand,by side do you mean the side of your head or the side of the headphones?

If it's the headphones they may be dirty,so cleaning may solve it.

A PC Enthusiast since 2011
AMD Ryzen 7 5700X@4.65GHz | GIGABYTE GTX 1660 GAMING OC @ Core 2085MHz Memory 5000MHz
Cinebench R23: 15669cb | Unigine Superposition 1080p Extreme: 3566
Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, Vishera said:

I don't understand,by side do you mean the side of your head or the side of the headphones?

If it's the headphones they may be dirty,so cleaning may solve it.

Side of headphones of course! Nope they are new ones.

Link to comment
Share on other sites

Link to post
Share on other sites

Cheap potentiometers, like those often used in headphones, tend to have large channel imbalance at low levels since mechanical inaccuracies in the construction have a magnified effect in those sections.

 

The recommendation that you not use digital volume control generally only applies if you have a good powered analog volume control like the potentiometer on a heapdhone amplifier (and even then, isn't always valid). The impedance mismatch and reduced damping from lowering the volume using an unbuffered series potentiometer like those used on passive headphones are massive compared to any noise contribution that digital volume control could ever produce.

 

Why digital volume control doesn't matter for anyone who's just plugging their headphones into their computers:

Spoiler

The issue with digital volume control is that you lose the least significant bits of the digital signal when you attenuate it. There are methods to mitigate this error, but I will ignore these and instead focus on a simplified worst-case scenario to show why concerns about digital volume control for the end listener are in most cases overblown.

 

If a 4-bit signal for instance is represented as [0,1,0,1], then to reduce its level 50% it would become [0,0,1,0] and noise would be introduced due to the error caused by losing the information contained in the last position. In this case, the 4-bit representation of 5 changed to 2 when reduced by 50%; however, 2 is obviously not 50% of 5! Because the odds of this error are functionally random with most signals of interest (corresponding to whether or not the smallest bit is a 0 or 1) they can be treated like white noise.

 

Furthermore, changing level by something other than a factor of 2 would introduce additional error: in our example, for instance, attempting to reduce the volume by 10% is impossible without introducing error since there are only 16 valid levels in a 4-bit signal to begin with.

 

However, note that these errors are only introduced at the level of the least significant (smallest) bit. On a 4-bit signal this error can be no greater than 1 part in 16 relative to a full-scale signal. On a 24-bit signal like those used for volume control in most modern devices, this error is limited to 1 part in 16 million. Note that a 16 bit signal (CD-quality) has an inherent digital noise level 8 bits greater than this; volume on a standard end-consumer audio track may be reduced by up to 48dB, or a factor of 8, before the noise from the volume control begins to overtake the minimum amount of noise already guaranteed to be present in the recording. Windows volume set to 2/100 on default settings (the lowest that can be achieved on most computers) is only roughly -33dB; in other words, as long as you are using a 24 or 32 bit output device setting, it is impossible for Windows volume control alone to appreciably reduce the dynamic range of 16-bit audio playback on most computers. For a signal chain containing higher bit depth files or multiple stages of amplification/attenuation the outcome might be different, but for the normal end-user already using default Windows settings, it doesn't matter.

 

TL;DR: If you're just plugging your headphones into your computer, set your Windows output device to 32 bits and don't worry about volume control.

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×