←back to thread

917 points cryptophreak | 1 comments | | HN request time: 0s | source
Show context
fschuett ◴[] No.45763249[source]
> Free audio editing software that requires hours of learning to be useful for simple tasks.

To be fair, the Audacity UX designer made a massive video about the next UX redesign and how he tried to get rid of "modes" and the "Audacity says no" problem:

https://www.youtube.com/watch?v=QYM3TWf_G38

So this problem should get better in the future. Good UX (doesn't necessarily have to have a flashy UI, but just a good UX) in free software is often lacking or an afterthought.

replies(4): >>45764008 #>>45764615 #>>45768773 #>>45769218 #
eviks ◴[] No.45769218[source]
the "modal disruption" is misguided - he cites as the challenge a very poor implementation in a MS app where the modes were barely visible!!! That's not a proof that modes are bad, just a statement that invisible information makes it hard for the users to adapt! Brushes (another mode he cites as great) are great precisly because their state is immediately visible in your focus area - your primary pointer changes

Now he got rid of the modes by adding handles and border actions - so 1) wasted some space that could be used for information 2) required more precision from the users because now to do the action you must target a tiny handle/border area 3) same, but for other actions as now you have to avoid those extra areas to do other tasks.

While this might be fine for casual users as it's more visible, the proper way out is, of course,... MODES and better ones! Let the default be some more casual mode with your handles, but then let users who want more ergonomics use a keybind to allow moving the audio segment by pressing anywhere in that segment, not just in the tiny handle at the top. And then you could also add all those handles to visually indicate that now segments are movable or turn your pointer into a holding hand etc.

Same thing in the example - instead of creating a whole new separate app with a button you could have a "1-button magicbrake" mode in handbrake

replies(3): >>45769514 #>>45771165 #>>45774283 #
TazeTSchnitzel ◴[] No.45771165[source]
> wasted some space that could be used for information

The space is used for information. The fact clips in Audacity finally have names and you can see those names is a fantastic improvement. The space taken up by the clip title is the handle.

replies(1): >>45771263 #
1. eviks ◴[] No.45771263{3}[source]
Indeed, it's fantastic to see those useful

"Audio 1 #1" "Audio 1 #1" "Audio 1 #1"

"Audio 1 #1" "Audio 1 #1"

names replacing the audio wave height!

But sure, if you need names permanently right there and are ok to lose space to show them, and if the handle is inconveniently small to only fit the text, then yes, you wouldn't lose space in that case. You'd only have other issues.

But that coupling likely has other design implications, e.g., you're unlikely to get an option to only show names on hover instead of having a bar, or to show names as an overlay (in many cases the names aren't that long to need to take the height of the the whole segment)