Sign In:     

Forum: General Discussion

Topic: discussion about VirtualDJ 2026 Part 2 - Page: 7
Thanks once again!
 
Suggestion for the BPM editor:

There doesn't seem to be a way to precisely edit the BPM for a section, it moves very fast when you drag it.

Also, it would be nice to be able to delete the first beat anchor, as I find that's the one that's most often wrong!


Another feature I'd like (which tbh I would get more use out of than variable beatgrids!) is being able to have the downbeat change on rigid tracks
 
DJ Entrada wrote :
Another feature I'd like (which tbh I would get more use out of than variable beatgrids!) is being able to have the downbeat change on rigid tracks
If anything change during the track, it's by definition a fluid grid (even if it's just the downbeat). So for the few rare cases where a track has a steady beat but the downbeat suddenly change mid-song, you need to select fluid, right-click anywhere and select "delete all anchors" (if you want the exact rigid grid), and then right-click on the beats where the downbeat changes and add an anchor and set it to "force 1/4"

EDIT: if you meant changing the downbeat for the whole song, then indeed it can stay a rigid grid, you just need to adjust the first anchor. You have a few ways of doing this: in bpm editor, you have [ < ] and [ > ] buttons in the downbeat sections, that are obviously doing exactly that. or even without opening the bpm editor, on the default skin, click on the bpm value to open the adjustment panel, and you also have [ |< ] and [ >| ] buttons there.
 
hello everybody.
i have a small problem and i don't know what to do: a friend of mine have the license for virtual dj pro till 07.03.2026, and he have a gig on 06.03.2026. Now the question is: if the gig it will be longer than 24.00h, he can still playing or have to rebuy the linces???
 
If he starts playing at March 6th and the gig doesn't take 24h to complete, but it's a regular "few hours long gig" he'll be fine.
Even if he ends the gig after midnight.
 
Multi scan for fluid beat grid yet?? Or have I missed something?
 
the SOUND INSURGENT wrote :
Multi scan for fluid beat grid yet?? Or have I missed something?


BUILD 9209 (2026-03-01)

- improved fluid algorithm with better bpm stability
- automatic use of fluid grid when needed on modern computers

it will do it on a batch scan
 
Hope a detailed walkthrough or manual will be available when Fluid Beatgrid is finally released. I believe it would be both appreciated and important for users to clearly understand how the new system works, and how to properly adjust its parameters and functionalities.
 
Any potential date for the VDJ 2026 part 2 official release?✨️❤️ can't wait!
 
Just set up a 2nd instance like Phantom told you too and try it out. Many of us are using it and it has been great for me at least.
 
the SOUND INSURGENT wrote :
Just set up a 2nd instance like Phantom told you too and try it out. Many of us are using it and it has been great for me at least.
indeed! But before using it for a gig, I prefer waiting for the official ✌🏾
 
Fluid BPM is great! The new release seems better thant the one before, solving the few issues I had.

And I am super happy with 1:16 feature to align the phrases! Thanks!

A suggestion for a potential improvement. It would be nice to have either a beat counter in the BPM editor interface (to know where we are with respect to 16) or, better in my opinion, have a visual clue on the grid itself. I would suggest a thin white or pale grey line between the 4 and the 1 at every 1:16 beat.
 
I agree, a strip above the lower waveform that has a bar count (numbers), and beat sub divisions (lines) would be useful.
 
BUILD 9229 (2026-03-16)

-autoBpmStabilizerMaxRange to set a limit to big tempo changes on multi-bpm tracks to be stabilized (default 20%)
-Sync during fluidlock relock to current average bpm
-Visuals dialog moves to drop-down for groups when window too narrow
-Fix play at time in automix not respecting Daylight savingfs time on mac
-Fix crash deleting list from folder search
-Different shading for 1 of 16 beats in bpm editor
-Fix groups not working on per-deck samplebank when triggered from sampler sideview
-Reduce cpu usage for timecode when noise present
-Improve filling in Artist for SoundCloud results
-search_playlists dialog has right-click option to remove track from playlist
-Fix karaoke history folders replacing automix on double-click when searched from folder search
-Fix dragging anchor in fluid editor
-Fix exporting lists for CDJ only exporting one track

We almost there ❤️✨️🙏🏾
 
DJ Faber Zee wrote :
BUILD 9229 (2026-03-16)

-autoBpmStabilizerMaxRange to set a limit to big tempo changes on multi-bpm tracks to be stabilized (default 20%)
-Sync during fluidlock relock to current average bpm
-Visuals dialog moves to drop-down for groups when window too narrow
-Fix play at time in automix not respecting Daylight savingfs time on mac
-Fix crash deleting list from folder search
-Different shading for 1 of 16 beats in bpm editor
-Fix groups not working on per-deck samplebank when triggered from sampler sideview
-Reduce cpu usage for timecode when noise present
-Improve filling in Artist for SoundCloud results
-search_playlists dialog has right-click option to remove track from playlist
-Fix karaoke history folders replacing automix on double-click when searched from folder search
-Fix dragging anchor in fluid editor
-Fix exporting lists for CDJ only exporting one track

We almost there ❤️✨️🙏🏾


still no fixes for the midi 2.0 with denons
 
It’s not for VDJ to fix. It’s down to InMusic to release new drivers for Windows.

There maybe work arounds that can be done in Virtual DJ, but not really a fix.
 
DJ VinylTouch wrote :
Stephane Clavel wrote :
DJ VinylTouch wrote :
It is sometimes almost impossible to drag anchors in the fluid BPM display
I experience a drastic change in the BPM instead of actually dragging the anchor itself
drag changes the BPM, shift+drag changes the phase (so the beat position).
(same as it's always been in the bpm editor for rigid grids)


So I know this. I'm saying that personally, when I tried to just do a regular drag (no shift modifier) with the trackpad on my Mac, the BPM itself was changed - it's almost like it ignored that an anchor was there and it dragged the measure beat line.

Stephane Clavel wrote :

DJ VinylTouch wrote :
has a section where the algorithm is calculating the BPM to be too fast in the zone
the best (and expected) way to fix this, is to set a bpm range that is more narrow, and then re-analayze, so the AI will know not to put a fast bpm.


I'm not sure why this is a considered a solution for the song I mentioned. Try the song and you'll see what I'm talking about.
The song goes from roughly 100 BPM at the beginning to like 145-150 BPM when it picks up. The default BPM range selection (60-180) should get that right - technically it does get it right, but it's applying the faster BPM almost 1 measure too soon (which is wrong).


I just want to point this out again, because I found a second sing where this happens.
In both cases, the sonf starts off with a slow BPM, then goes to a faster BPM almost instantly at a certain part of the song. The fluid analyzer is applying the BPM of the faster part at least 1 measure too soon (there is normally a cluster of anchors at that point with the too fast BPM).