Sign In:     

Forum: VirtualDJ Technical Support

Topic: SoundSwitch unable to read Beatgrid since update to Build 9246
When I updated to Build 9246 on April 1st 2026, I added new tracks that day with BPM & everything analyzed but when it came to auto-scripting in SoundSwitch, it suddenly skipped them all since it doesn't have a beatgrid (or so it thinks there is no beatgrid). Tried multiple solutions like re-analysing the tracks & other solutions to no avail.

So I reverted back to Build 9005 & re-analysed with the old BPM detection, this time, SoundSwitch did detect the beatgrid.

So, I assume that the new Fluid Beatgrid & such changed the way it is written in the database which SoundSwitch can't read.

As a result, I have to stay at the version I'm currently at (Build 9005) for the time being unless VirtualDJ adds an option that allows users to switch between the new or old BPM detection thing or that SoundSwitch works into releasing an update that fixes this issue.
 
Posted Wed 01 Apr 26 @ 11:26 pm
This was stated on the SoundSwitch FaceBook a few weeks ago (they recommended staying in b9005 until further notice).

The ball is kinda now in SoundSwitch's court (they knew about the engine
update since first EA that announced it and it's been pretty much a month already).

There is a switch to use stable beatgrids (verb and BPM editor), but I'm not sure if that translates to what SoundSwitch understands.
 
DJ VinylTouch wrote :
There is a switch to use stable beatgrids (verb and BPM editor), but I'm not sure if that translates to what SoundSwitch understands.

Yes, someone shoud probably test that...
 
I will probably check that later (after work).

I suspect that:

  • autoloops are probably unaffected
    Those are loops over a set of bar that conforms to no specific track grid - it most likely gets all the timing event info from the OS2L communication.
  • Existing tracks that have already been gridded by earlier versions and pocessed and autoscripted by SoundSwitch are unaffected
  • New tracks that are gridded, switched to a stable BPM and then autoscripted in SoundSwitch might still work
  • New tracks with a fluid grid just don't work at all with autoscripting
    I can't remember if the original multibpm grid worked and had a different format or not - I I'll run through my collection to see if I did analyze such songd for Soundswitch autoscripting/manual scripting use.
 
Any update on your tests? I‘m still in waiting with the upgrade mode, because I work with soundswitch loops. Thank you
 
Sorry I got busy and I forgot to do this.
Here is something you can try if you have time:


  • Add a new song, scan it and set its grid to stable (BPM editor or verb).
  • Import that song into SoundSwitch and see if it gets the proper grid


Also, check that any existing song you imported into SoundSwitch should still have a grid/work correctly (this should be the case).

The theory is that SoundSwitch probably doesn't read/understand the new Fluid Grid format yet, but it shluld still understand the old formats (multi BPM and stable), and stable should still be written in the old format.