Sign In:     

Forum: General Discussion

Topic: discussion about VirtualDJ 2026 Part 2 - Page: 9
Ah i didn't realize that was changed - I guess you could just keep it off, scrub through and enable it on the BPM you want.
 
So just to confirm - the BPM display behavior is still the same (Jogs show the stablized BPM, but the deck info part shows the actual fluctuations).
 
@VDJ DEV

I was wondering whether it might be useful to create a dedicated forum thread where users can upload tracks that present issues with FLUID Beatgrid.

This could give the dev team direct access to real-world problem cases, making it easier to identify specific malfunctions and further refine what is already an excellent new feature.

Curious to hear your thoughts.
 
Name tracks, yes. Upload them, no - because of copyright.
 
groovindj wrote :
Name tracks, yes. Upload them, no - because of copyright.

Yep!
 
I have a question about the new AI-powered lyrics, which were improved again in part 2.

I have already analyzed a few songs in Part 1. How can I get the songs to be re-analyzed without selecting each song individually?
 
DJ A Sharp - The One Man Band wrote :
Stephane,

Any info about keeping the two decks synced as mentioned earlier in this thread when auto-sync is engaged? When I click the stabilizer lock on deck A, the BPM on the platter displays (for example) 85.00 BPM, and locks there. The BPM up near the title bar continues to fluctuate with the variable BPM. When I load a track on Deck B, it syncs to whatever that tempo at the top is at the precise moment the track is loaded to Deck B. For example, if the LOCKED tempo is 85, but at the instant I hit load, the variable tempo is at 83.56, the track on Deck B will load at 83.56 instead of 85.00.

Is this by design? Am I doing something wrong? Or is this a bug? I know it's early release...I'm just trying to wrap my head around this so I can build a workflow around how it operates (or is designed to operate).


Stephane, in your reply to this post, you acknowledged this bug and said it would be corrected in the next build. I have tried this in every build since then without success. With auto-sync active, I engage the lock on a track after the fluid analysis, I then load a track on the opposite deck, but instead of the second track loading at the same tempo of the locked fluid track, the second track loads at it's analyzed tempo (0%).

Am I doing something wrong, is this a bug that hasn't been fixed, or is this just not possible?
 
It looks like there was indeed still a bug with autoBPMMatch, will be fixed in next update.
Note that alternatively, it still works fine with smartPlay enabled on play.
 
kradcliffe wrote :
I take it the Rane System One support is not part of this release?

No, but new controller support doesn't need a new release. It can be added silently to your existing release
 
The fact that you can't manually set anchor points anymore while in the BPM editor had basically ruined it. The point of an update should be to add or fix, not delete features.

Having to rely on AI and crossing fingers that two beats from two diffrent mashuped tracks will smoothly overlap and not have a 0,3 second delay between them (making it a huge mess) is a huge let down.

Before hand you could manually rectify a track to make sure its beats are well aligned, adding and moving anchors to precisely adjust the beat grid on certains parts if necessary, now you can just drag the automatically pre-established grid (and not the mutliple anchor points if its create multiples) but if the AI miss-analyzed the track, there's basically no fixing it...

I have a perfect example of how this update ruined it :



The beats aren't correctly detected. As you can see with the green arrows it won't align with the beats on deck 2, and it can't be manually fixed, making it impossible to synch with another track or beatloop. When played together even with the new BPM stabilizer button, it just creates a huge mess, the beats are not overlapping but playing with a terrible delay.

AI keeps misscalculating the beats, I've tried everything in this new BPM editor to make it so that the track on deck 1 plays smoothly with the beat on deck 2, I didn't manage to make it work.
Before this update, it would have been a piece of cake.

Huge disappointment, please at least bring back the "add" or "delete" anchor buttons
 
Anchors can be added, but the must be added on measure lines.
Anchors can also be moved, but you must hold down shift to move them, and there is (imo a bug), where even when you move them, the BPM that was detected in its zone stays the same until you drag a measure line within the zone.

This has been brought up before - I also don't see why this change was required, and is a fundamental shift from how the multi-BPM editor used to function that will cause persons to have to relearn manual editing but we are here.
 
Ah yes indeed, saw one of your earlier reply in this thread, I swear I tried to make that "add anchor" button appear by right clicking everywhere but that's on me.

To add an anchor simply right click on a measure line in the "fluid" section of the BPM editor.

Thank you DJ VinylTouch

Though I have to say, I would still prefer to have the old buttons (add or remove anchors) shown clearly.
Also, a tutorial should have been released alongside the feature, for its so disorienting when you are used of making things a certain way and have to dig into chats and forums to figure out how to use a feature that was so important.
 
Polygo Ned wrote :
Also, a tutorial should have been released alongside the feature, for its so disorienting when you are used of making things a certain way and have to dig into chats and forums to figure out how to use a feature that was so important.


Amen 🙏🏾

we are not all (me for sure) developers 😅
 
I am having trouble understanding the fluidAnalysis setting in Options & Tweaks and how that affects tracks when they are loaded into a player. My understanding of the fluidAnalysis setting is that if it is set to auto, then when I load a track in a player, the track should automatically switch from rigid to fluid in the BPM Editor if the track requires it, but it does not seem to do that. When I load a track that requires it, I still have to go into the BPM Editor and change from rigid to fluid. I also do not understand the difference between the manual and auto options in the fluidanalysis setting. If I have it set to manual, and then go into the BPM Editor and switch from rigid to fluid, the track seems to be adjusting the grid, but the same thing occurs when I set it to auto in the settings, so I am not sure what difference it makes when it is set to manual instead of auto.
 
I think at this stage the software is not perfect at deciding if a track is fluid or not. There are adjustments for sensitivity.
 
Note also that existing analysis are not modified, so if you load a track that you already had before, it was likely already scanned, so you'd need to go in the bpm editor to switch to fluid anyway.
 
Adion wrote :
It looks like there was indeed still a bug with autoBPMMatch, will be fixed in next update.
Note that alternatively, it still works fine with smartPlay enabled on play.


Woke up and saw this post...thought this was great news. Then I fired up VDJ and saw the update to fix this bug...Tested a few tracks and YES!!!!!!! Thanks for addressing it....outstanding feature!
 
Yesterday I had my first gig using Fluid Beatgrid and it has been awesome ❤️ having the chance to finally include my large 60s 70s collection to the set gave me such intense emotions. PS I humbly honored Marvin Gaye heavenly birthday 🕊❤️

In case you want to listen:

https://djfaberzee.fabriziooriani.com/portfolio-item/my-mixtapes/

It's the first "Music with a View - 02.04.2026"

Thanks VDJ for making this possible 🙏🏾
 
Adion wrote :
It looks like there was indeed still a bug with autoBPMMatch, will be fixed in next update.
Note that alternatively, it still works fine with smartPlay enabled on play.


this happened to me too and I thought I was doing something wrong
 
Note also that existing analysis are not modified, so if you load a track that you already had before, it was likely already scanned, so you'd need to go in the bpm editor to switch to fluid anyway.

Are you saying that tracks that have been on my hard drive before the update which already have BPMs need to be rescanned in the BPM Editor by switching from rigid to fluid, so that the auto feature will only work with newly added tracks?
 
73%