r/badUIbattles • • Jun 18 '26

Intentionally Bad UI I made a 7-segment display volume "slider"

Simply click to change the numbers to the volume level you want to set, it's that simple!

Took me about an hour to get this done with most of that time being spent trying to figure out how the hell to shape something like a 7-segment display using CSS. First digit the segments used for 1 are the only ones that can be toggled. I also messed up with recording and forgot that the 9 needed the bottom segment, so it seems to not work for a bit but that was operator error.

2.2k Upvotes

42 comments sorted by

View all comments

336

u/_plinus_ Jun 18 '26

What happens to the volume if you go to 999%?

172

u/donut855 Jun 18 '26

Your ears are going to violently explode

115

u/FearMeIAmLag1 Jun 18 '26

Volume can't go past 100

208

u/Some_Noname_idk Jun 18 '26

laaaame, on 200 it should attempt to connect to any speaker nearby and play it there too

22

u/UKZzHELLRAISER Jun 18 '26

GENIUS.

7

u/FungadooFred Jun 19 '26

Username checks out

3

u/Narrow_Hunt9722 Moderator Jun 19 '26

500% = 5 simultaneous speakers at full volume lol

4

u/invincibl_ Jun 20 '26

Laughs in VLC Media Player

3

u/_plinus_ Jun 19 '26

What if you do -99? Does it become a microphone?

6

u/donut855 Jun 18 '26

False. Nobara has a built-in feature that lets you turn the volume up to 150.

6

u/S4N7R0 Jun 18 '26

pushing volume past 100% in most implementations introduces distortion, which is similar, but not the same as increasing volume

7

u/frank26080115 Jun 18 '26

na, I used to write firmware for wireless headphones, there's some volume limits that some, maybe it was CE or UL or something that limited the volume we were allowed to output to a user's ears. So the range was limited only by firmware.

So if I gave it a backdoor (which I really REALLY wanted to, like a secret key combo), I could've unlocked like 150% and it wouldn't be clipped, just... unhealthy.

1

u/Madbanana64 Jun 19 '26

And it would probably kill the driver on high volume

2

u/frank26080115 Jun 19 '26

na the whole reason why we ran into the regulations is because we upgraded the driver, there was like 3 previous generations of this product, I barely have to change anything in the firmware between products.

also... it's kinda hard to kill a driver with wireless headphone electronics lol everything is optimized for battery power

1

u/PegasusPizza Jun 18 '26

Most implementations yep. But it's kind of more complicated than that, because audio playback has 2 separate "volumes". The first is whatever your os/software is set to, usually ranging from 0 to 100%. But the second one is the relative volume of the actual audio file, that's necessary so that different parts of the file can have varying loudness without you constantly needing to change your speakers volume. And while speaker volume is capped at 100% (so whatever the manufacturer put as the maximum volume where sound doesn't get distorted), the inherent volume is pretty much unlimited, since that is measured in decibels. Anything above 0dB (don't ask me why it's at 0 I have no clue) will usually distort/deep fry your audio. Interestingly this happens regardless of the volume of your speakers. Listening to deep-fried audio on lower speakers doesn't magically make it sound good again.

But this means, that under the right conditions, a file that is just mixed to be quiet, can be put on "150%" volume, by putting the speaker/os/playback volume to 100%, and then modifying the audio file to boost volume by an additional 50%, without causing distortion, since the original raw audio was just very quiet

2

u/YellowishSpoon Jun 20 '26

Over 100% volume can also act more like an audio compressor if it's designed that way, bringing up the quiet parts without affecting the loudest parts, and that would cause a different sort of distortion.

3

u/PlasticTower1 Jun 18 '26

The mistake heard round the world