You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When auto-diarization is enabled the transcription loaded into pocketbase has a first timestamp of null instead of 0. This causes displayPane to throw an async promise error and keep it from displaying the output. The first speaker is also marked as null but does not seem to throw an error.
Attempt 1 Undiarized
{
"transcription": [
{
"speaker": null,
"text": " All right so I'm",
"timestamps": {
"from": null,
"to": "00:00:01,300"
}
},
{
"speaker": "SPEAKER_02",
"text": " recording this. This is just a test. So just say whatever you want. Anything.",
"timestamps": {
"from": "00:00:01,300",
"to": "00:00:07,000"
}
},
{
"speaker": "SPEAKER_00",
"text": " Okay. Um today's a good day. I hope you probably good day into you.",
"timestamps": {
"from": "00:00:07,000",
"to": "00:00:14,000"
}
},
{
"speaker": "SPEAKER_01",
"text": " Thank you. All right.",
"timestamps": {
"from": "00:00:14,000",
"to": "00:00:15,000"
}
}
]
}
Looking at the rttm generated by pyannote I think I've found where the error is occurring, the first 1.280 seconds has no speaker label. So when loading the rttm and matching against the transcription from whisper it runs into an error and leaves the timestamp and speaker as null.
When auto-diarization is enabled the transcription loaded into pocketbase has a first timestamp of null instead of 0. This causes displayPane to throw an async promise error and keep it from displaying the output. The first speaker is also marked as null but does not seem to throw an error.
Attempt 1 Undiarized
Attempt 1 Diarized
Attempt 2 Undiarized
The text was updated successfully, but these errors were encountered: