
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
OSX 10.7
|
|
Issue Links:
|
Relates
|
|
This issue is related to:
|
|
PICARD-255
The colors and list position used to indicate when tags are being added, changed, or removed is inconsistent when multiple files are selected
|
|
|
|
|
|
|
|
1) Load one disc a multi-disc set into picard (but not the complete release). Verify the tags are all current.
2) Select the album.
RESULT:
The values in the "Original Value" column are based on the actual files that have been loaded, while the values in the "New Value" column are based on all tracks on the album. This can cause some tags to indicate they need to be changed when they don't.
For example, say you load Disc 2 of a set:
- In the Original Value column, the Disc Number will be 2, but in New Value it will say "(different across ## items)". It will also be yellow and listed at the top if "Show Changes First" is enabled.
- Say a track on Disc 1 has a Lyricist credit, but nothing on Disc 2 does. The New Value column will indicate that the Lyricist tag needs to be added – it will have (missing from ## items) in green, and will be listed at the top.
|
|
Description
|
1) Load one disc a multi-disc set into picard (but not the complete release). Verify the tags are all current.
2) Select the album.
RESULT:
The values in the "Original Value" column are based on the actual files that have been loaded, while the values in the "New Value" column are based on all tracks on the album. This can cause some tags to indicate they need to be changed when they don't.
For example, say you load Disc 2 of a set:
- In the Original Value column, the Disc Number will be 2, but in New Value it will say "(different across ## items)". It will also be yellow and listed at the top if "Show Changes First" is enabled.
- Say a track on Disc 1 has a Lyricist credit, but nothing on Disc 2 does. The New Value column will indicate that the Lyricist tag needs to be added – it will have (missing from ## items) in green, and will be listed at the top.
|
Show » |
Sort Order:
|
Are you suggesting "new value" should not take tracks into account at all?
The first issue is a bug that could (and should) definitely be fixed regardless, but the second one seems inherent to the ability to edit track metadata.