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

LibWeb/WebAudio: Define and partially implement AnalyserNode #1430

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

noahmbright
Copy link
Contributor

https://webaudio.github.io/web-audio-api/#AnalyserNode

Most of the interface is naively implemented. Container types probably need adjusted (Vector is used for all the processing). A Fourier Transform is needed, but that's waiting on either a 3rd party library or a complex number type.

There are lots of simple miscellaneous filters that need to be applied. It could be reasonable to implement from scratch, supposing that it can be parallelized. It might be hard to find one library with everything. Not my call though.

Some additional scaffolding around blocks and render quanta is probably needed before this is developed much further, which probably comes in at the level of the AudioNode.

@AtkinsSJ
Copy link
Member

Test failure is because the all-window-properties.html test needs rebaselining. In general it's a good idea to run the test suite locally to check if any tests are broken. (Meta/ladybird.sh test)

https://webaudio.github.io/web-audio-api/#AnalyserNode

Most of the interface is naively implemented. Container types
probably need adjusted (Vector<double> is used for all the processing).
A Fourier Transform is needed, but that's waiting on either a 3rd
party library or a complex number type.

There are lots of simple miscellaneous filters that need to be applied.
It could be reasonable to implement from scratch, supposing that
it can be parallelized. It might be hard to find one library with
everything. Not my call though.

Some additional scaffolding around blocks and render quanta is
probably needed before this is developed much further, which
probably comes in at the level of the AudioNode.
@noahmbright
Copy link
Contributor Author

Test failure is because the all-window-properties.html test needs rebaselining. In general it's a good idea to run the test suite locally to check if any tests are broken. (Meta/ladybird.sh test)

Lesson learned. Thanks a lot. This was way more helpful than an indirect memory leak message

@AtkinsSJ
Copy link
Member

The memory leak message is unrelated, but it does make it hard to find the actual test-failure message. 😅

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

Successfully merging this pull request may close these issues.

2 participants