Skip to content
This repository has been archived by the owner on Apr 28, 2021. It is now read-only.

Add support for RTTM files #3

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Conversation

nryant
Copy link

@nryant nryant commented Mar 9, 2019

Adds support for reading speaker diarization stored in NIST RTTM files.

Adds support for reading speaker diarization stored in NIST RTTM files.
@hbredin
Copy link
Member

hbredin commented Mar 11, 2019

Thanks @nryant !

Can you please let me know what you would use this RTTM parser for?

I am asking because I am not happy with this whole pyannote-parser library and plan to get rid of this dependency in all other pyannote-xxx projects in the future.

Is this for pyannote-metrics to support RTTM files?
I have the (secret) plan to make it the default (and only supported) format by pyannote-metrics anyway.

@nryant
Copy link
Author

nryant commented Mar 11, 2019

Hi @hbredin ,

Yes, the intent was to support RTTM files for use with pyannote-metrics. I've actually been sitting on the code since last year and finally got around to committing it. But, if you're already planning to integrate RTTM parsing directly into pyannote-metrics, that makes perfect sense.

hbredin added a commit to pyannote/pyannote-metrics that referenced this pull request Mar 12, 2019
- setup: remove pyannote.parser requirement
- setup: switch to pyannote.database 1.6
- doc: update documentation

Deprecates pyannote/DEPRECATED-pyannote-parser#3
@hbredin
Copy link
Member

hbredin commented Mar 12, 2019

Just pushed pyannote/pyannote-metrics@7c6126f that does just that.

May I ask you to check if that suits your needs?
It is in the develop branch of pyannote-metrics for now but will be part of next release.

It relies on the new pyannote.database 1.6 that adds support for RTTM-based custom protocol that you might also find convenient.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants