Wavelet transform UI
- Dominant language
- C++
- Stars
- 18.4k
- Forks
- 2.7k
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 78
Description
Ongoing PR https://github.com/audacity/audacity/pull/10142 from external contributor [Klaus Gram-Hansen](https://github.com/kgramhans) does the backend work of computing, caching and painting a wavelet version of the spectrogram. This is most of the work.
To make this available to the user, some design work is needed so that the spectrogram settings accommodate this particular transform. Some of the "normal" spectrogram parameters become irrelevant, and new ones are needed.
Then this UI modification of the dialog would have to be implemented and wired to the backend. This might be a bit more difficult than it sounds due to the different layouts of the global and per-track setting dialogs, but still not difficult.
Additional work, to make these new parameters persistent, would be needed in `SpectrogramConfiguration`. I do not expect this to be difficult at all.
I will ask Klaus to provide a list of the parameters that would be obsolete and of the new parameters needed.
Contributor guide
Research direction
Start by reviewing PR #10142 for the wavelet backend, then inspect the global and per-track spectrogram settings dialogs and SpectrogramConfiguration. The issue still awaits a parameter list from Klaus, so clarify which existing options are obsolete and which new ones are needed. Done means the dialogs expose and persist the wavelet settings and are wired to the backend.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- audio-video-rtc, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100