Global Cables Don't Work when compiled
-
@griffinboy said in Global Cables Don't Work when compiled:
I started my own fork of juce to try and get around graphics limitations in Hise (using visage)
Have you found a way to embed a Visage component into a JUCE UI? That's the new UI framework from the Vital guy, right? If that's possible then we could talk about a "HighPerformencePanel" component powered by this framework...
-
oof, yeah that would be really great wouldn't it.
I haven't, but i'll look into it. I may have to pester him about it directly : )
I've been having some silly dependency issues, even getting it work normally. I'm new to cmake and it's not super fun to learn it xDI'll see if I can get that to happen.
-
mmm, the people in the Audio Programmer Discord aren't recommending it XD
It does look like a big amount of pain -
@griffinboy What about the yup framework as an alternative? I imagine the integration to HISE would be somewhat complicated as well.
https://github.com/kunitoki/yup
I have been meaning to get my hands dirty with it but I have only scratched the surface so far.
I definitely like the idea of a High-Performance Panel however, it would let us experiment with more advanced graphics without requiring a complete overhaul of HISE's graphic's framework.
-
@griffinboy yeah that was also my initial assessment.
-
They said it would be better to overhaul using bgfx directly xD
Yeah, not a small task probably. Ah well. -
-
@Christoph-Hart said in Global Cables Don't Work when compiled:
you are correct Global Cables DONT work in compiled scriptnode
...
I think the issue that @griffinboy is having is if you load these networks into another scriptnode network (instead of loading the compiled effect into a hardcoded effect), but that's another problem and (potentially exotic edge case which you can easily work around).
I don't understand why it would be "exotic edge case" here, and how you can work around this... Seems rather a normal workflow to me...
I have a compiled node in a network, that is (I think) busy enough to justify a compilation too...
And then my global cables won't work...What can I do?
-
@Christoph-Hart And aside of this we still have some nodes like
cable_exprthat are requiring the network to be compiled for the plugin to export.I could transform it into a C++ node with another
global_cable, but since it prevents the network to be compilable...This causes quite annoying frictions
-
@ustk can you rearrange your setup so that the global cables are in the outermost network that you compile?
I haven‘t checked / tested the global cable initialisation in C++ nodes to be recursive so it might fail if you try to wrap another node that uses a global cable. Can you check with a simple two level nest test if that‘s the case?
