Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Questions Regarding Time Resolution & Input Signal Length #5

Open
cwitkowitz opened this issue Aug 3, 2023 · 0 comments
Open

Questions Regarding Time Resolution & Input Signal Length #5

cwitkowitz opened this issue Aug 3, 2023 · 0 comments

Comments

@cwitkowitz
Copy link

Hi @eloimoliner,

Thank you for this implementation of CQ-NSGT. I would like to use it as a drop-in replacement of the more standard CQT implementation, but I am confused on several points:

  • I am having trouble developing an intuition for the precise location in time that each coefficient corresponds to. Is there a way to compute these values? For the standard CQT, this is trivial, since each coefficient corresponds to the dot-product of each basis at user-defined intervals of hop_length. However, I cannot figure out from the CQ-NSGT code how one would go about determining the analogue to this concept, or if one even exists (i.e., does time resolution depend on signal length?). A similar question was raised here, and the advice of simply dividing the input signal length by the number of coefficients was given. But then is there some offset from t=0 for the first coefficient?

  • Given that signal length is a parameter to the CQ-NSGT implementation, I am wondering if anything fundamental changes about the coefficients when the signal length is changed. What exactly depends on the signal length of the input signal, and would coefficients based on one signal length be comparable to coefficients based on another, even if the two signal lengths are very different (e.g., 10 s vs. 100 s)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant