New Traktor? NI should sort the current version first.

[photojojo]

hmmm, interesting.

[steveboyett]

One reason I have only just upgraded to TPro from 2.5.3 is because I simply could not abide NI's habit of introducing new features and bugs without correcting existing ones, and the clear lack of a throughline in their vision for the app's ergonomics. Changes in function and layout seemed completely arbitrary and there was a constant learning curve with even incremental versions.

The current Traktor is the first version that has been stable and functional for me (I need a LOT of BPM increase with key lock) since 2.6.2 (which I never used cuz I liked 2.5.3 better).

I quit the NI forums out of frustration with the lack of any coherent vision behind Traktor's development, with the ways they ignored their beta tester's complaints (no, I wasn't a beta tester), and with their absolute denial regarding bugs and functionality/ergonomic demands (no deck mute? Really?).

Naturally I have misgivings about the upcoming version (oh, boy -- another learning curve, right after I upgraded!), and I want to have a positive outlook. But NI's track record hasn't helped with this.

[LanceBlaise]

I never experience any of these bugs... i guess i'm just lucky! KNOCK ON WOOD!!

[BradCee]

Big difference between Traktor 3 and Pro is that Pro was totally and completely rewritten from the bottom up.

The difference between 3 and Pro cannot be understated.

admittedly it was a weak example, but i think we all know what i meant

[Zac Kyoti]

Are there any showstoppers that anyone is experiencing?

There is one that drives me batty (other than the aac bug) - it's not a show stopper, but definitely puts a kink in my workflow: Using "reset" in an FX unit resets the values to the snapshot of the last effect you loaded, not necessarily the effect you are hitting reset on. It's really frustrating, since snapshots are a really efficient way of getting the perfect sound you want instantly. But as it stands, usability is half-baked. You can duplicate this yourself: load delay in unit one, beatmasher in unit 2, then hit reset on unit one > the delay settings are now those of the beatmasher. The only way to straighten it out is to take the extra step of reloading the effect again.

I would LOVE this to be fixed before/in the next version.