hi all
why there is no update to engine for long time
anyone knows why
hi all
why there is no update to engine for long time
anyone knows why
As ive explained to you on similar threads youâve created previously, this information isnât made public. As far as release timelines go, you can look at the full history of prior releases on the link below, this should give you some indications of timeline.
Because theyâre working on things that doesnât include us and theyâll release it when itâs ready?
[sarcasm]Due to the popularity of CDJ3000X over the SC6000, InMusic has no money left to pay developers and is about to go bankrupt. Your player will ofcourse stop working when InMusic finally files for bankruptcyâŚ[/sarcasm] ![]()
![]()
![]()
[again sarcasm]The board of InMusic feels the platform is complete and doesnât feel money should be spent on new features. Instead theyâre going to take a huge dividend. You will never see stacked waveforms, unless you pay up for the SC6000+âŚ[/again sarcasm]
I could go on fantasising disaster scenarios, although I believe the above comment are closer to the truth ![]()
Iâve been analyzing the historical release history of EngineDJ software (versions and dates) and wanted to share some observations and expectations for upcoming releases. My findings are based on publicly available information from EngineDJ Downloads and summarized using ChatGPT analysis.
Release Frequency
Minor updates (x.x.x) are released roughly every 1â3 months, usually focused on bug fixes and optimizations.
Major updates (x.0, x.1) appear roughly every 4â6 months, often introducing new features, workflow improvements, or visual enhancements.
Release Content
Major updates bring new functionality and features (e.g., Stems support, Bluetooth audio, updated visual design).
Minor updates mostly handle bug fixes, performance improvements, and OS compatibility.
OS Compatibility
Overall Trend
| Expected Release | Version Type | Expected Content | Notes |
|---|---|---|---|
| Late Sept â Early Oct 2025 | Minor update (x.x.x) | Bug fixes, performance improvements | Follows typical 2â3 month cycle |
| December 2025 | Major update (x+1.0) | New features, workflow or UI improvements | Roughly 4â6 months after previous major release |
| Feb â Mar 2026 | Minor update (x.x.x) | Bug fixes, OS compatibility, small tweaks | Usually patches previous major release |
| Mid 2026 | Major update (x+2.0) | New functionality, larger features | Continuation of regular major release cycle |
Summary:
Based on the observed patterns, EngineDJ users can generally expect minor updates every 1â3 months and major updates every 4â6 months. These updates focus alternately on stability/bug fixes and new features or workflow improvements.
Source: ChatGPT (based on EngineDJ download history)
Not all heroâs wear a cape Ben
âŚ. top work.
NO CAPES
Jokes aside I would actually sayâŚ
Minor update x.x.1
Mid update x.1.x
Major update 1.x.x
SooooooooâŚ.. dare we ask? What âworkâ are you thinking needs to be done very very very quickly. Be sure to include those easy bits that are very very quick and simple to do.
Also, as you posted in âGeneral Areaâ, do you mean work on Engine OS (firmware inside the decks) or Engine DJ (software on PC/Mac) ?
It would be nice if the OP did reply and provide some context, right now they have more âtopics createdâ than âcomments addedâ, how does that work?
Iâm a simple creature, my ÂŁ600 mixstream pro go does me fine recreating 2 decks & a mixer from days past at a fraction of the size with portability to boot, anything else is an added bonus.
Considering we get 99% of features/updates for free (not including the 1 off payment of ÂŁ10 for stems) I really donât get why people worry about it.
Obviously thereâs some outstanding little bits here & there that arenât 100% yet that people have been waiting for & obviously software bugs can cause issues/delays (Iâve actually experienced this) but this happens in all sorts of hardware from computers/phones to tvâs & soundbars etc
I understand people paying ÂŁ2000-ÂŁ3000 want the latest & greatest but come on it doesnât stop you from doing the basics of what it says it would on the tin when you bought it.
Kids nowadays donât know how easy/good they got it, should try 2 vinyl decks & a basic 2 channel mixer.
Its all to do with this imaginary race Andy, where one company is âsmokingâ another, or leaving it âtrailing in the dustâ etc etcâŚ. it fuels online tech talk like no other subject.
If InMusic go a few months without releasing something its seen as the end of all time, the death of the brand, falling off, losing their way and all the other superlatives.

Im just in the process of saving for those RP7 decks from Reloop and a good 2 channel DVS mixer to go with them, bring on the 45s ![]()
For me itâs just the speed of response. I reported a bug on the Prime Go+ firmware in December and it was acknowledged and forwarded to the Dev team. 9 months later and still no fix, even after 2 new software versions.
In contrast I reported a VirtualDJ bug on the Mac version of the software last week and it was found and fixed with a new build released in 48 hours.
I know itâs apples and oranges but a 9 month wait for a bug to be fixed is a bit long when you use the kit all the time and itâs constantly there. Thereâs also no feedback, you just have to hope it will be corrected at some point but how long?
Adding some insight on-topic.
We know that InMusic has several DJ devices in the pipeline. As stated in the Mojaxx video about the surprise showcase of the, in the meantime released, Rane One MK2.
So, next to bringing us updates, devs are also busy building firmware with specific features for those new devices. It all takes precious time. Ready when ready.
What was/is the bug? it is entirely possible it has uncovered something more complex that requires additional work and coding to correct⌠it might seem like some on the surface fairly simple issue that needs fixing but it can often open a can of worms, i know this from my day job dealing with this stuff. Often the complex things end up being pretty easy to resolve, the simple things not.
The preview player keeps enabling itself after a reboot despite being turned off in the settings.
So i can see why that is annoying, but i imagine they will have larger issues that need to be worked through. Most dev teams will have a priority system and in this case stuff like lagging, performance issues, freezing issues will be getting the most resource due to how they impact the user experience.
Is that a general setting or is it tied to your profile?
Itâs a device setting separate from the loaded profile.
Ok, so its not able to be tied to your drive profile. Im sure they will have added it to their list as an issue that shouldnât happen, but as its not impacting the overall user experience in the same way som other things are, im betting its been put on a lesser impacting list of fixes.
Hi @Homeland101 - Could you send me the bug report for this? Thanks