Menu rework, db scaling according to settings not max signal#4
Open
Menu rework, db scaling according to settings not max signal#4
Conversation
per JO's quip: "Is is a point where you go: hmm, version control is something I should have done more of?"
It picks up notes and keys, but I have a pretty silly mistake decaying the aggregator bin each note each octave, so doing version control then checking that.
…HS-Melbourne/Spectrogram into Teardown-and-rebuild-syn-mode
Version control before building a chord tracker and pivoting to operating on the amplitude of the closest FFT tone, instead of max(bin)
Not so good for microtones. Better for the key determiner
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.