microsoft / microsoft/GFB-audio-control
Why did you switch back to STFT from CQT?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
This seemed cool: https://arxiv.org/pdf/2210.15228
STFT seems like it would waste compute on frequencies that are perceptually irrelevant. Problem with CQT is most implementations on the internet are not length invariant.
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
Read the linked paper first, then inspect the repository’s current time-frequency representation choice and the rationale for returning to STFT. Determine whether a length-invariant CQT alternative is feasible and document the tradeoffs before proposing any change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100