New squelch implementation based on maximum filter#7
Open
cborss wants to merge 4 commits into
Open
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
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.
This pull request contains the following changes to the frontend:
The "SQ" button no longer enables/disables the squelch but sets it slightly above the current noise floor. This reproduces the behavior of the OpenWebRX squelch button, that I really like.
I replaced the first order auto-regressive smoothing filter by a short maximum (rank order) filter, that results in constant opening/closing times of the squelch. In the current implementation, the exponential smoothing results in longer closing times with longer noise tails for stronger stations. Since I prefer a shorter closing time that is independent from the signal level, I simply use the maximum value of the last N power values.