Waveform #22
Merged
Waveform #22
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@icalvin102 this is a great idea and fantastic implementation, thank you so much for contributing! The next version of the library containing the new functionality will be distributed in the next day or so, the corresponding online documentation for the Processing website will probably be added to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I was wondering why there is no way to get the audiowaveform from the processing-sound library,
as I think it is a very essential part of audiovisualisaton.
The FFT and JSynFFT classes already used the audiobuffer to perfrom the FFT so I wrote a analyzer
based on the code of those two classes.
The example at examples/Analysis/AudioWaveform show explains the how to use the waveform in processing.