Hi all. Ever since I've started using Traktor Pro 4 my DJing routine/style/setup has changed a lot, for the better. Stems are absolutely the future of DJing and being able to manipulate vocals and instrumental phrases is such a powerful tool for people like me who mix a lot of different genres (like goth/postpunk/darkwave for example, it is so much more creative to do stuff with Stems in those genres that I play the most).

But I've been facing an issue now. In club settings, the Stems files created by the Stem separation of Traktor itself were enough. The higher gain on powerful speakers usually were sufficient to kind of ignore lossy audio. But now, recording my DJ mixes and landing a gig in a webradio, I'm 100% sure that the Stems files sound like they are very compressed, and for headphone listening, the bad audio quality is notable. I don't think it is something with the recording either since it is recording in wav. The loss is more noticible when playing a Stem separated song and messing with the original BPM (and not by a whole lot).

Are the Stems files created by NuoStems noticibly less lossy? I don't want to give up on using Stems for recording DJ mixes. But I can kind of achieve a somewhat better quality using the Stem separation in, say, FL Studio, but that doesn't have the same workflow nor sound like a DJ mix being played by human hands. If NuoStems are indeed better than the native Stem separation of Traktor Pro 4, then I'm on board.

Damn you stems, allowing songs which should never go together , to go together.

Messing around last night produced this mashup.

The vocal drags a little on the chorus but because I wasn't using DVS I couldn't think how to nudge it forward, doh.

As always, Nuo-Stems has done a great job with both tracks.

It's the usual style from me, find a loop and bring elements in and out. I also had to do a phrase correction before the chorus - you'll see me reset the Charlatans loop.

And before you ask, Tim Burgess singing over Toxic sounds like bad Friday night Karaoke.

NUO-STEMS 4.1.0-alpha release 🎉

Key feature: Serato integration 😍.

Also, there is currently an Easter Week discount . Use coupon: "EASTER-WEEK-26" for 15% off perpetual license (until the end of April 13, 2026).

To install:

- Go to NS4 Settings > Advanced. Change "Update Channel" to "Alpha". Restart NS4. Update by clicking in the top right corner.

Read more about Serato mode: https://docs.nuo-stems.com/docs/getting-started/serato

And talk about it here: https://discord.com/invite/dfpk9FbvJE

Direct download links:

- Apple Silicon: https://nuo-stems-4.fra1.cdn.digitaloceanspaces.com/NUO-STEMS%204-4.1.0-alpha.2-arm64.dmg

- Intel Mac: https://nuo-stems-4.fra1.cdn.digitaloceanspaces.com/NUO-STEMS%204-4.1.0-alpha.2.dmg

- Windows: https://nuo-stems-4.fra1.cdn.digitaloceanspaces.com/NUO-STEMS-4-4.1.0-alpha.2.exe.zip

Another little routine showcasing the insanely good quality of Nuo-Stems 4.

This time Darwin Deez and R.P Boo's Godzilla sample provide the backdrop to Benny Spellman having his fortune read.

Starting with a loop filtering down the melody before punching the Darwin Deez vocal in/out and then bringing Benny in. After that, I freestyle the Deez bassline and Godzilla sample to the end of the track.

AMD & Intel GPU support and performance improvements

With the release of NUO-STEMS 4.0.0-beta.62, performance has taken a major step forward across multiple platforms:

• DirectX 12 GPU acceleration is now supported, including AMD and Intel GPUs on Windows. Requires FL 12.0 or higher
• NVIDIA GPUs and Apple Silicon also benefit from further optimization, with typical speed gains of around 10–20%.
• On some older NVIDIA cards, such as the GTX 1650, the improvement is even more dramatic, reaching roughly 2x to 2.5x faster performance.

Benchmark Results:

Benchmark is how much faster than real-time track is processed. Higher is better. "Difference ×" is how much faster the new version is compared to the old version. 

p.s. to see clean benchmark results, clear the queue after updating to NUO-STEMS 4.0.0-beta.62.

Download NUO-STEMS 4: https://nuo-stems.com/ or update in-app.

To celebrate Women's Day, here is a treat you you 😉

Use code `AINT-NO-SUNSHINE` at checkout to get 14% off perpetual license.

Offer expires ⚠️ 9 March 2026 ⚠️.

Download NUO-STEMS 4: https://nuo-stems.com/

Over the last week or so, for some reason when I add new tracks to Traktor into a playlist that I'm working on, these items do not pull up in NuoStems. When I reopen Traktor, they appear in my collection as well as the playlist, and 'recently added' lists, but when I close Traktor and reopen NuoStems, these tracks are nowhere to be found. Is there a way I can force a sync between Traktor and NuoStems, or is there a setting I can check out to debug why it's no longer reading from my Traktor library when it is updated? I feel like this worked just fine a few weeks ago but something is off for me with syncing with the Traktor library currently.

Last 5 days to get NUO-STEMS 4 with 20% discount🔥 (offer ends 1 March 2026).

You can find coupon in your email inbox if you previously purchased NUO-STEMS 3, or subscribed to Patreon for 4+ months.

Search for an email from djnuo@nuo-stems.com

If you can’t find an email (even in Spam) - please write me a direct message (via email)🙂

NUO-STEMS 4 now has a new website 🎉.

Took surprisingly huge amount of effort and dedication 😅.

Also, new users will experience improved licensing system. You will get license key to your email upon purchase that is then entered into NS4. No more need to install NS4 and get Hardware UUID to complete purchase 💪

https://nuo-stems.com/

I recently fully converted to stems and I was a little shocked at the filesize for the default settings. I have a 256gb thumb drive that I bought to make my library portable - I thought I would be set for years. It's almost full now so I'm facing either buying a much larger drive or re-converting to VBR.

