You are here: Home » Topic » Scanning of iTunes.xml stops at half thereafter CPU usage at Scanning of iTunes.xml stops at half thereafter CPU usage at FireFly Media Server (formerly mt-daapd) › Firefly Media Server Forums › Firefly Media Server › Setup Issues › Scanning of iTunes.xml stops at half thereafter CPU usage at This topic contains 4 replies, has 3 voices, and was last updated by fizze 8 years, 9 months ago. Log In Register Lost Password Viewing 5 posts - 1 through 5 (of 5 total) Author Posts 22nd October 2008 at 9:54 pm #2670 NeomaDParticipant Scanning of iTunes.xml stops at half thereafter CPU usage at 99% forever… As the subjuct states, I have a iTunes library containing 11000 songs… …at song 8062, it stops scanning everytime. The CPU usage rushes to 99% and are there … …forever… Is my iTunes lib corrupt? How fix? //Best regards Martin Stegmark, Sweden 23rd October 2008 at 9:37 am #17797 stretchParticipant song 8062 has corrupted metadata. It’s the music file itself, not the iTunes library file. You will have to fix it or remove it. You could run something like this http://mp3val.sourceforge.net/ over your entire library to find & fix any other corrupted files you may have. 23rd October 2008 at 2:25 pm #17798 fizzeParticipant If you bump up firefly’s loglevel to 5 or even 9 before the rescan you’ll see the file being scanned. The last file it attempts to scan makes firefly bail, so that’s the culprit. 😉 23rd October 2008 at 7:21 pm #17799 NeomaDParticipant It fixed the problem, working fine now… The app mp3val, reported problem with 75% of all my mp3:s… 🙁 …so I skipped that and used debug 9 to find the corrupt song. //Martin 24th October 2008 at 8:23 am #17800 fizzeParticipant Yes, it appears a great deal of tools out there just dump crap into the id3 headers 🙁 Author Posts Log In Register Lost Password Viewing 5 posts - 1 through 5 (of 5 total) You must be logged in to reply to this topic.