i hope this year,engine dj upgarde the stems more ,make sound much better
1 Like
Is this your personal opinion or just based on that video?
it my personal opinion ,but i belived there is more room of improvment
Of course any algorythm can be improved, that is the whole process of machine learning. I just wondered if you had just taken that video as gospel or if you had done your own testing.
yes i hav done my own testing personally ,that y i say engine dj have to upgrade more on the stems, about the video i was jst shaing it
Why not add the ability to read Traktor stems? Then we could also use stems generated by Nuo-Stems, which is currently the best separation algorithm.
1 Like
Agreed, and im sure it will.
Or why not one better, have a standardised file format for stems so you analyse once and carry it across all platforms.
2 Likes
The standard separation format exists, in Native Instruments’ plans it was supposed to be theirs, and it was offered free of charge to everyone.
Wasn’t that pre split stems from the studio though? not the same as what most platforms are offering.
You are confusing the Format with the separation algorithm, the file format is the same that Native Instruments has made available to everyone, stems.mp4 which in their plans was to become a sort of mp3. Then each program uses a different algorithm to obtain the separation from a complete track that is saved in a proprietary format, it would be enough to add the ability to read Native’s stems.mp4, we will have the ability to access programs like ripX and NuoStems.
2 Likes
The point I’m making, each software when rendering stems creates a new ‘stems’ file, these are all proprietary to each software. They need to be standardised so you can analyse for stems in one software and use it in others, without having to create additional files.
1 Like
Pre-computing stems is not the ideal workflow for cohorts like myself.
So hopefully thats a possibility in the future.
3 Likes
The same could be said for enhanced ID3 tags, beatgrids, cues and loops, but you know well that we are dealing with walled gardens and there is no market incentive to change.
Or even way beyond that, the DB files themselves, why the hell are all these companies using their own DB files instead of a standard format… literally wasting dev time when they could have pooled it into a standard.
Do all DJ apps do this, even the ones that do stems on the fly, like Algoriddim? I don’t know anywhere near enough about this side of the game.
No I think the on the fly doesn’t create any files, so that really is the nirvana for stems, but will need power from the hardware to do it.
Serato, Rekordbox, Engine and VDJ all create a new file for pre-prepared stems though and all are only useful to each individual software. So if you use multi you could end up with 6/7 times space needed for each track.
It’s hit and miss with pre-analyze to proprietary container file. On one hand it’s nice to have the ability to use stems with your favourite software especially with engine standalone hardware (it’s better than nothing)
But on the other hand the files are too big and the tracks have to be re-analyzed when ever improvements to the stems feature are made.
I’m satisfied with the results of real-time stems on my iPhone.
The best is Virtual DJ. Vocal Synth Bass Kick Highhats
Perfect for live/studio remixes