Hey Guys, i downloaded the new update and after installing it i started Traktor to play around with my S2. Even when i am not doing anything at all, the CPU load is nearly in the red space… Anybody having an idea what to do? I own a Windows Laptop with intel i5(2x2.3-2.53GHz) which shouldnt be the problem…
Multicore support is not enabled, and i’ve never had any problems with wlan on while DJing. Before updating, it didnt even use 1/4 of the cpu load i have right now. When i set the latency a bit higher, its alright… but i didnt need to change that with traktor 2.1.3 … kind of a step back, isnt it?^^ How high can the latency get without getting problems? i got it stable at 7.6ms… is that alright or should i start saving money for a new mac instead of my pc?
Well, this shit is making me feel bad. After playing around a bit with higher latency i just recognized that it is nearly impossible to set the cuepoints correctly. Now i set it back to the lowest latency possible, but now i am a bit scared about any issues because of the high cpu usage… It’s time for a mac i guess… wanted one for years now. I’ll save all my money for one now. mf 3D can wait haha
Didn’t have the time to try it out yet but as far as I’ve heard there are several people recognizing a way lower cpu load with Traktor 2.5.
This topic seems to be quite ambivalent…
To the OP, did you update your S2 driver? I’m not sure there is a new one, but the S4 has a new one and installing it made a difference with 2.5. However, the software still seems CPU hungry with my S4.
There havent been any updates in the service center for me, so i guess im with the newest driver. I didnt change anything in the settings after the update, i really have 0 plan why the cpu usage is so much more as usual. Other question: Since 2.5, the loops can only be set onto a beatgrid, as well as cuepoints… Anybody having a hint for me how to fix this?
I have a black macbook pro, dual core, 4gb ram and have been having issues with cpu load in the red as well. Did not have this with my previous version so i switched back and its fine. The main diffence tho is that the cpu load only spiked when I have more than one fx bank selected on my s2 which is a huge problem because I use one effect bank per channel. Not gonna upgrade to 2.5 for a few months until all of the other bugs are addressed as well. Cant believe they release this crap with all of the issues it has. beatmarker issues, audio clipping, cpu load to name a few
I was having terrible issues with high cpu load causing popping in the audio playing from Traktor. I found that my F1 had key lock engaged on all 4 slots, which was contributing significantly to the overall load. Once i turned them off the load went down to back under a 1/4 which i think is a perfectly reasonable amount. I can control the remix deck output with timecode vinyl, and scratch normally with the buffer size down to 128 samples and the fx turned on, without the cpu peaking out. I think that’s about the most the most demanding task i could ask the program to perform, so that seems to have been a good fix for my problems.
All the other things you had tried (multi core support etc.) also made no difference to me. The key lock (along with making the buffer size huge, which is clearly a useless endeavour) was the only thing to dramatically reduce my cpu load.
@OP, do you have key lock turned on in your track/remix decks? It seems that this feature is (or has become, i don’t know whether it was the same in previous versions…) really cpu hungry. If you do have a remix deck active, it seems an understandable load. Whereas you would only have been able to have 4 keylocks max in previous Traktor versions, you can now have that amount engaged with just one remix deck…
Hope this is a help to anyone else suffering the same kind of problem
I’ve found that on occasion I’ll get some drop outs when assigning fx banks to decks the first time. If I go ahead and assign the banks on then off when I fire up Traktor I don’t have any issues.
I am having the same problem. I turned down the sample rate and now it seems to be fine - but I did not have any issues until today which is strange. I started up my macbook pro after work today and I could not even play a track without it lagging.
I am using the Traktor control s2 with the newest Traktor 2.5 software.
Any idea what could have happened over night? I did not do any updates as far as I am aware.
This is affecting me as well, I’m running a brand new S2 on a MacBook Pro with 2.5. My CPU load goes through the roof and the audio cuts out. I do not have the multi-core processor enabled, and my latency is around 13.1 ms, I have a the biggest gig of my life sunday, and needless to say there is NO Way i could play a set like this!! Anybody have any idea what the problem could be? Any help would be much appreciated!
What was your latency at before? 7.6 is pretty good. If you’re doing straight mixing, and some hotcues, then anything under 20ms is good. For any DVS, or cue point juggling you’d want under 10ms. I also heard from a lot of people (and the review on here) that Traktor 2.5 had significantly less CPU load. I didn’t notice any change, but my CPU load was kind of high to begin with. I have to set it between 11-12ms otherwise I get dropouts.