Yes, a device was returned because we couldn’t add the feature. Eventually, patience runs out, and then you have no other choice.
Especially with brand-new products advertised with specific features, this can be the very reason for purchase. If the feature is still unavailable after months, customers get frustrated.
And yes, devices were also returned because there are apparently still bugs. Whether these bugs justify a return or not is irrelevant! They want to return the device, and I can’t do anything about it.
Either I fix the problem within a certain timeframe, or I don’t because I can’t.
That’s why we recently decided to discontinue the sale of some InMusic devices.
I wasn’t consulted. I understand why…
I would have preferred a different decision, but I lack the arguments.
If you have any, please share them with me!
I was tempted to sell my sc live 4 and upgrade to the rane studio one, but held back as i would rather know the full capabilities first, hopefully when the next update comes out it can clarify what is happening
Announcing features that later turn out not to be available—and when they do become available, they differ from expectations—is understandably disappointing!
After everything that has happened (or rather, not happened) in recent months, the question is: Would I, as a private customer, buy another InMusic device?
You say the product is “incomplete,” so I must have missed something… !
As usual, a lot of buyers rush in without reading the manual, which are usually provided by default when a product is released! I didn’t see anything mentioned on the box or in the notice about “embedded stems.”
During the demos, they mentioned compatibility with SDJ Pro: “A public update 4.6.0 was indeed released at the end of February for SDJ Pro compatibility.” (SDJ Pro is a feature indicated on the box, in the manual, and on the product itself, so this functionality should have been included, and it was.)
Also in the demo, they mentioned an update that would allow the creation of stems.
Okay, but which version: “Alpha/Beta/Public”? If it’s an alpha or beta version, we could be waiting days, months, or even years.
Regarding the product being “incomplete” at launch… at no point in the demo videos do we see anyone performing a Stems procedure on the fly as an example. (If I missed this part in the X/Y demo videos, I’d like to see it!).
An Algam France sales representative told me that an update is planned for the second quarter.
In our Star’s Music and partner stores, the R.S.One is the best-selling product, and not for embedded Stems! Our customers don’t look at that and they’re not naive; they know perfectly well that an 8-core processor and 4GB of RAM aren’t enough to create Stems on the fly.
(We still have some optimistic customers, others who are doubtful, and a large number who don’t believe in it).
Except this must be a demo of an Alpha version! The problem is that the video cuts out; we can see processing at 6%, then the video cuts to something else! I think the creation process is too slow, and that’s why we don’t have anything yet. I don’t understand why the R.S.One doesn’t have at least 16GB of RAM, or at least the option to upgrade it.
But in any case, if this were an option included from the start, there would be instructions in the manual and it would be clearly highlighted on the box, like SDJ Pro, Wi-Fi, Bluetooth…
We don’t know how much time passed between the first and second “1 minute / 2 minutes or more” ??
The sequence is so very short that I hadn’t noticed it before (I must have been doing something at that moment, like making a coffee or taking a call).
Yes, for customers who watch videos and understand English! But in France, not all potential semi-professional and professional buyers are fluent in English, so they’ll either wait for a French representative or influencer to do a demo, or they’ll prioritize what they like, such as the feel of vinyl, so rotary platters, faders for scratching, and effects banks for transitions or other effects on a standalone unit.
The people who bought this product were mostly fans of the vinyl feel. They had hesitated for a long time between buying Rane Twelve, SC6000M, or controllers like the REV7, Rane One, or Performer (some already owned one of the products I mentioned), but they no longer wanted to carry around a computer. They were looking for an ergonomic, standalone unit with rotary platters, and their patience paid off.
Just have to wait!
The second quarter isn’t over yet!
But perhaps the update* that Algam France told me about isn’t exclusive to the R.S.One, but also applies to other Denon and Numark products… To be continued!!!
*To be clear, I’m not specifically talking about embedded Stems for the other products, to avoid any confusion!
If you were hoping to save storage space on stems with the RSone, you’re likely to be disappointed. The RSone uses an RK3588 and 4GB of RAM. Clearly, this doesn’t have the processing power necessary for high-quality stem separation with temporary RAM storage at a speed fast enough to achieve an acceptable separation time for a complete track in a live setting.
With this kind of hardware, which has relatively modest processing power, a pre-rendering step is mandatory.
For comparison, on the club’s PC running Virtual DJ, when stem separation is performed by the GPU (GTX 1080 8GB), the processing speed is between 16x and 18x. You can configure Virtual DJ to have the separation process performed by the CPU, rather than the GPU. I experimented to see how fast the Ryzen 7 5800x could go. Well, the maximum it can achieve is 2.5x (with 32 GB of DDR4 at 3200 MHz).
So, if a 5800x with 8 cores/16 threads, capable of reaching 4.7 GHz with a 32 MB L3 cache, can only achieve 2.5x, even though it’s four times more powerful than an RK3588 with 8 cores/8 threads, which only has a few MB of cache and four of its eight cores are actually low-power, low-performance cores, you can imagine how underperforming the RK3588 must be for real-time stem separation.
And the weak onboard NPU, which doesn’t even reach 1 Tops, certainly isn’t going to save the day.
People tend to think/believe that “onboard stems” means on-the-fly stem separation performed onboard without pre-rendering.
That’s not what it means. All it means is that the device will be able to perform pre-rendered separation onboard in the background—a process that will take as long as it takes—and that you’ll always do it much faster on your computer. This is clearly demonstrated in Jake Hill’s video.
It must be said that InMusic maintains this ambiguity with the “onboard stems” promise, which is both vague and ambiguous, leaving it open to interpretation. Some will see it as a promise of real-time stem separation without pre-rendering and will buy the product thinking they’ll get it someday (and they will be disappointed). And others, the more pragmatic ones who will know how to read between the lines, will only expect a pre-rendered mode on board which will always store the stems locally (and they will be right).
exactly, people are hyped on this onboard rendering and its kinda pointless, just render in EDJ and export. the last thing i want to do is load a track i want to use STEMS on and then have to wait while the STEMS are being rendered. i could not care less if they ever add this “feature”, once added everyone will just complain that its slow and sounds like crap. And it will not save you any room, it still will need to save the rendered file on your drive
the one thing that would be nice is to set a playlist with an option to create stems on adding a track so if i have a “2026CLUB” playlist, it will auto render the STEMS for any track i add
Let’s say that pre-rendering stems in the background can be suitable for some people in certain situations.
Typically, for a DJ who rarely uses stems but knows they’ll need an acapella of a particular track later in their set, even if they hadn’t initially planned for it. In that case, even if the system takes 6 or 7 minutes to perform the background separation, and the DJ needs to use the acapella in question 20 minutes later… okay, why not?
But clearly, for a DJ who uses stems on almost every track, in a completely improvisational/performance style, it’s not a viable solution in live conditions, unless they’ve prepared their set in advance and pre-rendered the stems for each track in their setlist. So even less for the DJ who hoped to be able to obtain stem separation in “load & play” mode with just temporary caching of stems without any local storage to save space.
Here’s the thing though, if a consumer sees that stems can be rendered on-board, they’re assuming it will be processed in a reasonable time. If it turns out not to be the case then that’s misleading at best.
I can also assume that when Jake made that video (assumedly before the RS1 was released) the dev team would know the speed of rendering at that point.
As I say, there definitely seems to be a disconnect between the marketing and product teams.
There’s other companies that would gladly take your money for “complete products”. Also complete products is a fallacy in the real world, even Artemis 2 isn’t a complete product so I highly doubt a DJ controller is either.
FYI early 2026 in corpo-world means it’s 4 months from the time it’s announced. RS1 was released January 20 2026, we’re just coming up on “early 2026”.
I’m involved in the logistics business and the 5th month of the year would never be classified as “early”. But each to their own.
I just want an answer as to when they will come and the capabilities of them. Is that too much to ask as a customer who has paid £2200 for something? Once the company provide this information (assuming they will) we can close the thread and move on.
If you want semantics, it’s not in the 5th month, we’re not in May.
I’m not in logistics, I’m in the side of “hey where’s our firmware/software for this mass EVAC hardware? It’s holding up a major airport project for the integrator”. You deal with minor irritants, I deal with multimillion dollar projects that impact people’s safety, we’re not the same. I can temper my expectations with DJ equipment. And now the obligatory image once again of what this thread has become.
No one owes you anything. You want results, join a beta program and give your input and criticism so it becomes productive and beneficial for all. Otherwise you’re whining about sour grapes.
As I said yesterday, the whole MIDI 2.0 situation has probably disrupted the original timeline.
That video from Jan was probably filmed before the Windows updates, which then caused chaos and the staff have since been dealing with the fallout from that - and rightly so IMO.
I think it’s far more important to get our controllers working again properly than to have stem separation onboard, especially when we already have it via the desktop s/w should a DJ consider it essential to their sets.
Homeland101 should be well aware that companies (software or hardware) generally avoid telling people in advance what’s coming, or giving dates - for the very reason we see in this thread. The constant bickering about why it’s not out.
I guess it’s partly Rane’s fault for mentioning it (if they hadn’t, would you still have bought the product?) but no one could have known about the fallout from the MIDI thing.
