2.0.2 seems to work a little better. But you can’t always expect to start it and go sometimes you’ll have to adjust your latency and may turn of some other running processes.
I’d call my self as close to an Expert with OSX & windows based hardware and Soft Setup as you can get, being a long time user since OS8 and Cubase days.
Latency was the first thing I checked, Increased it to 20ms (ugh! 1.2 ran at 1ms) helped somewhat but still glitches every so often on track loading.
Closed other Apps I’d normally have open (IMHO I should not need to though).
Analyzed a music folder for use (60 tracks for testing)
I’m just trying to figure is there any reason it takes up so much CPU juice or spikes the CPU occasionally ?
With 1.2 I could happily set Traktor in cruise on the macbook and go place play a game of CS on the same machine in a virtual XP machine enviornment on a separate spaces page without so much as a hiccup in the Audio !
And that was using un-analyzed tracks only
So If i’m not using the sample Decks or S4, and not sold on colored Wavforms … any reason to upgrade that I’m missing?
Kinda feels like I’ve stuck Vista on a 6 year old windows XP box … It works mostly just Kinda clunky and not very “performancey”.
I have a 2009 MBP with 4GB ram and ran TSP2 with no problems although I’m still using TSP 1.27 because of layout issues and waiting for the next update to TSP2. Did you turn off all extraneous features ie airport and close browser & mail?
[quote]Did you turn off all extraneous features ie airport and close browser & mail?
[/quote]
I dont close Airport, I did close browsers etc … but in all fairness it sounds a lil too much like a “your holding it wrong” statement.
i’ve been using Traktor for years without needing to jump though hoops, close other software etc. to make it work correctly, why should I have to start now - its the reason I enjoyed it so much until now - hell I could run Ableton with a ton of effects at the same time before, really don’t see that happening anymore
I certainly didn’t mean to offend you but you have to understand that MOST of the problems I’ve seen people complain about with TSP2 can be attributed to operator error. I should also point out that I was using TSP 2.02 and had no problems. I skipped 2.01 entirely.