#RVC Mac Help!

1 messages · Page 1 of 1 (latest)

median nimbus
#

Hello, I've been trying to get either RVC Mainline, RVC_CLI, and Applio, but to no avail. I am on Mac M1. I keep getting errors for RVC_CLI and Applio about huggingface hubert ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1007). And for RVC Mainline, it doesn't seem to be for Mac as it's run by a bat file. I'd appreciate the help in setting something up to be able to run RVC models. Thanks

chrome stratus
#

try appending os.environ['CURL_CA_BUNDLE'] = '' to the app.py file in it's code. (Hope you know where to put it 😅)

median nimbus
median nimbus
chrome stratus
#

Retrieval-based-Voice-Conversion-WebUI

#

There's no proper mac releases (no fat .zip like there is for windows), but the repo does contain a run.sh file that installs everything

#

and bugs out if python 3.11+ is the default, or if it can't compile c++ code due to missing xtools

median nimbus
#

this one? ^

median nimbus
median nimbus
# chrome stratus *Oh*

so im trying the webui one rn just to check, and got error when installing requirements.txt

#
  Downloading orjson-3.10.0.tar.gz (4.9 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.9/4.9 MB 49.3 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error
  
  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]
      
      Cargo, the Rust package manager, is not installed or is not on PATH.
      This package requires Rust and Cargo to compile extensions. Install it through
      the system's package manager or via https://rustup.rs/
      
      Checking for Rust toolchain....
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.