mirror of
https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI.git
synced 2026-11-05 00:27:30 +00:00
[GH-ISSUE #984] After converting audio twice in a row, the second output has a much deeper pitch? #642
Labels
No labels
AMD/Intel
bug
bug
bug
colab
dependencies
documentation
duplicate
enhancement
following up
good first issue
help wanted
invalid
question
stale
stale
stale
todo list
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
RVC-Project/Retrieval-based-Voice-Conversion-WebUI#642
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @moolzebub on GitHub (Aug 12, 2023).
Original GitHub issue: https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI/issues/984
I have NO CLUE how to approach explaining this issue, but it's consistently happening.
I do the regular steps towards converting audio and it goes without a hitch the first time! Then I convert the same audio file cause I changed some settings, but the result is much deeper and noticeably slower than the previous.
I found a way to temporarily stop it from doing this: just unloading the voice. Okay, fine, I can deal with unloading it everytime... but when it comes to batch conversion it's annoying!
The first audio generated is fine.
Then the next generation, no different settings, no unloading.
@ben-mkiv commented on GitHub (Aug 13, 2023):
also happens in the opposite direction, with female voices the pitch increases.
maybe the pitch algorithm result doesn't get purged correctly?!
same issue: https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI/issues/885
@JarodMica commented on GitHub (Aug 14, 2023):
The issue occurs when resampling the audio. If you leave it at 0, this does not occur, though, it's definitely a bug. It's been in RVC since I've been using it back for a few months now, though, I don't notice much of a difference between audio at 48k vs 0 so I just leave it there.
@RVC-Boss commented on GitHub (Aug 16, 2023):
Fixed now.
github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI@deb756bf1b