@griffinboy yeah that was also my initial assessment.
administrators
Posts
-
RE: Global Cables Don't Work when compiled
-
RE: 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...
-
RE: Is it possible to create a midi note from ScriptNode/c++ node and direct it to a synth in the module tree?
I decided they aren't for anything fast anyway due to the copying involved.
Ah now I understand you, that advice is when you send complex data over a global cable, but the default operational mode of just sending a single numeric value is fast and realtime capable.
-
RE: Is it possible to create a midi note from ScriptNode/c++ node and direct it to a synth in the module tree?
Wait, we can do synchronous global cables?
How fast will this be? We aren't talking sample accurate audio thread type fast are we?
Sure:
-
RE: Global Cables Don't Work when compiled
Is there a way to pick up event data callbacks (event data reader node) directly inside of a c++ node?
Yes:
// instantiate this as a class member and forward those callbacks to it: // -prepare() // -reset() // -handleHiseEvent() scriptnode::routing::event_data_reader<NV> obj; // somewhere where you want to check if there is a new event data value: double mv; if(obj.getWrappedObject().handleModulation(mv)) { // there's a change in the event data // do something here... }
}
-
RE: Global Cables Don't Work when compiled
@Orvillain said in Global Cables Don't Work when compiled:
when I compile a plugin, does that automatically compile networks, or only if the network has the allowCompilation flag enabled?
It does not compile any networks automatically - we've been over this a few times and there is literally no solution that won't mess up any workflow.
If you're writing C++ nodes, you shouldn't touch any scriptnode network at all but directly add it into the hardcoded FX modules, this way you have no overhead & the best development experience.
-
RE: Getting the sample rate for an externalData object?
@Christoph-Hart haha, My Funky summary, lol that autogenerator has gone crazy...
-
RE: Getting the sample rate for an externalData object?
@Orvillain
data.sampleRate
should be populated with the file samplerate if the audio buffer comes from an external file. -
RE: Is it possible to create a midi note from ScriptNode/c++ node and direct it to a synth in the module tree?
@Orvillain yeah there's currently not a real line of communication for MIDI messages back from scriptnode, but you're pretty good on track with the global cable approach - just analyse the audio in the C++ node and send it back to HISE via a global cable, then attach a synchronous script callback there that will add an HiseEvent to the MIDI queue with
Synth.playNote()
et al.