Se Connecter:     

Forum: General Discussion

Sujet: discussion about VirtualDJ 2026 Part 2
Since the [NEWS] thread is locked, feel free to post here your first impressions or comments.
 
Posté 5 hours ago
Quick questions about the Variable BPM part of the update (great work btw!!! it's worked well for all the tracks I held back on manually gridding):

  • Is there any minimum requirements to use the new analysis? Is it based on Stem 1.0 or Stem 2.0 analysis requirements?
  • I noticed that the new analysis takes quite a bit of time on my M1 MacBook (like about 30+ seconds). Given all the new analysis potentially all happening upfront on song load (Lyrics, Stems and now new Beatgrid analysis), what kind of max load/average wait times are we expecting here, especially if we are trying to do things that are intensive (e.g. play video, livestream direct, broadcast to radio)? Also, would the analysis be piecemeal like stems analysis, so the track is usable with some subportion of the grid immediately (like the stem analysis), or will it have to be completely computed before use?
  • Is reanalyze "multi" deprecated now or is it an alias to reanalyze variable?
  • Is the BPM stabilizer based on the Master Deck BPM? Or it is based on the last BPM experienced in the display?
    My take on it was it would work with the current BPM displayed for the deck but it doesn't seem to work for me (I tried it with the deck by itself, and with the deck synced to another deck, with the bpm_stabilizer verb)
  • Is there a way to export the stabilized track?
    Basically a way to create a quantized edit for others, or for CDJ Export/standalone usage, which could prove very useful
 
- it's not "based on stems", it's a new AI, but the requirement to run it on GPU are the same as stems2.0
- it has to analyze all the song before giving the grid
- "multi-zones" is only used on songs >15mn
- BPM Stabilizer is not based on the other deck. you can activate it on a track that is loaded on a single deck. It will "lock" the current BPM of the variable track, so that the BPM stops to vary.
- yes it's coming
 
Thank you for the quick responses 🙏🏾..I'll try again with the bpm_stablize verb, I must have made a mistake somewhere in using it (the BPM varied in the display regardless when I tried).

Is there also going to be a way to batch-analyze files with it as well?

I'd like to just drop a set of tracks with varying BPMs in a list folder and let it go to work.

Also, given the requirement is the same as Stems 2.0, what will happen in the case of machines that do not meet its requirements?
 
the bpm stabilizer is accessed with the small lock icon that will appear near the bpm display if a track is set to variable BPM.


and about if a computer doesnt meet the requirement, same as stems2, it will then run the AI on the CPU (so it's slower, but still useable)
 
Stephane Clavel wrote :
the bpm stabilizer is accessed with the small lock icon that will appear near the bpm display if a track is set to variable BPM.


So I think that only displays with the default skin currently, so that's why I ended up using the verb mentioned.
 
Thanks, great feature!