I sure hope they come up with a fix for that. I strive for perfection every time and these issues are unacceptable.
What matters is that this gets reported to Support. The moderator will undoubtedly pass on a thing or two internally here, but—since I myself work full-time at a very large CAD/CAM software company here in Germany—I know just how important it is for bugs to be reported into the system through official channels as well.
I can confirm a specific master audio glitch on the PRIME 4+ running Engine OS 5.x that triggers during track loading and source switching.
The Issue: Playing a track on any deck and loading a fresh track onto another causes the live master audio to drop/glitch for a split second before recovering.
My Findings:
-
The glitch happens almost 100% of the time when Vinyl Mode is ON on the playing deck.
-
While turning Vinyl Mode OFF reduces it, the audio will still occasionally stutter during a load or when switching browser sources (e.g., SSD to USB) mid-play. Key lock or pad modes make no difference.
-
Happens identically using a high-end internal SSD (Samsung 870 EVO) and external USBs (both exFAT).
-
I downgraded the hardware back to Engine OS 4.3.4 using the desktop installer, and the issue vanished completely. Audio remains flawless under heavy loading and source switching.
This is clearly an Engine OS 5.x software regression. The 5.x architecture is likely starving the audio playback buffer when prioritising CPU threads to fetch, cache, and render new waveforms on the PRIME 4+ hardware.
I’ve raised a ticket with InMusic support. Anyone else seeing this on 5.x?
I really hope you’re right. Your workaround has at least significantly reduced the problem—until the first lag occurred after about 45 minutes. Unfortunately, more followed after that. At any rate, it points to a possible direction regarding where the root cause might lie.
I’m having the exact same problems with my Prime 4+, everything you mentioned. I hope they fix it soon. Cheers.
Hey mate, how did you revert to a previous version? In my case, 4.3.4 was working fine. Cheers. Sorry for my English.
You can still download Engine OS 4.3.4 from the downloads page and install it either via USB or the desktop updater.
Personally, I find it frustrating that, after several weeks, there is still no public timeline for a fix beyond the confirmation that the issue has been identified and escalated.
At the moment, rolling back to 4.3.4 seems to be the only realistic option for users who are affected and need a stable standalone setup for live work.
Unfortunately, that also means giving up some of the improvements introduced in 5.x and living with the older limitations and bugs that many of us were hoping had finally been left behind.
To be honest, that leaves me feeling stuck between two imperfect choices:
stay on 5.x and deal with the audio-dropout risk, or roll back to 4.3.4 and accept the older issues.
Everyone will have to decide for themselves which compromise is more acceptable for their own workflow.
scroll down and selct EngineOS scroll down to the 4.3.4.
Thanks a million for replying. I’m going back to version 4.3.4 and I hope it works well again like before. Cheers!
The only issue I had was my lc6000s not connecting on 5.0 which has be addressed other than than my sc6000s and sc live 4 are working as expected
Personally, I haven’t had any audio problems or crashes with version 5.01!
I’ve done five wedding gigs with my P4+ without any issues!
Three gigs in a Tech House themed bar with my Rane System One. I experienced a Wi-Fi disconnection after three hours of mixing with the R.S One (I don’t use it, so it didn’t bother me! I only received a “Wi-Fi Login Error” notification).
Two lounge/disco house gigs with my Prime Go in a snack bar with a private pool. I had a minor bug with the two Pitch Bend buttons, which can be bypassed by slightly manipulating the jog wheel, and then it worked again, but nothing insurmountable.
I made the mistake of updating to 5.0 and mid gig the decks stopped outputting to the speakers mid-song. At first, I thought it was something I did, then it happened two more times. Lucky, I keep a cheap microcontroller set up as a backup. I’ve had Denon products in the past (7000, 8000, Prime 4, and Prime 4+), and I’m disappointed that so many people are experiencing the same issue; did this update not get field-tested before the Go Live? This is the kind of failure that makes me want to hang up my Prime 4+ and go back to Pioneer 
Sorry for the delayed response getting around to doing this - now done here - in the meantime I’m back on 4.3.4 where I’ll stay unless this gets changed back. It may seem silly but I gave it the best part of 3 weeks and I cannot get used to the new, clunkier way of working!
Same. Fortunately I had a cheap Hercules back up for my gig. Someone needs to be fired!
This is not BUG. Devices running Engine OS have never been able to connect to Wi-Fi networks that require a web browser to confirm the connection. Never connect to such a network! Engine OS does not have a built-in web browser.
That’s not the point. We know this, but let’s says someone didn’t know a WiFi needed a web page to connect, there’s then no way to turn WiFi off or forget the network, and then led to the issue of booting up to a black screen.
Been having a few issues on my Prime Go+ since I bought it and updated straight away to 5.0.1
I bought it yesterday and updated, and have had a few issues on my first couple hours session:
- Scrolling through playlists feels way less responsive than my Omnis Duo, in comparison. Was it better before 5.0.1 ?
- I had a random complete reboot in the middle of a set
- Apple Music tracks not loading on the first couple of tries. Happened in a session, did another one without issues after that.
- Apple Music getting disconnected randomly
- The battery indicator stayed at 0% the first time I turned it on and plugged in
It seems that the experience you’re describing was simply your own mistake. This is because you didn’t thoroughly read the release notes for EOS 5.0 or the updated manual for this new version. If you had studied the updated manual for Engine OS 5.0, you would have found that a fundamental change occurred in this single feature. It is not enough to simply update Engine OS; you must also thoroughly study the release notes and the user manual for the new version of Engine OS. And this applies regardless of what I personally think about this change. This change in the gesture’s behavior is likely related to future editing features for track, that will be added to the future…
I can’t believe there are people who are upgrading with so little time before (or even during, as per social media) a gig, without giving themselves time to properly test new firmware on their own set up.
Similarly, giving time for the database on their drive(s) to upgrade up to version 5 database
Of course. It’s called brand trust.
100% incorrect. I read the release notes in full before upgrading, as I always do. I’m not going to read the manual again for software I’ve used for many years unless I wanted to use some of the new functionality mentioned in the release notes. The fact you’ve suggested I should have read the release notes ironically suggests you haven’t done so. There is NO mention of this change in the 5.0.x release notes. It is mentioned in the 4.6 release notes, a version that was specific to RANE SYSTEM ONE. I use a Prime 4+ and a Prime Go. I therefore didn’t expect to have to read release notes for a version that wasn’t applicable to my hardware.
I test that the basics work after every upgrade (at home, before going to a gig) but don’t expect to have to test everything in detail because of the point @LAUBE makes -
By testing basics I mean loading a track to each deck, checking they play as expected, mixing between them works, browsing the library and searching works, etc.