Currently the constructor takes a window duration in ms, which is nice for the user, but typically would not lead to a well-aligned frame_size (such as 1024 or 2048), which might prevent some optimization in the underlying FFT library.
A solution could be to add a "lower-level" constructor taking the frame_size directly and having the current one calling that other one.
Currently the constructor takes a window duration in ms, which is nice for the user, but typically would not lead to a well-aligned
frame_size
(such as 1024 or 2048), which might prevent some optimization in the underlying FFT library.A solution could be to add a "lower-level" constructor taking the
frame_size
directly and having the current one calling that other one.