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

AttributeError: 'NoneType' object has no attribute 'dtype'

Open
#2,134 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
38.4k
Forks
5.3k
PR merge metrics
No merged PRs in 30d

Description

2024-06-16 20:55:29 | WARNING | infer.modules.vc.modules | Traceback (most recent call last):
File "C:\RVC\RVC1006Nvidia\infer\modules\vc\modules.py", line 185, in vc_single
audio_opt = self.pipeline.pipeline(
File "C:\RVC\RVC1006Nvidia\infer\modules\vc\pipeline.py", line 410, in pipeline
self.vc(
File "C:\RVC\RVC1006Nvidia\infer\modules\vc\pipeline.py", line 235, in vc
score, ix = index.search(npy, k=8)
File "C:\RVC\RVC1006Nvidia\runtime\lib\site-packages\faiss_init_.py", line 341, in replacement_search
assert d == self.d
AssertionError

Traceback (most recent call last):
File "C:\RVC\RVC1006Nvidia\runtime\lib\site-packages\gradio\routes.py", line 321, in run_predict
output = await app.blocks.process_api(
File "C:\RVC\RVC1006Nvidia\runtime\lib\site-packages\gradio\blocks.py", line 1007, in process_api
data = self.postprocess_data(fn_index, result["prediction"], state)
File "C:\RVC\RVC1006Nvidia\runtime\lib\site-packages\gradio\blocks.py", line 953, in postprocess_data
prediction_value = block.postprocess(prediction_value)
File "C:\RVC\RVC1006Nvidia\runtime\lib\site-packages\gradio\components.py", line 2076, in postprocess
processing_utils.audio_to_file(sample_rate, data, file.name)
File "C:\RVC\RVC1006Nvidia\runtime\lib\site-packages\gradio\processing_utils.py", line 206, in audio_to_file
data = convert_to_16_bit_wav(data)
File "C:\RVC\RVC1006Nvidia\runtime\lib\site-packages\gradio\processing_utils.py", line 219, in convert_to_16_bit_wav
if data.dtype in [np.float64, np.float32, np.float16]:
AttributeError: 'NoneType' object has no attribute 'dtype'

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing infer/modules/vc/modules.py:185 into infer/modules/vc/pipeline.py:235 and the index.search call at pipeline.py:410, then reproduce the reported inference failure. Compare the FAISS dimension assertion with the later Gradio NoneType error; done means the original failure is diagnosed and inference has a verified, user-visible outcome.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.