Hi there,
getting a little puzzled by the documentation.
Among the list of ID3 V2 supported text frames (TIT1, TIT2, TIT3, TALB, TOAL, TRCK, TPOS, TSST, TSRC, TPE1, TPE2, TPE3, TPE4, TOPE, TEXT, TOLY, TCOM, TMCL, TIPL, TENC, TBPM, TLEN, TKEY, TLAN, TCON, TFLT, TMED, TMOO, TCOP, TPRO, TPUB, TOWN, TRSN, TRSO, TOFN, TDLY, TDEN, TDOR, TDRC, TDRL, TDTG, TSSE, TSOA, TSOP, TSOT.) i cannot see "TYER", which is the recording year.
On the other hands, from the VB6 sample "TagsEditor", i can see that "TYER" frame is both read and written. However, when i try to do it myself, nothing gets written into the file and, if a previous value was present, it gets cancelled.
My code:
...
objASOED.TagsEditor.ID3V2_TextFrameSet "TYER", "1999"
objASOED.TagsEditor.ID3V2_SaveChanges ID3V2_FORMAT_2_4, ID3V2_ENCODING_UTF_8
...
Can anybody help to understand what's going on?
Many thanks in advance
Found the following work-around.
It's far from ideal, but it appears to work.
I save first all V2.4 frames, using UTF-8 encoding (to preserve the special characters).
After that, i save the frames available only for V2.3, using ISO-8859-1 encoding (because apparently i cannot use UTF-8 with V2.3 format...)
This way, i managed to save the TYER frame, although it is not in the list of supported frames.
Any idea of any better solution?
Hello,
as seen inside the ID3V2 specifications, support for the "TYER" field has been dropped by version 2.4 of the ID3V2 format and replaced by the "TDRC" field:
http://id3.org/id3v2.4.0-changes (http://id3.org/id3v2.4.0-changes)
so, if you need to save the "TYER" field, you should definitely use version 2.3 which, as you have seen, doesn't come with support for UTF-8 encoding introduced starting from version 2.4
Hope this helps.
Kind Regards
Severino Delaurenti
MultiMedia Soft
Hi Severino,
I've tried to save the TDRC (V2.4) instead of TYER and it works perfectly.
Grazie mille
Riccardo
You are welcome :-)
Kind Regards
Severino Delaurenti
MultiMedia Soft