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

wrong extraction of features #60

Open
chandrahaas02 opened this issue Dec 7, 2021 · 1 comment
Open

wrong extraction of features #60

chandrahaas02 opened this issue Dec 7, 2021 · 1 comment

Comments

@chandrahaas02
Copy link

This paper doesn't make any sence because you are taking average of 13mfcc features which is quite absurd as you it is ridiculous we actually have to mean for all the frames so there should .T at np.mean at feature extraction and from there everything should change your model, accuracy every thing as your function is fundamentally wrong , Hope you change it as this repo is most stared one ,so this lead to miss information for many

@jjostschulte
Copy link

I was also wondering about the feature extraction: In the README, it says that 3 seconds of audio are used, which matches the provided screenshot. But in this screenshot 25 mfcc are used, whereas in the notebook 13 are used with an audio duration of 2.5 seconds. Does anyone know with which features the saved model was trained?

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

2 participants