I’ve never used a DVS before… Please help, friends. (I’d ask in the NI forums, but I like you guys better)
Got everything hooked up right and grounded right (I think)… But it won’t calibrate, and the signal doesn’t look anywhere near right. Sometimes it will work… but with incredibly low accuracy and response, and plays at around +25%, no matter what I do.
Both decks act the exact same way, so I’m not inclined to believe it’s a problem with the turntables. I’m using an S4 as the traktor box, got the ins set to phono. Got brand new MK2 control records.
That happens when you use the wrong TC/TSP version.
Specifically, this is exactly what my scope looks like when I’m playing an MK2 vinyl after calibrating with an MK1 record. The speedup is to be expected since it kinda picks up some signal but the tone is at 2.5khz instead of 2khz.
What version are you running ? I forgot when exact version enables MK2 but you’ll have to be at least 2.1x to be sure.
2.1 was the first version that Mk2 control vinyls were used, i usually only get the messed up all over the place signal if i’m playing a piece of actual vinyl, not the incorrect control vinyl, have you checked all of your connections and that your RCA’s aren’t damaged, or that there’s corrosion on the connections between the cartridge and the tonearm?
@Pete - you bring up good check points however I’m positive that scope is virtually just like like feeding mk2 signal through the mk1 decoder. Notice how this spray pattern is very even on both sides. It stays pretty much like that instead of warbling about like an actual record would look like. I could post a screen capture if ya like as I can reproduce this at will (and this makes me think the good old timecode troubleshooting guide could use a little updating with more figures).
JesC had a similar problem though with 2.5 so I’m wondering what exactly he saw. In my experience feeding the mk1 signal through an mk2 calibrated decoder doesn’t look like this at all (two circles and a big dot with inverted cyan/yellow colouring vs a “proper” mk2 scope), but my result in that case is definitely biased since my license allows both timecode versions.
