I could try that. Is there any tutorial how to do it?
Just remove your ssd, add some tracks to a usb via engine dj on the computer and then attach the usb to your device and test.
Just to get one possibility out of the way - do you by any chance use SoundSwitch? Or is that option even enabled in settings on the controller? It should be in the Services tab
Just an early comment - it would seem, for those who have given some detail - that a common denominator seems to be the lazy/eazy link, using the wifi to connect engine on a laptop to the decks - that needs the prime and the laptop to be on the same wifi as each other.
Some users mentioned being on streaming services at the same time. I could see how the wifi signal throughout could get overly busy with both the streaming services and the laptop link - perhaps someone could try running engine link for hours without streaming services, and separately (a different day) run streaming services for hours without engine wifi link
1 Like
I was connected to WiFi with a Phone but not with Laptop Link and I didn’t use soundswitch.
Just to clarify: I’m sure I could eventually reproduce the issue, but it would probably require running the system in continuous use for 6–7 hours, which is quite hard to do on the side outside of actual gigs.
It only happened once over a long period, so I suspect it’s tied to very specific gig conditions. That’s why I believe there may be a bug somewhere in the software, and ideally Denon would run long-term stability tests to catch these kinds of edge cases.
I totally see the value in testing, and I’m sharing all the info I can to support the dev team.
Maybe it can have also something to do with the power on that location? High amplitude voltage drops on the power line?
Amps can handle that (have big caps to compensate), but more delicate computer based systems can run in to some issues.
6 hours test is very extensive, but it is not a bad idea to have once in a while a fresh export of new data base to keep things clean and running smoothly. Just a recommendation, not a must 
1 Like
Or a particular track either loaded or in search results.
There was an incorrectly tagged track on beatport or soundcloud a couple of years back , which had an erroneous duration tag, claiming the track was 180 minutes long and all sorts of systems, from hifi units to laptops and media players fell over even if the track was only within search results , not sctualled loaded/cued ready to play
Hi There , I had a similar issue last weekend with my Prime 4+. What is striking, is that it also happened after multiple hours of power-ON time, with a playlist in ‘continous’ mode for background music. Then when starten DJ’ing: 2 hours or so in the set, unit crashes and reboots from itself.
One novelty is that i used a new USB drive (not for the first time) and it was formatted as ExFAT. Before i alsways used SD cards or another stick in FAT32 format mode.
The new usb is larger, so jitter due to vibration is possible as opposed to the SD cards i used to use.
I don’t remember if the unit is updated to 4.3.1 as it is in a flightcase elsewhere. but it does have STEMs for sure.
Never had the issue before. For next weekend i will be using the former USB stick (FAT32) and reboot before i start my set.
1 Like
Do you have FAT32 formatted on your memory devices?
I just got an idea of what can possibly be causing it, but I need confirmation from everyone with this issue if they’ve been using Apple Music / have it enabled in services - this might have something to do with Apple Music DRM requirement in update 4.3.1, so the issues causing it might be as follows:
- DRM feature puts a lot of pressure on CPU after some time
- DRM feature causes crashing after using computer mode I guess this might happen even with Apple Music being turned off
just as a side note, i forwarded this thread via mail to the developers/support team as this needs attention instantly. I’m nervous for my 2 DJ sets this weekend - having to set up backup plans (ie. 2nd unit hotswap)
Beautifully built into the white console. A super elegant setup.
Meanwhile, since you’re on 4.2.1 these crashes are likely to have a variety of causes. Or, maybe 4.3 has inherited the bug. Let’s hope the developers will take a deep dive. It’s not easy when layers and layers of changes have been added onto software that supports the newest units and tries to be backwards compatible.
Moin @OliverAlex,
gorgeous venue and the white gear matches properly😊
Quick question: How do you handle the switches and rotary potentiometer on the front panel? And how do you connect your headphone?
Thanks in advance and enjoy your next gig.
Brgds BeatMaster
@BeatMaster if you look closely, the front panel is completely open, so i can just plug in my headhpones , and even have a charging cable going under the unit to the front for charging my phone
1 Like
So it happened again yesterday during a wedding party. Crash 2h is my set. this is bad - writing a bug report as we speak - will post here to see if any of my specific situations rings a bell to you guys.
I am experiencing critical crashes with my Denon Prime 4+ White running Engine DJ 4.2. During live performances, the unit has rebooted spontaneously in the middle of the set — twice so far (in each set since i’m using the unit which was in a case for a few months) — after showing screen jitter and slow response times.
Setup:
- Denon Prime 4+ White (Engine DJ 4.2)
- Music exported from Engine DJ 4.0.1 on macOS 11.7.10
- 512GB FAT32 USB stick (Transcend or SanDisk) with music, stems, and SoundSwitch shows
- SD card present as backup (not used during sets)
- No streaming, but Wi-Fi and Bluetooth were enabled
- SoundSwitch controlled via official USB dongle
- Stems used in ~50% of tracks
- Frequent use of loops, cues, match suggestions, and track info view
- No FX unit use, no roll/slicer, no crossfader
Before each crash, I noticed jittery screen behavior and delayed response when previewing or loading tracks. One crash occurred while recording; the second happened without recording. Tracks involved in the crash played back fine afterward, so it doesn’t seem to be file-related.
I’ve used this unit intensively throughout 2024 without any issues. These crashes only started after updating to Engine DJ 4.2. My library management laptop can’t run newer Engine DJ versions due to OS limitations, so I use version 4.0.1 for all exports. I create stems on a second laptop using the same USB stick.
This unit is built into my booth for wedding gigs, and I perform twice a week. A spontaneous reboot mid-set is disastrous in a professional context.
Preferred resolution: Please investigate this issue — whether it’s related to stems, USB handling, library size, or Engine DJ version mismatch. I’m happy to share logs, test scenarios, or recordings if needed. A fix or workaround is urgently needed to ensure stability during long sets.
2 Likes
Moin @OliverAlex,
thanks for your advise, I will look more carefully next time.
Sorry to read that your trouble persists. I’ll keep my fingers crossed for you that the issue will be solved asap.
Good luck BeatMaster
I used Apple Music
Hi all - We are looking into this issue
Just curious if everyone who has seen this issue is using a case with PRIME 4(+)?
We may have some more questions soon to try an narrow down the reproductions steps for this issue
Thanks!
3 Likes