Mid device post 2
-
I have a standalone app I’m creating whose main functions are to act as a udp server for communicating an ip broadcast and getting the ip address of a mixed reality app I am writing running on the network in a oculus headset. It also creates some osc endpoints as well as creating a virtual midi device on the system(Mac only). I have this all written and working in a standalone JUCE app. My question is if I were to port this over to HISE(is it even possible) where would I put my custom c++. I have a header file and cpp for the udp functions. I can probably do all I need to do in a 3rd party script node I just need access to that udp stuff. The reasoning for all this is I am ok with JUCE and c++ but i am clueless about creating a ui in my c++ code and would rather use HISE to do it.
-
Could I put the header and cpp file under src/ in 3rd party folder and just reference from my third party node code?
-
@jdurnil Yes that should work. Be aware of the lifetime of the class that wraps the third party node - it will be created and destroyed when you select the node in the hardcoded master fx drop down.
Another option would be writing a custom C++ UI component with an external floating tile, but then it would exist if the plugin interface is open which might not be what you're after.
hise_tutorial/ExternalFloatingTileTest at master · christophhart/hise_tutorial
The Tutorial project for HISE. Contribute to christophhart/hise_tutorial development by creating an account on GitHub.
GitHub (github.com)
I haven't compiled this in a while, let me know if it's broken :)
-
@Christoph-Hart thank you for your response. So we are talking lifecycle when creating in HISE or lifecycle when the compiled instance is running, wouldn’t it maintain existence so it could continue running process(). I’m very new and I don’t understand the need for hardcoded fx. I’m running this compiled in a regular script fx dsp network. Should I not be doing that?
-
@jdurnil If you need to run in in a network to modulate other nodes or combine it in a more complex signal chain you can do so, but the hardcoded FX removes the overhead of the script FX module if you just want to run your third party node.
-
I actually want to run it inside a dsp network linked with other available nodes in HISE
