Traktor Scratch Pro 2.8.1 Stability

What is the proper way to test the stability of TSP 2.8.1 and for how long should you do so to determine whether it is stable or not?


Im running at the moment TSP ver 2.6.8 with a 2013 Mac Book Pro 2.3 GHz Intel Core i7 , 16 gigs of ram and 500 gig solid state drive the os is Mavericks.

 

I tested 2.8.1 and personally i find it unstable. NI has a track record of missing major bugs that could create a crash and burn situation. I use 2.6.8 as 2.8.1 does not bring any major benefits to my DJing style. Ask yourself is the benefits worth the risk?

How i tested for stability:

First i take several of my past history playlist and add them together to create a playlist that has pretty much all the tracks i have played in the last month. I than take the playlist and let it run in cruise mode for a few days to see if Traktor will crash up loading the songs. I do this with no hardware hooked up.

After the above runs i than hook up all my hardware... i take the same playlist and basically do a live test DJ set using the songs in the above playlist and use everything you use in a normal DJ set. Effects, timecode, EQ. basically do a test set...exactly how you would a regular DJ set.

In my case i did 7 test sets. the test sets were about 1 to 3 hours long. BTW this makes for great DJ practice that you probably should be doing anyway. Out of the 7 test i had 2 sets that had issues and crashes. That was enough for me to stop testing and call it unstable. If i was able to do 10 sets with no issues i would have called it stable and used it live but sadly it was not the case.

NI support teams biggest excuse for crashing is "your file is corrupt". Which is why i use files that have played fine on past version for testing.

For the record. every time support has told me you may have corrupt files, they have not been able to explain why all my files play fine on past version of tracktor, on iTunes and on Serato. I really wish they would take complaints and tickets about crashing much more seriously instead just assuming its a always bad mp3 files.

Good luck with your testing. Let us know how it goes.

 

The only reason i would upgrade is because it now supports the new cdj and cdj 900 nexus in hid mode. But if its really unstable I'm fine with 2.6.8 and using 2000's/ 2000' nexus cdjs in hid mode.

 

so many different systems its running on, you never really know if its okay until you try it yourself. Mac or Windows etc etc
For me its running without any issues on my desktop PC and on my laptop (both windows 8.1) , only problem i have encountered is when assigning an effect the first time after startup it creates a short distortion, after that is okay changing effects without any issue.

 

I haven't spent a lot of time with it but the sound quality of m4a files appears to be on a par with 2.6.8

Still have problems with the Key text field randomly changing from MiK format to Traktor.

 

I'd say install both in case you need to use hardware that isn't supported in 2.6.8.
You just have to copy the collection.nml file from the folder of the last version you used to keep your playlists current (see other threads for how to run two versions side by side).
The problem I have with 2.8.1 is that the preview player always quits working after about 20 minutes or so of mixing. Quitting and restarting Traktor is the only way to make it work again. Obviously that's a non-starter, so I end up using Deck C for preview, which is cumbersome.
I really wish NI would focus on working out the obvious bugs in the existing software before pushing out superfluous new features left and right.

 

Same here , traktor froze on me today while loading a non curruped file after 45 min . I had this problem back in version 2.6.3 and 2.6.4.

NI Fails once again.

 

I've used another old dj program for over 8 years n rock solid. I stayed away from Traktor due to reading forums regarding instability. But anyways, I used Traktor 2.8.0 live for 4 weeks and it seemed solid. Cpu usage was low, until one day I loaded about 6 drop samples into the remix decks and I was red lining the cpu. Sound became distorted and had to put a cd on and restart Traktor. After that, I only loaded 3 drop samples n cpu was back to normal. Over all I think its stable but you cant really over load it. Intel i7, 16 ram.

 

my conclusing is every version after 2.6.8 isn't stable period .