Got this working, thank you everyone for your help! The fix was just updating Visual Studio past 2017. :)

@DanH Thanks! Trying VS2020 now.

Halo 2 looks epic, congrats

Well, after editing little bits of source code and recompiling HISE like 15 times, I finally found it in case anyone else needs to edit this.

The main reference for ALL the green colored sample stuff (back and frontend) is in hi_tools/hi_standalone_components/SampleDisplayComponent.cpp, line 383:

JUCE_LIVE_CONSTANT_OFF(Colour(0xff5e892f));

Just the sample start bar in particular is in hi_components/audio_components/SampleComponents.cpp, line 600:

auto c = SampleArea::getAreaColour(AudioDisplayComponent::AreaTypes::SampleStartArea);

Just change the first one if you want everything but the color to stay the same. If you want to remove it completely, change the second one. You'll also need to change the alpha value on line 607 to 0:

g.setColour(c.withAlpha(0.3f));

You can probably figure out how to remove just the solid line or just the shaded rectangle in the neighboring lines.

Would be nice if there was a way to do this without recompiling but this worked for me for now.

@d-healey Thank you. codesign --remove-signature does the trick.

@gorangrooves You could do it a few different ways depending on what exactly you're looking for/what your setup is... If you're using a sprite sheet, you could export it in reverse order, then in the slider's custom callback, set whatever it controls to the max possible value minus the current value (i.e. for a 0 to 100 knob, "100-value").
You could also put an invisible control on top of it (a slider with an empty png as its image, or a script panel if you prefer), then in the invisible slider's custom callback, set the visible slider's value to max - current value. Like this:

const var visibleSlider = Content.getComponent("visibleSlider");
const var invisibleSlider = Content.getComponent("invisibleSlider");

visibleSlider.set("min", 0.0);
visibleSlider.set("max", 100.0);
invisibleSlider.set("min", 0.0);
invisibleSlider.set("max", 100.0);

inline function oninvisibleSliderControl(component, value) {
	if (value) {
		visibleSlider.setValue(100-value);
	}
};
Content.getComponent("invisibleSlider").setControlCallback(oninvisibleSliderControl);

@Casey-Kolb Coming back to say thanks! I replaced those 3 waveforms with pngs and that seems to have solved it. It wasn't super reliably replicable so won't be 100% sure till the plugin is released and people do or don't complain lol... but I haven't gotten the error again yet.

A year on and I just had this same issue for the first time, so I thought I'd update this thread for anyone else in my shoes. I got the same slew of ipp.h errors when trying to compile the master branch with VS2017 and IPP 2021.5.3.585, but I also got it to work by choosing "Static Library" in the Project > Properties > Intel Libraries for oneAPI dialog in VS. I didn't change anything in the HISE Standalone.projucer file (or elsewhere). I opened my finished HISE project and everything worked as expected, including the convolution reverb and analyzer, so I thought I was home free, but trying to export my plugin resulted in yet another slew of IPP errors. I downloaded IPP 2020.0.166 from the archive.org link above, plopped it on my desktop, and tried exporting again. To my shock and joy, it worked immediately. I didn't update any paths anywhere so I guess it just needs to exist somewhere on your computer? Seemed too good to be true but I'll take it.

Also a heads up: If you have both installed and recompile HISE, the VS Project > Properties panel will have two categories for IPP. The 2020 one says "Intel Performance Libraries" and the 2021 one says "Intel Libraries for oneAPI." So if you changed the setting for the new version and then downgraded IPP to recompile, you'll probably need to reenable it since they're different options.

Got this working, thank you everyone for your help! The fix was just updating Visual Studio past 2017. :)

@DanH Thanks! Trying VS2020 now.

Halo 2 looks epic, congrats

@HISEnberg Ok thanks! I think I built with VS2017 so trying that now.

@Christoph-Hart Thanks! I will see if I can find that other post.

Thus far I've tried a couple versions of Rnbo and I'm still getting the same errors.

I've tried other Rnbo effects as well, and its the same result. I downloaded the Rnbo guitar pedal suite they released and tested out 3 (Plate reverb, EQ, Tuner).

@Christoph-Hart said in RNBO compilation errors on Windows:

That's a bit optimistic for building a Windows binary on Friday the first time :)

The client wanted to add a last minute 11th hour effect that makes use of Rnbo and at the time it sounded simple enough and the mac version went super smoothly last week. Thankfully there is another release candidate binary sans the Rnbo.

I'm going to test some alternate versions of Hise maybe there's a magic combination.

@DanH Yes, sorry I should've been clearer--this issue is happening when I try to compile the dll.

Hi everyone, I have a finished plugin that uses one RNBO effect. It compiled perfectly fine on Mac. I'm now trying to compile on Windows and I'm getting these 2 errors:

error C2440: '<function-style-cast>': cannot convert from 'RNBO::number' to 'RNBO::TransportState' ' (compiling source file ....\Source\Main.cpp)

error C2660: 'RNBO::PlateRevRNBO::processTransportEvent': function does not take 1 arguments (compiling source file ....\Source\Main.cpp)

Any ideas? This is pretty urgent as this is slated to release on Monday. I'm using Visual Studio 2017 on a Windows 10.

Thanks for posting about this converter! Was hoping you could point me in the right direction as I cannot get it to work correctly.

Are you exporting from the converter as an SFZ with samples or just an SFZ?

Did you have to edit any of the text in the outputted SFZ file?

When I export the SFZ and try loading it up in Hise, it loads up one zone, C-2, and every sample from my auto sample folder (Lets 64 samples for this example) is somehow playing from that one zone lol. I actually jumped a little in my seat when I played that note.

Any tips would be greatly appreciated.

@johnmike Having the same issue on Intel... How did you fix it?

@ericchesek Good thinking, it does appear to be that midi cc message(s).

After extensive testing, I think it may be a bug or at the very least a less than ideal behavior.

I downloaded some of the various Hise instruments that are linked on the main page of the Hise site as well as even bought a couple commercial releases that were made with hise.

It appears that if in the MIX tab <> Auto Select Automation Parameters <> is on, the behavior in the video posted above happens.

If you have that mode unchecked, it does not happen.

@d-healey thanks!