Issue Details (XML | Word | Printable)

Key: PICARD-73
Type: Sub-task Sub-task
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: Scott Hunter
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Picard
PICARD-171

Original date field in ID3 2.3 causes file to be out-of-date immediately after saving

Created: 28/Oct/11 03:26 AM   Updated: 29/Apr/13 05:42 AM
Component/s: Tags & Metadata
Affects Version/s: 0.16
Fix Version/s: None

Environment: Windows 7
Issue Links:
Duplicate
 


 Description  « Hide

If I add a file, save it, remove it, and immediately re-add it, the file shows up as requiring a save (no checkmark). I dug into the python code and it would appear that it's the original date field that makes the file dirty. I uncommented the print at file.py line 360, and the offending metadata item that causes similarity to be not 1.0 is:

originaldate [u'2004-06-07'] [u'2004']

It would seem that this is because originaldate is stored as TORY in ID2.3 which only holds a year, so when it's read back in from the freshly saved file, it doesn't match.



Sort Order: Ascending order - Click to sort in descending order
Scott Hunter added a comment - 28/Oct/11 03:32 AM

I should have mentioned that using ID3 2.4 is OK, as expected. I guess I should just switch to 2.4 anyway.


voiceinsideyou added a comment - 28/Oct/11 06:12 AM

Thanks for doing the digging; will make it much easier to find a workaround.