I could imagine a setting on the device/profile to follow experimental or stable builds. Ie the professional DJ requiring absolute stability will not get prompted to upgrade, only when a release is considered stable?
The problem is always in communication. It wouldn’t cost anything to be present in the forum and say, “Guys, we’ve received reports that there are problems. We’re checking and will keep you updated!” Instead, no one takes a moment to inform users if they’re trying to resolve the issues. This makes them lose credibility! What’s most annoying is that when they reply to a ticket, they always say, “I hope you’re well, we’re sorry you’re having problems!” This is the usual response they give! It makes you think there’s a bot behind it!
Those who actively seek information here in the forum make up only a tiny fraction of the actual user base.
None of my clients are active here. The update is simply offered to them, and they install it. Only a very few ask beforehand whether they should perhaps wait.
And honestly: What are we supposed to tell them? “You’d better not update just yet; it might still be unstable”? Especially when some users have already been waiting months for bug fixes for older issues.
At least here in Germany, customers also have legal rights regarding the rectification of defects. If serious problems cannot be resolved within a reasonable number of repair or rectification attempts, the devices can ultimately be returned—something that has, in fact, already happened in my case.
What I currently find interesting is the fact that major retailers no longer seem to be prominently listing the Prime 4(+)—aside from remaining stock, such as a few “White Editions.” This may mean nothing; but, combined with the current situation, it naturally fuels speculation.
Personally, it wouldn’t surprise me if the Prime 4 generation were approaching the end of its product lifecycle. A potential successor—such as a “Prime 5”—strikes me as more realistic than any significant future hardware evolution of the existing platform, particularly in light of the newer RS1 architecture.
At the moment, however, I face a difficult choice: Either I revert to an older firmware version with its already known issues, or I stick with version 5.0.x—a version I currently do not trust for live performances due to the audio dropouts I have observed.
Consequently, I have now spent my second weekend using an XDJ-AZ—pulled out of storage—as a backup system, instead of my own Prime 4+. It’s a shame…
Let’s not forget…. The players themselves offer us the option to install, or ignore -any- new firmware. New firmware doesn’t install itself.
We could, with a little willpower, easily avoid new firmware being installed. But…
Personally, I tend to think: The OS and the software have a new version number, from 4.0.0 to 5.0.0, so it’s a major version. Therefore, I’ll delete the database folder from my Mac and format my dedicated media drives. Then I’ll re-import my root folder, which contains subfolders, and then I’ll scan the entire library in EDJ Desktop before exporting my new database. By doing this, I’ll minimize the risk of conflicts with the various files created in the database (old vs. new): “hm.db, rbm.db, stm.db, trm.db, sm.db, itm.db, m.db”.
yes but when the bugs exist from day one, u cannot avoid them, lol
Except we all know that people who encounter problems will be the first to speak up, while those who don’t have problems will be nowhere to be seen. For example, if 200-300 users out of 4,000-5,000 worldwide are experiencing issues, it’s either due to bad luck (hardware problem) or because the user isn’t following any recommendations from the manufacturer/developer and doesn’t care about the quality of their audio files or their storage media.
If it is indeed a bug, then unfortunately for them, we can say that these are isolated cases! Therefore, it will be necessary to gather as much information as possible to reproduce the problem so that it can be fixed as quickly as possible, but it will be more complex to find the bug with such a small proportion of users.
Avoiding an update is a choice and a right, however, this is not what will advance the evolution of software. If no one installs an update, then no problems will be detected and even less corrected since no one will make feedback and the risk will be the accumulation of bugs that users will discover for themselves when they buy the product late, which will include the latest update by default upon purchase.
That’s both unfair and incorrect / there hasn’t been a firmware update for prime which -hasn’t- included bug fixes or patches
What some souls have described as bugs, of course, have been more ommited expectations
im referencing programs in general like Engine Dj that still has a few bugs since day 1
Exactly the kind of struggle you don’t want. If the same effort would be put in after sales / customer support as the fancy marketing material about new releases, experience of owning the product would be different.
Edit Note: im not saying everything is bad, just it feels like the previous major release(s) all over again. No lessons learned.
I doubt there’s a program over 50 lines of code anywhere that doesn’t have a bug in it. Engine DJ and Engine IS is in good company; no better or worse than any other
Even code that runs spacecraft have bugs, and the average cost per line of code is $1,000,000 USD at NASA.
Engine DJ, like almost all modern software, is built on top of abstractions and dependencies. Part of why I began to get involved with this communit has to do with a serious bug in 2023 where exporting music (syncing) would cause database corruption. I was part of the reporting & community issue testing. At first, we all thought it was Engine DJ that was the problem.
It took quite a number of months, and inMusic then thought it was SQLite (a dependency that is the underlying data base technology) that was the issue, given that the problem was easily reproducible using SQLite tools.
Fast forward some time, and we learn that it’s actually a bug from Apple and how they implemented FAT32 and exFAT.
It’s easy to blame Engine because it’s the software you interact with, however, the above case is proof that software complexity is far beyond the virtual touch screen & some buttons you see and interact with.
Please try to think bigger next time.
I wasn’t referencing any 1 certain bug, just in general with most companies like you said
Those who are BETA cannot say they are BETA, gentlemen, lol. 
What’s beta?
Waiting for someone to tell me too! 
Maybe a Brave New World reference?
Sci-fi for inMusic.
Here they struggle just to mark the implemented feature requests threads.
So you do the beatgrid adjustments and cues all over again in your whole library on every new major version? I ain’t got no free time for that