A post was split to a new topic: BPM Analysis issue
Hi @Slak_Jaw. Can you tell me what the other setting “Key” on this “Library” screen does.
It has 2 options “Fuzzy” and “Exact”, but as far as I can see it doesn’t have any impact on things.
Hi @DJ_Big_Blender, this affects how Key Match works. Please check out the linked article below explaining what fuzzy key mixing is.
Hi thanks,
Yes I am aware of that technique, but was looking for how this setting reflects the way the software works.
@DJ_Big_Blender if set to Fuzzy and you press Key Match in djay it will use the Fuzzy Match method instead of changing the key to Exactly match the other track.
Setting this to off does nothing for me, the BPM will still be automatically adjusted on some tracks. This is unintended behavior, right? Can you please check this again?
Automatically adjusted? You mean you’re seeing the BPM readout change when using sync?
Please give at least one example of a track, and exactly what you mean by “automatically adjusted”.
You can try Lustmord - Their souls asunder. It will straight from the beginning move from 55 to 66 BPM. I know it is an ambient track. The thing is, the BPM should never automatically change. I tried the new function switching automatic tempo detection globally to off so I am really confused that this could ever happen, no matter what track.
Just to be clear, setting the new option to OFF should make the BPM become fixed, right? If so, that is clearly a bug.
Thanks for your help!
Hi @axibert, if you open the Edit BPM menu, is the BPM set to Straight? For me this track is being set to 67 BPM using this setting.
I wanted to thank you and the team for implementing the ability to turn it off by default. I’m still a new DJ and use sync when recording mixes, and had the dynamic beatgrid totally botch part of one because it thought the section dropped over 50bpm, causing the other track to slow down drastically in turn, when the track was in fact in constant time. The ability to turn it off by default and enable it for tracks where it does occur is the perfect implementation in my mind. I appreciate your team listening to the community and taking their feedback into account.
@c20c20 when things like this happen, it’s best to report it here, giving as much detail as possible, so that the team can look into why it might have happened and improve the detection.
What was the track (artist and title) and where in the track (minutes and seconds) did it occur?
