Is anyone else having issues with key lock since the 2.1.1 update? With keylock on and the pitch fader moved anymore than 1% I’m getting missing transients and occasional skipping sounds. This didn’t happen before the update, and it only appeared around 2 weeks ago and has been getting worse.
It only happens with Keylock on, and it’s pretty annoying.
Hi, I used to keep my key-lock off but I had been hearing a lot of good stuff about TP2 key lock so I was playing with it the other day… And it was horrible. I was doubting everyone’s ears that were saying key-lock is fine… But then, when I tested quite a few tracks yesterday, I couldn’t reproduce the awful sound any more. It’s suddenly “good enough” for me.
I agree there might be an issue with the current version’s key-lock, but I couldn’t nail it. Got to be able to reproduce it before I email tech support.
Nobody’s mentioned specs. I’ve had no problem with keylock up to + or - 5% pitch fader and aliasing of audio. Anything beyond that and I really start to hear artifacts in the tracks. MBP 2.8 GHZ Intel core duo w/ 4GB Ram
Okay, I tried it with Multi core off and on, I found it better with it off, but it was still happening. Load meter hovers between 30-40%, less if Multi core support is off. I’m using a Traktor Audio 2, 44100 hz, 256 sample rate and have 9.7 ms.
Computer specs: 2.7ghz Dual core, 2GB RAM, Windows 7 Home Premium.
I might just go back to 2.0.3 for now, because I’m playing at a party on friday and don’t want any problems.
I had weird problems with the new sample deck keylock, (wrong pitch, glitchy transients, etc.) but i cant say i’ve had any problem with the track deck ones.
I have been trying to get off 2.0.3 for quite a while but 2.1.X just doesn’t work very well. Issues ranging from the keylock problem you mentioned to adjusting the phase with the jog is seriously laggy now with 2.1.X.
PS: turning off multi core corrected the pops hisses and cracks but the other issues remain.