Use an odd number of taps for PAL/NTSC LPFs #424
Merged
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.
I'd wondered why the LPF view in ld-analyse didn't quite line up with the other two views - it's because the filters had an even number of taps, so FIRFilter can't compensate for the leftover 0.5-sample delay.
Switch from 6 to 7 taps, and add an assert to FIRFilter to catch this in the future.
@simoninns - this might affect the DoD stuff you're working on; 5 taps would also work if you'd prefer that to 7.