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

:onnxruntime:, session_state.cc:1169 onnxruntime::VerifyEachNodeIsAssignedToAnEp] Some nodes were not assigned to the preferred execution

Open
#2,299 3 comments 0 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

while running inference coming across this error .

2024-09-11 11:17:28 | INFO | infer.modules.vc.modules | Get sid: guanguanV1.pth
2024-09-11 11:17:28 | INFO | infer.modules.vc.modules | Loading: assets/weights/guanguanV1.pth
2024-09-11 11:17:28 | INFO | infer.modules.vc.modules | Select index: logs\guanguanV1.index
2024-09-11 11:17:55 | INFO | infer.modules.vc.pipeline | Loading rmvpe model,assets/rmvpe/rmvpe.pt
2024-09-11 11:17:56.0223850 [W:onnxruntime:, session_state.cc:1169 onnxruntime::VerifyEachNodeIsAssignedToAnEp] Some nodes were not assigned to the preferred execution providers which may or may not have an negative impact on performance. e.g. ORT explicitly assigns shape related ops to CPU to improve perf.
2024-09-11 11:17:56.0261045 [W:onnxruntime:, session_state.cc:1171 onnxruntime::VerifyEachNodeIsAssignedToAnEp] Rerunning with verbose output on a non-minimal build will show node assignments.

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 reproducing inference with assets/weights/guanguanV1.pth and assets/rmvpe/rmvpe.pt, then inspect infer.modules.vc.modules and infer.modules.vc.pipeline around model loading. Determine whether the ONNX Runtime warning causes incorrect results or only affects execution-provider placement; done means documenting the cause and resolving it or confirming expected behavior.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.