We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Seems that utterance_id is used in elpis/engines/common/output/ctm_to_elan.py whereas it should be recording_id.
utterance_id
elpis/engines/common/output/ctm_to_elan.py
recording_id
Segment_id is being used for what is actually the utterance id.
Segment_id
Segment file is made of <utterance-id> <recording-id> <segment-begin> <segment-end>
<utterance-id> <recording-id> <segment-begin> <segment-end>
Also, check the ctm_to_textgrid file.
ctm_to_textgrid
The text was updated successfully, but these errors were encountered:
This Issue could safely be closed, couldn't it? Now that HF is used & not Kaldi any longer. 🍃 🍂
Sorry, something went wrong.
No branches or pull requests
Seems that
utterance_id
is used inelpis/engines/common/output/ctm_to_elan.py
whereas it should berecording_id
.Segment_id
is being used for what is actually the utterance id.Segment file is made of
<utterance-id> <recording-id> <segment-begin> <segment-end>
Also, check the
ctm_to_textgrid
file.The text was updated successfully, but these errors were encountered: