Problem setting up new collection - analyzing

Hello - and thank you in advance for your help!

I finally made the dive into Traktor and I am not able to get my collection setup properly. I have imported everything (137,000 tracks - 722 GB - so, large - but not crazy)

I have turned on the Analyzed Column and sorted by it.

I then choose the first 100 tracks, hit analyze and after that worked I selected my entire collection and hit analyze.

The problem is two fold - 1: speed, 2: not working


1. speed - I started yesterday afternoon - when I came back in this morning after 15 hours it was working and said it had completed 2700 / 137,000 - serious lag compared to Itch.

2. Not working - after about an hour it crashed.

My problem is that when I started it back up it did not show ANY of the tracks as having been analyzed! I thought it saved this data with the track itself? Even the first test 100 show as not analyzed now - Why?

Machine - HP Laptop - Core 7, 8 gig, windows 7 64 bit, external WD studio 4 TB drive (mirrored to dual 2 TD partitions).

I don't want to keep wasting days on this if I am going about it wrong.

I have now created a playlist called "Analyzing", I am moving the collection to it 2000 or so tracks at a time and doing it that way. But at this pace it could literally take me a month to just get my collection analyzed - a weekend project for Itch.

Please tell me I am missing something?

Joe

 

in between your analyzation chunks, right-click on the collection and choose "save collection".
the collection file will be usually only re-written when exiting the program - which doesnt happen if the program crashes...

 

If you did a consistency check then all the files that were already analysed would come back an report as analysed. You may also have a corrupt file which traktor didn't like and made it crash. If you were showing the status bar at the bottom you would be able to see the last file that traktor was working on when it crashed. Try removing that file from your collection before starting again.

 

OK -- The consistency check seemed to pick up the other files, thank you.

I have started 4500 files at 2:00 so I can check to see what type of progress it is making.

Thanks for your help.

 

I have opened a ticket - here is the details:

I get the following error:
Problem Event Name: BEX
Application Name: Traktor.exe
Application Version: 2.6.2.112
Application Timestamp: 51c317cb
Fault Module Name: Traktor.exe
Fault Module Version: 2.6.2.112
Fault Module Timestamp: 51c317cb
Exception Offset: 008dd88e
Exception Code: c0000417
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0995
Additional Information 2: 0995e829763b1b104cf1d40604d3d3bc
Additional Information 3: 3b44
Additional Information 4: 3b4423016ce17394f0e1b9bb3775f392

I have tried reducing the amount of tracks to 750 and the problem still occurs. It is random, but during the "writing to tag" part of the process. I can go back and redo the same section and it will crash at a different file. Total lib size is 137xxx tracks. I have spent 2 days and have managed to analyze only 4466 of them. I am creating a playlist called "analyze" and dragging a number of tracks to this list, choosing it, hitting Ctrl-A, then choosing analyze.

Thank you

 

please contact the NI support if they can see if there are bad files making traktor crash.

 

Support told me that I probably have a bad or MP3 file. My problem with this is that it crashes at a different point every time. I can scan the exact same group of files 3 times - once it will go through fine, then the other two times it will crash on different files. I am still working through it, I bought a new hard drive and transferred everything to it just to see if running on a USB 3.0 drive will help.
---
OK..I have found one file that will consistently crash the system. However, some very strange things:

1. I have checked it with MP3val and it checks out.
2. It will play in media monkey fine.
3. the exact same file works perfectly in traktor on my apple mini.

Are there more problems with the PC code?

 

At the Point during analyze when T2 crashes the T2 Window is gone already so u cannot see on what Track it crashed. Only the Windows Crash Requester is shown then.


Chris

 

http://www.native-instruments.com/forum/showthread.php?t=198597

 

Wont help due i cannot see on WHAT Mp3 he crashed..see above...


Chris

 

A fix in the short term, which will suck is just to analyze 100 - 250 files or so at a time until you get to the file(s) that cause it to crash. (obviously you can go bigger file block sizes as well, it's up to you) Once you get to the crash, instead of analyzing that batch, move on to the next, etc. And save your collection after each analyze block. Once you've gotten through your entire collection minus the blocks that aren't analyzed, take your file block number down and try to re-analyze those blocks until you find the culprit.

I had a bad file that caused my analyzing to stop, but it didn't kill Traktor completely I don't believe, so after saving the collection I was able to see what file was the culprit.