No I don’t. As I wrote earlier, I’m quite familiar with software development. You seem to be laughing a lot for nothing, and that tells me things about you… Stability and reliability are the biggest factors for any professional gear or software. It is of course ok to bring in new features and such, just not this way.
I use my gear professionally—event work is currently my main line of work—and perhaps by a stroke of luck (given that I’ve always had bad luck in the past), I haven’t had any issues so far. Yet, I’ve owned five Denon units running the OS: I sold the P4 since I have the Rane One, but I also have the P4+ and two Prime GOs—and prior to that, I was a Pioneer user for over 20 years.
I’m laughing because people can be so hypocritical! They want everything right away without paying a dime, and sometimes—just by bad luck—certain things take longer than others. I’m not laughing at you specifically, but rather at the way some people throw a tantrum, saying, “If this isn’t fixed, I’m going elsewhere.” Sure, that’s a choice, but there is another option: downgrading while Support tracks down the bug and rolls out a fix. The RGB wave effect isn’t vital, and neither is on-the-fly note entry, so downgrading won’t impact the use of the core functions.
I would add that when we don’t experience a bug—yet try to help figure out why others do while we don’t—we get attacked instead of receiving specific details about the issue.
We need information like audio file quality and source, oversized image tags, the storage medium used and its format, the number of files, the brand and performance of the storage drive, whether Wi-Fi is active (and if so, whether they are streaming simultaneously), whether Bluetooth is on, whether they are using SoundSwitch, how the gear is being used, the exact steps taken to trigger and reproduce the bug, and so on. So, it isn’t our fault if we don’t encounter the bug, and that certainly doesn’t make us so-called “fanboys.”
There are people here who are so full of rage that they lash out directly at our professional lives.
one thing that I like and that I’m having fun with is that I have a microphone in my hands, and every time the music stops, and people look at me, I say with the microphone in front of a thousand or even more people, (yes because they are big parties in this period) I pronounce the sentence don’t blame me but blame Denon DJ who has problems, he is not reliable at all!!
There is nothing hypocritical in what you describe. If Denon/inMusic chooses to release feature updates for free, be my guest. However, doing that and breaking an essential functionality (sound) is not acceptable.
*feels like spinning circles
@Reese is there anything possible to trigger some communication update about this topic?
It seems the current communication is not acceptable;
Impacted users are told:
- Official channel; support ticket is getting marked as solved
- Do not downgrade
- InMusic working on a fix, no timelines or updates whatsoever.
- Latest 5.0.2 update does not address the issue
Users are in limbo, with a stuttering, non reliable audio output. “Wait” can be a perfect reply if combined with some indication of timeline.
Know your role is forum moderator, but you seem closest contact to the dev team. What is your advice?
Already did. Awaiting staff.
Just as a small update for those following this thread:
I have received a reply from Brian regarding my open support ticket.
From my understanding, the issue has not been abandoned. Due to the scope of the work involved, it was not included in 5.0.2 and is still being worked on for a future release.
I have also shared a few additional observations from my own testing in the hope that they may help narrow the issue down.
This does not solve the problem today, but I thought it might be helpful to let other affected users know that there is at least some ongoing communication and that the issue still appears to be under investigation.
Like everyone else affected, I hope we see a proper fix as soon as possible.
Obviously an issue tougher than it seemed at first sight.
And solving the problem is taking more time than scheduled first
omg, brgds Beatmaster
other issues, but having the audio cut out when selecting another track—or even sometimes while actually mixing two tracks—makes it seem like the machine lacks power. Anyway, cheers, and I’m looking forward to that major update.
ye… haven’t continoued analyzin the changes below, but the list i attached here before made me think they introduced/changed use QT (gui library).
If i guessed right, it will be challengin task to prioritize ressources. I don’t like throwin’ random guesses 'bout tec-stack, but this is in my head since i posted the list…
… and now im loosing contenance
P.S: several audio libraries seemed to be replaced too.
At all: Please try firmware 5.0.3.
I will leave this topic open, as it is the largest one, and will set other related topics to “solved” or “close” for sake of housekeeping.
The gaps became a crackle on my device. So loading a track without sound influence on the master is still not given 
(Prime4+ & LC6000)
I’m gonna read the update log now…
With 5.0.3 The dropouts when changing tracks, skipping, or loading have NOT been fixed! On the contrary, the sound now sometimes cuts out for about 3 seconds!
I’ve had that too. After a factory reset, everything now works smooth however.
I just updated to 5.0.3 and nothing has changed; the audio stutters when selecting another track, and sometimes even while mixing two tracks—I haven’t noticed any improvement at all. Like the person above mentioned, I performed a factory reset, but it’s still the same; I reset the USB, re-analyzed the tracks, and everything is exactly the same…
I updated Prime 4+ to 5.0.3, converted my whole library to 24bit 44,1khz AIFF, removed all the cover art, removed everything from Engine DJ, Imported all tracks to Engine DJ, formatted the SSD drive inside Prime 4+, exported playlist to Prime 4+ SSD. Played about 1,5 hour and didn’t have any audio drops, or at least I didn’t notice any. The waveform kind of stuttered for a while in a couple occasions, but seems to be ok now.
Today its rainy weather here in South Sweden so I updated the p4+ to 5.0.3 and played for about 3,5 hour. Today I was running 4 decks.
I had no problem with anything, everything was smooth. The rgb waveforms was running without any stutter for the entire playtime. Thanks to engine team for this!!
After reading the recommendation to factory reset, i unboxed the device the 2nd time today.
I did the procedure and wasnt working for me too. i have to pack it now the 2nd time today … 
P.S. the next-track button rejected work on LC6000 after half an hour. Other buttons were still working and the 3rd deck was still able to load a track via touch display