Is this code being used into the pyannote-audio >= 2.1 ?

[nikifori]

Based on this paper may I assume that versions of pyannote-audio >= 2.1 are using the diart methodology?

For example, if I run this code, will it be executed in an online manner?

    pipeline = Pipeline.from_pretrained("pyannote/speaker-diarization-3.1")
    pipeline.to(device)

    # Apply the pipeline to the audio file
    diarization = pipeline(
        audio_path,
        num_speakers=8,
    )

Thanks

[juanmc2005]

Hi @nikifori ! diart leverages pyannote.audio models, but pyannote.audio does not provide online inference in their pipelines.

[ywangwxd]

Based on this paper may I assume that versions of pyannote-audio >= 2.1 are using the diart methodology?

For example, if I run this code, will it be executed in an online manner?

    pipeline = Pipeline.from_pretrained("pyannote/speaker-diarization-3.1")
    pipeline.to(device)

    # Apply the pipeline to the audio file
    diarization = pipeline(
        audio_path,
        num_speakers=8,
    )

Thanks

I have upgraded some depended packages to the latest version successfully based on feat/diart-asr branch:

pyannote.audio 3.3.2
pyannote.core 5.0.0
pyannote.database 5.1.0
pyannote.metrics 3.2.1
pyannote.pipeline 3.0.1
pytorch-lightning 2.4.0
pytorch-metric-learning 2.8.1
torch 2.5.1
torch-audiomentations 0.11.1
torch_pitch_shift 1.2.5
torchaudio 2.5.1
torchmetrics 0.11.4
torchvision 0.20.1

So yes, you can do it. It shouldn't be difficult to do so, just fix any issue you encounterted. I have done this because I usually hate restriction to lower package version.

[juanmc2005]

@ywangwxd would you mind opening a PR with the updated dependencies? I've been meaning to do this for some time.

[ywangwxd]

@ywangwxd would you mind opening a PR with the updated dependencies? I've been meaning to do this for some time.

Hi Juanmc2005,

For some reason, it is not convenient for me to commit any code onto github.com. So I have just attached two files which I have made changes. I reproduced it again before this. The whole process is smooth, I did not see any conflicts. There is no need to change any code. But if you or anyone else do find any conflicts, please let me know, I will try to solve it. I have been working on integrating faster-whisper into feat/diart-asr branch and I have completed that. All my work is based on this config, so there should not be any big issue.

requirements.txt
setup.txt

There are two warning messages, but I have ignored them.

Model was trained with pyannote.audio 0.0.1, yours is 3.3.2. Bad things might happen unless you revert pyannote.audio to 0.x.
Model was trained with torch 1.10.0+cu102, yours is 2.5.1+cu124. Bad things might happen unless you revert torch to 1.x.

Btw, I am using Python=3.10.16 on Linux.

Please do not forget to rename setup.txt to setup.cfg.