Crackling and stuttering sound on Windows 11

  • Device model: Samsung Galaxy Book2 Pro
  • Version of operating system: Windows 11
  • Version of djay: 5.4
  • Hardware/controllers used: djcontrol inpulse t7 (asio firmware djherculesmix series2 1.87)

I am getting constant pops and crackles while playing. Task manager says I am only using about 15% of CPU so that should not be the issues.
I have updated all my drivers,
set the computer energy mode to Performance,
tried all the different latency settings for ASIO,
tried using WASAPI,
tried lowering volume on controller in case the receiver could not handle it,
tried with offline songs rather than streaming from Beatport (which I usually use)

I have used LatencyMon to test my system and it says that everything should be fine for live audio usage.

I have tried the same songs on Serato DJ Pro and I have no stuttering issues at all.

Sadly I could not try to disable any Intel CPU boost/smart step, since the Samsung BIOS does not contain the option.
Any suggestions?

Hi @Pontus_Eliason, welcome to the Community! Sorry to hear you’re experiencing this issue. This really sounds like a hardware performance issue.

  1. I recommend that you use the ASIO Audio Driver that you downloaded from Hercules DJ.
  2. Start by setting the Audio Buffer Size to the maximum available. On my setup, this is 2048 frames. This will put the minimum load on your system, but will also result in the maximum latency.
  3. If available on your setup, select the ASIO Setup… to reveal additional options and make sure Safe Mode is enabled.
  4. Retest with these settings and if the crackling is gone, then try decreasing the buffer size and retesting until the crackling returns. Once you determine the minimum buffer size your system can handle, set is 1 or 2 levels above that.
  5. If you still get the crackling sound at the maximum buffer size, then I recommend you try a high quality USB cable with dual ferrites on either end - I personally recommend the Chroma Cables by DJ Techtools.
  6. Also, avoid using any low quality USB adapters or hubs in your setup if possible as these can cause problems as well. Direct connection with a single cable between your DJ controller and Samsung device is best.
  7. Please also make sure the T7 is connected to a reliable, properly grounded, power source (don’t use cheap power bars), with the supplied Hercules DJ power supply.

Thank you for the response.

I forgot to add to my post that I have already tried all buffer sizes.
There is no “Safe mode” for the DJControl Inpulse T7 ASIO driver control panel. But I have it set to 2048 samples. Still crackles and pops.

I am using a very sturdy and good USB cable, the one supplied with the controller. I am also not using any USB hub, it’s a straight connection.
Also using the controller-supplied power supply.

And as I said, things work just fine in Serato…

1 Like

You’re welcome @Pontus_Eliason. Thanks for the additional details. In this case, please start by checking for any Windows updates and install them if available.

Then I suggest that you backup your djay Media Library database and any custom MIDI mappings, then uninstall djay, reboot your device, and reinstall the latest version of djay. You can find the files above in the following location:

  1. Windows: https://help.algoriddim.com/hc/en-us/articles/360014912131-Where-does-djay-Pro-store-cue-points-and-other-metadata
  2. Copy the files to a new location or external drive before uninstalling djay. After reinstallation, you can simply copy these files back to their original locations to maintain your Hot Cues, Saved Loops, My Collection Playlists, History and Queue.

Hi @Pontus_Eliason, we believe we may have discovered the source of the issue. As a temporary workaround, please try setting the Audio Buffer Size to 256 frames and let me know if that helps. Thanks!

This happened to me too, ive been using djay a LOT and it just happened with this update.
Also, in event log you can see a ton of warnings from the DJay app now that I never got before.

Thanks for the additional info @mvz. Our team is aware of this and is working on a fix. In the meantime, the temporary workaround as recommended above, is to set the Audio Buffer Size to 256 frames. Do not try using other buffer sizes even if they are higher. The workaround requires the 256 frames setting. I hope that helps!

Hi @Pontus_Eliason and @mvz, 5.4.2 is rolling out to the various app stores and should be available to all users over the next several hours.

• Fixed possible audio dropouts with larger buffer sizes (Windows)

For more details on the full release, please see below: