Sign In:     

Forum: VirtualDJ Technical Support

Topic: `pitch_lock` on | off global in XDJ-AZ?
On Pioneer DDJ-1000, I reprogrammed a deck button (Slip Rev) to toggle `pitch_lock`

`SLIP_REVERSE: pitch_lock`

and this would toggle `pitch_lock` for THIS particular deck.

On AlphaTheta XDJ-AZ, the same configuration affects `pitch_lock` on ALL decks.

Is this on purpose for this controller?
Similar to how quantize is now global?
Or am I missing something?


Is there still a way to control `pitch_lock` per deck?
I've tried `deck active pitch lock` but that didn't work...

Thanks!
 
Posted 5 days ago @ 10:26 pm
1) Technically, both DDJ-1000 and XDJ-AZ use the same behavior for this button.
This means that the button itself is capable to send different messages PER DECK.

2) I fail to understand how your DDJ-1000 mapping turned on pitch_lock on a "per_deck" basis.
As far as I know, all these years, pitch_lock has been an action that affects ALL decks no matter from which deck it's called. It has always been the case that it would lock the pitch of ALL decks at once.

3) Quantize (quantize_all) is not supposed to be a global action that's on/off on all decks at the same time.
It behaves like this only on some controllers like XDJ-AZ or Rane Four, that have a SINGLE "Quantize" button on them.
When "Quantize" exists on both sides of the controller, then "quantize_all" can be turned on/off on a "per deck" basis.

PS: Is there any chance that on your DDJ-1000 you didn't had "pitch_lock" programmed, but used a different action instead ? Maybe you used "beatlock" ?
 
PhantomDeejay wrote :
1) Technically, both DDJ-1000 and XDJ-AZ use the same behavior for this button.
This means that the button itself is capable to send different messages PER DECK.

2) I fail to understand how your DDJ-1000 mapping turned on pitch_lock on a "per_deck" basis.
As far as I know, all these years, pitch_lock has been an action that affects ALL decks no matter from which deck it's called. It has always been the case that it would lock the pitch of ALL decks at once.


Gone back and checked the DDJ-1000. "pitch_lock" is global there too.
Must've been confusion on my part - I would disable `pitch_lock` pushing a button on one deck, do something with the pitch slider on that deck, re-enable `pitch_lock` and continue working with the other decks, but it was a global setting there too.

Thank you, @PhantomDeejay, for clarifying and confirming what the expectation should be.

What I'm still a little confused about and need to experiment more - might be a tangent for this thread - is that `autoBPMMatch` might behave different when VDJ controls the AZ versus the 1000. I noticed that when I load a new track, (occasionally!) automatically changes the bpm of the other decks playing. I thought that was the effect of `autoBPMMatch` with "smart" setting and I thought I had it disabled. Am I correct here? Is `autoBPMMatch` = "smart" the only setting that auto adjusts the tempo of the mix?

 
Also, would you please explain (or point me to doc) what controls `smartPlay` and `smartLoop` behavior?

Looking at my settings, both of them are set to 'No' with `per decks` and enabled on some decks via checkboxes. I do not assign my decks to a particular function that would call for the "per deck" setting. Wondering how I ended up with these settings.
 
kenziekkay wrote :

What I'm still a little confused about and need to experiment more - might be a tangent for this thread - is that `autoBPMMatch` might behave different when VDJ controls the AZ versus the 1000. I noticed that when I load a new track, (occasionally!) automatically changes the bpm of the other decks playing. I thought that was the effect of `autoBPMMatch` with "smart" setting and I thought I had it disabled. Am I correct here? Is `autoBPMMatch` = "smart" the only setting that auto adjusts the tempo of the mix?



No. There are a lot of things that can change Tempo "automatically"
But the most important thing is WHEN it happens.

If it happens "on Load" then indeed it's the "autoBPMMatch" setting that's doing it.
If it happens when you press PLAY it could be "smart_play" or "quantize_all" that's doing it.

