I am a professional DJ and I am using my Prime 4+ (which I am still currently paying for) for daily live broadcasting, multi-streaming on Twitch, official web radios, and professional 3D virtual environments and metaverse platforms.
For my workflow, using the console in PC Mode with Virtual DJ is absolutely mandatory because I need the native Broadcast/Icecast features to stream high-quality audio feeds to multiple platforms and online servers simultaneously.
Ever since the latest Windows 11 security and MIDI 2.0 architecture updates, the official Denon DJ ASIO driver has become completely unstable. After 5 to 10 minutes of usage in PC Mode, the audio starts heavily crackling, distorting, and degrading.
Please note: We have already tried every single workaround. Disabling “Core Isolation / Memory Integrity” in Windows 11 DOES NOT FIX THE ISSUE. Completely wiping and reinstalling the ASIO drivers or changing USB sample rates does not fix it either.
As a customer, I choose the product that best fits my professional needs, and I chose the Prime 4+ because it advertises both Stand-alone and PC Mode capabilities. I must be free to choose the mode that works best for my specific workflow. You are strictly required and obligated to fix these critical software/driver issues after I paid a premium price for this hardware.
I know for a fact that InMusic has already solved this specific Windows 11 driver conflict for other brands under its umbrella (like the RANE Performer drivers, which run flawlessly). Why is the Prime 4+ being completely ignored?
Forcing users onto Stand-alone Engine OS by neglecting basic Windows ASIO drivers is unacceptable for working professionals. We need an official, updated ASIO driver for Windows 11 immediately. Please forward this directly to the development team.
Thanks Reese, I will definitely open a ticket as suggested. However, I posted this here because the ASIO driver conflict on Windows 11 is a known and shared issue among Prime 4+ users. Since InMusic has already successfully deployed a driver fix for other hardware in the group (like the RANE Performer), we are simply looking forward to seeing the same development and support dedicated to Denon DJ’s flagship standalone. I hope the team logs this feedback internally. Best Regards
Please do not tell me to open a support ticket, because I have already done so and I am posting here precisely because the ticketing system failed.
For the past 3 days, I have provided the support team with precise technical data, hardware logs, and a detailed description of my setup regarding severe issues in PC/Controller Mode on my PRIME 4+.
Today, a Level 2 agent completely dismissed my case by copy-pasting a generic, automated template about the Windows 11 MIDI Services bug. This feels extremely disrespectful and unprofessional after all the hours I spent compiling accurate data for your team.
My case is different: I am already strictly following every single best practice and power-on sequence recommended for Windows 11, yet the hardware freezes and lag persist. The support team treated my ticket with absolute superficiality instead of reading the actual logs I attached.
Since the private support channel is just dodging the issue with pre-written templates, I am bringing this to the public forum. Can a product manager or developer actually look into my case logs?
Has anyone suggested this? In Windows (doesn’t matter what version), go into Settings>Device Manager>expand Universal Serial Bus controllers, right-click USB Root Hub, and then select Properties. In the USB Root Hub Properties (check other USB devices as well) dialog box, select the Power Management tab. And make sure the “Allow the computer to turn off this device to save power” check box is UNCHECKED. Common issue for USB audio devices on Windows (like since the 90’s), this causes so many problems.
You say you need to use the Prime 4+ with VDJ because you’re broadcasting…
As the unit is designed to be used standalone, why not run with EngineOS and feed the output into OBS for example? Even if temporarily until the MIDI 2.0 issues are resolved.
Thank you @Reese for taking a closer look at my case and for tagging the staff members. I really appreciate your help with this, and I completely understand it will be reviewed after the weekend.
To the others, thank you guys for the suggestions, but as I stated in my initial post, I have already tried everything.
@djdragon - Yes, changing the USB Root Hub power management settings is a classic Windows tweak, but I already did that a long time ago when I first started troubleshooting. Unfortunately, it doesn’t change the behavior with this current driver conflict.
@PKtheDJ - I am actually already using EngineOS standalone and routing the audio into OBS as a temporary workaround to save my live broadcasts. I know how to bypass it for now, but that’s exactly why I am pushing for a real solution.
This unit was not designed to be used only as a standalone hardware. It is marketed and sold as a hybrid unit, and I specifically chose and paid top dollar for the PRIME 4+ because of this dual capability. If I didn’t care about PC Mode, I would have bought a strictly standalone-only device and saved my money. I expect every advertised feature of a flagship product to work reliably.
Looking forward to hearing from the staff next week since all basic and advanced user-side troubleshooting has already been exhausted.
That part alone makes it sound like latency issues. As a test, try setting the laptop / virtual dj latency up to something crazy like 512ms and see if, after a reboot, whether the audio crackles disappear.
First , try turning off the laptop for 2 hours to let it cool totally back to fresh “first use of the day” temperatures and see if the crackles start immediately, or whether the crackles only appear after 10-15 mins , or after an hour or so etc.
Once the crackles start, try turning the laptop off for just a minute or two , then try it again and see if the crackles start more quickly now that the laptop is toasty
Yes I know - and I never used the word “only”. Maybe the word “primarily” would be more suitable. The controller functionality is an added bonus rather than the main purpose.
If you’re already using it as I proposed, then the issue is not as urgent as the tone of your posts implies…
Have you tried checking to see if the crackles occur when you’re NOT broadcasting? i.e. is it really the Prime driver causing the issue?