global send / receive

[ccbl]

@aaronventure second question then, will compiling the node as hardcoded FX break the global cables? Or will the work as expected?

[ccbl]

@aaronventure also I can confirm that solved the problem thanks.

[aaronventure]

@ccbl I haven't tried with global cables, but I've seen @Lindon mention them preventing network compilation.

Also, glad to hear the Allow Compilation flag solved your problem. There really should be a safeguard for that. @Christoph-Hart

[Lindon]

@ccbl said in global send / receive:

@aaronventure second question then, will compiling the node as hardcoded FX break the global cables? Or will the work as expected?

so you cant use Global Cables or Global Send/Receive nodes and have the network that uses them compiled - you have to run them "as is" not in HardCoded FX modules...

[ccbl]

@Lindon hmm ok, how much of a performance hit is there, when you don't compile?

[d.healey]

@ccbl It depends on what your network does.

[aaronventure]

@ccbl should be none in the final plugin

[d.healey]

@aaronventure said in global send / receive:

should be none in the final plugin

How'd you figure that?

[aaronventure]

@d-healey I vaguely remember reading somewhere about it. It should be the same whether the network gets converted to C++ on project export or on its own first, no? The only difference is some nodes, like SNEX and Faust, require in-HISE compilation first, and if you have a really hungry network, then you can get the CPU usage down by compiling it.

Though it's probably not a bad idea to get @Christoph-Hart to confirm.

[d.healey]

@aaronventure If that were true there would be no reason to compile the network to a DLL

[ustk]

@aaronventure @d-healey @Lindon @clevername27 @Christoph-Hart
This is something we haven't discussed in the last Hise Hang, though it might be a good idea to put it in the priority list, isn't it?

[Lindon]

@ustk said in global send / receive:

@aaronventure @d-healey @Lindon @clevername27 @Christoph-Hart
This is something we haven't discussed in the last Hise Hang, though it might be a good idea to put it in the priority list, isn't it?

well getting global cables and global send/receive nodes into a compiled network would be very nice.. no idea how complex it is to do...

[ustk]

@Lindon Yeah absolutely, and to go beyond, it would somewhat inconvenient to be unable to compile a network because you use this or that functionality.
Implemented functionalities should be compatible with the environment they are meant to be used in

[aaronventure]

@d-healey well no, you are reducing CPU usage in HISE while developing, and SNEX/Faust nodes need to be compiled first.

Also sometimes you want to blackbox a network and use it in different places with different modulators.

[d.healey]

@aaronventure said in global send / receive:

@d-healey I vaguely remember reading somewhere about it. It should be the same whether the network gets converted to C++ on project export or on its own first, no? The only difference is some nodes, like SNEX and Faust, require in-HISE compilation first, and if you have a really hungry network, then you can get the CPU usage down by compiling it.

Though it's probably not a bad idea to get @Christoph-Hart to confirm.

@Christoph-Hart What say ye?