iTunes-private COMM frames are ignored so they don't pollute comment fields and are always preserved when retagging.
Can you please further explain?
I maybe misunderstood but:
1. Here is foobar 1.1.6 b4 in action:
(http://i51.tinypic.com/4rbyw0.png)
2. What would happen if user writes to comments tag (assuming foobar ignores iTunes comments), and then opens file in Winamp or iTunes?
klonuo: Did you Reload Info from file(s)?
I just d&d file not in my library
[edit] seems same if I reload info
Is this a file you had previously re-written the tags with with an older version of fb2k? Because older versions would have rewritten all comment data without using the "special" iTunes COMM frames that beta 4 now ignores.
I didn't tag those files with foobar, but did RG processing. Here is dump:
(http://i55.tinypic.com/2cmvslw.png)
I didn't tag those files with foobar, but did RG processing. Here is dump:
Adding ReplayGain tags is retagging.
I didn't tag those files with foobar, but did RG processing.
RG processing involves retagging.
too slow...
I did burn on mass tagging, but I just don't get it: are you saying that if I RG process some MP3s (force preferred tag is not set) foobar rewrites all tag scheme for me without explicitly setting it to do so?
Fields can not be changed and saved individually. Similar to how if you change the spelling of one word in a MS word document, the entire file has to be saved.
When you click the "Update file tags" button on the RG scanner results, all fields in your tags are rewritten. This means any peculiarities the tag reader has with reading a field is preserved in the rewritten tags. Beta 1-3 (and previous versions) placed all fields in the COMM frame into the COMM frame. iTunes's weird way of using the COMM frame as psudeo-TXXX wasn't taken into consideration. Starting with beta 4 it is.
(force preferred tag is not set)
This refers to writing between id3v1, id3v2 and APE tag standards. This setting has nothing to do with writing subversions of tagging standards (e.g. id3v2.2 or id3v2.4), or particular behaviors within individual fields (e.g. itunes COMM).
I thought that RG just adds values at the end all frames and not necessarily rewrite everything
Personally I couldn't care less about iTunes tags, but someone else is using it
Here is metamp3 output (hex would be better but harder to read) from original file, which copy is mentioned above (it's ID3v2.2 BTW):
[font= "Lucida Console"]TYE: 1995
TT2: Testone
TRK: 1/15
TPA: 1/1
TEN: iTunes 10.0
TCO: Electronica
TCM: `0.x
TAL: 1000 Fragments
COM: [iTunes_CDDB_TrackNumber]{eng}: 1
COM: [iTunes_CDDB_1]{eng}: AC0DAE0F+262820+15+150+677+7885+11585+13645+17965+20592+34390+37125+50222+85100+106187+120405+150312
+189395
COM: [iTunSMPB]{eng}: 00000000 00000210 000006FC 000000000004BA74 00000000 00028415 00000000 00000000 00000000 00000000 00000000 00000000
COM: [iTunPGAP]{eng}: 0
COM: [iTunNORM]{eng}: 00000155 000001F2 00000311 00000702 00000343 00000343 00002AAE 00002B91 000009E5 000009E5[/font][/color]
here report after RG processing with foobar 1.1.6 b4:
[font= "Lucida Console"]TYER: 1995
TXXX: [replaygain_track_peak]: 0.340388
TXXX: [replaygain_track_gain]: -6.41 dB
TXXX: [replaygain_album_peak]: 0.340388
TXXX: [replaygain_album_gain]: -6.41 dB
TRCK: 1/15
TPOS: 1/1
TIT2: Testone
TENC: iTunes 10.0
TCON: Electronica
TCOM: `0.x
TALB: 1000 Fragments
COMM: [iTunes_CDDB_TrackNumber]{eng}: 1
COMM: [iTunes_CDDB_1]{eng}: AC0DAE0F+262820+15+150+677+7885+11585+13645+17965+20592+34390+37125+50222+85100+106187+120405+150312
+189395
COMM: [iTunSMPB]{eng}: 00000000 00000210 000006FC 000000000004BA74 00000000 00028415 00000000 00000000 00000000 00000000 00000000 00000000
COMM: [iTunPGAP]{eng}: 0
COMM: [iTunNORM]{eng}: 00000155 000001F2 00000311 00000702 00000343 00000343 00002AAE 00002B91 000009E5 000009E5[/font][/color]
here is report after RG processing with pre 1.1.6 (it's 1.1.4 set to compatibility mode):
[font= "Lucida Console"]TYER: 1995
TXXX: [replaygain_track_peak]: 0.340388
TXXX: [replaygain_track_gain]: +1.81 dB
TXXX: [replaygain_album_peak]: 0.340388
TXXX: [replaygain_album_gain]: +1.81 dB
TXXX: [comment]: 0
TRCK: 1/15
TPOS: 1/1
TIT2: Testone
TENC: iTunes 10.0
TCON: Electronica
TALB: 1000 Fragments[/font][/color]
finally this is output if I write comment ('foo') in foobar 1.1.6 b4:
[font= "Lucida Console"]TYER: 1995
TRCK: 1/15
TPOS: 1/1
TIT2: Testone
TENC: iTunes 10.0
TCON: Electronica
TCOM: `0.x
TALB: 1000 Fragments
COMM: [iTunes_CDDB_TrackNumber]{eng}: 1
COMM: [iTunes_CDDB_1]{eng}: AC0DAE0F+262820+15+150+677+7885+11585+13645+17965+20592+34390+37125+50222+85100+106187+120405+150312
+189395
COMM: [iTunSMPB]{eng}: 00000000 00000210 000006FC 000000000004BA74 00000000 00028415 00000000 00000000 00000000 00000000 00000000 00000000
COMM: [iTunPGAP]{eng}: 0
COMM: [iTunNORM]{eng}: 00000155 000001F2 00000311 00000702 00000343 00000343 00002AAE 00002B91 000009E5 000009E5
COMM: []{eng}: foo[/font][/color]
The hex view is probably more accurate - less translation is happening with a hex view. THe previous hex view you showed (post #5) told a different story than what is shown in post 11. The hex view you posted shows that your comment fields were written to TXXX frames, not COMM frames, and this explains the original behavior you complained about in the other thread.
To correct, you need to redo your iTunes comments tags to get them into COMM frames, and I recommend you use a hex reader to confirm that.
THe previous hex view you showed (post #5) told a different story than what is shown in post 11.
Yes, it's shown now even more, including the case from #5:
here is report after RG processing with pre 1.1.6 (it's 1.1.4 set to compatibility mode):
[font= "Lucida Console"]TYER: 1995
TXXX: [replaygain_track_peak]: 0.340388
TXXX: [replaygain_track_gain]: +1.81 dB
TXXX: [replaygain_album_peak]: 0.340388
TXXX: [replaygain_album_gain]: +1.81 dB
TXXX: [comment]: 0
TRCK: 1/15
TPOS: 1/1
TIT2: Testone
TENC: iTunes 10.0
TCON: Electronica
TALB: 1000 Fragments[/font][/color]
To correct, you need to redo your iTunes comments tags to get them into COMM frames, and I recommend you use a hex reader to confirm that.
Thanks for your efforts, I dig that but forgot to mention
Cheers