Metadata Panel/Editing Suggestions
Posted: February 18th, 2019, 20:52
I'm really looking forward to the metadata editing features. Here's a couple of humble suggestions, based on the current (Resonic Pro 0.9.2b) metadata panel:
- Offer users the option of displaying a user-defined configuration of metadata tags, similar to how columns are chosen for display already.
- Offer users the option of storing and recalling such configurations (columns and metadata panel). This would facilitate switching between workflows for managing sample libraries, tagging MP3s vs. WAV files for distribution, etc.
- Offer users the option of displaying tag fields with empty values. As is, empty fields disappear from the panel, making the display a bit herky-jerky when flipping between audio files. Adobe Bridge (media manager) offers a good example - all chosen metadata is displayed, whether it contains values or not.
- Offer users the option of a "dense" metadata display, with one tag name and value per line (in two columns). As is, each tag consumes at least two lines - one for the tag name and another for the value(s).
- When multiple files are selected, metadata tags with disparate values should display "multiple values" or similar. As is, values for one of the selected files is shown, and suggests that all of the selected files share the same tag value, when in fact, they do not.
- Non-editable metadata tags (e.g., bitrate) should be denoted as such, either by typeface or color, so that those of us who've started our weekends early - don't ask - aren't dumbfounded by the fact that we can't select those fields for editing with our mouse pointers.
- When multiple files are selected, editing metadata tag values should update those tags in all selected files, but with a warning, "You are about to modify X files. Are you sure?"
- Being that the aforementioned operation can be very destructive, many levels of undo would be very nice, if not critical. This feature is available in Mp3tag, for example, and has saved my bacon on numerous occasions.
- Offer users the option of searching metadata tag values when filtering. As is, filtering appears to work only on file names.
- Offer additional filtering operators, such as "kbps:>=6144" or "comments:=''" (is empty) or "chn:=1" etc. This way, users can filter for audio files that are at least 24 bits, 5.1 surround, missing critical tag values, etc.
- Offer users a filter history or the option of remembering or "favoriting" certain filter strings. This way, one can simply choose "Broadcast Surround" from a list, instead of typing "Path:masters bits:>=24 Hz:>=48 chn:>=4," for example.