Skip to content
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

The timeline is wrong #1737

Closed
Lixi20 opened this issue Jul 9, 2024 · 2 comments
Closed

The timeline is wrong #1737

Lixi20 opened this issue Jul 9, 2024 · 2 comments
Labels

Comments

@Lixi20
Copy link

Lixi20 commented Jul 9, 2024

Tested versions

pyannote.audio = 3.3.1

System information

ubuntu

Issue description

from pyannote.audio import Pipeline
pipeline = Pipeline.from_pretrained(
"pyannote/speaker-diarization-3.1",
use_auth_token="hf_KkqHxRTGcaXXXXXXXsZvlMCDgAmBuSGCmXE")

import torch
pipeline.to(torch.device("cuda"))

diarization = pipeline("/root/Audio/Test.mp3")

for turn, , speaker in diarization.itertracks(yield_label=True):
print(f"start={turn.start:.1f}s stop={turn.end:.1f}s speaker
{speaker}")

start=0.6s stop=2.2s speaker_SPEAKER_00
start=3.5s stop=4.0s speaker_SPEAKER_00

start=0.6s stop=2.2s -> 00:00:00,600 --> 00:00:02,200
start=3.5s stop=4.0s -> 00:00:03,500 --> 00:00:04,000
The timeline is wrong

The right time is:
00:00:02,600 --> 00:00:04,486
00:00:05,439 --> 00:00:06,013

please help me!!!

@FrenchKrab
Copy link
Contributor

It is not clear where the problem really is, maybe you could fix the formatting...

If you mean the pipeline segments are wrong/misplaced, it might be due to lots of factors that makes it very hard for the pretrained pipeline to perform well out-of-the-box : noisy audio, specific acoustic conditions that were not seen when the model was trained, etc
You might want to finetune the model on the type of data you target (and take a look at the available tutorial notebooks).

Copy link

stale bot commented Jan 9, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 9, 2025
@stale stale bot closed this as completed Feb 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants