tonality analysis
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.3k
- Forks
- 808
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
FFT for calculating tonality in analysis.c file.
for (i=0;i<N2;i++)
{
//Why assign real number(audio sampled points) to image parts for FFT?
float w = analysis_window[i];
in[i].r = (kiss_fft_scalar)(w*tonal->inmem[i]);
in[i].i = (kiss_fft_scalar)(w*tonal->inmem[N2+i]);
in[N-i-1].r = (kiss_fft_scalar)(w*tonal->inmem[N-i-1]);
in[N-i-1].i = (kiss_fft_scalar)(w*tonal->inmem[N+N2-i-1]);
}
and then:
opus_fft(kfft, in, out, tonal->arch);
tonal->inmem is 10ms smoothed input float point audio data(Total length is 30ms). So Why assign real number(audio sampled points) to image parts for FFT? and what does FFT out spectrum mean? could some one help?
Thanks!
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
Start in analysis.c at the input preparation loop and the opus_fft(kfft, in, out, tonal->arch) call. Trace the surrounding tonality-analysis code and any existing FFT documentation or tests to establish what the real and imaginary inputs represent and how the output spectrum is used. Done means documenting those points clearly, including the rationale for the assignments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100