File: c6469f79671756ef829720613(...).jpg (238 KB, 1608x2048)

238 KB JPG

>>106998623
Just use RCV Anon

File: saber-3.png (86 KB, 240x240)

86 KB PNG

>>106998682
RVC*

>>106998682
>>106998691
Does that work in real time?

File: 20251005_143939.jpg (118 KB, 689x906)

118 KB JPG

>>106998733
Yes
https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI/blob/main/docs/en/README.en.md

File: 1756687238666966.png (44 KB, 1094x452)

44 KB PNG

>>106998752
let me guess

>>106998752
I just installed Poetry and it's telling me this:

To get started you need Poetry's bin directory (C:\Users\Owner\AppData\Roaming\Python\Scripts) in your `PATH`
environment variable.

You can choose and execute one of the following commands in PowerShell:

A. Append the bin directory to your user environment variable `PATH`:

```
[Environment]::SetEnvironmentVariable("Path", [Environment]::GetEnvironmentVariable("Path", "User") + ";C:\Users\Owner\AppData\Roaming\Python\Scripts", "User")
```

B. Try to append the bin directory to PATH every when you run PowerShell (>=6 recommended):

```
echo 'if (-not (Get-Command poetry -ErrorAction Ignore)) { $env:Path += ";C:\Users\Owner\AppData\Roaming\Python\Scripts" }' | Out-File -Append $PROFILE
```

Alternatively, you can call Poetry explicitly with `C:\Users\Owner\AppData\Roaming\Python\Scripts\poetry`.

What do I do?

>>106998926
Did you try the suggestions? If this is one time thing, the alternative is simple but tedious to write the whole path in each time. Just do A. Having an extra directory on your path will do no harm to your computer. The PATH variable is just a list of directories your computer will look for executables under.

File: poetry install error.png (5 KB, 479x88)

5 KB PNG

>>106998961
I tried A and it wasn't working but now it is. But now when I type poetry install, it gives me pic related as an error.

>>106998996
The directory you are currently in is important. I opened the README and they are skipping some steps.

You have poerty installed so that's step one. Now clone the repo somewhere with git. So you'll need to install git as well. And also be considerate of where you are cloning the project. Somewhere under your user is good. Then use `cd` to enter the new `Retrieval-based-Voice-Conversion-WebUI` directory. Now you can run `poetry install`.

>>106999091
That worked, thanks.

>>106999091
Now I'm getting this

RuntimeError: Cannot install on Python version 3.11.9; only versions >=3.7,<3.11 are supported.

with the full text in pic related.

How is 3.11.9 not >=3.7?

File: full Python error.png (54 KB, 804x728)

54 KB PNG

>>106999478
Forgot pic related

>>106998623
>I'm running a tabletop RPG for a group of 3 nerds and it needs to be a full Las Vegas show with computer-generated special effects
Just talk in a funny voice

>>106998623
Get a Zoom V3, it's basically real-time since it's done in dedicated hardware. All the software solutions have enough delay to be unusable with anything where you can hear your own voice.
Zoom is pretty basic, and it's not going to turn your male voice into "anime girl".

>>106999521
No, I want to use a voice changer.

>>106999567
If it doesn't have actual AI voices (I assume that's what you mean by 'it's not going to turn your male voice into "anime girl"') what advantage does it have over VoiceMod?

>>106999478
It's greater than 3.7 but not strictly less than 3.11. The correct solution is to install pyenv and use that to manage multiple python versions that won't impact your global python (and anything that is dependent on that). You can then have poetry use that with something like `poetry env use` I don't remember the exact way of doing it but you can find it in the poetry docs.

Alternatively you can try modifing the pyproject.toml constraints to have <3.12 instead of 3.11. It's extremely unlikely that this will cause any issue (like essentially no chance it won't run with python 3.11).

Up to you. The first option is much more effort but more correct and would be useful if you intend on using more python projects like this. The second is half-assed and it might interfere with updates via `git pull` in the future but it's trivial to fix that with `git restore pyproject.toml` `git pull` then changing the constraint again

>>106999683
Thank you, but Jesus Christ. Why does it require me to do this shit? Is RVC just badly made?

