usability review of the mixdown process

Bug #350628 reported by Jeff Fortin Tam
2
Affects Status Importance Assigned to Milestone
Jokosher
Fix Committed
High
Michael Sheldon

Bug Description

Here is a usability review of the steps required to mixdown a project. Attached is a demonstration of what a user would have to go through to export a simple timeline, with associated (slightly exagerated) remarks/thoughts that could occur to the user.

My goal would be to reduce the number of steps and to reduce confusion.

Here is the list of changes that need to be done:

======= visual feedback =======
Buttons such as Remove, Mixdown, Preferences, do not convey their contextual nature. When they cannot be used, they should be set gtk.insensitive.
- when no action is selected, the Remove (action) and Preferences buttons should be insensitive
- when no configured action is set, the Mixdown button should be insensitive
- when no mixdown profile exists, the Remove (profile) button should be insensitive
- vice versa when the above becomes false

======= appropriate widgets and defaults =======
The "export" action uses two widgets for selecting the local output folder. Instead, it should be a GTK filechooser button (there's a widget made exactly for that, with a property to make it select only folders).

The last used folder should be remembered across sessions. Otherwise, by default, it should be ~.

======= useless clicking ========
Do not show a "successfully created mixdown foobar" dialog. It's useless. See also http://www.codinghorror.com/blog/archives/000676.html if you want a humorous take on the issue.

Other than that, the rest is pretty good! ;)

Revision history for this message
Jeff Fortin Tam (kiddo) wrote :
Revision history for this message
Laszlo Pandy (laszlok) wrote :

Excellent excellent work. You are on fire with the bug reporting today.

We have been intending to replace this dialog for a long time, but it hasn't been done yet because it would be a bit of work to make is really simple and just as flexible. This dialog was designed from a really high level, without a whole lot of attention to detail. It was designed for flexibility, and now serves as a very good example of a much too general solution.

The original idea was to allow extension developers and users to easily extend this dialog. In its current form with two types of extension actions (one which is rarely used) it is pretty useless. If someone can propose some ideas for how to streamline this dialog for the use case of simply exporting to mp3/ogg/flac/wav and still have the flexibility for extra actions this would be great. If not, I vote we just scrap it and put in a Save As dialog with an extra combobox to select format type. Comments?

Changed in jokosher:
importance: Undecided → High
milestone: none → 0.12
Revision history for this message
Jeff Fortin Tam (kiddo) wrote : Re: [Bug 350628] Re: usability review of the mixdown process

Well, for the KISS principle, I would be in favor of just scrapping it
and making a save dialog that asks for the format type. I can easily
design glade mockups if you need usability assistance on that front, but
then, I tend to agree that this dialog as it is now has been
overengineered :)

Ps: I've read another bug report that basically said mixdown was a weird
term. Have you considered something more general such as "export"?

Revision history for this message
Laszlo Pandy (laszlok) wrote :

"Mixdown" is a term used by Jono Bacon. I don't think he invented it, but I agree its not the most common. The only issue with the term export is it can also refer to saving the project in a different file format. For example we have considered allowing Jokosher to export your project to a single file (basically just a tarball) so you can easily send it to your friend. Say for example we got the ability to save in Audacity project format, that would be what I call "Export".

However no other file formats have been implemented yet, and won't be in the foreseeable future so I have no problem just using export to refer to rendering to a single audio file.

Revision history for this message
Michael Sheldon (michael-sheldon) wrote :

In terms of making the mix down dialog better for simple uses I'd thought of perhaps adding an "Always ask me where to save this file" option to the current "Save to Local/Remote" options, then providing 3 mixdown profiles by default (Ogg, Mp3, Flac) that make use of this option. So the user can just go to "Mixdown As -> Flac" and have a dialog pop-up asking them where they want to save. So unless the user really wanted to do some custom things they never have to go through the more complicated mixdown setup procedure.

Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

Yes, providing some default profiles would at least be more useful to
the majority of users, but if that's the case (instead of tearing
everything down and just using a save dialog with a filetype combobox),
I guess that means you would have to implement the suggestions I made
initially :)

Changed in jokosher:
status: New → Fix Committed
assignee: nobody → Michael Sheldon (michael-sheldon)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.