Allow EasyID3 to write id3v2 tags.

[GoogleCodeExporter]

Calling save() on an ID3 object will only write id3v1 tags.
Normally, this is fixed by calling update_to_v24() prior to the save.

EasyID3 can't do this, the only current workaround is to reopen up the file 
with an ID3 constructor, and call the appropriate method.

Original issue reported on code.google.com by jiawei.h...@gmail.com on 17 May 2011 at 10:39

Attachments:

• easyid3.py.patch

[GoogleCodeExporter]

Can you please describe the problem you're having? Calling save() saves all 
fields. update_to_v24() is called to translate 2.2 and 2.3 tags into 2.4 tags, 
not 1.x tags into 2.x tags - and EasyID3 will call it internally anyway, since 
it's part of the default ID3 loading path. The method should be called only if 
you passed translate=False to ID3.load, which is impossible for EasyID3 users.

The goal of EasyID3 is to expose as little of the details of ID3 as possible, 
so exposing a manual version upgrade method seems counterproductive.

Original comment by joe.wreschnig@gmail.com on 18 May 2011 at 7:44

[GoogleCodeExporter]

Oh, I seem to have misunderstood what the method was doing.
I was unaware that Windows could not read id3v2.4 tags, and some of my code did 
not reflect the changes I made.

The issue can be closed.

Original comment by jiawei.h...@gmail.com on 19 May 2011 at 4:33

[GoogleCodeExporter]

Original comment by joe.wreschnig@gmail.com on 22 May 2011 at 2:43

• Changed state: Invalid