VirtualDJ wordmarkVirtualDJrekordbox.dev

Before the gig

When stems, sound, or a controller misbehave.

When VirtualDJ is not working, the usual causes are live stems on a weak GPU, a buffer that is too small, a sleeping drive, or a controller the license does not include. The steps below are the ones support threads and the publisher wiki actually point to.

Page updated 26 October 2026. Software build dated 22 October 2026.

01

The stems message: this computer might not be able to handle real-time stems

Live stem separation is the feature people keep, and the one that overruns a laptop. The warning means the split is falling behind the playhead.

  1. Read the message on the deck. If it says the computer might not be able to handle real-time stems, stop treating that track as a live mashup.
  2. On Windows, open Settings, then Options, then Performances. If a GTX, RTX, or Radeon card is installed, clear Don't use GPU on the stemsFix setting and install that card's current driver.
  3. Before a gig, drag the tracks you will play into the Stems folder and let preparation finish. The publisher describes leaving that job overnight.
  4. If the laptop is hot after two or three hours, turn stems analysis off and test the same song. A February 2023 forum report on a Nitro 5 with an i7-11800H and Intel UHD graphics cleared the heat, the latency, and the slow browser that way.
  5. An unprepared track can still fall back to the lighter stems 1.0 split. Use that only if you have heard it on that song.
Stem pads labeled vocal, instrumental, bass, kick, and hi-hat

02

Stems stay on the CPU even with a graphics card

Stems 2.0 can ignore a GPU when the option or the driver blocks it. Intel graphics on a laptop are a common case.

  1. Confirm the card is an NVIDIA GTX 1050 or better with 4 GB of VRAM, an RTX with 6 GB, or a Radeon RX 5600 XT or better. UHD graphics are below that line.
  2. Open Settings, Options, Performances, and remove Don't use GPU from stemsFix.
  3. Install the latest driver from the card vendor, then restart VirtualDJ and load one local track.
  4. On a Mac, live GPU stems are for Apple Silicon on macOS 13 or newer, and the publisher asks for macOS 14.4 and 16 GB for stems 2.0 and fluid beatgrids. A discrete AMD or NVIDIA card in an Intel Mac is not used the same way.

03

Sound skips, stutters, or pops

The wiki lists skipping, stutter, and pops as a sound-setup problem, and distorted sound when two sound cards are in use.

  1. Quit other heavy apps and try the song from an internal drive, not a sleeping external disk.
  2. In the audio setup, select the interface driver. If the interface has an ASIO driver, use that one device for the master output.
  3. If two sound cards are assigned, move the master and the headphones onto one interface. The wiki calls out distortion in the two-card case.
  4. Raise the audio buffer until the pops stop. Do not copy a buffer size from another DJ. The right size is the smallest one that stays quiet on your interface.
  5. Turn stems analysis off and play the same track again. If the pops leave with the stems, the CPU or GPU path is the cause, not the song file.

04

A deck shows Error when a track loads

Error on the deck means that file did not open. It is a load failure, not a license screen.

  1. Load a different track from the internal drive. If that one plays, the first file is missing, moved, or unreadable.
  2. If the track sits on an external disk, wake the disk and load it again. The wiki lists a delay or freeze on external drives.
  3. For a streamed track, open that catalog and confirm the account is signed in. Deezer playlists over 1,000 songs had a loader fix in build 9482. Update if you are behind 9729.
  4. If every track fails, restart VirtualDJ after the audio device is connected, then load one local WAV or MP3.

05

A controller is not detected or a knob does nothing

Plug and play covers the supported list. A silent knob is often a mapping or a license limit, not a dead USB port.

  1. Connect the controller to a USB port on the computer for the first test, then restart VirtualDJ.
  2. Wait for detection. Supported gear from Pioneer DJ, Numark, Reloop, Denon DJ, Hercules, and Rane is meant to map on connection.
  3. If faders move and one knob does not, open the mapper and reset that device to the factory mapping. The wiki lists a reset for mappings that do not stick.
  4. Check the license. Home only enables entry-level controllers. A club mixer on Home will not behave as it does on Pro.
  5. MIDI learn can map an unsupported control. Softonic's review notes call that mapping hard the first time. Map one control, store it, and test before a gig.

06

The BPM is wrong, or the grid drifts

A steady club track and a live disco record do not want the same grid. Build 9246 added fluid beatgrids for the second kind.

  1. Re-analyze the track from the browser. A wrong first pass is common on short edits and on tracks with a long intro.
  2. If the tempo wanders, as with old rock, disco, a warped record, or a megamix, use the fluid beatgrid instead of forcing a single BPM.
  3. Turn on BPM Stabilizer when you want to mix that fluid track by ear without Sync. It steadies the tempo for the transition.
  4. Open the BPM editor if the grid is half or double the real tempo. On a fairly stable fluid track the editor offers /2 and x2.

07

VDJ Remote will not connect

The remote is a second screen for pads and requests. It needs a path to the computer, not a second copy of the mixer.

  1. Put the phone and the computer on the same local network.
  2. Open VirtualDJ Remote on iOS or Android. The publisher also allows USB or Bluetooth tethering, with or without internet.
  3. Restart the remote and VirtualDJ. Confirm the computer firewall allows the local session.
  4. If the phone can see the computer and then drops, move off a guest Wi-Fi that blocks device-to-device traffic.

08

Antivirus warns about an add-on or the installer

A warning is a reason to check the file, not an automatic click of Allow.

  1. Install skins, effects, and pad pages from the Extensions list inside VirtualDJ. The publisher says those add-ons are checked, and that a warning can be a false positive.
  2. Do not run a setup that arrived by email, a forum attachment, or a repack with a serial in the same zip.
  3. For the Windows program, confirm you are on build 9729 and that the MSI is 563.18 MB.
  4. Hash the MSI and compare it with SHA256 4d4941b7ee70e33db741e82d5a9ba4864b0f90281bfed4e21d8a0ea19c226db4, printed on the download page. The publisher site itself does not show that hash.

09

A second-hand serial will not register

This is not a glitch in the installer. The license was never yours to move.

  1. Stop entering the code. Auction and classifieds serials are rejected because licenses cannot be transferred.
  2. Use the email that paid Atomix Productions, or buy a new license. This site does not sell licenses.
  3. Do not send a serial, a password, or a card number to anyone who claims they can move the license.

10

Before the next gig

  • Prepare stems overnight for the list you will actually play. Do not pre-separate the whole hard drive the afternoon of the wedding.
  • Match the operating system to the build. macOS 10.15 and 11 stop at 9644. 32-bit Windows stops at 2020 build 8336.
  • Use one audio interface for the master output. Two sound cards are a known cause of distorted sound.
  • Buy the license from the publisher. A serial from a person will not register, and this site does not sell one.
  • Install add-ons from Extensions inside the program, then read the no-malware note if a scanner complains.

Related questions in the FAQ

Take VirtualDJ with you

Download Buy
Download
AboutPrivacy PolicyTerms & Conditions