Cool_Tools/ultimatevocalremovergui
1
0
Fork 0
mirror of https://github.com/Anjok07/ultimatevocalremovergui.git synced 2024-12-01 02:27:21 +01:00
Code Issues Packages Projects Releases Wiki Activity
2fd50e11f8
ultimatevocalremovergui/README.md
Anjok07 88d48c3d0e
Update README.md
2021-06-01 18:05:02 -05:00

13 KiB
Raw Blame History

Ultimate Vocal Remover v5 Command Line Beta

About

This application is a heavily modified version of the vocal remover AI created and posted by GitHub user tsurumeso. You can find tsurumeso's original command line version here. The official v5 GUI is still under developement and will be released some time in Q3 2021.

  • Special Thanks
    • tsurumeso - The engineer who authored the AI code. Thank you for the hard work and dedication you put into the AI code UVR is built on!
    • aufr33 - Model collaborator and fellow UVR developer. This project wouldn't be what it is without your help, thank you for your continued support!
    • DilanBoskan - The main GUI code contributor. Thank you for helping bring the GUI to life! Your hard work and continued support is greatly appreciated.

Installation

Install Required Applications & Packages

Please run the requirements command even if you have v4 installed!

pip install --no-cache-dir -r requirements.txt
pip install torch==1.8.1+cu111 torchvision==0.9.1+cu111 torchaudio===0.8.1 -f https://download.pytorch.org/whl/torch_stable.html

FFmpeg

FFmpeg must be installed and configured in order for the application to be able to process any track that isn't a .wav file. Instructions for installing FFmpeg can be found on YouTube, WikiHow, Reddit, GitHub, and many other sources around the web.

  • Note: If you are experiencing any errors when attempting to process any media files that are not in the .wav format, please ensure FFmpeg is installed & configured correctly.

Running Inferences & Model Details

Each model requires specific parameters to run smoothly. Those parameters are intricately defined within the JSON files provided. Please make sure the correct JSON files are selected when running inferences!

Option Guide

Please note, this version is based on vocal-remover 4.0.0 of tsurumeso's original code. Significant improvements and changes were made. Those changes include the following -

  • New format of spectrograms. Instead of a single spectrogram with a fixed FFT size, combined spectrograms are now used. This version combines several different types of spectrograms within specific frequency ranges. This approach allowed for a clearer view of the high frequencies and good resolutions at low frequencies, thus allowing for more targeted vocal removals.
  • The arguments --sr, --n_fft, --hop_length are removed. JSON files are now used instead.
  • The following new features were added
    • --high_end_process - This argument restores the high frequencies of the instrumental (but not the vocals). It is intended for models with a narrow bandwidth, 16 kHz and below. The 5 choices for this argument are:
      • none - No processing (default)
      • bypass - This copies the missing frequencies from the input.
      • correlation - This also copies missing frequencies from the input, however, the magnitude of the copied frequency will depend on the magnitude of the generated instrumental's high frequencies. It will be removed in the final release.
      • mirroring - This algorithm is more advanced than correlation. It uses the high frequencies from the input and mirrored instrumental's frequencies.
      • mirroring2 - This version of mirroring is optimized for better performance.
    • --aggressiveness - This argument allows you to set how strong the vocal removal will be. The range is 0.0-1.0 The higher the value, the more the vocals will be removed. Please note, the highest value can result in muddy sounding instrumentals depending on the track being converted, so this isn't always recommended. The default is 0.1. For the vocal model specifically, the recommended value is 0.5-0.6.
    • --deepextraction - This argument generates an additional instrumental output with deep artifact vocal removal. This option is experimental and is more suited for acoustic or other light types of tracks with stubborn vocals. Many others might sound bad.

Models Included

All of the models included in the release were trained on large datasets containing diverse sets of music genres. These are all beta models that may or may not make it into the final release. We are working to have even better models in the final release of v5! You can download the model pack here

