Audacity Forum

steve wrote:

Gale Andrews wrote:If you enter the common metadata before Export Multiple, then you save having to enter it 10 times, but you still have to press OK 10 times (one "OK" for each window)

but does that have anything to do with the "bug" or is that just streamlining the work-flow?

As strictly titled no it doesn't have anything to do with the bug (feel free to suggest another succinct title). Perhaps "unintuitive/repetitive metadata handling in Export Multiple"?

"Streamlining the workflow" is definitely part of the problem. Who wants to transfer several albums every day, then click OK on the metadata window for each track? We're asking users to find far too much for a decent experience. They have to find the correct section and correct control in Preferences. And they have to find File > Metadata Editor.

steve wrote:

Gale Andrews wrote:Now imagine a "new user" of Audacity 1.2.6 and a new user of 2.0.3. Factory Preferences in each case. Record from an album and export multiple. Which experience is better, 1.2.6 or 2.0.3?

Sorry Gale, I've not used Audacity 1.x for years, you'll have to remind me. (and I rarely use Export Multiple or metadata so I'm not really up to speed on this stuff).

I never use metadata for my own stuff. The benefit to me of fixing 551 will be a quieter inbox.

In 1.2.6, set up your 12 labels and set up Export Multiple. Press OK. The dialogue for entering tags appears. Track Title and Track Number are prefilled as they are automatic. Enter whatever other common tags you want which will be added for each track. Press OK. "Successfully exported 12 files".



Gale

Gale Andrews wrote:I never use metadata for my own stuff. The benefit to me of fixing 551 will be a quieter inbox.

So that we can avoid analysis paralysis I think that we need to split this into separate achievable tasks. The overview is that we want an efficient work-flow for export multiple, with or without metadata, and we want a convenient and discoverable ability to disable metadata for those users that do not want metadata in their exported files. Agile software development may help us to achieve all of these goals and avoid stalemate.

1. Disable Metadata. This is a simple matter of adding a "switch" to turn it on or off. My vote is to add it to the Metadata Editor, though it could be moved at a later date if it is found to conflict with resolving the other issues.
2. Metadata that is added after Export Multiple has been started is not passed through to the next file. This is the issue as stated in the title of bug 551. I think that this should be a relatively easy fix.
3. Metadata handling makes work-flow for Export Multiple horribly inefficient. This is partly due to bug 551, (metadata is not passed through to the next export), but is not adequately resolved by fixing bug 551.

I suggest that as items 1 and 2 appear to be easily fixable, we do so now.

Item 3 is more tricky, but will certainly benefit from fixing items 1 and 2. Fixing item 1 improves item 3 is metadata is not required. Fixing item 2 improves item 3 if metadata is required, though in this case we would want further improvement.

I would urge for fixing items 1 and 2 now and I believe that doing so will greatly simplify resolving issue 3. It will certainly be better than no action, so in the words of Capt Picard, "Make It So"

(please see also: http://forum.audacityteam.org/viewtopic ... 00#p220500)

Fine words but essentially meaningless without some meat on the bones as to how to do 2) and 3).

For example if we "pass metadata through to the next export multiple file", we have to provide a solution for people who are doing export multiple of compilation albums where the metadata has to be different for each file. This group are of course fairly happy with the current feature.

Leland and I both worked out a fairly similar plan to solve 1), 2) and 3) as outlined in bug 551. We both thought it makes no sense to treat 1), 2) and 3) in isolation. These plans were deemed too complex, but no alternative has been proposed.

I doubt developers will be keen to put "disable metadata" in one place then move it (which confuses regular users and looks like we are changing our minds). What will happen is that 1) will be implemented (which is easy but not very important) but 2) and 3) (which are important) will risk getting kicked into the long grass.



Gale

Gale Andrews wrote:Fine words but essentially meaningless without some meat on the bones as to how to do 2) and 3).

I think you added a link to a small amount of meat http://forum.audacityteam.org/viewtopic ... 00#p220500 after I started my reply. If I missed it in the original reply, sorry about that, though my overall sentiments are the same.


Gale

Gale Andrews wrote:I think you added a link to a small amount of meat viewtopic.php?p=220500#p220500 after I started my reply.

I couldn't add the link until I'd posted the other topic

Gale Andrews wrote:For example if we "pass metadata through to the next export multiple file"....

This feature request is about not using metadata.
The topic here is about Metadata when using Export Multiple.
There will probably be cross-over issues, but to escape the current analysis paralysis I think that it is worth discussing them separately rather than jumbled all together.

The developers appear to dislike patches that do not focus on one thing or "re-architect" too much at once.

@Gale: do I assume correctly that you have collected the votes from here and that I can now delete this thread?

Peter

waxcylinder wrote:@Gale: do I assume correctly that you have collected the votes from here and that I can now delete this thread?

Your assumption is correct.


Gale