Skip to content
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

the number of frames in label and acoustic features are different: 1285 vs 1276 (Casting_Correct_0080) #12

Open
rmmal opened this issue May 30, 2018 · 7 comments

Comments

@rmmal
Copy link

rmmal commented May 30, 2018

How could i handle such error when i use magphase with merlin using constant frame rate ??

@rmmal
Copy link
Author

rmmal commented May 30, 2018

The wav has 103120 sample
which by sampling rate 16000 will be 6.445 second
and since frame shift is 0.005

so the wav must have 1289 frame

when i run the feature extractor , the output number of frames become 973 and by interpolation it become 1276 , so how could it be like the exact number of frames of the wav ?

@felipeespic
Copy link
Member

Hi,
Thank you for posting. I have some questions:

  • Which data are you using?
  • Are you using the slt_arctic/s2 recipe?
  • Could you send me the example pair (wav and corresponding lab file), please?

@rmmal
Copy link
Author

rmmal commented Jun 3, 2018

  1. Custom dataset
  2. yes , i am using slt_arctic/s2 recipe
  3. Sure , i will , here it is :
    https://drive.google.com/drive/folders/1nJtKWbufEIUEY93H-zxRMH7uwPr8Psjh?usp=sharing

@rmmal
Copy link
Author

rmmal commented Jun 5, 2018

Also there are some waves that repear produces empty file so it doesn't continue getting features for it , i don't know if it's a bug or what ?

@ZhaoZeqing
Copy link

I also faced this problem. I use the LJSpeech dataset and constant frame rate:

CRITICALListDataProvider: the number of frames in label and acoustic features are different: 1211 vs 1182 (LJ010-0079)

@1271086950
Copy link

Have you solved the problem?I meet it too

@felipeespic
Copy link
Member

I just commited a fixing for the inconsistency of number of frames given by REAPER (ec6ae28). That may solve the problem.

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

No branches or pull requests

4 participants