There isn’t a self-respecting podcaster or YouTuber alive who hasn’t overspent ridiculous money on that style of microphone, when the one in their crappy boxed earbuds would do just fine.
Literally Google for “podcast mic” and you’ll get a picture of a $100 Blue Yeti or a $200 Røde.
It seems like the best solution would be to take a page from the play/pause button in media apps and change the icon itself based on the current state of the toggle. A mic icon with no slash means you’re live; a mic with a slash means you’re muted.
Fair point. The play/pause toggle icon pretty universally tells you what clicking on it will do, whereas what I suggested indicates the mic’s current state. (After looking closer, this is what Slack does too, but with the potentially confusing addition of a different background color.) Given that most of these UIs combine the mute toggle with other actual buttons like “hang up” (which has its own increasingly-anachronistic icon, incidentally), following the full UX pattern of the play/pause toggle and having the icon indicate the action to be performed would be a better approach.
I would say for added clarity, the toggle should be combined with some other separate visual indicator that can display the mic’s current state. Discord is halfway there with their UI since it shows a row of buttons at the very bottom, and a row of icons in the chat channel UI that indicate state. In Discord’s case, the button icons should be flipped so that “mute mic” and “mute server” show what they will do, rather than what they are doing.
I suspect that this would be as situationally inappropriate as it would be technically effective; but abandoning attempts at symbolism focused on the state of the microphone in favor of symbolism focused on whether the user has been silenced or not seems like it might work.
I’m just not seeing ballgag icons making it to release in most software development environments.
Blue even has an ad for their Yeti desktop mic using a cooking show as a use case, a cooking show, where the cook is talking while cooking across the room from the mic. Groan.
Good Grief. Use a body worn mic, not a desktop mic.
The HCI community has worked to expand and improve ourconsideration of the societal implications of our work andour corresponding responsibilities. Despite this increasedengagement, HCI continues to lack an explicitly articulatedpolitic, which we argue re-inscribes and amplifies systemicoppression. In this paper, we set out an explicit politicalvision of an HCI grounded in emancipatory autonomy—ananarchist HCI, aimed at dismantling all oppressive systemsby mandating suspicion of and a reckoning with imbalanceddistributions of power. We outline some of the principles andaccountability mechanisms that constitute an anarchist HCI.We offer a potential framework for radically reorienting thefield towards creating prefigurative counterpower—systemsand spaces that exemplify the world we wish to see, as wego about building the revolution in increment
Sond quality is what separates an enjoyable and engaging podcast from a podcast or video that I’m strangely tempted to turn off within the first minute or two. I often act on that impulse.
I learned very quickly to ignore bloggingheadstv (despite being linked to all the time in the websites I enjoyed) because they don’t give a fuck about soundquality, and they use crappy boxed earbuds. Are they good? Are they irrelevant? I don’t care because the sound quality was crap, and probably still is crap.
What’s even worse is the newer ones where no light = not muted, red light = muted. This trips people up all the time in conference rooms (myself included). It’s too easy to assume “no light is no worky”. It’s just poor design all around.