Since there's only ONE quantize button on XDJ-AZ that turns on/off quantize for all decks at the same time, it is possible that unintentionally you have started a deck with quantize enabled. Which means that if the track is within 10% pitch range, it will also match BPM and sync with the other deck.

So, please observe better WHEN the BPM changes and let us know.

kenziekkay wrote :
Also, would you please explain (or point me to doc) what controls `smartPlay` and `smartLoop` behavior?

Looking at my settings, both of them are set to 'No' with `per decks` and enabled on some decks via checkboxes. I do not assign my decks to a particular function that would call for the "per deck" setting. Wondering how I ended up with these settings.


Smart play and Smart loop are core options of the software.
What they do is explained at the settings window.
Basically smart play forces 2 things:
1) All of the jump/play operations (like hot cues goto actions e.t.c.) work at a beat aware function. This means that the track always stays in sync with an internal "clock" copy of itself.
2) It will snap the CBG to match that of the other deck if pitch range is sufficient (10%). If pitch difference is greater than 10% it will only snap the first beat.
On the other hand smartLoop is more simple:
It corrects your timing when you trigger a manual loop (by using the loop in/out buttons) by making sure that your loop is a perfect loop in beats. So, if your timing is "close to" but not "exactly" 4 beats, smart loop will automatically correct that.

Usually these options/controls are not accessible via buttons on controllers (because the controllers don't offer them printed on their silkscreen)
However, they are offered on GUI (skin) and most likely that's how you ended up having them enabled on some deck(s) and disabled on some other(s)

You can enable/disable them globally from the setting window, and if you use the GUI or any other means to change them, they will switch automatically to "per deck" adjustment.
 
WHEN is exactly right! These "magic" auto tempo changes happen on deck changes - when switching from Deck 1 to Deck 3, for instance.

`autoBPMMatch` is definitely evil in the context of XJD-AZ and is set to 'NO'.

I'm still experimenting with Quantize to see if it is somehow behind the auto tempo changes.
I do need Quantize for the ease of manual loop control for acapellas, so need to understand when it is "safe" to enable it so that I don't end up tripping a "helpful" tempo change.

Another reason could be the position of the tempo slider on either deck and whether "TEMPO RESET" has been pressed or not. The degree of tempo changes seemed to be inline with the "Tempo + 2.3%" reading on the display reflecting the position of the tempo slider on a deck.

Also exploring whether to `autoPitchLock`. I do have a way to manually toggle it though.

Finally, I need to approximate my VDJ configuration as close as possible to the standalone behavior.

Lots of variables to track.

Grateful for all the detailed explanations - thank you!
 
kenziekkay wrote :
Finally, I need to approximate my VDJ configuration as close as possible to the standalone behavior.

Honestly, I think that's the WRONG way of doing things.
While I understand that it's desirable for many reasons the 2 operations to be similar, there's no point to try to limit yourself to how firmware (stand alone) works.
Software (and especially VirtualDJ) is far more powerful and versatile than "stand alone"
So, instead of trying to force stand alone operation logic to software (and thus try to "limit" the software), you should be open to learn to work with 2 (quite often similar but some times very different) concepts.
1) Software logic that allows for far more many things to be done and your skills to expand, and
2) Stand alone operation for when backup is needed, or for that odd case you can't bring your laptop with you.

kenziekkay wrote :
I do need Quantize for the ease of manual loop control for acapellas, so need to understand when it is "safe" to enable it so that I don't end up tripping a "helpful" tempo change.


No, you don't need quantize for that.
You need to turn on "smartloop" and leave it enabled like the 99,999999999% of VirtualDJ users.
Then your loops will always be perfect, even if you don't enable quantize.
Stop thinking hardware.. :P
Think software..
After all, you choose to operate with a superior system (computer + software)
Learn to use it how it was meant to be used..
 
Thank you for the insight @PhantomDeejay - MUCH appreciated!