Hey guys I just finally updated to 2.1.2 and grabbed some MK2 vinyl. I’m running an Ecler Nuo 2 (just received this and it’s AMAZING) and Vestax PDX-2000 with Shure m35x.
I can’t however get Traktor to give me a good signal for timecode calibration. It says “Skipping” everytime no matter how much tracking force I put on the stylus. I also get the exact same results in the picture when adjusting tonearm height or adding/removing a headshell weight. Can you help me out?
Idk why they changed the calibration display, I should’ve just stuck with 2.0.3 and my MK1 vinyl. I had 2 very nice solid circles back then and none of the “SKIPPING” messages.
The weird this is it doesn’t skip at all, or none that I notice. I’ve tried absolutely murderous rewinds and scratching back and forth with not a single skip, however I feel like there is an underlying issue and it worries me. In fact, even with my sound system cranked (The subwoofer is right under my tables) I never experience any significant BPM flutter than the usual .01 or .02 bpm
A side question: Can I roll back to 2.0.3 and still use MK2?
I actually tossed my MK1 when the MK2 arrived, as it was so worn out. They had a previous owner and I got the short end of the stick as far as life on the MK1s. I should’ve just bought more! 2.0.3 is still my favorite release.
Anyone out there with some ideas? I have an odd feeling this is on the Traktor side of things and really want to nail down my signal and never worry about it again. I noticed that messing with latency and sample rate settings are improving the signal a little so this leads me to believe that Traktor is finnicky about what a “good” and “bad” signal are.
Still no signs of actual skipping from the table, but Traktor swears that it is.
Cool I’ll try that tomorrow as well. Also should I use a headshell weight? I’ve been pretty in the dark about that whole affair. It’s the Vestax PDX-2000, with the Vestax HS-1 headshell and m35x. As far as the scopes that I posted, are those bad?
Me neither, it’s not covered in the manual as far as I’ve read. I found this arbitrary posting from NI forum stating this
“During the calibration this is normal. The reason is that calibration basically is automatically setting the input gain into a suitable value. It starts from very high gain and then lowers it into a “good level”. With high gain, the waveform received from the timecode is actually clipped, which - for the application - looks exactly the same as if the needle is skipping.”