Hello Algoriddim Team and Fellow DJs,
The Fluid Beat Grid works great most of the time, but it has its downsides as well.
I think many of us encounter issues every now and then due to how the Fluid Beat Grid interprets tracks with intentional BPM interruptions or breaks.
In the attached video, I’ve used “No Diggity” by Blackstreet ft. Dr. Dre as an example. The track has an overall BPM of approximately 76.4, but at 4:17, there’s a vocal break where Djay falsely detects the BPM as 109. This section is actually an “open” part without any rhythm. After the break, the track returns to its original BPM, and Djay correctly resumes the grid from that point. However, during the vocal break, the BPM detection goes crazy.
This causes sync issues as Djay tries to maintain the 76.4 BPM during the rhythm-less section, resulting in unwanted and distracting sound during live performances.
The Problem:
These types of abrupt BPM fluctuations are often deliberate and artistic choices by the producer. They are not subtle and typically aren’t points where DJs would mix in or out. When Sync is enabled, these misdetections create awkward moments and disrupt the track’s sound quality.
Proposed Solution:
I suggest Djay implements a safeguard within the Fluid Beat Grid to address these scenarios. For example:
- If a sudden BPM fluctuation exceeds a defined threshold (e.g., 8%), Djay could ignore the Sync function at that point and assume the BPM remains consistent with the value before the break.
- Optionally, a toggle in the settings could allow users to enable or disable this behavior for tracks with such characteristics.
This feature would prevent unnecessary tempo adjustments during pronounced BPM breaks, ensuring smoother transitions and more reliable Sync functionality.
I’m curious to hear feedback from other DJs and the development team. Do you think such a feature would enhance the experience with Djay?
Thanks for considering this!
Best regards,
DJ Big Blender