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

Front-End is quite bad #48

Open
dhdaines opened this issue Dec 8, 2022 · 0 comments
Open

Front-End is quite bad #48

dhdaines opened this issue Dec 8, 2022 · 0 comments

Comments

@dhdaines
Copy link
Contributor

dhdaines commented Dec 8, 2022

First of all because it has a couple of layers of historical cruft around it ... you pass a config_t which then gets "parsed" into a separate parameters structure, which then gets "parsed" into actual parameters.

But more importantly because everything is directed from this top-level configuration, so once you have configured it, it will only give you one particular kind of features. This in particular makes the case where we'd like to do visualization (using power-spectrum, mel-spectrum, or smoothed spectrum) and also recognition (using MFCC) at the same time non-possible.

Also there are like 5 kinds of VTLN, none of which we use, and probably none of which we will ever use.

And finally because the code which does the buffering and windowing is just utter trash (and I should know because I wrote it).

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

1 participant