The worst that actually existed as a shipping product was probably the QuickTime player that had a skeuomorphic thumb-wheel: http://hallofshame.gp.co.at/qtime.htm
The worst volume control UI in the world (2017)
311–320 of 490 posts
Re: The worst volume control UI in the world (2017)
#312Earlier quoted context omitted.
I've had that happen on Slack mobile so much I just don't trust it anymore. I always tell people (even if it seems counterintuitive) to email me when things are urgent because very rarely (or not, since I can't tell), it's decided not to show me critical messages.
I get that a lot. A DM arrives, there's a red blob with a number next to the sender's name, but the actual message doesn't appear.
Re: The worst volume control UI in the world (2017)
#313I find Apple's suggestion to use Siri to control the volume on the AirPods Pro [0] to be worse than some of the ideas on that page. The idea of having a spoken conversation in public in which I must request a volume change via a branded AI (and then repeat that request multiple times if necessary to reach my desired volume) just feels humiliating. [0] "To change the volume, say 'Hey, Siri,' then say something like 'T…
It's like how redbull reps tell the barkeep to only pour half the can In the drink and give you the can to hold and carry around. It makes you into a billboard for the product talking to Siri in public.
Re: The worst volume control UI in the world (2017)
#314Runner up is the touch bar on MacBook Pro. I really miss the simple volume up/down buttons.
Honestly the way the touchbar handles volume is about the only thing I like about it. It's also literally the only thing I use on it besides the software "ESC" button.
I probably use this feature 10-20 times a day, and it would be a noticeable irritation for me if it was key based. I am disappointed they're dropping the touchbar in upcoming M1x/M2 macbooks, I would definitely have preferred a touchbar. Apple, are you seeing this?
Re: The worst volume control UI in the world (2017)
#315I 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…
Just in case an MS engineer is reading these Teams gripes… On Mac, Teams does not honor system-level Do not Disturb. So when I turn off notifications during a presentation at work and my friend sends me snarky comments about our boss…
Re: The worst volume control UI in the world (2017)
#316Earlier quoted context omitted.
Teams’ notifications on Mac are an ongoing debacle. Because they are Microsoft’s own implementation, rather than using the system API, not only do they not respect DND, they also helpfully get lost behind other notifications that come in from properly designed applications. According to the Microsoft admin updates I’m subscribed to, native notifications on Mac have been in a beta channel for months, with a full rollo…
To add insult, the notifications are a separate window on macOS. So when you use cmd+tab to switch _to_ Teams, you might end up in that notifications window. Even when there are no Teams notifications, that window remains. This is very painful when in full-screen mode, as cmd-tabbing to Teams simply doesn’t work. I’m on the beta where you can switch to native notifications, but they’ve only implemented that (poorly)…
My main question is, why are people still doing desktop apps in JS? (Yes, I know, cross-platform... There are other ways to do that.) They always end up breaking with the native UI conventions on the host OS, and they're stupidly resource hungry.
Re: The worst volume control UI in the world (2017)
#317I'd look at something he'd done with controls snaking left and right as you scanned down the dialog, and I'd (sigh to myself internally, and) say "OK, go ahead and clean it up and check it in", and he'd look confused and ask "clean what up?"
He was actually UI blind in the same way some people are face blind...
Re: The worst volume control UI in the world (2017)
#318Nearly all volume controls suck because by and large the software world is ignorant of the fact that loudness scales logarithmically. 99.9% of volume controls scale the output linearly.
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,…
Re: The worst volume control UI in the world (2017)
#319Earlier quoted context omitted.
> 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…
Outlook also has had this problem of emails just not showing up. Sometimes it takes a whole day for an email to arrive. Amazingly low quality for such a wide used product. MS in particular has the habit of actually introducing small bugs like this regularly through their usual updates. It's infuriating. One day something works the next it just doesn't. I know people who never update their machine because of this. Can…
HA!
I was just testing a VR app that has a Windows component when things started failing in VR. I took off my headset and noticed my test machine going through power-on self test.
"Oh crap!", I thought, "a bug caused the system to reboot".
Nope. Just Microsoft deciding it's time to apply some updates. Doesn't matter that I scheduled for a time that I wouldn't be testing.
I've NEVER been able to successfully gain control of this, despite reading up on it and doing all the recommended things.