Updated my Prime 4 to 5.0.1 - nevermind that I’ve had audio dropouts when loading new music for the last 4 gigs…but I’ve also noticed my crossfader was messed up, regardless of where my x-fader contour is set. Even with the x-fader contour all the way out, my music would dip in volume when the cross fader was centered.
Rolled back the drivers to 4.3.4, lost all of my artwork, but fixed my audio dropouts, and fixed my crossfader issues.
Denon, we need you to spend some time optimizing for the Prime 4+. We use this tool professionally, and these issues are anything but that.
Hi, I was dealing with this same issue on my PRIME 4+ and spent days troubleshooting it.
Two pieces of great news for you:
1. How to get your artwork back on 4.3.4: You lost your artwork because Engine 5.x changed how it writes database files, and 4.3.4 can’t read it. To fix it completely:
-
Uninstall Engine DJ Desktop 5.x from your PC and download/install Engine DJ Desktop 4.3.4.
-
Open your performance drive on your computer, navigate to the Engine Library folder, and delete the folder named Database2 (this wipes the 5.x cache).
-
Open Engine 4.3.4 Desktop, select your tracks/playlists, right-click and choose Re-import Track Information (or Re-analyse) to restore the artwork images.
-
Use Sync Manager to export back to your drive. Your artwork will fully return on the controller!
2. Denon has officially acknowledged the audio bug: I managed to get my support ticket escalated to an InMusic Level 2 Tech Support Specialist named James. He officially confirmed that the developers are fully aware of this 5.x track-load audio stutter issue and are actively coding a fix for an upcoming firmware update. > Fascinating that it broke your crossfader contour curve, too, which further proves 5.0.1 has some serious real-time processing thread bottlenecks. Stick to 4.3.4 (hardware and software) for your pro gigs until the patch drops, hopefully soon! 
Nonsense. The issue with the crossfader curve has nothing to do with the update itself. The driver version for the mixer section hasn’t changed in either EOS 5.0.0 or 5.0.1.
This may cause the mixer section driver to load incorrectly when the Engine OS system is booting up. This has absolutely nothing to do with the “real-time processing thread…”
The solution is a simple factory reset. If this does not help, downgrade to EOS 3.3.0 (switches for assigning the crossfader to the Thru position), then perform a factory reset and subsequently upgrade to 5.0.1.
You may need to check the physical condition of the potentiometer: the crossfader curve setting.
This potentiometer often breaks or gets damaged. The damage may not be visible! This can also cause various audio dropouts. I have already replaced these potentiometers on 10 Prime4 consoles. They were causing random and strange problems.