Anmelden:     

Forum: General Discussion

Topic: discussion about VirtualDJ 2026 Part 2 - Page: 6
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).
 
apopsisdj wrote :

Plus you have multi-level undo now for grid edits, so you can try things without re-analyzing each time (Early access b9209 or later).


This I wasn't aware of. I'll try that out (thanks for mentioning that).
 
DJ VinylTouch wrote :
when I tried to just do a regular drag (no shift modifier), the BPM itself was changed
yes that's what I said. drag in fluid changes the bpm (on any beat).
shift+drag moves the beat (also on any beat).
"anchors" are visual indications of where the bpm changes, they're not more or less dragable than a regular beat. (though "anchors" have more options on their context-menu when right-clicking)

DJ VinylTouch wrote :
I'm not sure why this is a considered a solution for the song I mentioned.
What I meant is that instead of giving the option to double or half bpms like in rigid, in fluid it's better to adjust the range to what you know the song is, and run the AI again, because the AI not only find the bpm, but also adjust all the phases of each beats to compensate for small drifts, and this is lost when you manually adjust the bpm of one part.
 
Stephane Clavel wrote :
DJ A Sharp - The One Man Band wrote :
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).
Yes it's a bug. fixed for next build.


Circling back to this...The grids themselves have been IMMACULATE. But for my workflow's muscle memory, this is triggering my frustration (LOL), and the newest EA doesn't seem to fix it...Is it still a work in progress?
 
BUILD 9209 (2026-03-01)

- improved fluid algorithm with better bpm stability
- automatic use of fluid grid when needed on modern computers
- bpm editor: drag changes bpm, shift+drag changes phase
- "heatmap" on fluid editor to show zones with phase drifts
- fix midi2 on latest windows update
- fix loop out behavior to use stutter point as loop in
- fix history export play time not showing time if playlist older than 6 months
- new actions "get_time to_lyrics", "has_lyrics", "get_lyrics_language"
- new option variableBpmDownbeatSensitivity

Wow dev team is working around the clock...cant wait for the official release to be live!!!

A quick one... "automatic use of fluid grid when needed on modern computers"
What is this?

GO VDJ FAM!
 
DJ Faber Zee wrote :
A quick one... "automatic use of fluid grid when needed on modern computers"
What is this?


Essentially it means it will automatically analyse the track using fluid bpm, if your PC is capable of doing it on the fly.

Generally if you computer can handle Stems 2.0 on the fly, it should be ok with Fluid BPM too.
 
Dan (djtouchdan) wrote :
DJ Faber Zee wrote :
A quick one... "automatic use of fluid grid when needed on modern computers"
What is this?


Essentially it means it will automatically analyse the track using fluid bpm, if your PC is capable of doing it on the fly.

Generally if you computer can handle Stems 2.0 on the fly, it should be ok with Fluid BPM too.


ahhhh ok! thanks!
 
apopsisdj wrote:
Plus you have multi-level undo now for grid edits, so you can try things without re-analyzing each time (Early access b9209 or later).

How does it work ? (multi-level undo)
 
Benz Werner wrote :
apopsisdj wrote:
Plus you have multi-level undo now for grid edits, so you can try things without re-analyzing each time (Early access b9209 or later).

How does it work ? (multi-level undo)



If you drag the grid with the mouse to change phase, bpm etc you should see an undo button (Next to Tap button when in rigid mode). Currently includes grid changes only.
 
@apopsisdj thanks
 
Stephane Clavel wrote :
yes that's what I said. drag in fluid changes the bpm (on any beat).
shift+drag moves the beat (also on any beat).
"anchors" are visual indications of where the bpm changes, they're not more or less dragable than a regular beat. (though "anchors" have more options on their context-menu when right-clicking)


So I'm dragging an anchor (which used to just adjust where the BPM change for the region introduced it started, not a beat line (which should change the BPM, as it did before). Now, dragging an anchor itself changes the BPM instead of moving the region (and keeping the BPM, as it did before).

Previously, a person would drag an anchor because it was known that the BPM it introduced was correct...but was just at the wrong time (which would be one way to solve the manual BPM error problem with the song I mentioned (BPM introduced too soon)...now an anchor has to be explicitly placed where it should start and the old anchor deleted).
If this change was purposefully done, what was the reason for this change (as now an entire use case of dragging the anchor is now gone)?

Stephane Clavel wrote :

What I meant is that instead of giving the option to double or half bpms like in rigid, in fluid it's better to adjust the range to what you know the song is, and run the AI again, because the AI not only find the bpm, but also adjust all the phases of each beats to compensate for small drifts, and this is lost when you manually adjust the bpm of one part.


