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

Use the WebAudio API for more of the heavy lifting #1

Open
veltman opened this issue Jul 21, 2016 · 1 comment
Open

Use the WebAudio API for more of the heavy lifting #1

veltman opened this issue Jul 21, 2016 · 1 comment

Comments

@veltman
Copy link
Contributor

veltman commented Jul 21, 2016

The earliest Audiogram prototype used the WebAudio API to get the waveform data, and we still use it for the summary version in the editor. But we ran into a lot of inconsistencies with decoding and duration detection. If we can get that working properly, we would reduce the server-side complexity and be able to drop the libgroove and node-waveform dependencies.

@veltman
Copy link
Contributor Author

veltman commented Jul 28, 2016

Anecdotally, libgroove dependencies seem to the sticking point for a lot of local installations. It would be great to ditch them.

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

No branches or pull requests

1 participant