Unknown Exception During Itunes Import

This Bug still Exists for almost 10 years, will this ever be fixed?

Asking us to manually check for invalid characters between thousands of tracks it's not a fix.

 

Hi SpirosG, thanks for your report!
Did you experience a crash while importing from iTunes?
Can you share a crashlog and/or some more details on your environment?

Best, Enzo

 

Hi Enzo @ NI ,

No I am not experiencing any crash, it's more than a year I haven't experienced any crash (great job in stability ) i only get that message on the bottom bar everytime I try to sync the itunes library and the procedure stops.

I use windows 10, am aware that there are tracks containing unsupported characters (cyrillic, Chinese or unicode) in the xml and this is why I get that message.

Update : I've tried to import the same xml file to a different DJ software and the import was successful, it's clear that the problem is in Traktor's side.

This is my log:




2019-10-01 05:20:52 -
2019-10-01 05:20:52 - >>> LOG OPEN, Tue Oct 1 05:20:52 2019
2019-10-01 05:35:57 - Applying preferences.
2019-10-01 05:36:00 - Applying preferences.
2019-10-01 05:36:00 - Applying preferences.
2019-10-01 05:36:00 - Applying preferences.
2019-10-01 05:36:00 - Applying preferences.
2019-10-01 05:36:37 - *** Traktor CPU Info ***
Packages: 1
Cores: 4
Processing Units: 8
Requested Render Threads: 3
Optimized Processing: false

2019-10-01 05:36:37 - *** Traktor CPU Info ***
Packages: 1
Cores: 4
Processing Units: 8
Requested Render Threads: 3
Optimized Processing: true

2019-10-01 05:36:38 - - 1 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:39 - - 0 entries found
2019-10-01 05:36:44 - - 1 entries found
2019-10-01 05:36:47 - WARNING: unknown exception during ITunes import
2019-10-01 05:37:08 - Applying preferences.
2019-10-01 05:37:10 - Applying preferences.
2019-10-01 05:38:32 - WARNING: unknown exception during ITunes import
2019-10-01 05:38:46 - Applying preferences.
2019-10-01 05:38:47 - Applying preferences.
2019-10-01 05:39:07 - WARNING: unknown exception during ITunes import
2019-10-01 05:39:47 - Applying preferences.
2019-10-01 05:40:24 - Applying preferences.
2019-10-01 05:40:58 -
2019-10-01 05:40:58 - <<< LOG CLOSE, Tue Oct 1 05:40:58 2019

 

How is it possible that in 2019, there is still such thing as "unsupported characters" ?

 

Can anyone please tell me what more should i post because this thread it's still tagged under "need info"...

 

Hi SpirosG,
we fixed few issues related to Unicode and non-Latin characters in the latest beta - Traktor Pro 3.3.0.45 - so it would be nice if you could try to reproduce the problem with it. In case the bug is still there please get in touch to share your iTunes Library XML.

Without a way to reproduce the bug in-house we can't proceed with fixing it, that's why I put this thread in "need info" state

Best,
Enzo

 

Hi Enzo @ NI ,
I still experience the same problem, my library is huge and the XML file is 1.2Gb,
I compressed it in .rar, I hope it will be ok, I will send you the link in PM.

Thanks for the support.

 

Thanks SpirosG,
got the file and will look into this today.

Best, Enzo

 

Thank you Enzo @ NI , I know it will be a tough thing to do due to the size of my library, I assume you will probably find multiple errors!

 

Hey SpirosG,
looking into the huge XML file showed multiple errors! Seems like the file is not generated by iTunes but MusicBee instead and all the errors are encoding ones: invalid Unicode character, incomplete surrogates, few other minor encoding issues. I double-checked at binary level (so skipping all the iTunes/XML/Traktor logic) and those strings are actually "wrong" (at least when compared to the UTF-8 encoding of the XML file).

I know other editors are still able to load the file despite the errors, so one approach (still to be verified) could be to relax Traktor's strictness when parsing XML music library files... but I'm not sure that's the right way to go!

Best, Enzo

 

Hi Enzo @ NI ,

Thank you for the effort you've put on this.
I was sure that you would find multiple errors as i told you, you are right i use Musicbee to export the XML but i thought they were both (Itunes & Musicbee) using the same syxtax. What i understand is that the problem is not Musicbee but the fIles and their tags, i wonder if Traktor could just skip those files.

If you could relax Traktor's XML parsing strictness or just skip files with such problems it would be nice, i understand that this needs to be tested and it would take some time to look into it.

Once again thank you for the support, fingers crossed that there will be a solution in the near future.

 

Whatever files / tags / wrong codes you throw at Traktor, it should never crash/stop with an "unknown expception". If Traktor finds an error in the XML, it should just skip the XLM-tags the error is in. Maybe give a nice report about the skips when finished?

 

Hi Enzo @ NI any chance to take a second look at this now that you are focusing in browser functionality?

 

So yeah, any resolution here? This is killing me.

 

A solution! XML reformatting script. This worked for me. https://getmusicbee.com/forum/index.php?topic=25608.0