Plugin build funkyness
-
@d-healey I compiled with the HISE menu command so I guess it’s all set up the default way, but that’s a good thing to check for sure! I’ll look into it tomorrow.
-
@tomekslesicki try if it works changing the frame1 containers to normal chain containers... we're having a lot of pain with frame block nodes lately
-
@d-healey where would you set this? can't find anything in the project settings about ARM. I assumed it would always make universal
-
-
The nodes are compiled correctly by default, using universal binaries so this part is good. I removed all frame containers from the project and built from there, but that didn't solve the issue. I run the autogenerated JUCER file and got some extra - maybe useful @Christoph-Hart ? - info in the XCode log:
-
If that’s of any help, I’m using scriptnode for multi-channel processing and scriptnode envelopes for some modulation. The processing node is hardcoded as Poly FX, the modulation networks are not of course. In the mod networks, there are global modulator nodes, cable tables and midi nodes in there. Nothing super-fancy. I’m using the NUM_MAX_CHANNELS, NUM-HARDCODED_POLY_FX_MODULATORS (I hope I typed them right from top of my head, I’m not by my computer now) preprocessor in HISE build.
-
@tomekslesicki I don't think it's something within HISE or some scriptnode flag - more likely a linker issue because of a ARM architecture mismatch.
Looks like one of the more annoying build glitches because of how your macOS build pipeline is set up.
If a vanilla project builds, then there must be something in your project that messes up the build configuration. Check whether the project.xml file contains some funk.
-
@Christoph-Hart something particular I should look for?
-
@tomekslesicki paste over the project info xml from the vanilla that builds, compare it in git and go line by line until it breaks.
-
Thank you for the clues!