@dannytaurus Worked like a charm!
Thanks for your input.

@pcs800 And strangely enough, today I can compile to the network drive again without issue.
The server must have been low on bluetooth fluid

@David-Healey I copied one of the projects to the local C drive and compiled the vst3 without error.
I am perplexed as to why this is suddenly happening. I have been running projects from my file server since I started using hise, with no issue.
I guess I will put in a new drive in case there's something wrong with the current one.

@David-Healey A plugin developer we know, made a plugin that is daw locked to Mixcraft. However, he does not use Hise. I will see if i can find any info on that, and post here

@David-Healey I sent a link to you in chat.

@David-Healey I found the issue.
ParamEQ.setAttribute(band * 5 + 4, bandColors[band]);
band * 5 + 4 is an invalid attribute index for the CurveEq

@David-Healey Yeah I removed it and readded it too, but the issue just comes back. I will try to debug the script.

@dannytaurus This is what I came up with

Original signal only: 7232
-1oct:3068
-2oct:2659
+1oct:6143
+2oct:7232

Max: 7232

-1oct: Needs 4164
-2oct: Needs 4573
+1oct: Needs 1089
+2oct: Needs none
Original Sig: Needs none

I'll try it

I have a dsp network in a project that I would also like to apply to another project, without rebuilding the whole thing.
I see that I can export the main container node by right clicking it and choose to export as CPP or Template.
Which should I use? Also, how to import to the other project?

@Lindon And I went over it three times looking for missing commas! Dang it, I need to pay closer attention. Thanks very much.

@David-Healey Can you help me understand why editable is the default? Is there some reason users need to be able to change the label text?

How can I set Hise to make labels non-editable by default? It seems to me that having them editable is almost never going to be needed by a user. I am constantly going back to projects to make sure I set them all as non-editable.

@pcs800 And strangely enough, today I can compile to the network drive again without issue.
The server must have been low on bluetooth fluid

@David-Healey I copied one of the projects to the local C drive and compiled the vst3 without error.
I am perplexed as to why this is suddenly happening. I have been running projects from my file server since I started using hise, with no issue.
I guess I will put in a new drive in case there's something wrong with the current one.

@David-Healey That would be the dev pc, lots of space.

@David-Healey Claude says:
That's a linker crash, not a code error. The key line is:

ExceptionCode = C0000006

That's STATUS_IN_PAGE_ERROR — the linker (link.exe) tried to read a page of memory that couldn't be loaded from disk. It's crashing inside the linker itself, not failing due to bad code. The LNK1000: Internal error during BuildLibrary.EmitMember confirms this — it's an internal linker fault, not something wrong with your HISE script or C++.

The most likely causes in order of probability:

Disk/file issue — The project is on H:\, which looks like a network drive or secondary drive. If that drive had a hiccup during the link stage (slow response, brief disconnect, full cache), you'd get exactly this. C00000C4 in the exception info points to a file mapping fault.

Low disk space or RAM — The linker is mapping large object files into memory. If you're tight on either, it can fail this way.

Corrupted intermediate files — The x64\Release\Shared Code\ intermediates may have gotten into a bad state. That MSB8028 warning about shared intermediates between projects is a red flag for this.

What to try:

1. Do a full clean of the build (delete the Binaries\Builds\VisualStudio2022\ folder entirely, or use HISE's clean option), then rebuild fresh.
2. If H:\ is a network or external drive, try moving the project to a local C:\ path and compiling from there.
3. Check available disk space on H:\ and on C:\ (where temp files land).
4. Try compiling again immediately — sometimes it's a one-time I/O glitch and it just works on retry.

The fact that it repeated the crash dump ~25+ times in a loop before hitting LNK1000 suggests the linker kept retrying internally and hitting the same bad page each time, which further points to a storage/I/O issue rather than anything wrong with your actual plugin code.

@David-Healey Of the server or the dev pc?
Dev pc 614GB
Server 1.7TB

@Sifres There's 119GB free on that drive

@Sifres Yes I am running from a networked drive. I always have.
I'll go check to see if the drive is getting full

@David-Healey But it happens with any project, not just this one