iTunes XML Export – Accented Characters Not Recognized in VirtualDJ on Windows [#21547]

[adamlove]

**Hello Support Team,**

I’m encountering a character-encoding issue when using MediaMonkey’s new “iTunes.xml” export for VirtualDJ on Windows. Accented/special characters in track paths (e.g., “Señorita” or “Beyoncé”) appear garbled in VirtualDJ, causing a “File Not Found” error. However, if I load M3U playlists from the file system, accented characters work fine.

**Steps to Reproduce:**
1. Use MediaMonkey 5 on Windows to export the library/playlists to an iTunes Library XML file (e.g., via the “Export iTunes Library.xml” addon).
2. In VirtualDJ or similar, open the “iTunes” node referencing that exported XML.
3. Attempt to load any track whose file path contains accented or special characters.
4. VirtualDJ fails to locate the tracks with accented characters, showing “File Not Found.”

**Behavior Observed:**
- VirtualDJ’s browser displays question marks or missing characters for accents (e.g., “Señorita” → “Senorita”).
- The screenshot (attached) shows a track path mismatch due to missing accent marks.
- The same M3U playlists exported from within MediaMonkey via the "Export All Playlists" menu option *do* recognize accented characters correctly, when those playlists are loaded from the file system, so the issue seems unique to the XML export.

**Impact:**
- Tracks with accented/special characters cannot be played via the iTunes.xml node in VirtualDJ or similar.
- This disrupts the DJ workflow for multi-lingual libraries or any file names with diacritics.

**Environment:**
- **OS:** Windows (10/11)
- **MediaMonkey Version:** 5.x
- **iTunes XML Export Addon:** Most recent
- **VirtualDJ Version:** Current build (Windows)

**Request:**
- Guidance on whether there’s a known workaround or setting for proper UTF-8/Unicode export of iTunes.xml in MediaMonkey 5.
- Any recommended steps to ensure accented characters remain intact when VirtualDJ reads the exported XML.

Thank you for your assistance. I’ve attached a screenshot highlighting how VirtualDJ reports “File Not Found” for tracks with accents. Please let me know if you need further details or test logs.





**Best regards,**
Adam

[Lowlander]

Please start with updating to the latest 2024.1 release.

[Peke]

Hi,
I tested with Traktor, Platinum Notes, Mixed in Key, Mashup2 and Serbian Latin/Cyrilic filenames and could not replicate.

Can you create iTunes library export in iTunes and MM with same problematic files (note which files so that we can search thru both exports), then ZIP them and attach ZIP to Support Ticket.

[lucky_phil]

Hello,

I have noticed the same thing.

My file path is: E:\Lossless cd images\Garbage\Garbage (20th Anniversary) • The Remixes\19 - Garbage - Milk (The Tricky Mix).flac

It is the '•' character causing the problem.

The MM5 export to XML produces this:
file://localhost/E:/Lossless%20cd%20images/Garbage/Garbage%20(20th%20Anniversary)%20•%20The%20Remixes/19%20-%20Garbage%20-%20Milk%20(The%20Tricky%20Mix).flac

While the MM4 plugin to export to XML produces this (which works):
file://localhost/E:/Lossless%20cd%20images/Garbage/Garbage%20(20th%20Anniversary)%20%E2%80%A2%20The%20Remixes/19%20-%20Garbage%20-%20Milk%20(The%20Tricky%20Mix).flac

Traktor can't locate my file. But if I update the location to the one produce by MM4 then it can find the file.

I also have the problem with the accented characters, with the track 'Moira Jane's Café (Live Version)':

MM5 produces: Moira%20Jane's%20Café%20(Live%20Version).flac

Let me know if you want me to send you the two xml files. The MM4 one works.

MM4 produces: Moira%20Jane's%20Caf%C3%A9%20(Live%20Version).flac

Traktor can't find this file either.

[lucky_phil]

I have also found that if the replace the names of these fields in the MM5 itunes XML export:
<key>Comment</key>
<key>Bpm</key>

To these names:
<key>Comments</key>
<key>BPM</key>

Also, if the Date Added column is renamed to <key>Date Added</key> instead of <key>DateAdded</key> (i.e. add a space), and the field is populated as a date instead of a string, then it will show in Traktor before the track is imported/analyzed into Traktor's library, which is handy to know when you added the track to MM.

Example:
MM5: <key>DateAdded</key><string>16/03/2021 10:43 PM</string>
MM4: <key>Date Added</key><date>2021-03-16T22:43:43</date>

I hope I'm not being too nit-picky.

[Peke]

Hi,
Are you sure that you are using Latest MM 2024.1 Version from viewtopic.php?t=86639&sd=d ? There was recent fix to better standardize iTunes Export function.

[lucky_phil]

Hi Pete,

Thanks for your response.

I downloaded the latest beta version just now. I can see improvements to formating of the XML file when I open it in Notepad++, which is great. And also the nested playlists now showing in Traktor, which is also fantastic.

However the accented character issue still persists. The accented é in café still shows as "&#233;" in the file Location, rather than "%C3%A9"

Also, I noticed that the XML now converts the Title and Album fields to XML where they have accented characters:
<key>Title</key><string>Moira Jane's Caf&#233; (Live Version)</string>

which I would say is not correct behaviour as they are strings and not links. So they will display like that on the screen.

Later last night, I found the same issues with the letters ğ ç and â.

I'm no expert, but I just did a quick google search and it looks like the XML export is using UTF-16, but maybe it should be using UTF-8 to convert the special characters?

UTF-8 rpodcues: c3 a9 https://www.utf8-chartable.de/
UTF-16 produces: &#233 https://asecuritysite.com/coding/asc2

[Peke]

Hi,
Thx for investigation I can confirm your tests so I added it as https://www.ventismedia.com/mantis/view.php?id=21547

Good Catch! Sneaky one.

[Ludek]

Also, if the Date Added column is renamed to <key>Date Added</key> instead of <key>DateAdded</key> (i.e. add a space), and the field is populated as a date instead of a string, then it will show in Traktor before the track is imported/analyzed into Traktor's library, which is handy to know when you added the track to MM.

Example:
MM5: <key>DateAdded</key><string>16/03/2021 10:43 PM</string>
MM4: <key>Date Added</key><date>2021-03-16T22:43:43</date>

I hope I'm not being too nit-picky.

Just tested the newest official build 2024.1.0.3113 and the 'Added' date is exported as
<key>Date Added</key><date>2025-03-24T17:20:54.000Z</date>
which seems expected, so you have tested probably an outdated build / script ?

Otherwise https://www.ventismedia.com/mantis/view.php?id=21547 will be fixed in the next build 2024.2.0.3151

[lucky_phil]

Thanks Ludek. I did notice that after I installed 2024.1.0.3113

Thanks also for being so responsive.

I'll keep an eye on the builds.

[adamlove]

Hi Peke, Ludek & everyone,

Sorry for the delay—I had email notifications turned off and only just saw your replies. I’ve just installed MediaMonkey 2024.2.0.3150 (portable) and re‑exported the iTunes XML into VirtualDJ (screenshots below).





From what I understand, the accented‑character export bug is fixed in the upcoming build 2024.2.0.3151. That build isn’t publicly available yet, but will be soon. Is that correct?

I’m happy to upload the XML, database, or any test files if it’ll help track down any remaining issues. Thanks again for all your responsiveness and support!

[Peke]

Hi,
Latest 3151 build is available for download, can you confirm.

[lucky_phil]

Hi Peke. Thanks a lot for that. I have been on a holday, but I have just installed 3151 and have found the issue with the accented characters to be resolved. I check a few files with different characters and they load correctly into Traktor.

The only three remaining issues I have now with the XML file, if there is appetite to address them, are:

• 1. The <key>Bpm</key> field should be named: <key>BPM</key> so it can be read by Traktor before the track is analysed into the library

• 2. The <key>Comment</key> field should be named: <key>Comments</key> so it can be read by Traktor before the track is analysed into the library

• 3. I think the <key>Length</key><string>00:06:03</string> field should be replaced with <key>Total Time</key> and the track length should be displayed as: <integer>363000</integer>, which is the number of seconds multiplied by 1,000. This would allow the track length to be displayed into Traktor before the track is analysed into the library.

Regarding the Length/Total Time, I have checked against the XML file produced by the MM4 Export EXL plug-in and determined that the Total Time integer is the length in seconds of the track * 1,000.

The use case is that for large music collections where not all tracks have been analyzed into the Traktor library, it is useful to see the BPM and Track Length of each track when scrolling the playlists. Otherwise, each track needs to be analyzed in Traktor to be able to see this information, which uses up time.

None of the suggestions above are urgent for me, but would be nice if they could be done at some stage. I have a macro in Notepad++ that changes the names of the Bpm and Comment columns, but I can't use a macro to change the Length to Total Time.

Thanks again for your time and assistance. Happy for any of your team to contact me if you want further information.

[Peke]

Hi,
Reopened original bug an dcreated https://www.ventismedia.com/mantis/view.php?id=21591 for Total Time key.

[lucky_phil]

Thanks Peke. Appreciate it.