Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The worst volume control UI in the world (2017)

uxdesign.cc

Post reply on HN
Print view View original

171–180 of 490 posts

Re: The worst volume control UI in the world (2017)

#171

Post by ygra »

hackthememes wrote: post #142
HelixEndeavor wrote: post #129

Earlier quoted context omitted.

Developers stubbornly refusing to utilize the tools provided by the operating system because they think they can do it better (90% of the time they can't) is one of my greatest pet peeves. You should ONLY ever use your own engine for things like notifications if the particular OS doesn't support them (pre-10 Windows)

I believe that in this case it's simply convenience/laziness to have a single notifications codebase across both operating systems? That and Windows didn't have native notifications when it was first developed. Not that it excuses a big chat application from MS behaving this way, just saying that they probably didn't deliberately choose to re-implement notifications just because they didn't like the OS ones.

Some software also presents that in the settings as the choice between "native notifications, which don't have as many features" and "custom notifications, which have all bells and whistles". And the default of course is the one with more features, not the one that respects your settings. I think Mattermost was where I've seen that distinction.

Re: The worst volume control UI in the world (2017)

#172

Post by mark-r »

jeffbee wrote: post #12
temporallobe wrote: post #7

Car manufacturers are easily the winners here. If your car’s audio system doesn’t have a simple knob you can grab and twist, well, that just sucks.

I can twist mine as much as I like, but the radio comes on instantly and the software that cares about the volume knob being twisted starts about 3 seconds later.

I have a Toyota Camry and I haven't timed it but I think it's more like 10 seconds. Before that neither the volume knob nor the on-off button work.

Re: The worst volume control UI in the world (2017)

#174

Post by _n_b_ »

audiometry wrote: post #151
mianos wrote: post #48

Earlier quoted context omitted.

Teams is the reference for bad UI. Paste a code block. Select a word in the code block. Copy and you get the whole block copied not the selected word. I could write a page of the issues like this. Maybe it would not be so bad if you only used Teams but when you use slack at the same time it is like someone is wacking you in the back of the head every few minutes.

stupid teams chat doesn't even have a 'reply with quote' but yeah, it's got lots of edgy emoticons and gifs.... stupid.

> stupid teams chat doesn't even have a 'reply with quote'

Don’t worry guys, it’s on the roadmap for this month! https://www.microsoft.com/en-us/microsoft-365/roadmap?featur...

Next maybe we can fix issue where if you have the iOS app, you randomly appear available for hours?

Re: The worst volume control UI in the world (2017)

#175

Post by sellyme »

titzer wrote: post #85

The volume controls in Tuxguitar are legitimately worse than some posted here. To adjust the volume of a track, you choose "View > Show Instruments" and then the unlabeled first circle in each row is the volume "knob". It's a "knob" because it is basically a circle with a dot with the 6-o'clock position indicating 0 and the 3 o'clock position indicating maximum. To adjust it, you click and hold (with no visual feedba…

I'm not usually a fan of capital punishment, but whoever said "no, it needs to look like a real instrument knob" is on track to change my stance there.

Re: The worst volume control UI in the world (2017)

#176

Post by nayuki »

mgdlbp wrote: post #111
roland35 wrote: post #30

The subreddit /r/Programmerhumor sometimes had a whole bunch of memes around volume controls, but there are often times other funny themes that can go on for weeks... - bad phone number inputs - how large node packages can get - software interview process - backend vs front end engineers And my favorite meme was when they parodied the Hawaii missile alarm back a few years ago: https://www.reddit.com/r/ProgrammerHumor…

There's an entire subreddit for bad UI: https://www.reddit.com/r/badUIbattles/top/?t=all

I like the volume control with imaginary numbers: https://www.reddit.com/r/badUIbattles/comments/ey74ya/volume...

Re: The worst volume control UI in the world (2017)

#177

Post by sellyme »

HelixEndeavor wrote: post #138
FriedPickles wrote: post #27

Earlier quoted context omitted.

Ford moved volume control to the touchscreen, but people wanted a knob. Solution? They stuck a knob to the touchscreen. Under the knob is an artificial "finger" that touches the screen. I haven't used it personally so all I can say is it's a hilarious solution. https://techcrunch.com/2020/12/02/im-obsessed-with-the-ford-...

It looks cool, and that's the only nice thing you can possibly say about it.

It's a work of genius, that's just not necessarily a compliment.

Re: The worst volume control UI in the world (2017)

#178

Post by koyote »

mianos wrote: post #48
stefan_ wrote: post #36

I think the worst UI is simply the Teams one, because it presents as an app volume control but then simply controls the global device volume . Fuck off, you are not the only app running. But that comes second to the microphone gain control, which Teams similarly exerts unilateral control over - only this time through an automated algorithm that for some microphone types just ends up muting them entirely. It's wild, y…

Teams is the reference for bad UI. Paste a code block. Select a word in the code block. Copy and you get the whole block copied not the selected word. I could write a page of the issues like this. Maybe it would not be so bad if you only used Teams but when you use slack at the same time it is like someone is wacking you in the back of the head every few minutes.

> Paste a code block. Select a word in the code block. Copy and you get the whole block copied not the selected word.

I feel like this used to work properly until a month or so ago.

The worst bug I've seen, and this is also something that only started happening in the last several months, is select messages simply not appearing! So basically I open my computer in the morning and look at Teams and it'll have messages from overnight. EXCEPT some messages did not make it, like, at all. There was a whole thread that had replies that were simply not visible to me. I even replied to that thread and on my screen the reply appeared right after the last visible message whereas for everyone else it appeared after the 40 or so messages that came in overnight.

I haven't been the only one to run into that issue either. Restarting Teams is the only thing that brought the messages back.

Now that's what I call a critical bug! Who knows how many things I've missed.

Re: The worst volume control UI in the world (2017)

#179

Post by jiggawatts »

fomine3 wrote: post #34
jiggawatts wrote: post #24

Earlier quoted context omitted.

This is in the same category of error as most programmers thinking that sRGB uses a linear light model. They try to do arithmetic like blending or blurring on the raw image data this inevitably does the wrong thing. Similarly, most non-AAA game engines ignore the sRGB tone curve and treat all inputs and outputs as if they were linear, which results in unexpected brightness shifts in textures. Up until very recently,…

Could you provide good documentation about such thing?

I really liked this article: https://bottosson.github.io/posts/oklab/

OKLAB is a perceptual colour space, which is really useful for things like colour-picker tools, image editor controls, web development, CSS styles, etc...

You can use this kind of colour space to make two colours that are equally bright and equally saturated, but exactly 180 degrees apart on the colour wheel. If you use this instead of RGB hex codes, you get much better looking results. It'll make your app or web page "pop" with minimal effort...

Re: The worst volume control UI in the world (2017)

#180

Post by sellyme »

bombela wrote: post #117
cm2187 wrote: post #90

The volume control in VLC deserves a place somewhere in this list. It works fine if you click on it. But if you use the keyboard's up/down arrow keys, it seems to severely rate limit how fast you can increase or decrease sound. Not great when you need to stop a big bang from waking up your neighbors.

It also can go above 100%. And it seems that I can never get it back to 100% if I move it by mistake. Even using the keyboard it will never comes back to exactly 100%. Maybe 103%, or 98%. It drives me crazy.

> And it seems that I can never get it back to 100% if I move it by mistake.

Move it to 0%/200% by whatever means you'd like, then use keyboard increments to return it to 100%.

Post reply on HN