RNBO~ FFT Plugin Function Windows Missing
Thestral Sound
May 15 2023 | 7:55 pm
Hello folks,
I've made an FFT based plugin in rnbo~ that uses a hanning window, but the hanning function disappears when I export to vst3 and try it use it in my DAW. There is an option to load a function into the plugin for use, but the problem is that I have no idea what file type it is expecting, or where to even find such a file which contains a hanning function in the first place.
Any help solving this would be much appreciated.
- Roman ThileniusMay 15 2023 | 10:04 pmno idea about RNBO here, but i would not trust samples for windowing functions, it seems better to always calculate the function live.hanning is nothing more but a cosine (i.e. the first half of it), that´s what you use by default for FFT, granular delays, frequency shifters and many more tasks.
- Alex NormanMay 16 2023 | 2:10 pmI'm confused by "the hanning function disappears when I export", how does it 'disappear'?RNBO has the [hann] object that you can use to compute the window. If you want to load buffers in a vst, you can load any of the audio file formats that JUCE supports as of Juce 7.0.3. There is an option when you export, if you're using the cloud compiler, to "Package Sample Dependencies" as well. In this case, if you use a buffer like: [buffer foo @file blah.wav], and max can find and load 'blah.wav', you should get that file data automatically loaded in your VST, if you've selected that option.
- Thestral SoundMay 17 2023 | 10:46 amWhat I meant by it disappearing was that once the patch was exported it seemed as though the vst no longer knew where to find the hanning function. This has been disproven by myself while reviewing the patch and finding a mistake I'd made. It essentially was applying the hanning window, but then outputting the version of the signal that was not yet windowed.
