Set deprecated ID3v2 frame TYER when Mp3 exported

Bug #794308 reported by Guillermo Guerrero
This bug report is a duplicate of:  Bug #691233: mp3 export fails to save id3 tags. Edit Remove
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
audacity (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: audacity

How to reproduce it:
------------------------------
1) Open a track on the audacity program
2) Export it as Mp3 file (may need the Mp3Lame library installed). Click save.
3) When Metadata dialog is open then set the field year. Save it.

You got a Mp3 file with a ID3 v2.4 TAG but containing the Date frame as TYER (deprecated on this version)

This bug makes other read/write ID3 libraries to fail. For example 'python-eyed3' module.
So far I'd test with a Mp3 track by exporting it previously setting the year as 2011. Then, when we try to read it from the eyeD3 module we get:

>>> import eyeD3
>>> tag = eyeD3.Tag()
>>> tag.link('MyMp3_audacity_metadata_year_edited.mp3')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/pymodules/python2.6/eyeD3/tag.py", line 474, in link
    padding = self.__loadV2Tag(f);
  File "/usr/lib/pymodules/python2.6/eyeD3/tag.py", line 1359, in __loadV2Tag
    raise TagException(str(ex));
eyeD3.tag.TagException: Invalid frame id for DateFrame: TYER

Was thinking to report a bug to the python-eyed3 mantainers but looking at the official ID3 site we got that this frame is certainly removed on the IDv2.4.
Look at the deprecated frames from the site: http://www.id3.org/id3v2.4.0-changes

"TYER - Year
    This frame is replaced by the TDRC frame, 'Recording time'
    [F:4.2.5]."

So basing on that, the eyeD3 Python module seem to act properly (anyway would be great to have an "autorepair" method on this module code)

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in audacity (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.