@vinyl ok thanks! Hopefully One Library will be adopted by VDJ too...
Inviato Thu 19 Feb 26 @ 1:18 pm
@DJ Faber Zee, does One Library work for you?
Or rather, what do you mean by "One Library"? Do you mean "Music Library Doctor"?
Or rather, what do you mean by "One Library"? Do you mean "Music Library Doctor"?
Inviato Thu 19 Feb 26 @ 1:26 pm
DJ Faber Zee wrote :
@vinyl ok thanks! Hopefully One Library will be adopted by VDJ too...
There is nothing to "adopt" other than AlphaTheta's blessing (which prob has licencing involved) - OneLibrary, as it exists currently, is CDJ export/import. That does not solve the alignment issue as it's a different problem (DJay has alignment issues too - go to the forums and see).
Btw, this forum thread is about the VDJ 2026 Part 2 features (Variable Beatgrid Update, AI Visuals and AI Lyrics improvments, so this particular topic is off topic with respect to that - maybe create a new topic for that?
Inviato Thu 19 Feb 26 @ 1:30 pm
Of course...lets focus on the topic!
Inviato Thu 19 Feb 26 @ 1:47 pm
@DJ Farber Zee yep not trying to be mean/downplay your issue - it is a real issue that I hope they take time to look at too, but let's not hijack this thread for it.
@devs/others...Some more questions on the Variable Beatgrid update topic:
I notice a few settings have been added to adjust its behaviour for stabilization, etc, and they are mostly self explanatory from description.
There is one option however that would be helpful to have a bit of clarification on - variableBPMSensitivity
I also noticed that in some cases the variable analysis seems to be done once tracks are loaded into the deck, seemingly after stems analysis is completed (the green bar for the variable analysis is seen on the track in the browser). Is that being done for variable BPM songs automatically when fluctuations are detected?
I also randomly got a "Your computer isn't powerful enough to run real-time Stems separation" on the M1 MacBook while playing a recently variable BPM analyzed track in the BPM editor.
@devs/others...Some more questions on the Variable Beatgrid update topic:
I notice a few settings have been added to adjust its behaviour for stabilization, etc, and they are mostly self explanatory from description.
There is one option however that would be helpful to have a bit of clarification on - variableBPMSensitivity
- Is this just controlling BPM window/zone sizes for calculation or is it doing more?
- I see on my M1 machine, it defaults to 30 (I didn't try other machines yet). Is this the default chosen overall or is this calculated? Would there ever be a reason to want to change this value or should we just leave it alone (e.g. performance on lower spec machines, or just seeing if it would place less markers because the beat is mostly stable)?
I also noticed that in some cases the variable analysis seems to be done once tracks are loaded into the deck, seemingly after stems analysis is completed (the green bar for the variable analysis is seen on the track in the browser). Is that being done for variable BPM songs automatically when fluctuations are detected?
I also randomly got a "Your computer isn't powerful enough to run real-time Stems separation" on the M1 MacBook while playing a recently variable BPM analyzed track in the BPM editor.
Inviato Thu 19 Feb 26 @ 2:04 pm
@vinyl no worries I got it! thanks for your help and support every time!
Inviato Thu 19 Feb 26 @ 2:06 pm
DJ VinylTouch wrote :
Like the help text says, it sets the balance between getting very precise position for each beats, but then adding a lot of anchors and having the bpm potentially fluctuating on each beats, vs getting a more smoothed-out bpm with less fluctuations, but the anchors getting further away from the actual beats to respect the bpm.There is one option however that would be helpful to have a bit of clarification on - variableBPMSensitivity
The default is 30ms (maximum distance between anchor and actual beat).
It's really a matter of personal taste.
Some people don't like to see the bpm reading fluctuating a lot.
But some people want their anchor to be dead-on on each beat.
So adjust the setting according to your perference.
Inviato Thu 19 Feb 26 @ 8:37 pm
DJ Faber Zee wrote :
One Library was implemented in VDJ many years ago. Long before Pioneer ;)@vinyl ok thanks! Hopefully One Library will be adopted by VDJ too...
(except we named it "CDJ Export", but that's really exactly the same thing as One Library).
Inviato Thu 19 Feb 26 @ 8:41 pm
Stephane Clavel wrote :
The default is 30ms (maximum distance between anchor and actual beat).
The default is 30ms (maximum distance between anchor and actual beat).
Thank you for explaining this - this was the key piece of info I didn't gain from the description...now I understand what it is and how to use it.
I'm also guessing that you guys are preparing updates to the manual/tip of the day videos for all of these features - this "Part 2" release, with all the new offerings, is just as big as the initial release imo...really big thanks and good job done to you and the team 🍺.
Inviato Thu 19 Feb 26 @ 8:54 pm
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).
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).
Inviato Fri 20 Feb 26 @ 12:31 am
I just want to take the time to say something simple.
Thank you (VDJ Team). Awesome 2026. Not as impactful to as many people as Stems, but certainly as useful to me personally (and I use Stems all the time, rarely EQ much in tracks anymore).
I've deliberately purchased 10 credits for AI vids as a tip of sorts.
Thank you (VDJ Team). Awesome 2026. Not as impactful to as many people as Stems, but certainly as useful to me personally (and I use Stems all the time, rarely EQ much in tracks anymore).
I've deliberately purchased 10 credits for AI vids as a tip of sorts.
Inviato Fri 20 Feb 26 @ 12:39 am
DJ A Sharp - The One Man Band wrote :
Yes it's a bug. fixed for next build.
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).
Inviato Fri 20 Feb 26 @ 2:20 am
Stephane Clavel wrote :
DJ A Sharp - The One Man Band wrote :
Yes it's a bug. fixed for next build.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).
Cool...Now I can stop beating my head against the wall thinking I was doing something wrong...lol...THANKS!
Inviato Fri 20 Feb 26 @ 2:59 am
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.
Unfortunately I haven't installed yet as I am waiting for the official build.
Any help is truly appreciated.
Inviato Fri 20 Feb 26 @ 5:05 pm
First of all, I am thrilled that the new variable beatgridding is finally available! But I am missing a couple of fix-up features for difficult tracks.
I am playing around with Diana Ross Upside Down, and it gets the first downbeat wrong. This is perhaps to be expected, but I can’t figure out how to override it and set 1.1 explicitly.
The track starts with 2 beats of percussive guitar strumming before the band falls in at what should be 1.1.
But the first 2 beats become 1.1 and 1.2, and what should really be 1.1 becomes 1.3. I can use the “downbeat” arrow buttons in the BPM Editor to make the third beat become 2.1, but then the phrasing is off by one bar for the rest of the track. How can I force the third beat to be 1.1? The first 2 strumming beats would then be -1.3 and -1.4.
Another (related) issue is that several places in Upside Down there are 2–beat bars. It seems that it is not possible to mark a beat as “1st beat of bar” and continue with that phrasing until next override.
I am playing around with Diana Ross Upside Down, and it gets the first downbeat wrong. This is perhaps to be expected, but I can’t figure out how to override it and set 1.1 explicitly.
The track starts with 2 beats of percussive guitar strumming before the band falls in at what should be 1.1.
But the first 2 beats become 1.1 and 1.2, and what should really be 1.1 becomes 1.3. I can use the “downbeat” arrow buttons in the BPM Editor to make the third beat become 2.1, but then the phrasing is off by one bar for the rest of the track. How can I force the third beat to be 1.1? The first 2 strumming beats would then be -1.3 and -1.4.
Another (related) issue is that several places in Upside Down there are 2–beat bars. It seems that it is not possible to mark a beat as “1st beat of bar” and continue with that phrasing until next override.
Inviato Sun 22 Feb 26 @ 10:29 am
Niels a question... are beat grid lines properly put where the beats occur?
Very curious as I haven't installed it yet.
Very curious as I haven't installed it yet.
Inviato Sun 22 Feb 26 @ 10:34 am
Yes, judging from the few tracks I have inspected, the anchors are spot on.
It works by putting anchors in like we are used to, but the algorithm does the boring work for us! There’s a setting ‘variableBpmSensitivity’ that you can tweak. It governs how often it wants to set anchors. The default is 30, but I tried it at 0, which is most sensitive, and then it puts anchors on most beats. It means that the BPM display will change all the time, but that doesn’t bother me.
From what I have seen so far I am impressed, and I look forward to never having to manually grid a track again 😅 Only thing we need additionally is the ability to override the phrasing.
It works by putting anchors in like we are used to, but the algorithm does the boring work for us! There’s a setting ‘variableBpmSensitivity’ that you can tweak. It governs how often it wants to set anchors. The default is 30, but I tried it at 0, which is most sensitive, and then it puts anchors on most beats. It means that the BPM display will change all the time, but that doesn’t bother me.
From what I have seen so far I am impressed, and I look forward to never having to manually grid a track again 😅 Only thing we need additionally is the ability to override the phrasing.
Inviato Sun 22 Feb 26 @ 11:05 am
Thanks! All feedbacks seems very positive!
Looking forward to the official release 🔥
Looking forward to the official release 🔥
Inviato Sun 22 Feb 26 @ 11:08 am
Niels (cph) wrote :
Only thing we need additionally is the ability to override the phrasing.
To correct this, in the BPM editor you could select anchors that give the wrong beat count, right click and shift the downbeat left or right for the local area until it is correct.
However this is even more tedious than before (we were able to select an anchor and immediately make it the 1 beat with a checkbox, but you had to set the anchor correctly for the one count), because now you have to know what the shades of coloring of beats are or you have to load the song in an inaudible deck, make a downbeat change and then move the playhead position in the BPM editor...you will see the movement in the deck and where the nearest downbeat is in the deck's waveform display.
I suspect getting the downbeat right is a much harder problem to solve (even DJay gets that wrong with the rock track I mentioned earlier), but manual correction of it is much faster than having to set anchors.
It would be helpful to see where the nearest downbeat is and be able to select a beat for a select anchor (1 to 4) directly in the BPM editor itself.
Inviato Sun 22 Feb 26 @ 12:55 pm
Is anyone else noticing randomly placed markers that have a much different BPM to the track, or surrounding markers?
I see it most often for just one beat. If the track is c125 for example, there'll be the occasional beat marked as 104 or 149 or something completely off kilter.
Even when restricting the range, putting in e.g 124-126, it'll still place markers outside the range.
I've been having to check through tracks and remove them manually.
I see it most often for just one beat. If the track is c125 for example, there'll be the occasional beat marked as 104 or 149 or something completely off kilter.
Even when restricting the range, putting in e.g 124-126, it'll still place markers outside the range.
I've been having to check through tracks and remove them manually.
Inviato Sun 22 Feb 26 @ 2:21 pm





