Se Connecter:     

Forum: General Discussion

Sujet: discussion about VirtualDJ 2026 Part 2 - Page: 8
WOW Part 2 is finally GA released...soooooo happy thank you VDJ...

I have a couple of questions:

1) Let's say I have a batch of songs I want to be FLUID BEATGRIDDED... I try to select let's say 10 and ask VDJ to Analyze for BPM...I noticed not all those 10 have Fluid Beatgrid enabled, I had to select Fluid in BPM Editor.
2) I noticed when FLUD is used I cannot halve...so I have songs at 115 which are clearly on the half BPM...I believe this should be re introduced...

Thank you!!!!
 
I noticed the lack of halve/double for fluid myself when I needed to divide the fluid analysis recently.

I agree it should be there.
 
Anyway I did some tests and so far IT IS A GAME CHANGER ✨️🔥❤️ can't wait to have my gig this Thursday and use it to create even more amazing mixes. THANK YOU VDJ ❤️
 
DJ Faber Zee wrote :
I try to select let's say 10 and ask VDJ to Analyze for BPM...I noticed not all those 10 have Fluid Beatgrid enabled
If the regular (fast) analysis shows that a track is stable, VirtualDJ will not try to use the (slower) AI algorithm on it. If you really want you can force it manually in the BPM editor.

DJ Faber Zee wrote :
I noticed when FLUD is used I cannot halve
Because the grid is "fluid", just halving or doubling the average bpm would risk mis-aligning some of the fluid anchors, so in Fluid mode, the better way is to adjust the BPM Range and let the AI run again, this way it will get the correct BPM but still find all the small drifts correctly.
 
Dear Stephane, thanks again for everything you do for us.

Regarding batch analysis, I selected only tracks with real drummers, and I noticed that some of them are not automatically recognized. Good to be aware of this. I have run batch analysis on all tracks that require Fluid, but I will double-check each track before loading it.

As for halving/doubling, I understand the behavior now. After testing, I can confirm that by reducing the BPM range, VirtualDJ correctly detects the half BPM.
 
It's just a little bit confusing that there are now 2 different methods for the same process (finding the tempo).

For rigid we still have /2 and x2 buttons, but for fluid they don't exist and people have to use a different method to get the result.
 
Actually changing bpm range leads to a more precise analysis, thus for tracks where I know the bpm is halved, I will reset the bpm range. The only thing I would modify is that when I change the range within BPM editor for a specific track now it changes the bpm range default... and I believe it's not the way it should work... BPM editor range change should stick to the track I am actually editing.
 
Agreed, it should be "analyse this track at..." rather than "analyse everything at..."
 
groovindj wrote :
Agreed, it should be "analyse this track at..." rather than "analyse everything at..."


Also because we have the default bpm range in Options...
 
Yes, because when doing rigid analysis the /2 and x2 buttons apply only to the track you're editing - so in fluid mode (where we have to change the range to achieve the same thing) the range should only apply to the track you're editing, otherwise there's no logic to it.
 
in real life, most DJs will be analyzing folders that are mostly in the same BPM range, so it made more sense to make the setting global, especially when it's so easy to modify
 
Stephane Clavel wrote :
in real life, most DJs will be analyzing folders that are mostly in the same BPM range, so it made more sense to make the setting global, especially when it's so easy to modify

Ok but as halving the bpm (changing the range) is an exception, why modifying the default then?
 
Stephane Clavel wrote :
it made more sense to make the setting global

For analysing multiple tracks, yes - but the BPM Editor can only edit one track at a time, and the /2 & x2 buttons apply to the single track, so (in the editor) the BPM range should too - as that's the only method available for half/double.
 
@groovindj I don't think any of the EAs had the half/double buttons for fluid - as said before I think the idea was you adjust the range to guide it to the right set of BPMs and rescan.

It might be helpful though to have it- half/double just adjust the zone for a selected anchor.

Unrelated (but related)
I just wondering thought if the engine was updated for the identied song or if devs were able to confirm the behavior I had described (Queen - Don't Stop Me Now) -
On last check it still applied the faster BPM too soon around the slow to very fast BPM swing area (start of the first verse).
I've also seen a few cases where the fluid BPM analysis was picked automatically but the regular stable grid was the better choice (BPM of tracks are stable, and the stable analysis put the downbeat more accurately on the start instrument (e.g. kick)).
 
Still digging down the Rabbit Hole...and I tried to analyze this amazing song from 1975.

https://www.dropbox.com/scl/fi/jgb70r3g6jzgddvdbrx2v/12-Major-Harris-Love-Won-t-Let-Me-Wait.mp3?rlkey=16z5znhp8shxgvr85hnf04086&st=xkphto1b&dl=0


VDJ fails to correct identify both phrases and bpm... I leave you with this in case it's needed for fine tune the new FLUID algorithm.

Its an exception and I am aware we cannot have a tool working perfectly 100% of times...this is the only one which I found until now...
 
I take it the Rane System One support is not part of this release?
 
Tried Major Harris here, and sure enough it's analysed at 115.6 which is double the tempo.

I enter a range of 55-60 and re-analyse - it still insists the BPM is 115.6

[update] a range of 50-70 worked.
 
groovindj wrote :
Tried Major Harris here, and sure enough it's analysed at 115.6 which is double the tempo.

I enter a range of 55-60 and re-analyse - it still insists the BPM is 115.6

[update] a range of 50-70 worked.


yes it's not about halving the bpm...it's about phrases and tempo changing which is not so FLUID....try to mix it...and you will see...
 
Also, was stablized BPM export added to Track Cleaner/CDJ Export? If not, that would be a nice addition too, although there may be extra input needed to select the final steady BPM to use for the stable export (within the min and max BPMs detected for the song).
 
@vinyltouch that was another advantage of the previous system! 🤬

You could click through the track and the BPM readout would show you the actual BPM at each location, enabling you to choose and lock at that BPM. Now if you click through, the BPM readout stays the same, so you can't take your pick.

Grrr LOL
 
99%