-
-
Notifications
You must be signed in to change notification settings - Fork 729
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
feat: send pipeline to device with Pipeline.to(device) #1204
Conversation
…annote-audio into feat/send_pipeline_to_device
Codecov ReportBase: 29.91% // Head: 29.75% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #1204 +/- ##
===========================================
- Coverage 29.91% 29.75% -0.17%
===========================================
Files 62 62
Lines 3817 3872 +55
===========================================
+ Hits 1142 1152 +10
- Misses 2675 2720 +45
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@hbredin When I run the speaker diarization pipeline on latest I suspect this piece of code in
When I change |
Good catch. Would you make a PR? |
Sure, Will do. |
Would you mind telling how do I call This is my code:
and am getting this error:
|
Install |
Thanks, it works now! |
Hey, for me its not working when using pip install https://github.com/pyannote/pyannote-audio/archive/refs/heads/develop.zip |
I'm running Mac M1 and think I've installed the develop branch by running Does this mean it should automatically use the gpu/mps or do I have to manually set with The diarization step is still taking longer than I would have expected it to. Though the audio file is 1.5 hours long... |
It will run on CPU by default. |
Took me a while to notice this post. Nothing would work until I manually add pipeline.to(device) to my code. Is there any reason why it doesn't use the GPU by default (as written in the README) since CPU would be extremely slow nonetheless ? Maybe i'm stupid, but I lost hours waiting the process to complete while it would took 300x less with my GPU. Tried multiple torch install, etc. |
Im having the same issue. The pipeline is running on the CPU by default. |
Fixes #1108 #1095 #1155 #1059 #1187