| From Richard Ash <richard@...>
| Sun, 28 Dec 2008 22:28:06 +0000
| Subject: [Audacity-devel] Metadata before filenames?
> On Wed, 2008-12-24 at 16:10 -0600, Leland wrote:
> > Martyn Shaw wrote:
> > > Hi Leland
> > >
> > > There was a bug listed on the Release Checklist (copied below). I
> > > think the problem was that if the same file name is requested, the old
> > > file gets renamed. If the Metadata is then asked for and the user
> > > cancels, the export is canceled but the file has the wrong name.
> > >
> > > Make sense? Feel free to change it again, remembering this issue.
> > >
> > Gale likes it as-is, so I'm inclined to leave it. But, showing the
> > Metadata before doesn't give us a chance to NOT show it based on the
> > type of file to which the user is exporting.
> > But, I'm kind of biased since I don't use tags and feel the thing just
> > gets in my face too often anyway. :-)
> I'm inclined to agree, now that I've stopped messing about in Export
> multiple which forces the operations to occur in the old order (because
> you set up the file names in the main dialogue, then it shows you the
> metadata dialogues when you do the export).
In any case, Export Multiple has a P2 problem with overwritten files
being silenced when you carry through with the export and overwrite
to the same name.
> I would normally turn it off altogether, but to me asking to export a
> file and being given the metadata dialogue is confusing - I wonder how
> many new users will never work out they have click OK to actually say
> where to save the file? So although I can see the logic of Audio > Metadata >
> File, I'm not 100% convinced we have a good reason for changing the way
> it works previously. I hope finding an alternative solution to the file name
> problem is relatively simple (basically, don't leave handling the rename
> to wx, but detect the need and do it ourselves after the metadata step)...
I still think Metadata before filename makes sense in theory. But I've
already seen enough users not realising they must OK the Metadata
Editor (or pressing Save in the Editor and wondering why the MP3 exports
as XML) to change my mind. It's not going to work.
If so, essentially that means the overwrite problem with straight WAV
exports is back as a P2. At least if we fix that, Export can have metadata
after filename like Export Multiple, and we can kill the Metadata Editor
where inappropriate (such as with command line export).
> Or we could be revolutionary and change the meaning of the Cancel button
> in the metadata window to mean "no metadata thanks, but carry on with
> the export", where as OK means "export this with the metadata I've given
> you". I remember at least one request for something like this from
> someone who was finding that users were exporting their file, getting
> the save dialogue and choosing the name, then clicking cancel in the
> metadata dialogue because they thought their file had been saved and the
> program had moved on to something else (the fact that a runt file got
> written at the time didn't help). If the user really panics and decides
> after pressing save they didn't want to they can always press cancel in
> the progress window ...
> The use-case for this is if you want a "clean" file with no tags for
> compatibility with other players, but don't want to try and strip the
> tags from your project permanently (either because you aren't convinced
> about the effectiveness, or because you want them for later exports).
> CoolEdit used to have a check-box in it's save dialogue which prevented
> any tags being written to the file, their use-case being for CD burning
> applications which didn't know about tag chunks in WAV files and wrote
> them as audio data ...
I think that shows that unless the Metadata is integrated into the
Export file window (which I've seen occasionally with a small height
file window and only about half a dozen tags), someone is always
going to be confused.
Anyway, I like Richard's idea, but think it will never be clear enough
that "Cancel" means "export no tags, but leave them in the editor".
I'd think having a checkbox like CoolEdit, but no Cancel button would
be far less confusing.
If user cancels progress dialogue while exporting to the same WAV
file they're reading, have we still got the same problem?