Windows Explorer in Windows 7 ruins TXXX frames, warning |
![]() ![]() |
Windows Explorer in Windows 7 ruins TXXX frames, warning |
Dec 15 2009, 15:35
Post
#1
|
|
![]() Group: Members (Donating) Posts: 391 Joined: 2-March 04 Member No.: 12414 |
Just a warning for any one that uses TXXX frames in his ID3v2.3 tags.
When you use windows explorer in Windows 7 to change a tag (i.e. change the star rating) it will alter all TXXX frames. The original content is removed and replaced with part of the name of the TXXX |
|
|
|
Dec 15 2009, 19:10
Post
#2
|
|
![]() Group: Members Posts: 239 Joined: 9-February 03 Member No.: 4921 |
Wasn't only the Release Canidiate affected by this?
|
|
|
|
Dec 15 2009, 21:15
Post
#3
|
|
![]() Group: Members Posts: 1303 Joined: 14-September 05 From: Helsinki, Finland Member No.: 24472 |
The released Windows 7 does the same.
Here is an example of the ruined tags (screenshots from Mp3tag): Before: ![]() After tagging a Rating value with Windows 7 Explorer: ![]() Apparently Windows 7 Explorer does not recognize ID3v2.4 tags at all and does not allow to tag files that contain such tags so those who use the v. 2.4 are probably safe. -------------------- http://listening-tests.freetzi.com
|
|
|
|
Dec 15 2009, 21:45
Post
#4
|
|
|
Group: Members Posts: 1543 Joined: 13-August 03 Member No.: 8353 |
A reason to switch to ID3v2.4!
|
|
|
|
Dec 15 2009, 23:41
Post
#5
|
|
|
Group: Members Posts: 377 Joined: 1-April 05 From: California Member No.: 21106 |
A reason to switch to ID3v2.4! Which isn't supported at all, so you see no tags at all? Yes, I've reproduced this. It seems through the entire 7 beta, nobody caught this. Oh, well. I haven't looked more deeply at what it's exactly writing, but yes... the custom TXXX frames are damaged if one uses the Explorer UI to manipulate the ID3v2.3 tag. |
|
|
|
Dec 16 2009, 02:05
Post
#6
|
|
![]() Group: Members Posts: 1303 Joined: 14-September 05 From: Helsinki, Finland Member No.: 24472 |
I haven't looked more deeply at what it's exactly writing... The ruins: ![]() -------------------- http://listening-tests.freetzi.com
|
|
|
|
Dec 16 2009, 05:30
Post
#7
|
|
|
Group: Members Posts: 377 Joined: 1-April 05 From: California Member No.: 21106 |
I haven't looked more deeply at what it's exactly writing... The ruins: ![]() Now, how many months/years will it take to get 7's shell fixed? This post has been edited by grommet: Dec 16 2009, 05:31 |
|
|
|
Jan 2 2010, 00:04
Post
#8
|
|
|
Group: Members Posts: 85 Joined: 19-October 02 Member No.: 3573 |
Someone should make sure to post about this on the official Windows 7 developer forums. Microsoft employees read those forums and usually the people responsible for that area of Windows will join the dicussion and work to get the problem fixed.
http://social.technet.microsoft.com/Forums...tegory/w7itpro/ This post has been edited by ogg: Jan 2 2010, 00:05 |
|
|
|
Feb 2 2010, 17:18
Post
#9
|
|
|
Group: Members Posts: 27 Joined: 12-February 06 Member No.: 27705 |
Someone should make sure to post about this on the official Windows 7 developer forums. Microsoft employees read those forums and usually the people responsible for that area of Windows will join the dicussion and work to get the problem fixed. http://social.technet.microsoft.com/Forums...tegory/w7itpro/ Just use mp3tag, or switch to Linux |
|
|
|
Feb 2 2010, 17:40
Post
#10
|
|
![]() Group: Developer Posts: 155 Joined: 22-March 06 Member No.: 28717 |
Or we could try get the bug fixed and not have to resort to workarounds.
|
|
|
|
Feb 2 2010, 21:13
Post
#11
|
|
|
Group: Members Posts: 169 Joined: 14-November 09 Member No.: 74931 |
Just use mp3tag, or switch to Linux Or don't switch to Windows Actually it is a valid concern is for people who dual boot Windows and any other OS, or who connect their portable device to a variety of different systems to add/manage/sync media. If you have spent considerable accumulated time and care in tagging your audio using an OS (or a good 3rd party tagger on MS) that doesn't have this issue then becoming aware of it by accident could be a very unhappy event indeed....and possibly aggravated if you have a great deal of cover art named as folder.jpg as that will all get unceremoniously mangled as well if you let WMP loose on your files. This post has been edited by Takla: Feb 2 2010, 21:14 |
|
|
|
Feb 2 2010, 23:17
Post
#12
|
|
|
Group: Members Posts: 62 Joined: 28-July 06 Member No.: 33374 |
That's why I set all my audio files as 'read only'. This way, Windows will never be able to modify any tags.
|
|
|
|
Feb 3 2010, 04:10
Post
#13
|
|
![]() REACT Mod developer Group: Developer Posts: 929 Joined: 14-November 07 From: Finland Member No.: 48750 |
Only if Windows (or anything else) respects that file attribute. It's not foolproof.
|
|
|
|
Feb 10 2010, 15:08
Post
#14
|
|
|
Group: Members Posts: 19 Joined: 13-January 10 Member No.: 77077 |
It seems through the entire 7 beta, nobody caught this. Because of a bug in the WMP12 library (both Beta and RC), such library had to be rebuilt from scratch every time you opened WMP12. Microsoft should have realised that, with such a bug, nobody would be seriously testing WMP12 in the Beta and in the RC so they should have immediately fixed the library problem to allow testing of the other WMP12 features. Instead they chose to carry the library bug until it was finally (sort of) fixed in the RTM. At that point people finally started using WMP12 and found another million bugs! WMP12 is a case study for software development mismanagement: from design decisions to code quality, from build cycles to interaction with the underlying OS. Anything that you can do wrong in a software project they have done it wrong. Seriously I think someone could write a book on this saga. This post has been edited by utenteanonimo64: Feb 10 2010, 15:10 |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 19th June 2013 - 17:32 |