Before the multi-core processor of the SC5000, no one even questioned what was in their overpriced Pioneer CDJ with chips of a few pennies.
A Bugatti uses VW parts. That’s how businesses work. Wake up. Doesn’t mean I like it, but that’s the sad reality currently.
I and others have complained in length (to all mixer manufacturers) to use high quality P&G, TKD or K-APLS faders. Even in the VCA/digital ones, but no. Just to save some extra money.
But, I think we’ve made some progress on this… tbc.
Minute 33:52 if anyone is interested
10:30
Times are changing.
When you buy a car, you want to know what kind of engine it uses, its power output, and how many horsepower it will produce for the price you pay.
When you buy a smartphone, you want to know what kind of processor it has and how powerful it is, what kind of screen it has, its refresh rate, what kind of camera sensor it has, and what kind of Wi-Fi chip it has. If the salesperson simply tells you it takes photos, lets you browse the internet, and runs apps without giving you any information about its technical specifications, you don’t just say, “Oh awesome, it costs $1500, take my money.” The same applies when you buy a computer.
Why should it be any different for DJ equipment? Exactly like for all other high-tech products!
We should know exactly what we’re getting for our money regarding hardware specifications, and we should demand more transparency from manufacturers (all manufacturers) to make informed choices and be able to gauge the product’s longevity. We shouldn’t just be satisfied with empty promises like “don’t worry, bro, it’s coming” without knowing in what form or condition.
“when stems is fully rendered”
That’s vague! How long? For a 3-minute track, for example? 3 minutes later? 6 minutes later? 15 minutes later?
You know what they say when something is vague? It means there’s something fishy going on. If it were very fast, it would be explicitly stated.
So we’re dealing with a background pre-rendering mode… which will take… as long as it takes… be patient.
Exactly the same way Traktor currently works, ultimately.
Just as I predicted… again…
I don’t really care what you think, I’m just sharing a video showing some functionality… I’m bored of your twisting, turning, peeing whichever way the wind blows conquest to prove some kind of sad little point on an internet forum.
Grow up man.
Times are not changing. Should equals won’t.
Your “I would pay the $100 extra” translates in 5 or even 10 fold in business. Not +100 on the current price.
It’s ok Reese. It’s gone from ‘flat out impossible to do it on such a poor processor’ to ‘people are going to be angry it’s not doing it live’ in less than 48hrs. At least his MO of changing his opinions with the landscape never fails.
Massive yawn fest from the biggest ‘bad actor’ on the whole forum.
Oh, you were expecting me to apologize and admit if I was wrong in the other post.
But I wasn’t wrong; itrs a pre-rendered stems in background, not on the fly, Words have meaning, . Rest assured, I don’t expect you to apologize by admitting I was right about the chip’s capacity… which is even lower than expected since it’s not even an RK3588…
I’m not expecting anything from you.
The same goes for you; you’re the most disingenuous fanboy on this forum. You’re willing to do anything to avoid admitting the obvious.
He’s running 4.6 Beta 2 and it seems the stems can be rendered in the background and not live. To be honest that’s what I expected. Nobody needs stems for every song in their collection so this makes total sense assuming they don’t take forever to process and are saved by the unit and can be used again.
If I were DJing in a pub for example and I though I’d need stems to mix, I’d be happy if they were done in say 30 seconds, which would be approx 10x.
Here we go again. back for 2 minutes and involved in another argument.
Unlike you, I havent made any bold claims that I need to climb down from (or in your case double down on). I have zero interest in this product or stems so I don’t really care either way. What I do like to do with everything in life is take the pragmatic approach and keep my mouth shut and wait for concrete information about something before providing commentary on it. I don’t fly off the handle and draw conclusions about things, even more so when I have absolutely no evidence to back those conclusions up, sticking to facts is so easy because you’re not burdened by anything other than the truth.
I have no idea why a piece of DJ gear gets you so riled up, you’ve been all over this forum for the past 3 days spewing nothing but utter bile, with no let up…. It’s a DJ controller, nobody started a war.
The fanboy comment is funny, it really is. Although I’d rather spend my life with a relatively positive outlook on things as opposed to drowning in obsessed negativity. I know which one is better for the soul.
I just posted a video relevant to the title of the thread, it wasn’t bait of any sort but it certainly seemed to ruffle someone’s feathers.
Anyway, the video is there that should at least put some people’s concerns at ease, the device is rendering stems without a computer.
P.S. I agree with your comment above, it would suit most people’s workflow to have it rendering, it’s pretty much what Serato does, throw it in the stems, wait til analyses, use it.
This doesn’t bother me ! From the start, and I’ve always said that these RK35 chips aren’t capable of “on-the-fly,” “real-time,” or “temporarily stored in RAM upon loading onto the deck” stems, or whatever you want to call it, using your preferred wording. I never said it was impossible to do on-board pre-rendering! But that wasn’t the point, because the core issue of all my comments has always been “on-the-fly stems.” You load the track, and in a few seconds you can use them; there’s no local storage of the stems. You understand the nuance, right? Because I can’t be any clearer!
I said that if this chip could do anything for on-board stems after they’ve been declared as arriving, it would, at best, be standalone pre-rendering, probably in the background.
Reread my statements. Again, words have meaning.
Can you honestly admit that, or are you genuinely acting in bad faith?
But I… I’m a psycho… 
But that’s why I mentioned it elsewhere, per-rendering, whether external or onboard, is okay.
The seat will be filled later anyway. 
Djay Pro list the 2nd generation iPhone SE and the iPhone 11 as the minimum requirement to achieve the highest quality in neural mix.
Why don’t you compare the specs of those devices to whatever chip is installed on the Rane and see if it can be capable of handling it.
And I don’t care what you say, it’s easy enough to go back and edit your comments, there’s even a little pen logo above the comment to show it’s been edited. You’ve been banging on for months that rendering stems inside the device is not doable, and that was your party line when the info about this first started appearing. Your whole backing for your argument was based on how long it took for the MPC devices to ‘render’ stems, nowhere did you mention ‘on the fly’, you’ve just moved onto that now it suits.
You’re clearly never going to admit that a $10 processor isn’t up to the task for this kind of work, and you’ll keep looking for every excuse and prevarication imaginable. Is it so hard for you to acknowledge the facts just once in your life?
What do you want me to say? Maybe the iPhone 11 SE’s CPU is far superior to any Rockchip? Would that be so surprising?
Rockchips are among the most entry-level processors of the entry-level market… They’re barely good enough for Android TV boxes… and for InMusic, which likes to spend between 0.4% and 1.8% on CPUs in devices that sometimes cost several thousand euros… (and make a lot of profit in the process).
Just a reminder that the current version of stems used by Denon and Rane is Stems Pro V1 by Zplane… not V2 (so not high quality). Just V1…
And since I know you guys inside and out and you’re annoying as hell, you’re going to ask me for my sources.
Good news for you, it’s mentioned right at the bottom of the stems page on the EngineOS website…
So, if this chip, just to process V1 stems, already takes 6 minutes to pre-render a 3-minute track in the background at medium quality, how long will it take to process the same 3-minute track the day they try to implement Stems Pro V2 (you know, the one DJay Pro and VDJ use… in real time!)?
20 minutes?
I sometimes edit my newly posted comments immediately when I realize after rereading that the translator hasn’t worded them exactly as I intended, but this doesn’t apply to my older messages that haven’t been recently edited. Check for yourself.
ON THE FLY! Not doable on the fly! Not a pre-rendered version.
And until proven otherwise, what we see here is pre-rendered
I’ve always been against pre-rendering for my use case, and that’s what interests me!
I really don’t know what to say in the face of so much bad faith.
I rest my case your honour, the wind changed and so did the direction of the pee.
