It’s almost like different boxes for dedicated tasks but still use core components. I wonder what makes them so different? Oh maybe. Coding!
I know that very well, which is why I am still waiting for Stu-C’s justification on this point, and for him to explain to me how the developers of a group that is divided between several brands could do on one side what they cannot manage to do on the other.
I’m going to explain it a simple as possible for you.
Sometimes when a mommy product division and a daddy product division inside the same house really like each other they help with the dishes. Even though some of the dishes are different from each other they still serve the same purpose and the mommy and daddy work to gether to make the dishes all clean and working well.
2 Likes
Answer
The
Question
I sincerely hope not; common sense dictates that every human being should learn from their mistakes.
But I also know that InMusic has a tendency to rush things, to, let’s say, “underestimate” the scope of the task, or to overestimate their ambitions only to realize that the hardware isn’t up to the task. It’s all a matter of perspective.
And when they make ambiguously worded statements like “Remix on the fly with stems FX,” which might suggest that it’s the stems that are “on the fly,” when in reality it’s simply the act of remixing on the fly (with pre-rendered stems), I think it’s a deliberate strategy, approved by the marketing department. They’re intentionally playing on the ambiguity.
This is very practical because it allows you to create buzz, boost sales, and then say, “Oh, but you misunderstood; in fact, we meant that it’s about remixing on the fly, but you still need to pre-render your stems for that. However, the FX stems are applied on the fly to your pre-rendered stems.”
And guys, we have Feedback Suppression on this unit! Which is HUGE for mobile DJs! I wish more people on YouTube were hyping this feature but I get most of them aren’t actually mobile DJs.
1 Like
now in the download engine os 4.3.4 has system one appeared?
This device has come about since stems became a thing again, the whole conception, research and development, everything.
So why would that not have been forefront of their minds when choosing the hardware to go inside? The exterior surface is littered with stems controls, more than any other device.
And to top it off, you’re whole argument is based on you assuming the internals are the same as the Akai, without actually knowing it for a fact.
Bottom line about above discussion: We need to wait what the future holds.
Algorithms might get better on lower specked hardware. Using current stems in a mix is fine already. I certainly don’t expect a perfect sounding acapella from a random EDM track tbh. Even if software with beefy hardware could generate that realtime.
This is temporary for the other EngineOS devices to catch up, firmware wise. Might be database scheme related as well.
4 Likes
Just like the Rane One MKII, and in fact all these buttons and markings do not necessarily indicate or guarantee in any way that it is intended to do anything other than pre-rendering or be used on the fly, but only when connected to a PC with Serato or any other software.
And what’s the number one ‘elephant in the room’ big difference between the Rane One and this device?
Answers on a postcard please.
IMHO if there was two separate workflow schemes, pre render or real time based on user owned hardware, it’s not deal breaker but should celebrated that it can be done on a AIO and the end user hasn’t been left out.
Also IDGAF about stems that much LOL
This is the other thing, it’s called machine learning and that is exactly what these algorithms are doing, training themselves to be more accurate, more efficient, the longer it goes on the faster it will get, purely inside the software.
Unless people are seriously thinking we have reached a ceiling point with this tech.
One is standalone and the other is a controller, but the first also functions as a controller. And pre-rendering remains a standalone use case. The markings and buttons therefore make sense for pre-rendering, just as they make sense in controller mode… To conclude from this that simply because there are a lot of buttons and labels, on-the-fly stems will inevitably appear one way or another, is a step I wouldn’t take.
And nobody is doing that, what we are using to conclude is the fact they have always stated it’s their goal, told gear reviewers they are doing it, and most of all included it slap bang in the middle of the device homepage, coupled with the fact their other brand is doing it on their production device.
….which I agree with - but his own site lists the System One as a “standalone DJ controller”, and he said this mystery unit is “not massively different”.
And it seems, bu looking at the EQ, it can control the level of STEMs…
This is a tough but very honest crowd!! lol 
Let’s not forget this unit (as any other) will be launching 
on its first public firmware, we all know “more goodness” and “rock solid support” will follow.
The FX seem more well rounded and not so much over the top.. Also has an X-Y Pad!! 
Hi everyone, I wanted to ask you about the RGB waveforms. Will they also be available on other devices that have the Engine Dj ecosystem, such as the Denon DJ, or is it just for this model, the Rane Sytem One?