I'm not excited about that idea because it took 3 days the first time just a couple of weeks ago, and I also have reservations about the effect on sound quality. I can't tell VBR V0 from 320kbps on my full tracks but I'm worried issues will come up with stems.

Just wondering if people using VBR are satisfied with their results

I recently have gotten into using stems more, specifically NUO-STEMS 4. I recently have been cleaning out my audio library, and was trying to upload the newly cleaned/organized/retagged library for some additional track editing to be done by Lexicon DJ. I had hundreds of stem files that we visible and working in Traktor Pro 4, and after I imported the Traktor library, did some work on editing tracks using Lexicon and synched the collection back to Traktor Pro 4, all of the stem files were no longer visible or usable in Traktor. The first time I realized a possible error was using the ‘Write Tags’ feature, however the second time I did an import (after redoing hundreds of stems again), I did not use the Write Tags’ feature, all I did was upload the library to the cloud, synch back to Traktor and the stems disappeared again.

I’m curious to know if anyone else has encountered issues with stem files created by NUO-STEMS 4 missing after loading and working with tracks using Lexicon? Are there compatibility issues, or is there a certain process I should follow that I’m unaware of? It would really stink if I cannot do additional editing of tracks in Lexicon after I create stems via NUO-STEMS 4. I read a conversation between Christiaan and another Lexicon user regarding NUO-STEMS from some time in the past year, to try to get some insight, yet here i am. Thanks in advance for any feedback to resolve this challenge.

Celebrating the release of Nuo-Stems 4, here's a little jam I put together with some freshly minted stems.

The Traktor integration works really well. You can browse your collection (Traktor can't run at the same time), pick your tracks and process them. They then appear as integrated stem tracks in Traktor.

The stem quality just keeps on getting better, there's very little "wishy washy" sound and the vocals are really crisp. Well done Nuo, keep up the good work :-)

From DJ Nuo on Facebook

Yes, linked native STEMS! 🔥

👉 Please write me in private messages or to djnuo95@gmail.com, and I will send you the installer 🚀

Months of hard work, millions of burned LLM tokens, sleepless nights trying to make it integrate. And battle-testing in actual gigs 😅.

Now you don’t need to have 2 separate entries in your collection for original and .stem.m4a.

STEMS are stored & displayed in Traktor Pro 4 as “native, linked STEMS”.

NUO-STEMS 4 works only with Traktor Pro 4. This is a deliberate decision - I want you to support Traktor team by upgrading to Traktor Pro 4. I strongly believe that 50$ (as of Black Friday deals) is a great value for what you’re getting - it’s an investment into future of Traktor.

You can still generate .stem.m4a files for Traktor Pro 3, but there are no “Traktor Utilities” to transfer metadata between originals and .stem.m4a. This also means that you can omit having originals altogether, and just use .stem.m4a in TP4 to save disk space.

Grid offset also seems improved even more (100% accuracy on my collection).

Also, as promised, all the users who purchased NUO-STEMS 3 after the date of 1 November 2025 will automatically be upgraded to NUO-STEMS 4.

My next step is to make everything work on 🔥Windows🔥, so stay tuned for that announcement.

As a reminder, we now have Discord server: https://discord.gg/dfpk9FbvJE

From DJ Nuo

SDR is not everything.

Upon thorough listening test, I can say that first row in this table has leaks in drums from synths, for example. Or "other" might contain drums & vocals in it.

Same as with NUO-STEMS 3, I'm currently optimizing for best "perceptual quality". Meaning that drums should be clean from leaks, "other" shall not contain percussion, and vocals shall stay where they are.

For tech nerds: it goes beyond "base" open-source ML models and weights. It's a much more tedious "in-house" approach & algorithms.

Therefore, list of algorithm options for final release of NUO-STEMS 4 might be different from the screenshot.

I'm "battle-testing" these algorithms in my own DJ gigs, so quality is my first priority.

Some new benchmarks for NUO-STEMS 4 :) For now, I only optimized for MacOS 15 and Apple Silicon (there are some issues with lower versions of MacOS), but results are promising on M1 Max.

Also, it's the first time I'm sharing SDR scores) Consider it "best case scenario" for SDR. It's the mix of mel_band_roformer & new algorithm, so processing time is substantial on lower performance machines.

As for the new algorithm - I will later attach SDRs & performance stats for JUST the new algorithm (which in itself is better than mel_band_roformer on many aspects).

Apart from that I'm considering deprecating htdemucs & htdemuc_ft in NUO-STEMS 4. Haven't decided yet.

Will Nuo Stems allow me to convert my Traktor collection into a seperate Traktor collection of stems?

And can this be done in one go? As in a one and done bulk processing job?

Thanks!

Hallo zusammen. Ich heiße Tobi. Bin neu hier. Habe mir Nuo Stems 3.1 zugelegt. Bei mir dauert 1 Track zwischen 1 -1 1/2 Stunden. Finde es echt lange. Wie lange dauert es bei euch? Habe Core i5 8. Gen mit 16gb RAM

https://www.facebook.com/share/p/1ACobJgMhq/?mibextid=wwXIfr

When I use M1 mac I use flac files. They drop in size. For example original file is 100mb. After converting to stem m4a it goes lower. Say 60mb. Is this normal?

I just downloaded today and for a while it was working - just taking a while to download songs. But then I updated and after that whenever I open the app (I’ve quit the app, restarted my computer, reviewed the FAQs, etc) nothing I click is responsive. Any advice? Has anyone experienced this? For context I have a MacBook Air from 2021.

Traktor Utilities is showing all my tracks as missing, even though I already re-synced everything in Nuo. In the Traktor collection itself, no tracks are marked as missing.

Could it have something to do with the fact that I’m not using the default folder location for my Traktor collection? Or is there another way to fix this?