scaler interpolation, reduced table size
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 86
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
much as i sort of hate the idea,
might want to use lin. interpolation in param scalers instead of full 4096k tables, because flash space is getting crammed.
it might be better to have more space for op nodes / presets, at the cost of e.g. less nicely tuned frequencies.
there is also computation cost of interpolation but worth checking into asf/dsp methods.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the param scalers and their full 4096k tables, then review the relevant DSP methods to compare interpolation's flash savings, computation cost, and frequency tuning impact. Done means establishing whether the tradeoff is acceptable and defining the resulting scaler behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100