-
Notifications
You must be signed in to change notification settings - Fork 10
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
Initialization #2
Comments
@echo66 yes, you can operate with other typed arrays. |
Greetings, @drom ! Thanks for the quick response. 👍 There are several ways, IHMO, to make a "nice" interface for this: a) The transform function should accept one or two arguments (one for forward and two for inverse transform). Optionally, the transform function should check the size of the provided arrays. b) Create a function like "setData" which accepts one or two arguments (one for forward and two for inverse transform). c) And, of course, your proposal. :) I'm suggesting (a) and (b) due to my experience regarding the usage of other FFT libraries. Oh, by the way, awesome work with this library! I'm using it with a Phase Vocoder with Identity Phase Locking. |
Hi @echo66 do you use the library? Are you still interested in changes that you requested? |
I'm still using it with the phase vocoder. :) |
Greetings, @drom !
One question: can I process different data heaps, using the same custom FFT object? Or is each object a "one shot" processor?
The text was updated successfully, but these errors were encountered: