RuntimeError: ""

Traceback Error: "

If you have these two lines without any text at the beginning of the error log as above using AMD GPU on every attempt of separation with GPU Conversion option turned on in UVR, for all archs and models

- You probably use outdated GPU drivers and/or older Windows/build not compatible with newer drivers:

>Go to Ultimate Vocal Remover\torch_directml and replace DirectML.dll from C:\Windows\System32\AMD\ANR (make a backup before).

>Use this older 1.9.1.0 version of the library. Restart UVR after replacing the file!
If you use other incompatible library version, you’ll encounter the “Unhandled exception” startup issue. The same fix might work on Intel GPUs.
Be aware that the linked older version of the library might potentially cause additional noise for MDX-Net v2 models like HQ_X, or it might come from GPU with errors in stress tests in OCCT (the issue is gone when you turn off GPU Conversion).

 

The same Runtime Error: “” also happens on Mac Pro 2009, at least on some older UVR versions. If updating UVR won't help, turn off GPU Conversion. Your Mac might be too old.

 

Theoretically all DX12 GPUs should be compatible with DirectML, but min. VRAM working with Roformers with low chunk_sizes on this backend is rather 4GB, and older NVIDIA GPUs than Maxwell might fail to switch to DirectML at least on 5.6.1 (in 5.6.0 and older, the option might be called OpenCL, and was probably deleted in later Roformer patches).

 

- All MDX-Net v2 models (maybe beside 4 stem variants), have so called MDX noise, which can be cancelled by using Options>Advanced MDX-Net Settings>Denoise Output>Standard (or Model). Just with older directml.dll it's more noisy, and dedicated models don't work so efficiently with this more elevated noise.

 

- At least beta #2 Roformer update caused some stability and performance issues with other archs than Roformers for some people when specific parameters started to take more time than before.

Roll back to stable 5.6 (non-5.6.1) in these cases if necessary (but you won't have Roformers support). Possibly make a copy of the old installation. Your configuration files might be lost. You can use two installations at the same time (or at least when one, e.g. Roformer patch is installed or symlinked in the default location).

 

- (I think I covered that issue above more thoroughly)

Roformer models in at least patch #2 work only in “Multi-Stem” mode in UVR. Using them in Ensemble causes layers errors (you can use manual Ensemble instead).
Iirc, it’s caused by yaml config where instead of Instrumental + Vocals (with V as capital letter) there’s written other + vocals, and you need to change it. Iirc it doesn’t happen on models downloaded from Download Center as Anjok was fixing the issue, but the problem might still exist in yamls of some custom models outside the center

 

- If you have sudden issues with not being able to separate esp. on Macs, try to reinstall the app, and/or on at least Windows, possibly make sure you didn’t turn on some power saving option in your laptop. Plus, you can simply try to reopen UVR (few fail tries on incompatible DirectML.dll with your GPU driver/OS will hang UVR on “Loading Model” till you close UVR manually from Task Manager).

 

- When using e.g. BS-Roformer SW: “RuntimeError: "The size of tensor a (2) must match the size of tensor b (6) at non-singleton dimension 0"

Traceback Error: "”
> Replace the yaml config manually in:

C:\Users[User]\AppData\Local\Programs\Ultimate Vocal Remover\models\MDX_Net_Models\model_data\mdx_c_configs

Restart UVR, start over. Make sure you were asked to replace it. If not, the yaml was maybe wrongly picked anyway. Then edit in the Edit config menu.

_______

 

You’ll find more UVR troubleshooting in this section

_____

 

Problems fixed in newer patches

- (deprecated since patch #10 - now convert dim_t it to chunk_size) dim_t = 1101 seems to be a sweet spot in terms of speed/SDR according to measurements (although on 1 minute files); use 1120 if UVR refuses to accept 1101 in GUI (or edit yaml file)

 

- (deprecated since patch #10) Some Roformer configs have wrong dim_t at the bottom of the yaml by default (e.g. 256), change it at the bottom of the yaml config for better SDR (not the one at the top), e.g. to 1101 (more explanations on it later).

 

- (fixed in patch #10) VIP code in Roformer beta patch #2-9 (and probably #1) doesn’t work -

Download all the VIP models you need before patching older 5.6 to beta Roformer or use two installations of the UVR if you can’t use patch #10 with the fix.

 

- (fixed in patch #6) People experience All stems error with viperx’ 12xx models in newer versions of UVR Beta Roformer patch (patch #2 was the last confirmed to work with these older models)

 

- (fixed in patch #10) mlp_expansion_factor: 1 or (when mlp line is deleted from yaml) mismatch for MelBand Roformer error
You probably use older Roformer patch incompatible with newer models (e.g. #2)

It also appears when you wrongly set v2 model type.