>>106999702
Python package management is a mess. There’s a lot of tools attempting to fix it as best as possible but they are perfect in the Python project is in the process of creating standards for the new pyproject.toml so it’s more that than this project. They have over constrained python version though. At least I can’t think of any reason to have that upper limit

>>106999963
I tried reinstalling python install manager, python, pip, and poetry, and now I'm getting this error:

PS C:\Users\Owner\RVC\Retrieval-based-Voice-Conversion-WebUI> poetry install
The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.
Installing dependencies from lock file

Package operations: 129 installs, 0 updates, 0 removals

- Installing rpds-py (0.20.0): Failed

PEP517 build of a dependency failed

Backend subprocess exited when trying to invoke build_wheel


Then there's a bunch of text that's too long to paste and I'm not sure which part's relevant.

>>106998623
ywnbaw

>>107001287
Okay the package may be poorly put together. I looked at it again and it has not been updated in a while. In theory that shouldn't matter but it's *possible* updates to poetry (again this is pretty new stuff and still changing a lot) is preventing it frmo building a dated package. My two suggestions would be to first try switching to a tag (i.e. a released version) instead of using main.

git switch 2.2.231006

Then trying poetry install again. If that doesn't work you can try to update the dependencies with

poetry update --lock
poetry install

I don't know why this sort of thing happens

>>107001359
When I tried the first command I got this:
PS C:\Users\Owner\RVC\Retrieval-based-Voice-Conversion-WebUI> git switch 2.2.231006
fatal: a branch is expected, got tag '2.2.231006'
hint: If you want to detach HEAD at the commit, try again with the --detach option.

By the way, how do you include formatted code in your post like that?

>>107001373
My bad. Use `git checkout` instead.

Wrap them in code tags

\[code\]
something like this
\[\code\]

That's probably not going to format right. See /g/'s sticky thread

>>107001430
Well, it got past rpds-py this time, but llvmlite is giving the same error, just with 3.14 now:

RuntimeError: Cannot install on Python version 3.14.0; only versions >=3.7,<3.11 are supported.

In addition to this:

  - Installing numpy (1.23.5): Failed

PEP517 build of a dependency failed

Backend 'setuptools.build_meta:__legacy__' is not available.

Note: This error originates from the build backend, and is likely not a problem with poetry but one of the following issues with numpy (1.23.5)

  - not supporting PEP 517 builds
  - not specifying PEP 517 build requirements correctly
  - the build requirements are incompatible with your operating system or Python version
  - the build requirements are missing system dependencies (eg: compilers, libraries, headers).

You can verify this by running pip wheel --no-cache-dir --use-pep517 "numpy (==1.23.5)".

>>107001430
>>107001491
I uninstalled poetry, uninstalled Python 3.14, and installed Python 3.10 (so it's within the version contraints), reinstalled poetry, and ran

poetry install

. It got much further in the installation, until this error:

Installing the current project: rvc-beta (0.1.0)
Error: The current project could not be installed: No file/folder found for package rvc-beta
If you do not want to install the current project use --no-root.
If you want to use Poetry only for dependency management but not for packaging, you can disable package mode by setting package-mode = false in your pyproject.toml file.
If you did intend to install the current project, you may need to set `packages` in your pyproject.toml file.

>>107001491
>>107001562
Yeah it looks like this has rotted a bit. Numpy updated to 2.0.0 a while ago but it was a real pain to get every up to the next version because everything depends on numpy. So if you want to use numpy 2.0.0 in your project but one dependency has bumped up to 2.0.0 you can't satisfy all the constraints. I guess newer python's no longer support the old build backend used pre 2.0.0.

Dropping to a lower python is the way to go. I looked at the Dockerfile and they are using 3.9. 3.10 may work as well. I got it installed in docker using 3.9. This is my last go because I'm going to sleep:
1. clean up any changes you made
`git restore :/`
2. go back to main
`git checkout main`
3. use the same version of pip they were using
`pip install --upgrade pip==24.0`
4. Install from req file
`pip install -r requirements.txt`
There's a few requirement text files. See the README for which one fits your needs.

>>107001655
I'll try that tomorrow. Thank you.