@aaronventure Okay thank you for your help, looks like I'm gonna learn how to create a virtual installation of Mac lol

@d-healey Oh shoot, I didn't even know I could build VST2, do I also need a license for VST3?

Hello HISE forum I am struggling to find a solution online for this, but is there a way to build my plugin in the Audio Unit format on a Windows 11 device? If so, how would I go about doing that, is there an SDK that I need in order to be able to successfully export the project?

I have successfully built my project in both VST and DLL formats but I don't see an option for AU when I hit the export as instrument (VSTi, AUI) button.

Any help would be greatly appreciated!

@d-healey
Wow thanks for the fast reply! It looks like the date on the executable is 03/20/2024, which does not seem to be the latest version, so that may be my issue with the snippet importing...

My onController callback code seems to be working for triggering the different samplers, I am going to have to mess with the button features to get it to be able to trigger the sustain pedal. What function would I use to turn on a sustain pedal via a button on the interface, like I know how to reference the button but how do I actually get it to trigger the sustain pedal (without having to press the actual pedal in real life...)

@d-healey

I might not be on the latest version, I compiled four or so weeks ago, where would I find what version of HISE I am on?

It would be awesome to have the button be assignable for those few who don't have a sustain pedal, or just want to map sustain to something else. How would I go about getting the separate sampler scripts to communicate with one another to recognize the buttons state, you mentioned using "setAttribute" but I don't think I understand the context to use it under. Are buttons midi assignable by default in HISE, or does that require additional scripting?

@d-healey
Okay good to know,

I was using the button on the interface to communicate the state of the sustain pedal on the UI itself, as well as a way to tell my other script modules to not play if the sustain is engaged. As I am explaing this I am realizing I could just use the "isSustainPedalDown" to accomplish the same thing :man_facepalming: am actively updating the code for both samplers as we speak.

(Notes with pedal, Sampler2) onNoteOn

function onNoteOn()
{
	if (Synth.isSustainPedalDown() == 0)
	{
	Message.ignoreEvent(true);
	}
}

How would I use the setAttribute or processor ID to communicate between modules? Would it be as simple as defining the "const var (insert ID)" within the onInit of the sampler I want to communicate with?

Here is the video of what happens when I try to import the HISE snippet into a new project
video of error message

@d-healey

I believe I got it working! Thank you, I still seem to have not been able to get the HISE snippet to work to see your exact code but thanks to the information you gave in your responses I was able to get it working. I am worried the way that I have done it is inefficient, so I am open to any suggestions for improvements.

I ended up using a global variable for my button on the interface, and I was wondering if that was the optimal way to do this or if there is a better way...

(interface) onInit

Content.makeFrontInterface(600, 600);
Globals.Button1 = Content.getComponent("Button1");

(interface) onController

function onController()
{
if(Synth.isSustainPedalDown() == true)
{
	Button1.setValue(1);
}
else
{
	Button1.setValue(0);
}	
}

(Piano Notes Without Pedal, Sampler1) onNoteOn

function onNoteOn()
{
	if (Button1.getValue() == 1)
	{
	Message.ignoreEvent(true);
	}
}

(Piano Notes With Pedal, Sampler2) onNoteOn

function onNoteOn()
{
	if (Button1.getValue() == 0)
	{
	Message.ignoreEvent(true);
	}
}

@d-healey okay sounds good, thank you!

@d-healey This seems like a better method than using midi muters, but I'm having trouble importing the HISE snippet, with HISE telling me its not a valid snippet or container file, so I've just tried to recreate what you are describing.

I have created a button on my NotesWithoutPedal Sampler interface, and I have specified my variables in the onInit like so...

Content.makeFrontInterface(600, 600);
const var NotesWithoutPedal = Synth.getSampler("NotesWithoutPedal");
const var Button1 = Content.getComponent("Button1");

Then in my onNoteOn callback of the sampler I have these lines

function onNoteOn()
{
	if (Synth.isSustainPedalDown() == true)
	Button1.setValue(1);
	Message.ignoreEvent(true);
}

But now my sampler is not triggering any samples regardless of whether any button is pressed.

Hello all! I have been working on a piano sampler instrument in HISE for a few weeks, (am still new to HISE) and am having issues triggering different samplers based on whether or not the sustain pedal is being pressed. I have loaded up a MidiMuter on both tracks and then I am trying to disable each sampler from triggering notes based on whether or not the sustain pedal is being pressed down.

I have two samplers loaded up, one of them for notes with pedal, and the other for notes without pedal. in the function onController of the notes without pedal I have this function...

function onController()
{
	if (Synth.isSustainPedalDown())
	MidiMuter1.setBypassed(0);
}

It seems to compile okay but it does not seem to do anything when the led is pressed. if anyone could have some minor insight into where I'm going wrong that would be greatly appreciated, thank you in advance!

@d-healey Ahhhhh such a simple solution, thank you!

Hello, I am very new to HISE/scripting and had a question about triggering certain notes within a RR group. I am building a piano sampler instrument but some of my RR groups don't have samples for some notes, while other groups have samples for those same notes. I am trying to figure out a way to maintain my random RR while also eliminating any dead notes. As it currently stands, the code seems to cause the RR's to stop working and just remain on one RR group.

onInit

const var NoteSamples = Synth.getSampler("NoteSamples");
NoteSamples.enableRoundRobin(false);

reg counter = 0;
reg lastCount = 0;

onNoteOn

function onNoteOn()
{
	counter = (lastCount - 1 + Math.randInt(2, 5)) % 5 ;
	NoteSamples.setActiveGroup(counter + 1);
	lastCount = counter;

	Message.getNoteNumber();
	if (NoteSamples.isNoteNumberMapped(number));
	Function.NoteSamples.setActiveGroup(1);
}

The code seems to compile okay, but when I play a note I get this error:

Round Robin 1:! onNoteOn() - Line 8, column 37: API call with undefined parameter 0 {Um91bmQgUm9iaW4gMXxvbk5vdGVPbigpfDIwOHw4fDM3}

I would still like to trigger the RR groups with less samples, but ONLY for the samples that they DO have, and not for the ones that they don't.

Thank you in advance, I apologize if this is a silly question, I am still very new to scripting and HISE in general.

@Lindon Yes! Compiling without IPP has worked!

I know I'm not missing a ton of functionality without it, but would like to know if there is a way to get it working as I was hoping to mess with the convolution reverb.

Hello all, I am really new to HISE and have been getting this error and I cannot seem to figure out what is causing it. It is happening when I try to build HISE standalone (or the plugin version) in Microsoft Visual. Any help in this area would be greatly appreciated, as this is all really new to me.

I am using Windows 11 and I am following both the HISE Docs/Readmes, as well as this tutorial https://www.youtube.com/watch?v=D3kthNOQ9_s

I have tried reinstalling the IPP and I am still getting the same error, it must be something I am doing wrong but I don't know what.

Below is what it looks like in the compiler...