-
-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when calling local model,(speaker-diarization-3.0) #1508
Comments
Thank you for your issue. Feel free to close this issue if you found an answer in the FAQ. If your issue is a feature request, please read this first and update your request accordingly, if needed. If your issue is a bug report, please provide a minimum reproducible example as a link to a self-contained Google Colab notebook containing everthing needed to reproduce the bug:
Providing an MRE will increase your chance of getting an answer from the community (either maintainers or other power users). Companies relying on
|
Same issue being faced here. There exists another thread (#1410) where someone seems to have found a way around it but it's not straightforward. The method you followed here seems like it should work as it follows the directions in the tutorial for VAD (https://github.com/pyannote/pyannote-audio/blob/develop/tutorials/applying_a_pipeline.ipynb). |
Renaming |
thanks for your reply. @ColtonBehannon .. |
@hbredin thanks ,after changing the model name according to the method you mentioned, the program can run normally. Thank you very much. |
FYI: #1537 |
Latest version no longer relies on ONNX runtime. |
When I execute the following code I get an error message。
from pyannote.audio import Pipeline
pipeline = Pipeline.from_pretrained("./models/config.yaml")
send pipeline to GPU (when available)
import torch
pipeline.to(torch.device("cuda"))
apply pretrained pipeline
diarization = pipeline("test.wav")
I have downloaded the required model and saved it locally for calling. The specific directory is as follows. When running, an error is reported. The config.yaml is as follows.
The text was updated successfully, but these errors were encountered: