Firstly, I’m using MBP 2012 running Yosemite, Traktor 2.10.2, Rane MP2015 with CDJ 900’s in HID (no issues there) or two techs with a DJM T1 (this is where the issues are).
Brief history of my recent issues…I recently noticed my needles were WAAAAAAY past the useable point, so I got some new ones. A few weeks later, I started experiencing an issue where after playing for a while, I’d get a random drop out, and my control vinyl would have very “slow” behavior. IE - I’d spin the record back to cue to a previous point, and I’d have 1/2 to 1 second of lag for Traktor to recognize, and then it wouldn’t be going fast… just VERY slow backwards. Basically unusable for control vinyl purposes; scratching etc.. The quick fix was to go into settings, and click on the latency slider. I figured it might be an old USB cable causing the problem, so I got a new one. Also figured I’d try out my MK2 control vinyl.
Anyhow, here’s the current problem… When using the new MK2 vinyl, if I hold the record in place, the deck starts going crazy. completely random movements and speed fluctuations when nothing should be moving at all. When I use to the old MK1 clear vinyl, I have zero problem. Can anyone fill me in on what that issue might be?
I had that on my old 2010 MBP and an Audio 8. All I can suggest is restarting your laptop and launching TSP2 fresh, and bumping the latency up a bit. I never figured out the culprit and my 2015 MBP was completely fine right up to me getting an Audio 10.
Sounds like the ‘mega-latency bug’ that is present in OSX from Yosemite to El Capitan.
All versions of Traktor above 2.6.8 are susceptible to it on any version of OSX in the range above. It is an issue introduced by Apple in CoreAudio and was only fixed in macOS Sierra. It is 100% fixed in Sierra.
Not all users experience it but enough did for NI to address it and publish that the only genuine workaround was to go back to Mountain Lion, however I didn’t have it at all on Yosemite or Mavericks but I was plagued by it on El Crapitan.
Changing the latency setting can fix it as that resets CoreAudio but it doesn’t always work and as you say, doing that in a live situation is risky.
I also had the slow timecode response issue with my DJM-T1 - it’s a piece of crap.
To be fair I also had the audio degradation issue with all my controllers until macOS Sierra.