Same node parameter names impossible?
-
Compilation fails in Hise (with as often, no information on the issue) and XCode complains for
Redefinition of 'SubGroup1_p', etc...
I can rename them of course... I understand the issue within the same parent, but with different nodes...
-
@ustk Ah yes fixing this should be possible, but quite complicated because the code generator would need to find a unique ID for each parameter.
I'll see what I can do.
-
@Christoph-Hart Not a big deal to be honest once you know what the problem is, but still it'd be useful have it fixed

The biggest problem is Hise not spitting enough info when failing to compile, so we always have to resort on xcode to get more details... -
The biggest problem is Hise not spitting enough info when failing to compile,
Yes, the problem is that this is not deterministic - sometimes the compile process will send its output back to HISE's dialog, and sometimes it doesn't and I have yet to figure out why it works or doesn't.
-
@Christoph-Hart Ok so the issue is not the fact that they have the same name.
After renaming SubGroup from 1 to 8, XCode is still complaining fromRedefinition of 'SubGroup1_p'up to SubGroup8.Effectively, those parameters get copied twice in the header
This might only be related to how branch nodes get compiled, I don't know... I verified the ID of the branches and that the network only has one set of those parameters. Cleared the build folder, deleted the network header that contains the redundancy, etc...
Only moving my parameters externally to the branches works as expected:

-
@Christoph-Hart Side question. In a modulation context with that many branches (64 in total). Are all the branches modulated no matter if they are active or just the selected one is modulated behind the scene to save CPU? Because I only have one activated at a time so it would be crazy to route 64 modulations at the same time
