View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000055 | MMW v4 | Main Panel/Toolbars/Menus | public | 2003-02-07 04:26 | 2006-07-13 17:18 |
| Reporter | rusty | Assigned To | |||
| Priority | low | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0000055: Tree Feature: New Inconsistent Tags (done) and Incorrect Filenames nodes (not done) | ||||
| Description | As a by product of bug 0000010 (and other db synchronization/property guessing bugs), the current 'Songs to Edit' node does not have any subnode that shows all songs in which the tags don't match the DB, making it difficult for the user to figure out which songs need to be 'cleaned'. This can be alleviated with a new node call 'Inconsistent Tags' which functions as follows: -The user clicks the inconsistent tags node and the application does a live comparison of the DB vs. tags and lists all titles for which inconsistency exists. He/She can then modify the DB entry/Tags as appropriate. (Everytime the user goes back to this node, a new live query would have to be done). | ||||
| Additional Information | This issue was first brought up in bug #89 and 0000010, however, I've created a separate entry since it is a distinct (though related) issue. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Note: I think I specced it out slightly incorrectly--the feature should identify all Files for which there is an inconistency between: -DB and Tags -Filename and tags |
|
|
Ok, wouldn't it be better to make two nodes for this? One for each comparison: - DB and tags - DB and filename (is better than filename and tags, I think) In the second case we need to let the user specify the mask he/she wants to use for the filename (always show a dialog with a drop-down list where he/she can select a mask? By default show the last one used, so that user would usually need to press Enter only). |
|
|
I think your suggestion makes more sense (DB&tags, BD&filename). Re. the feature to let the user specify the mask, I wouldn't bother with this at this point, since whenever the user goes into this node, they'll have the properties view enabled, from which they can decide exactly what they want to do (most of the time, I think they'll be going through the items one by one, since it's unlikely that all of the songs have the same kind of inconsistency). |
|
|
I think that it is necessary to enter the mask in order to find out which songs belong to the "DB&filename inconsistency" node. E.g. when user selects "%a-%l", all songs that do not follow this mask would be shown. Is it what you meant? BTW, how to call these nodes? |
|
|
I was thinking that we would add an item into the setup menu (on the 'Library' pane along the lines of: |--Save Files-------------------------------------------------| | For saving converted files, and validating filenames, use | | the following format by default | | <Artist> - <Album> / <Artist> - <Title> | Implemented as dropdown list. | ------------------------------------------------------- | | | ___________________________________________________|Add | | ------------------------------------------------------- | |-------------------------------------------------------------| Note: MusicMatch has a much friendlier implementation of Masks, which could also be considered. Re. names for the nodes: -Inconsistent tags -Inconsistent filenames I'd place both of these directly sub to 'Files to Edit' |
|
|
Yes, I think this is possible. Re. MusicMatch - I have played with it a little (I plan to do more). It definitely has a number of features, but Songs-DB still has some things that people probably like - is reasonably simple, while still powerful enough. This also applies to masks - MusicMatch implementation is unecessary limiting. Masks in Songs-DB seem to be quite easily understandable by users. |
|
|
If we decide to use AlbumArtist field in Songs-DB then I propose not to include it in the DB-Tag consistency check, because all tracks would be incosistent by default. This fields seems not to be used by applications, so this is a minor issue. |
|
|
Note: per metabug #89, 'Inconsistent Tags' node should be changed to 'Out-of-date Tags' (so the user easily associates 'Update Tags' with this node |
|
|
'Out-of-date Tags' is fixed in build 453 (with highlighting of different values). Re. Out-of-date filenames - We should review how should this work - it is probably too strong to require all songs to follow the same pattern (some folders contain miscs songs, which are probably best named as 'artist-title', while albums can be for example 'artist\album\#-title'. Maybe a list of acceptable masks would solve it and this node would list only tracks which would not follow any of these masks. |
|
|
Re. Inconsistent Filenames, I like your suggestion, although I think that in the short term, a single mask would be fine. No big deal either way... |
|
|
I changed the priority, because the main task has been done, the rest is not much important in my opinion. |
|
|
This issue has mostly been resolved. Opening a new bug to cover the remaining issue. |
