No longer possible to convert .itl library files on my Big Sur Mac

Question

Level 1

8 points

No longer possible to convert .itl library files on my Big Sur Mac

For over a decade I've been using iTunes on Windows, while often making a copy on an external drive in order to use it on an old Mac (2014 version). With the introduction of Apple Music things got a bit more complicated but so far it always worked... till today. While using the option key to open a new library I get a pop up saying the .itl file is 'not valid' and I should chose a different library or create a new one.

Been checking and trying a few things out myself and updated from version 11.4 to 11.7 (seems to be the maximum update for this machine). Been reading about similar issues with Monterey but iOS 11.7 is still Big Sure so that shouldn't be a problem to be compatible with iTunes files. The .itl is also not corrupted, I linked the exact copy to iTunes on Windows and it works fine there. Checked permission acces on the Mac, all is available to read and write. Tried to do it the other way around and chose to import the playlist from within Apple Music but I get the same error, now saying the file is not a valid 'export file' instead of not being a valid 'file'. Then tried to import the xml file, I red about that option in a different sub here saying it would generate all data except from 'date added' but when I do that I only get the music purchased from Apple while my imported CD's (big majority) remain excluded. All help is appreciated here...

MacBook Pro 15″, macOS 11.4

Posted on Jan 22, 2025 5:52 AM

Reply

Answer 1

turingtest2

Level 10

275,526 points

Jan 22, 2025 7:51 AM in response to cdnathan

Hi,

It was all straightforward when iTunes was updated in parallel for Mac and Windows at the same time, and the library was cross platform compatible. The Mojave version of iTunes broke that somewhat as it became an OS component that Apple updated when they felt like it. With Music in Catalina it became more complicated as, as far as I can tell, Music only considers iTunes libraries created by Mojave as valid. Older .itl files don't work. There is a separate issue with Monterey where it just stalls when attempting to convert what would otherwise be valid .itl libraries.

If you'd like to send me your .itl file (email in profile) I can try converting it to a .musiclibrary package, but success may depend on which version of iTunes for Window the library was created by. When using the XML export/import route the import phase only works if you've edited the XML file such that it correctly uses the paths that you've copied the files to on the new computer. Failing this all you see is your purchase history, assuming that you are signed into your Apple Account.

The other approach you could use is to take out a temporary subscription to Apple Music, which would let you clone the library from one machine to the other. After you download all content in the cloud you could turn off Sync Library in both computers and then cancel the subscription renewal, assuming you no longer want it.

tt2

Reply

Answer 2

cdnathan Author

Level 1

8 points

Jan 22, 2025 12:19 PM in response to turingtest2

Hi,

Thanks for your answer and clear explanation about the history of this error, obviously an accident just waiting to happen...

On Windows I'm no longer having the default path C:\Users\<username>\ etc. since my library became too big and I had to move it all to an external drive. Therefore the current path on that source is now as short as it possibly can, unlike the external drive with the copy on the Mac it does oc has a drive letter.

After importing the .xml on the mac (with disappointing result) that file itself seems to remain in the external drive. I actually have no idea how to start editing anything in order to make the import work as complete as possible?

The other approach... not sure if that's an option at all with a library that's over 1TB (currently over 102k songs). My biggest scare here is that Apple would bring back the original data in all purchased iTunes songs, a few thousands that are now all edited to my own preferences. The majority of the tracks is imported from CD in 256 aac, and a bunch of very old fashionned mp3's. I'm fine with taking risk creating copy's as long as the original Windows version remains safe :-) That concern is also the main reason why I do these manual copies for years now. Apart from that constantly cloning from the Windows device to the Mac (and iPhone) would suit me very fine!

Thank you for your offer to try to convert the itl.file, which sounds really tempting and surely easy for me but it wouldn't be a solution in the long run since I'm used to update those copies at least once a year. The creation date of that specific itl.file gets updated all the time in properties, so can't tell the date that counts. I'm running iTunes since 17 years now, however about a year ago I needed to restore a Backblaze back-up of the .itl file.

Nathan

Reply

Answer 3

turingtest2

Level 10

275,526 points

Jan 22, 2025 12:41 PM in response to cdnathan

Another issue moving between Mac and Windows is that Windows really only like NTFS, which Mac can read but not natively write. Both platforms can read and write exFAT, although Windows cannot create that format, and Macs prefer HFS+/APFS. The workaround here is to copy data over a network where the source and destination file systems don't have to match, and each computer can work with the disk format it prefers.

What build of iTunes is installed? See Help > About iTunes if you're not sure. I can run a test at my end to see if Mojave iTunes can read a library created by that version, and if that will then open in Music. I'm using Catalina, but Big Sur can also be persuaded to install iTunes at a push. (Search Retroactive iTunes for details). It that were to work you might be able to miss out a conversion step and stay in a familiar environment.

The main change when moving an XML between Windows and Mac is to flip any \ to / and replace the path to the media folder in Windows (something perhaps like X:\iTunes\iTunes Media) to its equivalent on the Mac (e.g. <VolumeName>/iTunes/iTunes Media) not forgetting that any spaces in the path need to be represented as %20. Typically it requires one or two global search and replace operations in a suitable text editor. Macs and Windows may also use different end of line markers (LF vs CRLF) which may or may not have an impact depending on which direction you are porting the XML.

tt2

Reply