Please Note: These models are not compatible with the v4 GUI! The GUI for v5 is still under development.

Here's a list of the models included within the v5 beta package -

  • V5 Beta Models
    • 2band_32000 Models
      • MGM-v5-2Band-32000-BETA1.pth - This model does very well on lower frequencies. Frequency cut-off is 16000 Hz. Must be used with 2band_32000.json file!
      • MGM-v5-2Band-32000-BETA2.pth - This model does very well on lower frequencies. Frequency cut-off is 16000 Hz. Must be used with 2band_32000.json file!
      • MGM-v5-KAROKEE-32000-BETA1.pth - Model by aufr33. This model focuses on removing main vocals only, leaving the BV vocals mostly intact. Frequency cut-off is 16000 Hz. Must be used with 2band_32000.json file!
      • MGM-v5-KAROKEE-32000-BETA2-AGR.pth - Model by aufr33. This model focuses a bit more on removing vocals from lower frequencies.Frequency cut-off is 16000 Hz. Must be used with 2band_32000.json file!
      • MGM-v5-Vocal_2Band-32000-BETA1.pth - This is a model that provides cleaner vocal stems! Frequency cut-off is 16000 Hz. Must be used with 2band_32000.json file!
      • MGM-v5-Vocal_2Band-32000-BETA2.pth - This is a model that provides cleaner vocal stems! Frequency cut-off is 16000 Hz. Must be used with 2band_32000.json file!
    • 3band_44100 Models
      • MGM-v5-3Band-44100-BETA.pth - This model does well removing vocals within the mid-rang frequencies. Frequency cut-off is 18000 Hz. Must be used with 3band_44100.json file!
    • 3band_44100_mid Models
      • MGM-v5-MIDSIDE-44100-BETA1.pth - This model does well removing vocals within the mid-range frequencies. Frequency cut-off is 18000 Hz. Must be used with 3band_44100_mid.json file!
      • MGM-v5-MIDSIDE-44100-BETA2.pth - This model does well removing vocals within the mid-range frequencies. Frequency cut-off is 18000 Hz. Must be used with 3band_44100_mid.json file!
    • 4band_44100
      • MGM-v5-4Band-44100-BETA1.pth - This model does very well on lower-mid range frequencies. Frequency cut-off is 20000 Hz. Must be used with 4band_44100.json file!
      • MGM-v5-4Band-44100-BETA2.pth - This model does very well on lower-mid range frequencies. Frequency cut-off is 20000 Hz. Must be used with 4band_44100.json file!
      • HighPrecison_4band_1.pth - This is a higher performance model uses a different architecture. Frequency cut-off is 20000 Hz. Must be used with 4band_44100.json file! Please include '-n 123821KB' within the inference command to run this model!
      • HighPrecison_4band_2.pth - This is a higher performance model uses a different architecture. Frequency cut-off is 20000 Hz. Must be used with 4band_44100.json file! Please include '-n 123821KB' within the inference command to run this model!
      • NewLayer_4band_1.pth - This model uses a different architecture. Frequency cut-off is 20000 Hz. Must be used with 4band_44100.json file! Please include '-n 129605KB' within the inference command to run this model!
      • NewLayer_4band_2.pth - This model uses a different architecture. Frequency cut-off is 20000 Hz. Must be used with 4band_44100.json file! Please include '-n 129605KB' within the inference command to run this model!
      • NewLayer_4band_3.pth - This model uses a different architecture. Frequency cut-off is 20000 Hz. Must be used with 4band_44100.json file! Please include '-n 129605KB' within the inference command to run this model!
    • 2band_44100_lofi
      • LOFI_2band-1_33966KB.pth - This model uses a different architecture. Frequency cut-off is 14000 Hz. Must be used with 2band_44100_lofi.json file! Please include '-n 33966KB' within the inference command to run this model!
      • LOFI_2band-2_33966KB.pth - This model uses a different architecture. Frequency cut-off is 14000 Hz. Must be used with 2band_44100_lofi.json file! Please include '-n 33966KB' within the inference command to run this model!

