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
[ ] Have you updated to latest MFA version?
I may be two minor versions behind, but I'm 90% sure this bug should be in the current version.
[ ] Have you tried rerunning the command with the --clean flag?
I'm using MFA library functions directly
Describe the issue
Technically, this is a bug with Kaldi. I plan to file a bug with them as well, but I think there is an easy mitigation for Kalpy. When an input audio file is of particular size[1], MFCC and Pitch values produced are of different lengths. When Kalpy attempts to use paste_feats to put the two together, the tolerance of 0 causes an empty array to be generated. When those features are then used, it causes a KaldiFatalError because the input is empty.
The size appears to be any size where (length - 400) % 160 > 156. This is related to the frame size (400) and stride (160) of the feature calculation at 16khz.
Mitigation
I think that setting the second argument of this command to 1 to account for a mismatch in frame length of 1 would avoid the error. I'm sorry that I don't currently have the time to fully test and validate this fix.
For Reproducing your issue
Here's a minimal repro of the issue:
Debugging checklist
[ ] Have you updated to latest MFA version?
I may be two minor versions behind, but I'm 90% sure this bug should be in the current version.
[ ] Have you tried rerunning the command with the
--clean
flag?I'm using MFA library functions directly
Describe the issue
Technically, this is a bug with Kaldi. I plan to file a bug with them as well, but I think there is an easy mitigation for Kalpy. When an input audio file is of particular size[1], MFCC and Pitch values produced are of different lengths. When Kalpy attempts to use
paste_feats
to put the two together, the tolerance of 0 causes an empty array to be generated. When those features are then used, it causes a KaldiFatalError because the input is empty.Mitigation
I think that setting the second argument of this command to 1 to account for a mismatch in frame length of 1 would avoid the error. I'm sorry that I don't currently have the time to fully test and validate this fix.
For Reproducing your issue
Here's a minimal repro of the issue:
Please fill out the following:
This happens for Polish, but not English. I have not triangulated exactly what options trigger this code path.
It's reproducible with a single file.
Wave and text files
Yes. I believe this occurs in acoustic feature computation before the dictionary is relevant, but we're using https://github.com/MontrealCorpusTools/mfa-models/releases/download/dictionary-polish_mfa-v2.0.0a/polish_mfa.dict
Yes, we're using https://github.com/MontrealCorpusTools/mfa-models/releases/download/acoustic-polish_mfa-v2.0.0a/polish_mfa.zip
Log file
Please attach the log file for the run that encountered an error (by default these will be stored in
~/Documents/MFA
).Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: