RVC-Project/Retrieval-based-Voice-Conversion-WebUI

error when the realtimegui starts up

Open

#342 opened on May 23, 2023

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Python (2,849 forks)batch import
bughelp wanted

Repository metrics

Stars
 (18,427 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

2023-05-24 07:44:09 | INFO | faiss.loader | Loading faiss with AVX2 support. 2023-05-24 07:44:09 | INFO | faiss.loader | Could not load library with AVX2 support due to: ModuleNotFoundError("No module named 'faiss.swigfaiss_avx2'") 2023-05-24 07:44:09 | INFO | faiss.loader | Loading faiss. 2023-05-24 07:44:09 | INFO | faiss.loader | Successfully loaded faiss. Use Language: zh_CN Traceback (most recent call last): File "C:\Users*\Downloads\RVC-beta\gui.py", line 570, in gui = GUI() File "C:\Users*\Downloads\RVC-beta\gui.py", line 205, in init self.launcher() File "C:\Users*\Downloads\RVC-beta\gui.py", line 209, in launcher input_devices, output_devices, _, _ = self.get_devices() File "C:\Users*\Downloads\RVC-beta\gui.py", line 526, in get_devices devices = sd.query_devices() File "C:\Users*\Downloads\RVC-beta\runtime\lib\site-packages\sounddevice.py", line 564, in query_devices return DeviceList(query_devices(i) File "C:\Users*\Downloads\RVC-beta\runtime\lib\site-packages\sounddevice.py", line 564, in return DeviceList(query_devices(i) File "C:\Users******\Downloads\RVC-beta\runtime\lib\site-packages\sounddevice.py", line 578, in query_devices name = name_bytes.decode('utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc2 in position 6: invalid continuation byte

Contributor guide

Research direction
Investigate the UnicodeDecodeError in sounddevice's query devices. The error occurs when a device name cannot be decoded as UTF 8. Research possible fixes: use 'ignore' or 'replace' error handling in the decode call, or wrap the query in a try except. Check if sounddevice library has an option for encoding handling.
Tech stack
python
Domain
None
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70