Id3 tags aren't being updated in 11.1.4 (Mac 10.6.8)

Nevermind folks - figured it out. Sorry for the post. Had selected to "copy songs to itunes folder" so the original files weren't being updated because the copies were. Thanks.

Tip: Mark this topic as solved so people don't check if you need an answer.

Similar Messages

  • Itunes, ID3 tags, & hard drive corruption

    My wife is having a strange problem with her iMac, and it’s got me a bit mystified. I’m hoping someone here can shed some light on what might be going on. I apologize in advance for the long post.
    The problem is that when she plays some songs in iTunes, and entirely different (wrong) song plays instead. Most songs play fine, but some just play entirely different songs (or sections of a song or podcast). All of the tracks are MP3 (either 192 kbps or 256 kbps) and almost all of them were encoded using Windows Media Player on an XP machine. Initially, I copied the music over from an NTFS drive to a newly formatted (Mac OS/HFS+) drive on the Mac, then I ran iTunes and created the library. At that point, everything seemed fine. All the meta data (song title, album title, artist, album artist, genre, album art) showed up in iTunes, and everything played correctly.
    Now we’re getting this weird behavior where we play some songs and get the wrong music. At first I thought the iTunes library files (ITL and/or XML) had been corrupted, but it seems on closer inspection that the entire hard drive has been corrupted. When I look at the files on Mac hard drive via the Finder, all seems ok – the directory structure is intact, the file names and sizes are all correct, and a Get Info on any MP3 file shows that the ID3 data is all there and seems accurate. This is true even for the songs that play wrong, but if I play one of those songs using the little mini player in the Get Info dialog, the wrong song plays (the same wrong song as in iTunes). So now I’m getting the behavior straight off the drive, with iTunes closed and the iTunes library completely out of the equation.
    Some other interesting clues/evidence:
    * This has happened before. When her first hard drive got corrupted (in the same way), I was mystified but chalked it up as a bad hard drive and got her a new one. Then we started over with a clean HFS+ formatted drive and clean music files and built a new iTunes library. And now the same thing has happened again. So I don’t think it’s just a bad hard drive.
    * It seems to be progressive. That is, everything was fine in the beginning, but over time more and more files get messed up. We know this because we have a backup that’s about a month old on which we can locate files that are fine (on the backup) but that are messed up on her connected day-to-day drive. So it seems like some activity on the drive is causing problems that are growing over time.
    * There is some weird meta data (ID3) behavior. I copied a few hundred MP3 files from the Mac drive back to the PC (over our home network) and looked at them in the Windows Explorer. The first thing I saw was that the same (wrong) music played for the bad tracks as had on the Mac. And I also saw that a lot of ID3 tags were not showing on the Windows side. Lots of tracks have no ID3 data (album, artist, genre, etc. is missing) when I look at them on the PC. There are many albums where tags show up correctly for some of the tracks but not for others. In fact, the number of files where the ID3 tags aren’t visible on the PC far exceeds the number of songs that play incorrectly on the Mac. When I look back on the Mac at the songs that have no ID3 data on the PC and do a Get Info, I see the ID3 data.
    * Often, though I can’t say always for sure, the wrong music that plays on the Mac is stuff that has been recently added. Either podcasts or music that my wife has added since the initial library was established.
    My best guess (though still full of holes):
    Something is confusing the Mac OS into writing on top of occupied space on the hard drive or into mapping files incorrectly in the drive’s allocation table, and chaos results. The Mac doesn’t think anything is wrong, and it shows everything as being clean in the Finder. So I started thinking about the kind of reads & writes my wife is doing on that drive. She rips new CDs to add to the library, she downloads new Podcasts and deletes old ones, and she changes ID3 tags.
    I’m focusing on the changing ID3 tag activity. My wife doesn’t like the way I tag genre. I like big broad categories, an she likes smaller, more specific categories. So she has gone through the initial library of 42K+ songs and changed the genre on thousands of songs. She’s change some from Pop to Power Pop or from Pop to Indie Pop or from Rock to Indie Rock, etc. Both WMP (where the tags were created) and iTunes support ID3v2.3, and so these two programs ought to be able to change tags in a totally interchangeable and safe way. But what if iTunes writes its new genre tags in a way that’s slightly different from WMP? Could iTunes be writing to memory/disk locations that are outside the boundaries of the file and thus creating some kind of buffer overrun?
    It really doesn’t make a lot of sense, but it does tie back to the evidence that this has something to do with meta data, gets worse over time, happened on more than one disk, and seems to be a file allocation table issue.
    Even if I get to the bottom of this, I think my wife’s HD is toast for sure. Here’s what I think I will do: I’ll reformat the drive, re-copy the music over from the PC, and build a new iTunes library. Then, first thing, I’ll open iTunes, select all the songs in the new library, and run “Convert ID3 Tags” to ID3v2.4. If that works and everything behaves correctly, I’ll try to change some genre tags and test the results. The problem is that the library is so large that problems can go undetected for a long time, so maybe I should do this first with a small subset of the music as a trial run.
    The thing I want to avoid is having to do this (ever) again, so I’d feel more comfortable if I understood the bug/problem before just following this guess (which feels like a roll of the dice). If anyone has seem similar behavior or has heard of any IDS incompatibilities between WMP 11 and iTunes 7, I’d love to hear about it. Any help is appreciated.
    Jim

    Wow, that was a long and detailed post. I haven't the energy to reply in equal fervor, but I will just say that lately these boards have been peppered with posts from people whose MP3s are being eaten alive by iTunes. What I don't get is why you suspect the hard drive is at fault. Unless the rest of the system is caving in, I don't think there's any reason to suspect a failing drive. Check the S.M.A.R.T. status in Disk Utility if you haven't already, and perform whatever maintenance you believe is in order.
    For the most reliable ID3 tag editing, I'd certainly recommend using foobar2000 on a Windows PC (or a Mac with Windows installed) or MP3Tag. I would definitely, at least for the time being, not put your huge music collection at risk by doing any further editing of the tags in iTunes.

  • Why can't I write ID3 tags?

    Hi gang. Odd problem. Just very recently noticed it.
    With some files, but not all, when I go to bounce them, it won't let me write ID3 tags.
    I click the Bounce icon. The bounce box comes up.
    I overtype the file name at the top.
    I select destination MP3. Stereo mode is joint stereo. Write ID3 tags is ticked, so are use best encoding, filter frequencies below 10Hz , mode offline and include audio tail. Bit rate mono is 80kbps. Bit rate stereo is 160kps. Bit rate VBR is not ticked.
    I click ID3 settings. The Bounce box goes out and then after a very short moment comes back set back to the PCM destination with the file name missing.
    I go through the whole routine again. This time the bounce box goes out and stays out.
    The only way it will bounce is without changing the ID3 tags. It flatly refused to edit them. Just no way, I can't get at them, that's it.
    Version is 9.1.5 (1 7 0 0.9) 32 bit. Yes I have tried saving the file, shutting the program down and restarting it, it still does it. Once a file starts doing this, that's it, it always does it.
    The only thing that's changed recently is DwellClick. Every file created after that seems to have the problem. Every one before it is still OK, even with DwellClick running. However, if I create a new project now, the problem doesn't happen, it's fine. Something must be happening during the project that stops the ID3 tag dialogue box being accessible.
    Is this a software incompatibility? a software bug? suggestions??

    Hi
    Erm, excuse me asking a really stupid question, but how would I do that?
    and why is it affecting some files but not others? The latest file here does not seem affected. If it was a global preferences issue would it not affect all files? is it not more likely that it is the project itself that has the issue?
    I notice that the project file can be examined as a package which apparently contains a folder LgDoc, which itself contains
    displayState, which appears to contain coding instructions and data
    documentData, which is mostly unintelligible coding with odd bits in clear text
    windowImage.jpg, which is just the graphic for the icon.
    This for example is a displayState file from a project that does not allow access to the ID3 tags:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
        <key>displayDataVersion</key>
        <integer>1</integer>
        <key>docPreferences</key>
        <dict>
            <key>EXSEditorGlobalPersistency</key>
            <dict/>
        </dict>
        <key>screenVisibleFrames</key>
        <array>
            <string>{{0, 97}, {1440, 781}}</string>
        </array>
        <key>screensetCurrSlot</key>
        <integer>1</integer>
        <key>screensetDictArray</key>
        <array>
            <dict>
                <key>layoutDictArray</key>
                <array>
                    <dict>
                        <key>docwWindowState</key>
                        <dict>
                            <key>currentDocwListID</key>
                            <integer>1</integer>
                            <key>docwEditorTabIndex</key>
                            <integer>-1</integer>
                            <key>docwListTabIndex_events</key>
                            <integer>0</integer>
                            <key>docwListTabIndex_media</key>
                            <integer>1</integer>
                            <key>docwListTabIndex_notes</key>
                            <integer>0</integer>
                            <key>focusedElement</key>
                            <integer>0</integer>
                            <key>inspectorIsVisible</key>
                            <true/>
                            <key>listsAreVisible</key>
                            <false/>
                            <key>markerTextIsExpanded</key>
                            <true/>
                            <key>markerTextSplitPosition</key>
                            <real>33.333000183105469</real>
                            <key>mediaListIsCurrent</key>
                            <true/>
                            <key>screenSpaceRect</key>
                            <string>0 97 1440 781/0 0 1440 900 0 97 1440 781</string>
                            <key>tabViewPercentMixer</key>
                            <real>100</real>
                            <key>tabViewPercentOther</key>
                            <real>76.597442626953125</real>
                            <key>toolbarIsVisible</key>
                            <true/>
                            <key>transportBarIsVisible</key>
                            <true/>
                            <key>transportLayoutDict</key>
                            <dict>
                                <key>CLgTransportBtnsDisplay</key>
                                <array>
                                    <integer>18</integer>
                                    <integer>19</integer>
                                    <integer>21</integer>
                                    <integer>22</integer>
                                    <integer>23</integer>
                                    <integer>24</integer>
                                </array>
                                <key>CLgTransportBtnsModus</key>
                                <array>
                                    <integer>29</integer>
                                    <integer>38</integer>
                                    <integer>39</integer>
                                    <integer>42</integer>
                                    <integer>43</integer>
                                    <integer>45</integer>
                                    <integer>30</integer>
                                </array>
                                <key>CLgTransportBtnsTransport</key>
                                <array>
                                    <integer>6</integer>
                                    <integer>5</integer>
                                    <integer>11</integer>
                                    <integer>12</integer>
                                    <integer>13</integer>
                                    <integer>14</integer>
                                    <integer>15</integer>
                                    <integer>16</integer>
                                </array>
                            </dict>
                            <key>udataArrange</key>
                            <data>
                            HAFJcASnAgA4AQAAAADdBEUCAAAA
                            AAAAAAAAAAAAAAAAAAAAAADbACcA
                            SXAAAAAABACAAAAAAAAAAIARAAAA
                            AQoAIADbAI+IAAAAAAAAgAAAAAAB
                            AQAAAABAAAAAAAAAAADkAAAAAAAA
                            AMaYAAAAAAAAAAB43/+/8HwAAAAA
                            tACAAQAAAAAAAAMAAAACAAAADA5/
                            cQBjFgBXADAAQAAWABYAGwAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AQQDBgUCAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            ACBCAAC4QQAAAAA=
                            </data>
                            <key>udataBin</key>
                            <data>
                            HAEVEABAAgCdAQAAAABlARUCAAAA
                            AAAAAAAAAAAAAAAAAAAAAACZABEA
                            FRAAAAAAAAAAAAAAAAAAAAACEgAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AAAAAABAAAAAAAAAAAAAAAAAAAAA
                            AMaYAAAAAAAAAADY7f+/8HwAAAAA
                            9AGAAAAAAAAAAAAAAAAAAAAADAD/
                            AABjFgAbABYAFgAWABYAGwAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AQQDBgUCAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AJBBAAAAAAAAAAA=
                            </data>
                            <key>udataMixer</key>
                            <data>
                            HAEhIFjyAgCMAQAAAADdBOEBAAAA
                            ACMAAAAAAAAAAAAAAAAAAAAfAAAA
                            ISAAAAAABAAAAAAAAAAAAAATAAAA
                            AAAAAAAAAPCvEBgAAAAAABgAAAAS
                            EgAAAABAAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            0QGAAAAAAAAAAAAAAAAAAAAADAD/
                            AABjFgAbABYAFgAWABYAGwAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AQQDBgUCAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AABAAACAPwAAAAA=
                            </data>
                            <key>udataPianoRoll</key>
                            <data>
                            HAFCcFjyAgDpAQAAAABxA5wB4i4A
                            ADYBAAAAAAAAAAAAAAAAAABCACcA
                            QnAAAAAABAAAAA4A//2AAAQVAAAA
                            AAoAIAAAAPz/UAAAAAAAuAAAAA4p
                            KQAAAABAAAAAAAAAAABRAQAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAQAAAAAA
                            ZQGAAQAAAAAAAAMAAAACAAAADAD/
                            AABjFgAbABYAFgAWABYAGwAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AQQDBgUCAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAABI
                            4RJCAAAgQQAAAAA=
                            </data>
                            <key>udataTransport</key>
                            <data>
                            HAEKAAAAAgACAQAAAAAlAigAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            CgAAAAAABAAAAAAAAAAiAAAAAAAA
                            AAAAAAAAAAAAAAAqAJgADQAAAAAA
                            AAAAAABAAAAAAAAAAAAAAAAAAAAA
                            AMaYAAAAAAAAAADo3/+/8HwAAAAA
                            GACAAAAAAAAAAAAAAAAAAAAADAD/
                            AABjFgAbABYAFgAWABYAGwAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AQQDBgUCAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                            AABBAAAAAAAAAAA=
                            </data>
                            <key>windowFrame</key>
                            <string>0 143 1440 735 0 0 1440 878 </string>
                            <key>windowIsZoomed</key>
                            <true/>
                        </dict>
                        <key>docwWindowType</key>
                        <integer>1</integer>
                    </dict>
                </array>
                <key>screensetLocked</key>
                <false/>
                <key>screensetName</key>
                <string></string>
                <key>screensetSlot</key>
                <integer>1</integer>
            </dict>
        </array>
    </dict>
    </plist>
    Question - is this corrupt, or is the other (mostly unintelligible one) corrupt?

  • Bug or Feature? iTunes doesn't write ID3 Tags when you recorded in VBR mode

    When you record music from a CD with iTunes (6.0.4 and 6.0.5) using higher bit rates (High Quality) together with VBR, then the iTunes database initialy shows a correct entry. But if you check the created mp3-files with the Finder application you will see that there is no id3-tag in the file.
    When you later move your iTunes music folder, iTunes asks you to modfify everything concerning the embedded infos (id3 tags). If you then say "yes" your database is gone.
    I saw a couple of postings where users complain about that iTunes loses the id3 tag when they burn a CD. I think that there has never been a physical ID3-Tag although the iTunes database shows a correct entry.
    Is some kind of a bug fix out there or should I use Musicmatch within Parallels Desktop for Mac in order to properly record in VBR mode?

    Odysseas,
    "But if you check the created mp3-files with the Finder application you will see that there is no id3-tag in the file."
    You can't see ID3 tags in the Finder. The data is imbedded in the song file itself.
    Regular, commercially produced CDs do not support ID3 tag information. When you insert a CD and it opens in iTunes, the application will go out on the internet and look up the track information in the Gracenote (CDDB) database.
    Then, when you rip the CD to an MP3 or AAC etc. the track information is then incorporated into the encoded song file. Using VBR shouldn't prevent the ID3 tag information from being transfered.
    However, if you then burn a music CD from that file, the ID3 tag information is lost.
    Matt

  • ID3 Tags Not Being Recognized

    Okay, so I have a problem and I am racking my brain trying to figure it out.
    Itunes isn't recognizing some of my music's ID3 tags. Worst part is I used Itunes to convert every song I have to ID3 v 2.4, but there's still a handful that aren't been recognized. I used Media Monkey to aid in my tagging. For further pain listen to this. I also just updated from Itunes 6 or whatever to 7.4.1.1.1.1 or whatever the **** it's at now, and it went from about 7 albums to like 30 that itune's won't recognize the ID3 tags for.
    For more help look at this image. Showing an example of how all my songs have and Artist, Album, and more set to them, but ITunes won't pick it up. Any idea how to fix this guys?
    http://img149.imageshack.us/img149/5493/wtfituneshu6.jpg
    Message was edited by: Taramoor

    Hi guys. If your music is in MP3 format, try downloading this program: http://www.download.com/Mp3-Tag-Tools/3000-2141_4-10106717.html
    Then click file > open directory. Find the folder that holds your music and click open. Make sure 'recurse subdirectories' is ticked so that it opens everything within the folder. This can take quite a while if you have a lot of music.
    Once all your files have loaded, press Ctrl+A to select all of your music files and then press F7. This duplicates whatever is in your ID3V2.X tags onto the ID3V1.1 tags.
    For iTunes to take notice of any tag changes you make in this program, the file either has to be played or re-uploaded into iTunes which can also take a while depending on how much music you have, but once you've done that, iTunes should start recognising your tags.
    Hope this helps!

  • Changing ID3 Tags - not updating?

    Hi
    I am updating Artist, Title information within iTunes - but for some reason the changes are not being reflected in the file ID3 tags?
    some of my files are updating and others are not?
    Any ideas?
    Thanks in advance?

    How are you examining the ID3 tags? Maybe whatever program you're using to look at them is caching the information, and not checking the tags when you look at the file a second time?

  • ITunes doesn't update Title in ID3 tags

    So, I've searched through this forum and found several problems that are similar to mine...but not 100% the same. When trying the new game Audiosurf, I found that it didn't recognize a few songs--it said that the title was "Unknown". Well, I know that all of my songs have titles in iTunes, so I did some investigating. It turns out that for a small percentage of my library, the Title in the ID3 tag is not complete--although the Album, Artist, Genre, etc. tags are! I'm verifying this using a 3rd party ID3 tag viewer, and even can see this by right-clicking the file in Windows Explorer and looking at the advanced summary.
    So I've tried several things within iTunes to get the ID3 tag to be written, including setting the files to have no ID3 tag (via the "Convert ID3 Tags..." dialog, as suggested in this forum) and then bringing them back. The tag is correctly removed, but when I restore the tag the Title is still left blank. Many of the files have "Unknown" as the encoder, but I have several that are either "Unknown" but have a title, or are iTunes encoded but don't have a title.
    The "easiest" thing that works for me is to modify the song title and then modify it back. This will finally create the Title field in the ID3 tag. So...does anyone know a faster way to do this? Some way to select these songs and force iTunes to update the ID3 tags (besides changing the tag type, which I have already tried)? I fear there is no easy way...I have some ideas with my ID3 tag program I downloaded, but I'd much rather do it in iTunes.
    Thanks!

    This may not help with whatever you did in Terminal but it may help with trying to update to 5.1.
    System Preferences>Network, select your network (ethernet or wifi on the left) and click on the Advanced button and then the DNS tab. On the left, under DNS servers, click the + sign and type 8.8.8.8 click the + again and type 8.8.4.4 and save your settings. See if iTunes will now let you update.
    If that fails you could try updating over wifi not using iTunes. These are the instructions for an iPod touch (I guess it'll be similar for the iPhone/iPad). Settings>General>Software Update.

  • Mediasource won't update ID3 tags!

    "Mediasource won't update ID3 tags!? Please help! I have been using Mediasource 5 over the years to painstakingly get my mp3 library organized just the way I want it. I know that the Media Source track info is not necessarily the same as what's stored in the ID3 tag of the files themselves. I am trying to update the ID3 tags so that the info matches what is in Media Source. The good news is, I can right click on my database in CMS and there is an option to "Update Track Properties". Within this window are two options: one to update the ID3 tags to match MediaSource, and another to update MediaSource to match the ID3 tags.
    So far so good, here's the problem. No matter which option you choose, it always does the latter of updating MediaSource to match the ID3 tags. ARGHH!! I've tried this over and over, trying both options, but no matter what I do, it's always copying in the wrong direction. That goodness I had backed up my database before doing it. I've tried both CMS 5.0.38 and the newer 5.20.23 but both have the same issue.
    So is there any way to get Mediasource to take it's data and copy it over the ID3 tag data? Anyone know of a patch or other software that read the CMS database file and do this?

    Mapleleaf3 wrote:
    2) Using the File>export button and clicking save in the CD drive is the correct way to put CD text onto the CD, right?
    Preferences > Advanced > Burning (tab)
    Under "Audio CD", check "Include CD Text"
    Mapleleaf3 wrote:
    3) Would this CD text be able to be read by other people's Itunes?
    CD-TEXT only allows capable audio players (portable CD players, certain car stereo CD players, etc.) to scroll that information across its display as the track is playing.
    For other people's iTunes to be able to retrieve the track listing, it has to be first uploaded into Gracenote's database, once Gracenote processes the information.
    Steve

  • ITunes very slow when updating ID3 tags

    Greetings,
    I've read about iTunes taking forever "processing file" when people have downloaded songs, but haven't seen a reference to this problem when changing the ID3 tags for songs within the program.
    Sometimes it will take many seconds to complete this task, often with the "processing file" box showing up and sometimes with the spinning pinwheel too.
    This hasn't always been such a slow process. Usually in the past my tags got updated instantaneously, even if I was changing, say, the album info for a whole batch of songs. More recently, iTunes has been consistently slow in carrying this out.
    Any insights would be appreciated.

    I also noticed that when iTunes updates the files, it opens multiple little windows with progress bars (I think so because I see only one window but with a very significant shadow -- which look like if there were several windows stacked).
    I SINCERELY hope I'm WRONG when I think iTunes does all the updating in parallel, regardless how many songs there are to update............? That would explain a lot...

  • Unable to update album cover images and sometimes ID3-tags

    Hello everyone,
    I'm having problems with updating my track information on those tracks that I imported from my hard disk (mainly mp3s). I'm unable to add an album cover to most of them and sometimes it doesn't save the changes when I'm changing title and album information.
    The last things I've done were updating iTunes to version 7.3.1.3 and additionally I chose the option "convert ID3-Tags to v2.4".
    Before those two changes everything worked very well, but now I don't know what to do.
    Thanks for your help already!
    Andy

    Anyone got a clue?
    I figured out that after the ID3-Tag-conversion there are some files that are still alterable and some are not.
    With the latter ones I even cannot re-convert the ID3-Tags back to version 1.

  • My ID3 tags not being recognized by iTunes 10.2.2

    Can't quite find my unique problem on this board so hopefully someone can help me.
    I have imported a lot of MP3 files into iTunes, successfully, which have v2.4 ID3 tags on them. I screwed up the song titles on one (Grateful Dead) show, and all songs came in titled '04'...
    I deleted the files in iTunes (and asked iTunes to remove the files as well), fixed up the ID3 tags in the originals, and reimported. But, titles are still '04'!?
    Since my music library is on my Linux box and I am mounting and importing from there, I thought maybe something was getting cached so I copied the whole album directory over to my iMac, but still I get the same '04' title for every song.
    I also changed the Album attribute in the ID3 tags, but that is still also coming out the old (wrong) way.
    It is as if iTunes has some sort of 'fingerprint' of the songs and refuses to recognize the ID3 tags.
    This is on OS X 10.6.7 on iTunes 10.2.2, so I'm up to date on all software. And, I've imported A TON of shows like this without issue, it otherwise works just fine.
    Anyone ever see this weird problem before?

    Sorry, should have been clearer.
    The first time I applied the ID3 tags my script for parsing the artist, album and track names from the directory name hierarchy and filenames (e.g. ~/Music/<artist>/<album>/<track number>-<filename>), my script had a bug and all ID3 'title' values were set to the month number of the concert (04 = April).
    So, the first time I imported into iTunes, all tracks were titled '04'. I deleted those in iTunes, fixed my script, but now despite apparently having correct ID3 tags, all songs continue to be named '04'. I also changed the album value to, changing from 'Hartford 04262010' to 'Hartford Apr 26, 2010', but again the original value appears to be "sticky", and despite the apparently revised ID3 tag, the album name also is the same as the first time I imported (i.e. Hartford 04262010).
    Like I said, it appears that iTunes is somehow caching the original values and not recognizing the new / revised ID3 tags.

  • Can I update ID3 tags in another program?

    I need to batch edit ID3 tags for a bunch of songs. Can I do so in an external program and then have the data show up the next time I open iTunes, without having to click "get info" for every edited song? That is - is there a way to mass refresh the displayed titles?

    I figured it out - I can select multiple files and click past the "Are you sure you want to edit information for multiple files?" dialog, then cancel the Edit Info box, and the changes made in the other program will take effect.

  • MP3 song information not retained after iTunes 7.0 - ID3 tags at fault?

    I'm having some strange problems with track information in iTunes. I first noticed it when I tried to copy some mp3's from my Mac to my mobile phone: certain tracks did not retain the song information, like artist, album etc., while others did.
    A similar problem has been discussed in this post:
    http://discussions.apple.com/thread.jspa?messageID=3698498
    However, my problem seems to be a little bit more specific.
    If I look at the music in my library in iTunes, all the track information is there. However, for MP3's encoded after 16th October last year, the "Imported With" field, using Get Info, is shown as "Unknown". Before this date, it is shown as "iTunes v7.0". For all MP3's the ID3 version is v2.2.
    I believe that I must have upgraded to iTunes 7.0.1 around this time, since I have a number of Apple Lossless audio files which have also been imported and don't show this problem.
    The main problem is with the file ID3 tag information (I think). If I select one of the problem tracks, find the original file, open it up in Quicktime and "Get Info", no track/album/artist/composer information is displayed. This is NOT true for 1) MP3's encoded before 16th October 2006 and 2) Apple Lossless files encoded at any time.
    In other words, the track information for songs encoded with iTunes 7.0.1 and later is either encoded in a way that no other application can read, OR is only being stored in the iTunes playlist, NOT the file itself. I can see all the track information for these problem files on my iPod, but NOT my mobile phone (where I have to manually copy them over), even if I drag and drop them directly from iTunes.
    I have this problem with Quicktime, my mobile phone music player and RealPlayer, so I'm assuming it's "system wide". It even occurs if I copy a problem file out of my music folder and onto the the Desktop, then manually add the track to iTunes: all the song information has disappeared.
    I have all my music stored on an external hard disk - 160GB Freecom ToughDrive formatted as HFS+. Previously it was stored on an external disk formatted as FAT32, but copying the files over to the new disk didn't change the problem.
    I considered using the "convert ID3 tags" option to see if it would make a difference, but both the good and bad files are listed as using v2.2. I also don't understand enough about them to feel confident converting them to something different - perhaps to v2.3 or v2.4 - just to see if it makes a difference.
    Any information on how to "recover" the missing information (for anything other than iTunes) would be greatly appreciated!
    MacBook Pro 17" 2.16 GHz 2GB RAM   Mac OS X (10.4.9)   iTunes 7.1.1

    Okay, some more information as I try and track down the source of the problem.
    By using an id3 tag editing program - ID3 Editor - I was able to view the song information for each track, even though all the other music players I had tried would not show it. If I then chose to modify and update the ID3 information, this would somehow modify the tags in such a way that they become readable in all other programs.
    I tried using the "Convert ID3" tags option in iTunes, just on a whim, but without any success. Saving the song information in ID3 Editor doesn't change the version of the ID3 tag - it's still listed as v2.2 in iTunes - but it DOES make it readable in other programs. I also tried the various text conversion options, again without any success.
    This looks to me like a bug in iTunes. While its possible for me to get around it, in an extremely long winded way, I still can't understand why iTunes would be writing ID3 information that other Apple programs cannot read.
    Any suggestions? Should I be posting this question in a different forum perhaps?

  • ID3 tags lose info

    I just got a Nano(2nd gen). My ID3 tags are correct when I use MP3 files in Winamp (even the CD text is accurate even if misspelled and in the wrong column) but when I move them to I-tunes I get Track 01, Track 02, Track 03, etc.
    The files that were on my computer don't lose info but my CDs do. When I put them on my Music they still have the info but sending them to I-tunes, they're lost. They are home-made CDs (compilations from all over the place) Will have to enter all the info manually? Hope not.
    What to do ? Thanks for any answer. Being new I'm still fumbling my way through the process. An instruction booklet about getting music into an Ipod would have been very helpful.

    Matt,
    I can't say that I've has problems with songs dissappearing completely, but I have pulled out a lot of hair when the id3 tags revert to old song info.
    I changed "johnny cash/june carter" to just "johnny cash" about 10 or so times because it just keeps going back even when i edit the tags with a tag editor. I had the same issue with a handful of songs. Very frustrating.
    Someone suggested that I check Windows Media Player, and if it's set up to Automatically fix song info in it's preferences. I think this is what was happening, every time WMP would be running, it would look up song info on the internet and think that my edits were incorrect.
    I unchecked the auto-update feature on WMP, so far, no problems, but it's only been a week or so. So we'll see.

  • ID3 tags - I can't be the only one

    iTunes 7.7.0.43, fully patched XP Pro SP3. "M:" drive on file server contains 4500 songs. Full read/write access.
    ID3 tags simply do not work in iTunes. I have "Convert ID3 Tags..."'d to "None" dozens of times for the whole library and have attempted to "Convert ID3 Tags..." to ID3vanything without them actually being written to the file itself.
    iTunes reports "None" on the info screen for ID3 tags after several hours of it supposedly converting tags.
    I have invested a large amount of time in ensuring the iTunes library itself is accurate and would like to carry over the information in the library to the MP3s themselves via ID3.
    After many searches I've found split results. Some people never have an issue with iTunes writing ID3 tags, others like myself have never gotten this to work. I will whip up a script to read the XML library and batch a program to update the tags outside of iTunes, but "Convert ID3 Tags..." is not a new choice and it is supposed to do what I'm looking for.
    What gives?

    Welcome to the discussions!
    Has Apple repaired your MB this last time so that it does work properly? I ask this not to be flippant, but out of curiosity. If it is repaired and working properly, then Apple has no reason to replace it.
    It is likely that if your MB needs a fourth repair that it would be replaced. An optical drive and case replacements are fairly striaghtforward repairs and not indicative of a completely faulty unit like a bad logic board or LCD would be.
    If your MB does require another repair, I would call AppleCare and escalate it to a second tier representative. They have more authority to make exceptions and issue replacements than a first tier rep would have.

Maybe you are looking for