Older news
Continues here (reaching GDoc limit here already, probably more content from above will be gradually moved to this separate GDoc later)
General reading advice
- If you found this document elsewhere (e.g. as PDF), here is always up-to-date version of the doc (www version hosted by Bas Curtiz is synced like every 15 minutes at this point, but it has some quirks in formatting vs GDoc)
- If you have anything to add to this doc, ping me @deton24 on our Discord server from the footer, but rather refrain from PMing directly if not necessary. Every time you request writing privileges via GDoc, God kills a cat. Don't click “ask for privileges”!
- You can use the (the outdated) Table of content section, but better go to Options and show “Document outline” to see an up-to-date clickable table of content (almost the same is in the SW version). If you don't have Google Docs installed, and you opened the doc in a mobile browser and no Table of content option appear, use the old Table of content or go to options of the mobile browser and run the site in PC mode to show document outline (but it's better to have Google Docs installed on your phone instead, as it’s more convenient in use).
- When you click from elsewhere on a GDoc link with “heading” string in the URL redirecting to a specific section, it should show the first page, and redirect after a few seconds
- Once you load the document and reach the document outline, redirection to any entry might not work at the very beginning till all the pages will be loaded. It takes some time. Tap a few times.
- Sometimes you cannot scroll down the list of headings on the phone in PC mode. Then you need to tap on the scroll bar in the very left, but it might suddenly look buggy all highlighted, but working nevertheless.
- Downloaded .docx will have a similar document outline as in the GDoc (but more messy - probably still with all the headers used in the GDoc). If you have an error on an attempt of opening the .docx file on Windows, go to RBM>Properties and check Unlock below Attributes.
- Even on a powerful phone with lots of RAM, GDoc app can occasionally crash, esp. while clicking on a specific section before the doc is fully loaded. Even deleting the app and reopening won’t help for occasional crashes. The document became too big to handle properly by Google apps (both mobile app and online).
- Be aware that the document can hang for a while on the attempt of accessing a specific section of the document - it doesn't happen often on a PC browser - PC browser is probably the most stable form of reading the doc online. At least on a decent PC (so not C2Q, but even a decade old i7 is usually fine). But it can be stable on Android phones too (e.g. Snapdragon 700 series instead of old 400 series). Google’s app support for old 32-bit ROMs in e.g. Android 9 and older is terrible and probably even deprecated at this point.
- Search and navigating through the document outline works faster when you download the doc as .pdf or .docx, but in the latter you’ll have access to the document outline on the left like in GDoc (if not, press CTRL+F>Headings, or check View>Navigation window).
- When visiting the online version of this doc, you can paste whole phrase when searching instead of single letters to avoid severe stuttering during using search function online.
- Use the search bar in Google Documents, not the one from the browser - the browser’s search won’t find everything unless all the pages were shown before - the doc is huge.
- Sometimes if you search for a specific keyword in the mobile app and the result doesn't show up, you need to go to the document outline, and open its last section and search again (so the whole document will be loaded first, otherwise you won't get all the search results in some cases). But it might happen mostly if you use the wrong search function.
- Make sure you've joined our Discord server to open some of the Discord links attached below (those without any file extension at the end).
But I think now it might be no longer necessary.
- Downloading links from Discord with file extensions at the end no longer work, but I reuploaded most of the important links already. If you need to download from previously shared Discord links which are now offline due to the Discord changes anyway:
1) Join our Discord server via invitation at the top of the document 2) Delete file name from the link 3) Open our Discord server in the browser 4) Leave everything in the link before the first slash and delete the rest (so channels\xxxx\ 5) paste two identifiers divided by slashes afterwards, but without file name (so channels\xxxx\xxxx\xxxx - where the last two are taken from inactive file link) *) If you paste offline link in any channel on the source server, the link will work again
- If you have a crash on opening the doc in the app, e.g. on Android - reset the app cache and data. Keep the app updates or find some old version (e.g. even from period when your phone was released or uninstall all updates if it's GDoc is your stock app
- If it loads 4 minutes/infinitely in the doc app, update your Google Docs app and reset the app cache/data, e.g. if you started to have crashes after the app update.
- You can share a specific section of this document by opening it on PC or on a mobile browser set in PC mode by clicking on one of the sections in the document outline (or hyperlinks leading to specific sections). Now it will add a reference to the section in the link in your address bar, which you can copy and paste, so opening this link will redirect someone straight to the section after opening the link (in some specific cases, some people won’t be redirected, but in fact, you only need to wait a few seconds after the first page of the doc has been shown, and then the proper redirect starts).
Some headers not referred to in the outline are also set in a way that when you click them, the address bar will change with a link leading to that specific section. Not all headers present in the doc are shown in the outline to preserve better readability.
- In the GDoc app sometimes you need to tap “wait” a few times when the app freezes. Afterwards, searching will start working all the time (at least till the next time). The doc is huge and the GDoc app on at least low-end Androids is cursed (desktop version on PC behaves the most stable, as long as decent phones). You've been warned.
- If you feel overwhelmed by the doc size, theoretically you can load the doc into Google Gemini or Google NotebookLM and ask questions from there, but I encourage befriending with the document outline and the content of the interesting section yourself - asking the AI chat for the best models leads to hallucinating of the LLM and providing list of outdated separation models from this doc. Also, they all miserably fail with generating model and config links from even cut fragments of the GDoc. They also cannot edit the document directly (unless you paste the text, but it will rather delete all the formatting and hyperlinks which are essential to the task), maybe Office 365 with paid subscription is capable of editing docs with AI directly already.
- Descriptions on the list of models are usually shortened compared to the news section information added when the model was released. You can use search with the model name for more possible descriptions.
- Published audio demos of models pasted from MVSEP get online after a while, so most links to audio files from there will be offline after a week or more.
- Without GDoc app installed, or when in not PC mode of the browser, if you you open links to this document ending with e.g. “#heading=h.hk34hc4d1ah7” or similar, you won't be redirected to a specific section of this document referred to in the heading. Redirections from such links don't work in the mobile version of the GDoc site.
To be redirected after a moment to proper section from outside links with “heading” in the URL, you should open these links with GDoc app installed, or on PC browser, or mobile browser with PC Mode turned on (in Chrome that option appears when you open a page already).
- (fixed in April) In February 2026 it started to happen that Chrome on Windows was closing after opening the document. It helped to reopen it a few times, maybe along with uninstalling offline GDoc extension and maybe after going to chrome://settings/content/all?sort=data-stored > Google > docs.google.com (I just did all of these). The issue was recurring even when you just disabled the extension (it was able to re-enable itself).
- If you click on any hotlink redirecting to a specific part of this document from the mobile version of GDoc in the browser, you won't be able to show options to display the document outline after switching your browser into PC mode - it will remain in the mobile layout. It's because redirections in mobile versions have their own linking scheme adding to the site address - you need to delete its ending or reopen the doc.
- If loading bar stutters suddenly very much on opening the GDoc in the app, most likely it will crash after a longer time, so then just reopen the doc - once your OS freezes/closes the app due to inactivity, task switching, or esp. the phone I sleep mode, reopening the app will fail in many cases (but sometimes it will redirect you to the last place you read)
- Links to the models outside the instrumental and vocal and 4-6 stems sections are no longer provided (they’re duplicates of models appearing in sections before - search the document for the model name or reach those sections)
- Besides me, jarredou (Discord: rigo2), dca100fb8 (both since 23 May 25) and isling (since 12 Feb 26), currently no one else has writing privileges to this document, although they were reluctant to be active editors, and were granted the privileges as the last resort for possible cases of my longer absence in the future.
- If you're an editor, there's a rare bug in the GDocs app when sometimes instead of the editing button, you will only see the doc title appearing at the bottom. Then you need to clear the app cache and start over (but it will require reopening the doc a few times till it becomes stable - on the first opening it will stutter a lot, then crash the app quietly and then it might start working more or less correctly unless you see stuttery loading bar - then it might crash again or stutter till you reopen the app). Sometimes saving might take a while, but most of the time it's instant, and visible for everyone in real-time even when you write (sometimes breaking the saving by clicking the edit button might cause massive stutters again). I reported most, if not all of those issues in the app feedback feature in options, but they're mostly deaf and never write back, releasing app updates which sometimes break more than fix, forcing reinstalling the app and collecting cache again. Most of this document was written using the GDocs app on mobile. This document constantly closes to the GDoc’s single document character limit. Last time, I was forced to move old news to the separation notes GDoc, literally everything below the UVR beta Roformer release linked at the top, and in the future, probably gradually news above it will be moved too when necessary (previously AI-killing tracks and Training were moved into one separate doc too). If you reach the GDoc character limit, sometimes you might still be able to write from the GDocs app, but not on PC, to reach the character limit later in the GDocs too. On PC, you can write only once, then the doc is locked from further editing till the reload of the doc. Maybe even pasting whole phrases would be possible this way if necessary. It's an artificial limitation. In fact, the doc started to work unstable iirc somewhere when 400-500 pages were in the doc in total.
(I’m trying to actively keep the following list always updated with the Last updates/news section at the top)
Before you read the models list
Everyone asks which service and/or model is the best for instrumentals, vocals or stems. The answer is - we have listed a few models and services which behave the best in most cases, but the truth is - the result also strictly depends on the genre, specific song, and how aggressive and heavily processed vocals it has, or how much distortion instruments have, style of mixing, etc. Sometimes one specific album gets the best results with one specific tool/AI/model, but there might be some exceptions for specific songs, so just feel free to experiment with each model, to get the best result possible using various ones, ensembles and services/AIs from those listed. SDR on MVSEP in the multisong dataset doesn't always reflect bleeding well. That’s why we introduced bleedless and fullness metrics for evaluation of the models as well. Although they’re not perfect either. Pay attention to also other metrics featured in MVSEP evaluation results on the site:
“-l1_freq = bleedless (higher is cleaner)
-aura_mrstft = fullness (higher is fuller)” - becruily, “more perceptually relevant than SDR for musical content imo” - gilliaan
You’ll find more precise info about it in this section.
“Some people don't realize that if you want something to sound as clean as possible, you'll have to work for it. Making an instrumental/acapella sounding good takes time and effort. It's not something that can be rushed. Think of it like (...) love to a woman. You wouldn't want to just rush through it, would you? Running your song through different models/algorithms, then manually filtering, EQing, noise/bleed removing the rest is a start. You can't just run a song through one of these models and expect it to immediately sound like this” - rAN
Sometimes you might want to combine results of specific models in specific song fragments.
If the song is too muddy, you might want to use demudder in newer UVR patches and/or use some free AIs like AudioSR, Apollo or other, to further enhance the result.
If you’re still not happy, you might want to manually mix separated song stems and/or master it using plugins or AI mastering services (more about it here).
Sometimes you might be capable of creating a loop out of the fade ins/outs/intros/outros so you could totally refrain from using AI separation in the key fragments of the song, so you could just only use the separation result as a reference to arrange the song as it was, and only fill missing fragments with it, or even use it as reference for Matchering. In order to create it, start with first peak which isn't normalized, mark all remaining audio and normalize it, then go to the next significant peak (usually snare or kick) normalize it, then continue to the end, clip gain of necessary to fix some sudden changes of volume or ducking.
If the fade is linear, you can also use de-fader by Makidanyee to automate the process.
A good starting point is to have a lossless song (the result will be a bit less muddy after separation).
Now, from free separation AIs/models, to get a decent instrumental/vocals, you can use the models below, starting from those at top, which are usually the best in most cases. But be aware that every song might work differently with different models - find the best for your song. Also, various headphones and speakers might be more or less sensitive to show bleeding in your songs - lots of the time it will be imminent without using the phase fixer for most instrumental models, esp. with high fullness metric, in songs with dense mix.
Models placement on the list usually depends on model versatility, opinions of people on our Discord, frequency of use, and metrics (sometimes specific) in comparison to different models. Sometimes it depends on just deliberate or subjective choices depending on the case. Older, outperformed models are usually lower on the list, or moved out from the main section.