This is an interesting video.
Interesting. Although this is achieved through modding rather than a supported API, it does show what could be possible if manufacturers opened up their platforms a bit more. Think of an app marketplace for Engine OS extensions. inMusic could even take a small cut from paid extensions while significantly expanding the capabilities and appeal of the platform.
I honestly don’t even know what expression I’m supposed to make right now. 
There is an incredible amount of effort going into this, just to replicate something Denon DJ has been doing for quite some time already.
Even more bizarre is seeing how many people apparently want this, while at the same time refusing to simply use a brand that already offers it.
And I think that says quite a lot about the mindset here. They haven’t really understood who is actually setting the standard in this particular area.
Now that I’ve written all of that, I finally know what expression to make.
Pitying. 
Every single one of them could already have it. 
One of the difficulties with opening up Prime OS to 3rd party apps, cracks and hacks is testing.
A massive amount of beta testing already happens prior to firmware releases - and even now it’s just not possible to catch every single bug by using every single combination of menu options, features, play mode (standalone, dumb midi box mode), soundswitch, nano. Some say not enough beta testing is done currently, but few want to wait 3 years between each firmware update “Christmas”. In fact social media has already started getting “when’s the next free firmware coming out for Prime? I want A and B and C added”
If 10 3rd party hacks came out for Prime, InMusic would have to take a stand of either:
• Our beta testing does not include testing while any 3rd party apps are in use.
Or
• Tested with App1 , App5, App6 (a partial nod to open source etc)
But who’s to say that it’s would only be 10 hacks? Beta testing across all combination of menu settings, sound source etc would be even more impossible with 20 hacks, 50 hacks? 100? And let’s not forget the dynamics BETWEEN more than one hack running at the same time…. Beta testing of new firmware with hack # 17 AND hack # 23 , with soundswitch, using USB source on deck 1, Tidal on deck 3, fx on , menu option 52 = “Medium” etc etc etc
Ok if you’re just a bedroom DJ or internet streamer then crash’s don’t have any impact - but keeping every line of code in-house means a more stable environment for sure.
And that’s what the majority of us want. Keep feeding it clean unleaded premium and let’s not hacksaw and gaffa tape in a gas canister of Nox.
Enter: Gate CUE … welcome to 2017 for the CDJ-3000X.
It simply is a religion in this time and space.
In 2001 Denon DN-S5000 already had this type of cues. You could even switch the bahviour of Hot cue from Hot start (regular hot cue) to Stutter (gated cue) with a FLIP button that was right next to hot cues A1 and A2.
CLUB STANDARD! 
Exactly this.
Using extensions would be at the user’s own responsibility. Routing your audio through various external hardware boxes isn’t fundamentally that different; only in this case part of the routing is done through software.
The vendor remains responsible for the product they deliver and for making sure the integration points/API follow documented standards. What users connect to those endpoints, which extensions they install and how they route things from there is their own responsibility.
That doesn’t mean inMusic would need to beta-test Engine DJ against every third-party extension.
The issue is , however , that when the music stops dead, everyone looks at the booth , and the words they see on the back of gear is “Denon DJ” not “Zak’s cracked hack”
The audience / promoter etc will incorrectly see the issue as Denon DJs fault, not some wierdy beardy half AI’d lump of code.
IMHO it’s part FU AT/Pioneer look at the innovation you’re gatekeeping for profit and part FU look at what I can do, and part “anything but Denon”
Honestly, I still think the whole thing is fake. And I agree with you that, whatever is actually being demonstrated here – a hack, AI, or something else – this is potentially more embarrassing for AT than it is impressive.
Assuming the firmware really has been modified, which I consider extremely unlikely, I would actually hope that such a hack would spread.
Because then AT would have a serious problem on its hands: suddenly there could be unofficial devices offering functionality that is not supported by event companies, technicians, or AT itself. At that point, they would eventually be under pressure to provide an official solution.
And this is where I disagree somewhat with the idea that AT is deliberately holding back features and releasing them slowly as a marketing strategy.
Looking at what has happened over the last few months, and especially at RB, I increasingly get the impression that the current platform simply may not be capable of supporting some of these features in the way they would need to.
Just look at track analysis directly on a CDJ or the XDJ-AZ. In my experience, the results can already be worse than what I have seen from other systems.
If there really is a hack, external workflow, or workaround that makes STEMS possible on these devices, I honestly hope it spreads.
Because then AT could suddenly find itself with devices that are technically capable of doing something that the official ecosystem does not support.
And that would be an incredibly powerful advantage for Denon DJ and inMusic – far more effective than almost any advertising campaign could be.
You would have a very simple comparison: one platform is missing a feature, while the competitor already has it and supports it consistently across its EngineOS hardware.
And I think there is another interesting aspect to posts like this.
It suggests that people are clearly starting to look at what inMusic/Denon is doing. Maybe quietly, maybe reluctantly, maybe even with a little bit of envy – but to me, that almost feels like a cry for help. 
AT will certainly notice discussions like this. Whether they can or will react to them is another question.
Personally, I doubt it. I suspect they currently have much bigger priorities, especially with new product lines that still need to be brought to market and sold.
And honestly, the part that might hurt AT the most is seeing people like James Hype, Phil Harris and others even engaging with this kind of discussion.
Whether you like those guys or not is beside the point. When artists at that level start publicly showing interest in functionality that a competitor already provides, that is probably a lot more uncomfortable for a manufacturer than another hundred-page discussion on an internet forum.
It’s not AI, another user did it on RX3, stems and key changes, and day mode, and everything is available for download and installation on giftub, and he even put his logo in place of the rekordbox one, when you eject the USB key the device returns to normal! He therefore demonstrated that stems can also work on CDJ 3000s and even on RX3!
I’ve been following him on Instagram for a few weeks now (since he first dropped the initial video) and he’s done some good stuff. Triode (Now Playing) is active on his socials too. It’s legit.
I’ve got all the links to resources which are in his profile on Instagram but I didn’t mention it on here and won’t post them but they’re easy enough to find. His journey is interesting and even on his Insta he shows the video of AT acknowledging his work but dismissing it as poor quality.
Root was gained for the players a while back but it’s opened the door to a lot of tinkerers and I’ve watched with amazement in how he’s done it.
Once you go down the rabbit hole of all-in-one modding it’s a nightmare to get out! Some certain units have been turned pretty much into a games console haha.
Yes, I’m aware of the Tratosca rootkit/toolkit and I agree that it is a very interesting technical achievement.
But that actually reinforces my point: if the community can achieve this through reverse engineering, it inevitably makes people look at what other platforms already offer natively.
So I still see this less as a win for AT and more as free advertising for their competitors.
And that’s exactly why I agree with djdragon’s “FU AT” interpretation here.
That reminds me of my Traktor export script I made for Engine USB sticks when I first got my SC6000s.
it worked flawlessly, until the Engine 2.0 upgrade, where the update of the library would fail. Took me the better part of a week and a few angry posts on the forum before I realised I created the bug myself by writing directly to the library, deviating very slightly from the standard format Engine was expecting…
That’s more or less exactly what will happen when plugins would be allowed…
To me that is actually more of an argument for a proper API than against it; An extension should use documented hooks, not mess directly with Engine’s database or core OS. Keep the important stuff protected, version the API and simply disable extensions that aren’t compatible after an EngineOS update.
There will be some survival of the fittest. Good, useful extensions will be used and maintained. Bad ones won’t. As a DJ you’re responsible for your own setup anyway. I wouldn’t install a new extension just before a gig, just like I wouldn’t jump from Engine 4.x to 5.x without testing it first. 
Anyhow, it probably won’t happen. Keep on dreamin’ and appreciate whatever the Engine gods give us. 
Meanwhile cheapest controllers do support most cutting-edge features.
As for AlphaTheta: classic declining cash cow. It’s good to see the community, including some prominent AT supporters, starting to call it out.
And that’s exactly where you’re wrong. Pioneer users will discover that by installing a modified firmware that’s available online, they’ll use it and get the stems and other features, rather than switching to Denon! It won’t bring anyone to you, in fact, Pioneer will be almost forced to include those features rather than risk losing customers! They’ll include these features themselves! Every day, the number of people who have downloaded that firmware and try it increases, and curiosity will lead more and more people to install it and get the stems without paying a cent to Denon!
I don’t think that contradicts what I’m saying. The ability to gain new features on hardware you already own makes a platform more attractive, not less.
If Pioneer users start installing modified firmware just to get features AlphaTheta doesn’t officially provide, that mainly shows there is demand for those features. If AlphaTheta then feels forced to add them themselves, the community has effectively pushed the platform forward.
I’m just saying that those who use Pioneer, if they were interested in stems and other features, would have already switched to Denon, but that’s not the case! Rather than switching to Denon, they will wait for Pioneer to include these features! I use both Denon and Pioneer, but even if I use Denon every now and then since I bought an AZ and a FLX10, but honestly I don’t care about the stems at all, I’ve never used them, the only use I have of the stems is to produce remixes or mashups with Logic and FL Studio software, but I will never use them for DJ sets!!
Honestly, I think you should look into this, because once you master them, it changes absolutely everything regarding the cleanliness, fluidity, and quality of your transitions.
Most DJs use stems the wrong way; they tend to think they’re only useful for live mashups—like isolating an instrumental or a vocal.
But that’s probably the most basic level of using stems.
Just mix normally using your EQs as usual, but use the pads in stems mode to simply remove elements that make your mix sound cluttered.
Try transitioning between two tracks and cutting the bass stem of the outgoing track—using the corresponding pad—right when the bass of the incoming track kicks in. You’ll immediately notice how much less muddy and more open your mix sounds, since there’s no longer a bassline clash.
This is even more effective when you’re mixing harmonically (something every DJ should be doing anyway).
Cut the vocal from the outgoing track using an “echo out” effect right as the vocal on the incoming track starts, or swap basslines or melodies between harmonically compatible tracks to make your mix more dynamic and surprise your audience.
Mixing with stems takes your performance to the next level.