Home → Problems →

beaTunes crashes repeatedly

• Edit

Jim

21 Apr, 2010 03:44 AM

Ever since upgrading to iTunes 9.1, beaTunes has crashed when attempting analysis on my Windows XP machine. beaTunes indicates that I have corruption in the song files; however, I am not seeing any signs of database corruption anywhere else.

I upgraded to 2.1.6 as soon as it became available and, if anything, that made the problem worse.

So, I guess I'm wondering if I am alone in this or if anyone else is experiencing similar problems?

Jim.

1. Support Staff 1 Posted by hendrik on 21 Apr, 2010 07:17 AM

   

   Hi Jim,

   does this problem also occur when you do not use the Detect Silence analysis task?

   -hendrik

   • Edit

2. 2 Posted by Jim on 21 Apr, 2010 10:10 AM

   

   Nope. I turned off that feature and it seems to process normally now.

   Thanks!

   Jim.

   • Edit

3. Support Staff 3 Posted by hendrik on 22 Apr, 2010 07:35 AM

   

   Good.
   I'll look into this and hopefully have it fixed soon.

   -hendrik

   • Edit

4. 4 Posted by Allison Kaese on 20 May, 2010 05:24 PM

   

   fyi -

   I was getting this same issue on 2.1.6 & 2.1.7 under both xp and win 7. the system would start to process a playlist, queue up the tasks & then get about 2 songs in and then the program window would close.

   again, turning off detect silence resolved the issue. Thank you for posting that fix.

   • Edit

5. Support Staff 5 Posted by hendrik on 02 Jun, 2010 07:11 AM

   

   I did some more digging and it turned out that the underlying cause seems to be a bug in Apple's QuickTime library. I filed a report with Apple and hope they will resolve this ASAP (wishful thinking). Unfortunately, for now there is little I can do to remedy the situation, but to recommend not to use the Detect Silence task on Windows. On OSX things seem to be just dandy.

   -hendrik

   • Edit

6. Support Staff 6 Posted by hendrik on 17 Jun, 2010 10:12 AM

   

   I believe I have found a workaround and implemented it in beaTunes 2.1.9. Please let me know, if you can still see this issue with the new version.

   Thanks.

   • Edit