open-unmix-pytorch VS free-music-demixer

In my first post, quite a lot of alternatives were discussed: https://news.ycombinator.com/item?id=36707877

The model I'm using is called Open-Unmix (https://github.com/sigsep/open-unmix-pytorch). In 2021, there was an update to Open-Unmix to include new weights, UMX-L, which made it perform better than it used to on the older weights (UMXHQ).

In the grand landscape of music demixing, I don't think UMX-L is near the top anymore.

_However_, the demixing performance of freemusicdemixer.com is very close to the full PyTorch performance of Open-Unmix UMX-L, despite the tricks I needed to get it working in the browser, such as splitting up the inference to operate on segments of the song, or making the LSTM operate on streaming segments rather than holding the entire track in the LSTM memory.

In my first release, I loaded and did inference on the entire track at once (like the PyTorch model), which frequently crashed or exceeded the 4GB WASM memory for medium or large-size tracks.

* Post-processing step (bigger impact)

I tried to tackle the post-processing step in my C++ code (which would win ~1 dB in quality across all targets) but it's too tricky for now [2]. Maybe some other day.

1: https://github.com/sevagh/free-music-demixer/blob/main/examp...

2: https://github.com/sigsep/open-unmix-pytorch/blob/master/ope...

Or open-unmix. I've found it performs better than spleeter in some of my tests.

There's maybe something useful for you here?

https://github.com/facebookresearch/demucs

https://github.com/sigsep/open-unmix-pytorch

https://github.com/bytedance/music_source_separation

https://github.com/deezer/spleeter

OpenUnmix ( is a neural network solution from Yuki Mitsufuji and Stefan Uhlich, music industry luminaries that work in Sony's core divisions.

Hi HN,

Over the Christmas break I added multi-threading to the WASM Demucs module in freemusicdemixer

Demucs (v4 hybrid transformer) is a much higher quality model than the previous default, but it ran very slowly when limited to one worker: ~17 minutes for an average 4-minute song

I have since implemented multi-threading with WebWorkers.

If you raise the "MAX MEMORY" setting to 16 GB or 32 GB, your track will demix within 7-5 minutes, producing state-of-the-art results.

There is also support for the Demucs 6-source model which adds piano and guitar stems.

Please reach out and be loud about any bugs or UX issues you encounter!: https://github.com/sevagh/free-music-demixer/issues

* Post-processing step (bigger impact)

I tried to tackle the post-processing step in my C++ code (which would win ~1 dB in quality across all targets) but it's too tricky for now [2]. Maybe some other day.

1: https://github.com/sevagh/free-music-demixer/blob/main/examp...

2: https://github.com/sigsep/open-unmix-pytorch/blob/master/ope...