Wow. That’s good news. Does it disengage keylock in VDJ when you bend with the platter when the motor is on like Engine OS?
Yes, in fact VDJ automatically detects in the same way as Engine whether it is a scratch or a bending. It seems to me that there is some sort of algorithm which beyond a certain percentage of slowdown or acceleration (30% it seems to me) automatically disengages the keylock.
So as soon as you hold the plater to scratch you are immediately beyond this threshold which allows VDJ to differentiate between scratching and bending
That’s weird. Engine OS disengages keylock with even slight drags or nudges of the moving platter when doing vinyl-style pitch bends, and different than how the DN-HS5500 does it. I don’t actually like how Engine OS handles the disengagement, as it’s not just for a scratch and doesn’t just disengage from extreme bending that’s clearly on the verge of a scratch. It’s odd, because Engine OS now doesn’t have any issue differentiating a bend from a scratch for the purpose of deciding if you should be allowed to assign a new main cue zero by pushing Cue while holding the platter. I presume the needle drop lock logic is the same, though I usually never have that lockout on. It seems perhaps, though, as if VDJ might be doing it better if it’s taking about ±30% bend to disengage keylock.
I couldn’t say for sure that it’s 30%. It seems to me that this is information that I read on the official VDJ forum.
I’m not a crazy scratcher, the scratches I do are relatively basic. Perhaps for very slow scratch movements this could be annoying for a more experienced scratcher.
But at my level the way VDJ manages the disengagement of the keylock during scratching has never posed a problem for me. The same goes for bending, it works very well and I don’t notice any variation in tone during the bending phases, even with quite rapid acceleration/deceleration.
What is a little destabilizing, however, is this feeling of hyper sensitivity of the platter on the M version on VDJ compared to Engine OS.
Either it is VDJ which amplifies the accelerations/decelerations too much during the bending phases compared to Engine OS. Either it is Engine OS which tends to attenuate them so that it seems more progressive during a stall adjustment.
I admit that I prefer the way EngineOS manages the motor from this point of view. On VDJ you have to be more delicate with the platter, the slightest touch can slow down your track too much and a poorly measured acceleration can seem too amplified and give you the impression of “jumping forward”
I have the same impression. With Serato or Traktor DVS (with flux) was feeling so much better. Unfortunately I do not have any hope that this will ever change.
1 Like
I don’t scratch a lot, either, but the keylock disabling is what’s bothersome on Engine OS.
As for amplifying acceleration/decelerations in VDJ with the M, are you talking about motor on or off?
Engine OS motor off jog bend is way too sensitive and not adjustable. If you’re talking about motor on, then that must be some quirk of how VDJ registers the bend stuff. So oversensitive on drags and nudges with motor on, but keylock usually stays on?
When the motor is switched on for that amplified feeling. I wouldn’t say it’s ‘too sensitive’ to be usable, I’d just say it’s ‘more sensitive’ than in EngineOS. If, for example, you want to slow down the turntable with your finger you have to touch it much more lightly, with less pressure. A bit like working with lower torque.
Except that the position of the torque selector remains the same. Quite strange to describe and it’s quite a subjective feeling. A bit unsettling at first when you know what it feels like on the EngineOS, but you get used to it.
But yes, with normal use of the edges of the platter and without obviously blocking/holding the control disc, the key lock remains activated when the motor is on. Unless, of course, you’re making deliberately exaggerated drags and nudges. In that case, you go above/below the 30% threshold of increase/decrease in motor speed compared to the speed at which it’s supposed to be running, and the key lock deactivates.
On the other hand, when the motor is off, using the M plate as if it were a jog is much more pleasant than on EngineOS, as you can set the amplitude value required for bending via the plate.
The default value for the JogSensitivityBend parameter was 0.300 on VDJ, which is more or less what it feels like on Engine OS, and I’ve personally set this value to 0.225 and I get something much smoother and more progressive. You have to make a larger gesture forwards or backwards but you get a lot more precision. It’s more in line with what I like. This setting also applies to non-motorised static jogs.
1 Like
Decision date (extension to 27 June 2024).
I wonder if some competitors are holding off on big moves (acquisitions, Serato-compatible products) until they know the outcome.
Not entirely surprising, although at this point im not sure what else they can say?
Honestly, just let it go through. The whole postponing it thing is just getting old at this point.
Another turn in this saga: The Post
Less of a turn, more of an end to the saga.
Isnt this a turn to rid the NZ commerce board in favor of the Canadians?
Still needs approval so it ain’t over yet.
If that goes thru, I think it will be good for the industry. Way better than Ali-Temu acquisition attempt.