Inference Command Structure

The following example shows how to run a model from the "2band_32000 Models" section above.

python inference.py -g 0 -m modelparams/2band_32000.json -P models/MGM-v5-2Band-32000-BETA1.pth -i "INPUT"

The following examples show how to run the ensemble model scripts -

python ensemble_inference.py -g 0 -i "INPUT"

Or if you wish to save all individual outputs generated in addition to the final ensembled outputs, please run the following -

python ensemble_inference.py -g 0 -s -i "INPUT"

By default, 14 models will be ensembled. However, you can also specify the models you wish to ensemble. For the ensemble_inference script specifically, do not input the ".pth" extension within the command, only the name. Here is an example -

python ensemble_inference.py -g 0 -P "MODELNAME1" "MODELNAME2" "MODELNAME3" -i "INPUT"
  • Please Note the Following:
    • Do not specify the model parameters or architectures for the ensemble inference script. Those details are already fixed.
    • When ensembling models with low and high bandwidth conversions, '--bypass' is highly recommended.
    • The ensembled outputs generated through the ensemble scripts can be found in the "ensembled" folder.

Ensembler

The stand alone ensembler has the ability to take 2 or more instrumental or vocal outputs generated by different models and combine the best results from all of them! Here is how to use it manually -

  • For instrumental outputs, run the following command:
python lib/spec_utils.py -a min_mag -m modelparams/1band_sr44100_hl512.json "INPUT1" "INPUT2" -o "CHOOSEFILENAME"
  • For vocal outputs, run the following command:
python lib/spec_utils.py -a max_mag -m modelparams/1band_sr44100_hl512.json "INPUT1" "INPUT2" -o "CHOOSEFILENAME"

To automate the ensembling process, please use the 'Ensemble-Outputs.bat' script reference below.

Windows Batch Files

We included the following Windows batch files to help automate commands:

  • Drag-n-Drop-CHOOSE-YOUR-MODEL.bat

    • Simply drag the audio file you wish to convert into the 'Drag-n-Drop-CHOOSE-YOUR-MODEL.bat' file provided.
    • From there you will be asked if you want TTA enabled, then prompted to type the letter associated with the model you wish to run and hit "enter".
    • Once you hit enter, you will be asked fs you want an additional "deep extraction" instrumental output in addition to the 2 to be provided.

  • Ensemble-Outputs.bat

    • Simply drag the instrumental or vocal outputs you wish to ensemble into the batch script.
    • From there you will be asked if the outputs are instrumental or not.
    • Once you hit enter, the script will take a moment to ensemble the outputs.
    • The ensembled outputs can be found in the "ensembled" folder.

Troubleshooting

Common Issues

  • This application is not compatible with 32-bit versions of Python. Please make sure your version of Python is 64-bit.
  • If FFmpeg is not installed, the application will throw an error if the user attempts to convert a non-WAV file.

Issue Reporting

Please be as detailed as possible when posting a new issue. Make sure to provide any error outputs and/or screenshots/gif's to give us a clearer understanding of the issue you are experiencing.

If you are unable to run conversions under any circumstances and all other resources have been exhausted, please do the following -

  1. Copy and paste the error output shown in the cmd prompt to the issues center on the GitHub repository.

License

The Ultimate Vocal Remover GUI code is MIT-licensed.

  • PLEASE NOTE: For all third party application developers who wish to use our models, please honor the MIT-license by providing credit to UVR and it's developers Anjok07, aufr33, & tsurumeso.

Contributing

  • For anyone interested in the ongoing development of Ultimate Vocal Remover please send us a pull request and we will review it. This project is 100% open-source and free for anyone to use and/or modify as they wish.
  • We only maintain the development and support for Ultimate Vocal Remover and the models provided.

References