FFT processing on gen~ slicer patch (Oopsy Field)
I'm fairly new to gen~ and oopsy~ and have been following the documentation and example patchers.
I am experimenting a little bit with FFT on this slicer patch and it seems to be working to some extent on my max patch. The problem arises when I push the code onto Daisy Field, the output is vastly different to compared to the Max msp. It seems like the Field is bypassing the external fft conversion and just behaving as the slicer example should. Could this possibly be because of the signal chain? Or the Oopsy cannot push FFT information? Spectroscope on the gen~ is also working fine. Attached screenshot. Any help would be greatly appreciated. Thank you so much!
EDIT: Also, wanted to mention that I have been following this older forum post: https://cycling74.com/forums/fft-inside-gen (a lot of it going over my head). Since I've been trying to implement a basic fft conversion outside of gen~, I haven't had any issues in max msp. Was happy with the result and just wanted to push this onto my Field and hear the same effect.......
Only the gen~ code is compiled and uploaded to Daisy hardware. That's just how it works.
Yes exactly as @HZ37 says, only the code inside the gen~ patcher is exported to the Daisy hardware. There is currently no way to export FFT transforms to the Daisy.
If you feel very handy with C++ it might be possible to modify the code in Oopsy and insert FFT transforms on the input and output audio processing.
I see. Not the most comfortable with C++ but I'll give it a shot. This means that I would be importing the FFT code to gen~ from C++ and then pushing it to daisy?
thanks for your time!!