Push!
Any update on this bug?
Comment actions
Post
Follow
[SOLVED] Bug: Location parsing XML (iTunes) in rekordbox 3 on Mac
First of all I like the new version 3 of rekordbox but there is a major bug in parsing the location of the tracks in a XML file (especially iTunes bridge).
Whenever %CC%88 is found, the previous character should be converted (german umlauts):
a -> ä
o -> ö
u -> ü
A -> Ä
O -> Ö
U -> Ü
Whenever %CC%81 is found, the previous character should be converted (apostrophe):
e -> é
%C3%9F shall become "ß" (without any attention to the previous character) -> this is working
So when I sync my playlist with version 3 (imported with 2.2.4) all tracks with these special charcters get duplicated because rekordbox thinks that it is a new track that is not in collection.
Look at the pictures for an examples.
Hope someone can pass this bug report to the developers of rekordbox.
Cheers, Alex
Post is closed for comments.
Date
Votes
6 comments
Hi
I can confirm that this problem is still in RekordBox 3.0.2. I live in Denmark, and have exactly the same problem with special danish characters.
iTunes Bridge duplicates all files with these special characters, as it can't find the tracks in the RekordBox database, and think the tracks have to be imported once again.
Best regards,
Hans
Comment actions
Hi,
I am glad to hear that I am not the only one with this problem.
I did some tests with the recent version and a Windows 7 virtual machine.
The error only occurs on Mac OSX. On both Mavericks (10.9.x) and Yosemite (10.10).
With exactly the same iTunes Music Library.xml file on Windows the location gets parsed correctly in rekordbox 3.x.
Hope this get fixed soon in newer versions.
Best regards,
Alex
Comment actions
Hi,
still not fixed in 3.0.3.
Since iTunes 12 changed the location tag as mentioned here: http://forums.pioneerdj.com/entries/61364409--SOLVED-Problem-with-RekordBox-integration-with-iTunes-12-Running-on-Mac I could not use rekordbox 2.2.4 to import my playlists correctly anymore. Now I must export them in iTunes to *.m3u and then import them in rekordbox.
If the engineers need more information to fix this problem, let me know what I can do.
Best regards,
Alex
Comment actions
It sounds like an XML parsing issue, I'll create a ticket for the engineers to investigate.
Comment actions
Engineers have been working on this and hope to have it fixed shortly. I'm told it won't be ready for 3.1, but soon after.
Comment actions