@noahcs it looks like some of those errors are because you didn't use an ";" after a declaration.

@d-healey thanks, the help isn't clear…

Same problem in Logic with AUv2. Bit better maybe but jagged.

@Christoph-Hart Oh yes my bad, actually I'm using the good syntax inside the project but it does not work for me, neither does my previous shader despite it was working before...

@Christoph-Hart does this also fixes my issue here?
https://forum.hise.audio/topic/7069/audio-inputs-aren-t-working-anymore

@Matt_SF got you, thanks!

@ustk

Well maybe it is just that you are used to add it for many things

This reason. And then once you've done it you don't realise your mistake until weeks later when you go to compile and nothing works :p

@Christoph-Hart Is scriptnode working on the GPU?

--- Okay well, this is a very interesting problem.....here's what I think was/is happening....

As I said this is a VERY big project, but previously I have divided it down into a set of 32 include files..yeah there's a lot of code...

Many of these operate in their own namespace, but (sadly) not all....until today...

So it seems that I ran out of variable space, despite my (inconsistent) namespace usage, and HISE wasnt telling me about this, instead it went ahead and tried to compile the code. At some point it reached this limit of variables, but was in the middle of a for loop assigning widget references to these vars (theres a LOT of widgets). So the for loop never completed, and HISE lost patience and killed the thread by force.

So the solution was (here) to use namespaces everywhere.....

..and the solution long term is:

Use namespaces everywhere Ask @Christoph-Hart to look at getting a slightly better error message out of HISE (I realise the "by FORCE" message is in fact from JUCE - but if we can intercept this and check our var usage that would be a good thing to do I think)

Dear God let this be the problem/solution.....

@Matt_SF said in Value can't be resolved in cable_expr node:

math.exprnode for incoming signals and cable_exprnode to modify a incoming parameter value...

Yes exactly 👍

@Christoph-Hart Thanks it seems stable now 👍

@Christoph-Hart Yep that worked, thanks

@Christoph-Hart Fair enough :)

@d-healey 😂😂😂

@Christoph-Hart Thank you :)

@Christoph-Hart recompiled and Looks god so far! Thank you!!!!