Plugin build funkyness

[tomekslesicki]

I'm running into a rather strange issue when exporting a project on a Mac (haven't tested other systems yet):

Yesterday I spent the whole day stripping the project back to basics. I ended removing everything, and leaving just a sine generator with the basic envelope. Still nothing.

Ok, so why is it a strange issue? I created a new project on the same drive, copied all the files over. It exports just fine. I have no clue what's causing this, and obviously having to create project duplicates like this is less than optimal.

Anybody experienced this?

[d.healey]

@tomekslesicki Tried cleaning the build folder?

[tomekslesicki]

@d-healey of course. Same with the PooledResources and network files. But then everything works fine if I just copy-paste all of the plugin files into a new project folder.

[d.healey]

@tomekslesicki Yeah that's a weird one, no idea what's happening there.

[aaronventure]

Are you exporting with faust?

[Lindon]

@tomekslesicki Ive had something similar to this, is the project o a removable drive? if so move it to an internal fixed drive.

[tomekslesicki]

@aaronventure no, I'm only using normal scriptnode stuff and some hardcoded networks. Some modulation networks have frame1 containers.

@Lindon doesn't help, sadly, but thanks for a tip!

I scrolled up the build log and this is the first critical error I get.

[d.healey]

@tomekslesicki Have you compiled your networks just for arm but you're compiling the plugin as a universal binary - or something like that?

[tomekslesicki]

@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.

[Morphoice]

@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

[Morphoice]

@d-healey where would you set this? can't find anything in the project settings about ARM. I assumed it would always make universal

[d.healey]

@Morphoice said in Plugin build funkyness:

I assumed it would always make universal

Me too

[tomekslesicki]

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:

[tomekslesicki]

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.

[Christoph Hart]

@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.

[tomekslesicki]

@Christoph-Hart something particular I should look for?

[aaronventure]

@tomekslesicki paste over the project info xml from the vanilla that builds, compare it in git and go line by line until it breaks.

[tomekslesicki]

Thank you for the clues!