Studi-Jo
Run latest VDJ release 2026 V9295 on a MacBook Air M4 with macOS Tahoe 26.2 and with Pioneer FLX-10.
Yesterday I had a gig and had to restart VDJ 2 times.
Even if 'Automatic BPM Match' and 'Auto Pitch Lock' disabled the players follow each other.
I've loaded a song with a big difference between deck A and B. When I pre-listened to the deck, the other deck took over the same BPM with a terrible pitch of 25 %!
Enabled and disabled above features but no luck.
After restarting VDJ the issue was resolved but about 1 hour later had the same problem!
Restarted again and luckaly it was stable till end of the evening.
Any idea how this happens or how to avoid in the future?
Yesterday I had a gig and had to restart VDJ 2 times.
Even if 'Automatic BPM Match' and 'Auto Pitch Lock' disabled the players follow each other.
I've loaded a song with a big difference between deck A and B. When I pre-listened to the deck, the other deck took over the same BPM with a terrible pitch of 25 %!
Enabled and disabled above features but no luck.
After restarting VDJ the issue was resolved but about 1 hour later had the same problem!
Restarted again and luckaly it was stable till end of the evening.
Any idea how this happens or how to avoid in the future?
Posté Sun 03 May 26 @ 5:43 pm
DJ VinylTouch
Since you are using the DDJ-FLX10, are you by chance using the sync button and holding it down for longer than a second?
When that is done, it engages beatlock for the deck, which does pitch match mirroring/etc.
If you are doing that and do not desire the behavior, perhaps you can create a custom mapping to delete the SYNC_LONG key mapping.
When that is done, it engages beatlock for the deck, which does pitch match mirroring/etc.
If you are doing that and do not desire the behavior, perhaps you can create a custom mapping to delete the SYNC_LONG key mapping.
Posté Sun 03 May 26 @ 7:17 pm
Studi-Jo
Honestly can't remember, I played around with the 'Automatic BPM Match' and 'Auto Pitch lock' setting; I enabled and disabled.
Anyway the other deck changed BPM when I started the other deck for pre-listening. I'm sure didn't use the sync button that time.
Will play around with the sync button and use it more than 1 second to see what it does.
Anyway the other deck changed BPM when I started the other deck for pre-listening. I'm sure didn't use the sync button that time.
Will play around with the sync button and use it more than 1 second to see what it does.
Posté Sun 03 May 26 @ 7:23 pm
PhantomDeejay
Also:
Quantize, which IIRC is a button on FLX10, can have a somewhat similar effect, so pay attention to that.
The only thing that makes me wonder, is that quantize by default will not match BPMs if the pitch change required to do so is more than 10%. Of course there's a setting for that, that you may have changed, or you may not.
Just saying..
Quantize, which IIRC is a button on FLX10, can have a somewhat similar effect, so pay attention to that.
The only thing that makes me wonder, is that quantize by default will not match BPMs if the pitch change required to do so is more than 10%. Of course there's a setting for that, that you may have changed, or you may not.
Just saying..
Posté Mon 04 May 26 @ 6:45 am
Studi-Jo
Thanks, I will make a custom mapper and remove 'beatlock' and 'quarantize' from the default mapper.
That way it can't be enabled during a set.
After that I will give it a try at home and play some hours to see how it behaves.
That way it can't be enabled during a set.
After that I will give it a try at home and play some hours to see how it behaves.
Posté Mon 04 May 26 @ 12:06 pm
DJ VinylTouch
They can always be enabled from another mapping (custom button, keyboard shortcut, skin, other controller, etc), but this remapping prevents you from accidentally enabling it from that (DFJ-FLX10) controller by mistake and not knowing it.
The default skins, as well as many other skins, show the enablement status of the auto sync/pitchlock options, and I believe having the script on a custom button/pad page button also shows highlighted status when enabled - those may be able to guide you on determination of whether or not you activated it or not and didn't know.
The default skins, as well as many other skins, show the enablement status of the auto sync/pitchlock options, and I believe having the script on a custom button/pad page button also shows highlighted status when enabled - those may be able to guide you on determination of whether or not you activated it or not and didn't know.
Posté Mon 04 May 26 @ 12:09 pm
Studi-Jo
Thanks everyone for the input.
Played around and believe 'beatlock' was the feature that gave me almost a nightmare.
Played around and believe 'beatlock' was the feature that gave me almost a nightmare.
Posté Tue 05 May 26 @ 4:02 pm