-
Notifications
You must be signed in to change notification settings - Fork 223
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
Using lhotse cut simple
to merge unsorted recordings.jsonl.gz
and supervisions.jsonl.gz
causes segment fault
#925
Comments
Seems like this happens because Lhotse doesn't support |
Yes, a warning would be useful.. Would you mind creating a PR with it?
What tokens do you mean? The manifests have |
Yes, I’ll look into that for a PR. And for the second question, the In the segments file, each item follows the following format: |
Hmm I didn’t know segments can have -1. A support for that would need to be added in load Kaldi data dir. can you also add this? Thanks! |
I think |
Hi all, I have the similar situation. I have imported kaldi data folder into {recordings, supervisions, features}.jsonl.gz with After decomposing I added features.jsonl.gz to make CutSet once again. Without --force-eager I have an exception like this: Could you please provide a minimal lhotse recipe on how to prepare CutSet in settings like my? |
@kfmn you can use |
I used --frame-shift (same as -f) option, so it doesn't solve my issue |
In that case, can you use |
Update this issue with a pull request.
#952
<#952 (comment)>
On Mon, 16 Jan 2023 at 22:17 Piotr Żelasko ***@***.***> wrote:
In that case, can you use lhotse cut simple with all three of recordings,
supervisions, and features? Then trim-to-supervisions will correctly trim
the features as well.
—
Reply to this email directly, view it on GitHub
<#925 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOON42HKV5NRQF2VU5ZGUY3WSVKBHANCNFSM6AAAAAAS4HFQYE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Best Regards
|
Closing via #952. |
Adding the
--force-eager
option circumvents the issue, but maybe throwing a warning would be better.Best
Jin
The text was updated successfully, but these errors were encountered: