4 ms·
The ideal workflow for that would be keeping open, until dismissed, a noise reduction GUI widget (like the ribbon in Microsoft Office or the side panels in Blen
by HelloNurse 6y ago
The ideal workflow for that would be keeping open, until dismissed, a noise reduction GUI widget (like the ribbon in Microsoft Office or the side panels in Blender), guaranteeing that you only dig through the menu once per session; then selecting audio (or using an existing audio selection) and stating that it is the source or the noise reference; then apply and undo noise reduction after seeing that both mandatory inputs have been set.
Not rocket surgery, but a very deep UI redesign compared to a dialog box.
- simias 6y agoIndeed. I think I like Inkscape approach for that: you can just stack whatever you want in panes to the sides of the work area, this way you can keep the often used tools handy and easily swap them in and out as needed. It's fairly intuitive and rather flexible.
- HelloNurse 6y agoIt's a traditional approach in image editors (other notable examples include Photoshop, CorelDraw, GIMP, Krita, Pixia, and as remarked in other comments AzPainter) but not in audio editors. I blame the traditional prevalence of highly self-contained plugins and little scripts (for example, Audacity has Nyquist scripts) that entail generic host applications that only really care about the subset of features that cannot be delegated to plugins (for example, Audacity has the waveform view).