| From "Richard Ash (audacity-help)" <richard@...>
| Mon, 21 Jan 2008 16:04:27 -0000 (GMT)
| Subject: [Audacity-devel] Export multiple colon wrongly accepted
| as legal character
| > Gale Andrews wrote:
> >I do have one suggestion
> > though for when we add the "pop up Metadata Editor" checkbox to
> > the Export Multiple dialog. Although having separate grids for each
> > file gives a lot more flexibility, some users are probably not going
> > to appreciate having to now go through 12 - 15 grids for their
> > album by one artist if they only want the auto-filled Track Title
> > and Track Number fields.
> > Is it possible for the control to have
> > three choices (would it then be a radio button?)
> > Show/Hide Metadata Editor
> > * Hide
> > * Show for first file only, use for remaining files
> > (horrible wording, but basically the old behaviour which
> > users are familiar and largely happy with)
> > * Show for all files
> > As second best, can we put up with losing the Hide option?
> > (means one more "OK" if you don't want tags).
> > Otherwise, I think users may rapidly get cheesed off with having to
> > enter the same field e.g. Year, Album for each fie. Either way, is
> > it possible to pass through all the non-automatic text fields to the
> > next grid, in the way that Genre is passed through? For example,
> > on a compilation album the year may be the same for all files, but
> > other fields might not be.
> If you filled the constant feilds in using Open Metadata Editor before you
> ran export multiple, you'd find they were filled in and you just pressed
> OK each time. Given this I would see the options "prompt for all" and "don't
> prompt" as enough - if you want to enter settings for all the tracks, you can
> enter those as project data....
> The export multiple boxes are deliberately independant in the export
> multiple case so they don't interact with each other (otherwise only the
> last set would be remembered and used).
That doesn't follow does it? If you set a field first in File > Open
Metadata Editor, you can still change any occurrences of that field and
each field will still be respected.
> They could be copied from the previous one not the project data, but
> I'd see that as a load more hassle if you want to change just odd tags
> for odd files (e.g. adding soloists to artist fields).
This assumes that you actually want the extra step of opening the
Metadata Editor first. This isn't necessary with 1.2.6 if you only do
one export, and isn't necessary at all before the latest change. The
majority of people I think will be content with the same information
for all files (otherwise there would have been lots of requests for
individual metadata grids for each file). While it will work with a
"Prompt for all" or "don't prompt" checkbox on the Export Multiple
dialogue, and having to open the Metadata Editor before you do
Export Multiple if you want to add some common fields for all
files, this will be a major change in behaviour and a large support
headache as a result.
Very typically a user will perhaps just want to add the Album tag to
all tracks. Coming new to 1.4.0, he will obviously choose to "prompt",
then will have to enter the Album name as many times as he has
tracks. Even when he understands that he now has to open the
Metadata Editor first, it's an extra step that isn't in the same process,
and a worse experience as a result IMHO.
If we don't want three "prompt" options then better to have "prompt
for first" or "prompt for all" and people such as yourself who don't
want the Metadata Editor can turn it off altogether with the (needs to
be fixed) Import/Export Preference.
> (which reminds me - why isn't it Edit > Metadata?)
I suppose if Metadata Editor was under Edit it would have to go at the
bottom as it is not a command for editing the tracks, so it would be