We've reported our initial findings from the first day in someone else's thread here, but i'll repeat them here... in summary - Traktor 2.6.1 is like the traktor from a few months ago, for us anyways... it crashes almost constantly, and at least it's reliable in at least doing that - crash... half the time it doesn't even produce a proper crash log to send to NI.... 1) Upon installation of 2.6.1 on top of 2.6.0 - it waits about 5-10 minutes at the 95% line when loading our (rather large) collection... this is when loading 2.6.1 FOR THE FIRST TIME.... it crashes after... no log ( or log of zero size ) is produced... CRASH UPON RECEIVING 2.6.1 ? CHECK 2) After running 2.6.1 again, it seems to work... the keyword here is SEEMS... once we started importing several hundred new tracks... a new crash soon to follow... does not save any work before it crashes... just crashes.. CRASH UPON IMPORTING NEW FILES? CHECK at this point i should say that we have open up a ticket on all these crashes months ago, and they were seemingly fixed in the last few versions - as in we didn't have any crashes until 2.6.0.... 3) Disgruntled that we cannot import new files, we start analyzing the KEY (just the Key portion) of our older files, as sooner or later they need to be analyzed... within 5 minutes Traktor crashes again... Did so with random parts of our collection - Traktor CRASHES UPON ANALYZING KEY OF OLD FILES? CHECK 4) Pissed off at this point, we decide to re-create our collection FROM SCRATCH and import all of our folders... this takes 3 days and sure enough, on the UPDATING <file> portion, Traktor takes 3 days but crashes again. CRASHING WHEN IMPORTING FILES TO NEW COLLECTION - CHECK. 5) At some point we figure out that we can SAVE COLLECTION *after* traktor has crashed.... however doing so, and restarting Traktor produces "Your collection is invalid and has been renamed" EVEN THOUGH TRAKTOR ITSELF PRODUCED THE FILE... NOT LOADING ITS OWN COLLECTION FILES? CHECK at this point i feel like giving up (again)... as you have to understand our collection takes at least 2 minutes to load every time so this is NOT quick troubleshooting here...how can we go through these problems again, when we opened up a ticket months ago and got them fixed! traktor 2.5 was working without any problems... importing... analyzing... whatever you wanted to do - no crash... now all the sudden back to this... very unprofessional coding here. of come to think of it let's add 6) Sometimes when Traktor crashes upon start (yes it does THAT as well) it deletes my .TSI file with all my settings in... does it bother to back it up beforehand? nope... just overwrites old one and then crashes... CRASH UPON STARTING TRAKTOR and destroying TSI file? CHECK How can you crash a program again and again and have the crash file size 0? How can an MP3 that's already been imported months ago, crash a program again when importing now? How come NI cannot produce code that's fail-safe? If an MP3 is incomplete, or an MP3 is a DJ mix or an MP3 cannot be analyzed JUST MARK IT, don't crash the friggin program with unsafe code. We will not be giving up - as in we will be opening up a ticket for all this behavior. We didn't pay for Traktor to get unusable software that crashes CONSTANTLY (which is what 2.6.1 does) We have a large collection, that was working flawlessly in 2.5, with some new problems arising in 2.6... however 2.6.1 is unusable and now that we have converted our collection file to 2.6.1 we're stuck with this one, because as i said re-creating it from scratch takes days, and traktor crashes anyways... I'm a programmer myself, although quite intermediate, i still do not understand how an advanced program, such as this, and GERMAN MADE, can crash soooooo much, especially when these types of problems have been reported (by us to you) and fixed by you... Blows my mind that COLLECTION INTEGRITY and the PROGRAM NOT CRASHING aren't your two most important priorities... seems like your priority of defeating MIXED-in-KEY has resulted in rushed, crappy, incomplete code that makes us do your QA work for you... that's our impression based on above behavior. hope you can fix these 'old/new' problems, even though your program doesn't produce many crash logs.