I understand that smartly using the BPM range would yield better results. That would not work here. It's not that the BPM introduced is too fast/incorrect for the song, it's that it is introduced too soon (2 measures too soon instead of 1 as I said earlier).
 
Just following up on above - I just wanted to know if I'm thinking about this incorrectly (the BPM Editor issue), because I was asked about it by another VDJ user.

I can provide a video for the latter problem if it helps.
 
yes, on a fluid grid, you cannot "drag anchors across beats" like you could with rigid grids, because the position of each beat is not fixed so it cannot be "reconstructed" while dragging. so anchors are not draggable.
so the solution is as you said, add an anchor on the beat where you want the bpm to change, and delete the anchor where you don't need it.
 
I understand. Thanks for the clarification.
 
Quote :

Deletion of anchors sometimes still leaves the BPM zone/section it introduced


Just wanted to re-highlight this (Fluid BPM Editor), it's not sometimes, it's all the time - the BPM of the previous anchor doesn't seem to take over the region until a drag is done.
 
DJ Faber Zee wrote :
Does anyone tried fluid Beatgrid with OldSchool Reggae songs (70s especially)?

Unfortunately I haven't installed yet as I am waiting for the official build.

Any help is truly appreciated.


Works fine!
Isolated a drum & hihats stems loop from this track in left deck, left it on 'static BPM':
https://www.youtube.com/watch?v=7lEB7V-KIb0&list=RD7lEB7V-KIb0&start_radio=1
Mixed it with this track, disabled it drum & hihat stems, activated 'variable BPM', pressed Synq :
https://www.youtube.com/watch?v=f6Q3FeAdrIQ&list=RDf6Q3FeAdrIQ&start_radio=1
Result:
https://drive.google.com/file/d/1VNKEoDoy6S3AGmbdTyEgkR7TO1UVXrDb/view?usp=sharing

Same again...
Drum loop from:
https://www.youtube.com/watch?v=SpjnzxtZ6Qg&list=RDSpjnzxtZ6Qg&start_radio=1
Reggaetrack from:
https://www.youtube.com/watch?v=V2CgAfoQ-50&list=RDV2CgAfoQ-50&start_radio=1
Result:
https://drive.google.com/file/d/1qJl2Mhi5KaiZiGpjcC2ZylgbZnvp1mNU/view?usp=sharing
 
@ANOK4U2 thank you!

@ALL sorry for the dumb question, but if I download and install the beta version on the same laptop where I currently have VDJ installed, will it replace my existing installation or will it run as a separate instance?
I’d be happy to contribute to the beta testing, but I’m concerned about affecting the latest official VDJ release currently installed on my system.
 
DJ Faber Zee wrote :
@ANOK4U2 thank you!

@ALL sorry for the dumb question, but if I download and install the beta version on the same laptop where I currently have VDJ installed, will it replace my existing installation or will it run as a separate instance?
I’d be happy to contribute to the beta testing, but I’m concerned about affecting the latest official VDJ release currently installed on my system.


Do this:
Copy your current VirtualDJ.exe file as VirtualDJ-PR.exe
Then start VirtualDJ normally and enable Early Access updates on settings.
Once VirtualDJ updates, turn the Early Access update setting off
Now you have two versions:
VirtualDJ.exe -> Latest EA
VirtualDJ-PR.exe -> Latest PR version


* EA = Early Access, PR= Public Release
 
PhantomDeejay wrote :
DJ Faber Zee wrote :
@ANOK4U2 thank you!

@ALL sorry for the dumb question, but if I download and install the beta version on the same laptop where I currently have VDJ installed, will it replace my existing installation or will it run as a separate instance?
I’d be happy to contribute to the beta testing, but I’m concerned about affecting the latest official VDJ release currently installed on my system.


Do this:
Copy your current VirtualDJ.exe file as VirtualDJ-PR.exe
Then start VirtualDJ normally and enable Early Access updates on settings.
Once VirtualDJ updates, turn the Early Access update setting off
Now you have two versions:
VirtualDJ.exe -> Latest EA
VirtualDJ-PR.exe -> Latest PR version


* EA = Early Access, PR= Public Release



Thanks but it's too tricky for me...I thought VDJ allowed me to have two instances (ie I have both Rekordbox 6 and 7 on the same laptop).

I will patiently waiting for the official release...
 
VirtualDJ allows you to have multiple instances with a simple copy/paste

Now if you prefer to instal multiple versions over and over again, that's the least efficient method, and no, we don't exactly do that.

If you take 3 minutes to "study" what I told you above, you'll see that it's literally a 2 minutes job and a simple copy/paste to get the two different versions running side by side.

It's not THAT complicated!

1. Copy/paste the original exe file
2. Start the program
3. Change a setting
4. Let the program update
5. Change the setting back

TADA!
 
92%