Best posts made by jdurnil

@aaronventure I am writing some code now that will demonstrate it, it really is quite simple I’d be happy to share it with you when I’m done.

I find SNEX and scriptnode to be incredibly powerful and flexible tools when worinf in the time domain. However I’m wondering what my options are for spectral processing with just HISE tools. ️ have looked under the hood and there is plenty HISE source code that deals with handling ffts but it doesn’t appear to be at least readily available to do that type of processing inside SNEX. I have the option of rolling my own with a third party node or using FAUST or RNBO. For now I’ve chosen RNBO as it was fairly trivial to do what I wanted to do in there but I’d love to have this inside HISE out of the box. Maybe I’m missing something but it doesn’t appear to be an option.

Hello, I am new to Hise and just learning but I have some specific plugins I want to construct. With Microsoft delivering their Midi 2 implementation in the os later this year and I’m not sure but apple already offers it or soon will. Daw manufacturers will soon follow. Juce has no implementation of Midi 2 but probably will at some point, sooner than later. I know Hise mainly works off of older versions of Juce(I’ve not been able to build Hise projects with the newest Juce(Mac). Will Hise roll its own integration with Midi 2 or will it adjust to the newest Juce releases when Midi 2 is available. Just curious.

I was thinking it could be added to the scripting api in globalroutingmanager

@griffinboy thank you this is extremely helpful!

Hello, I think I found one post referencing this. I am looking to implement a Juce named pipe because I want to have my plugin instances communicate the results of fft analysis block by block n real time. I don’t want a side chain I want interprocess communication. A static object will not work for many reasons the main one being some daws will run instances in different threads so interprocessserver is needed with a named pipe. I am looking into just implementing it in a 3rd party script node but I am brand new to HISE(not brand new to c++ or JUCE) and I don’t know if that’s the best thing to do. I received advice on this and it seems like that is the place to do it. It would be great if this was implemented in HISE as a feature at some point(JUCE named pipe) as some sort of cable or something.