@d-healey This has been doing the trick for me. Thanks!

Fantastic!

I'm very much in love with the idea of being able to hand someone a single, standalone VST, and I also like the potential to scale HISE's features with code. I highly doubt I'll need to be doing the latter, but its always a nice option to have.

Hello,

So for logistics reasons, I'm needing to use the {Global_Sample_Folder} link file to point towards my audio repo.

On Windows, everything works great. Once I figured it out, any and all sanity check errors vanished and the plugin compiled smoothly.

On my m2 mac, not so much. For whatever reason, it just would not want to build even if I cancelled the sanity check.

Luckily, after moving the samples in question to the sample folder and changing the file path to use the project wild card, I was able to get it to export correctly.

That said, it still technically failed the sanity checks; however, I confirmed that the vst is running correctly across multiple Mac rigs, so that's a plus. Nothing appears out of the ordinary.

Oddly enough, even once I manually modified the samplemaps to use the project folder, the path in HISE still kept pointing towards the location on my windows rig, even though I wiped all traces of that from the xmls in question.

@d-healey That's what I thought was going on.

Ya, it's for a quick demo, which is why I did it in this instance.

It'll be cleaned up later, haha.

Solved. Just had to use the artificial system and got everything working.

Hello,

I'm currently prototyping out a UI, which I'll refactor and clean up the code later, but I wanted to at least test it with a subset of the instrument's samples: Simple round robin selector and label.

The problem that I am running into right now is that the UI will not update unless I hit compile.

After that, everything works fine; however, I tested the vst3 of the instrument and all the underlying instrument logic (the important stuff) works except that the UI will not update as it should—like after I hit compile.

gGroupCounter is a global variable on a script beneath the interface where all my GroupTracking logic is occuring.

Init:

Content.makeFrontInterface(600, 600);

Synth.deferCallbacks(true);

const var Keyboard1 = Content.getComponent("Keyboard1");
const var Label1 = Content.getComponent("Label1");



for(i = 48; i < 79 + 1; i++ )
{
	Engine.setKeyColour(i, Colours.withAlpha(Colours.aquamarine, 0.5));
}

//Black keys within range.

Engine.setKeyColour(49, 0x00);
Engine.setKeyColour(51, 0x00);
Engine.setKeyColour(54, 0x00);
Engine.setKeyColour(56, 0x00);
Engine.setKeyColour(58, 0x00);
Engine.setKeyColour(61, 0x00);
Engine.setKeyColour(63, 0x00);
Engine.setKeyColour(66, 0x00);
Engine.setKeyColour(68, 0x00);
Engine.setKeyColour(70, 0x00);
Engine.setKeyColour(73, 0x00);
Engine.setKeyColour(75, 0x00);
Engine.setKeyColour(78, 0x00);

Engine.setKeyColour(36, Colours.withAlpha(Colours.gold, 0.5));
Engine.setKeyColour(37, Colours.withAlpha(Colours.red, 0.5));
Engine.setKeyColour(38, Colours.withAlpha(Colours.red, 0.5));

Label1.set("text", gGroupCounter + 1);

Note On:

function onNoteOn()
{
	Label1.set("text", gGroupCounter + 1);
	
	switch(gGroupCounter)
	{
		case 0:
				Engine.setKeyColour(36, 
				Colours.withAlpha(Colours.gold, 0.5));
				Engine.setKeyColour(37, 
				Colours.withAlpha(Colours.red, 0.5));
				Engine.setKeyColour(38, 
				Colours.withAlpha(Colours.red, 0.5));
		break;
		
		case 1:
				Engine.setKeyColour(37, 
				Colours.withAlpha(Colours.gold, 0.5));
				Engine.setKeyColour(38, 
				Colours.withAlpha(Colours.red, 0.5));
				Engine.setKeyColour(36, 
				Colours.withAlpha(Colours.red, 0.5));
		break;
		
		case 2:
				Engine.setKeyColour(38, 
				Colours.withAlpha(Colours.gold, 0.5));
				Engine.setKeyColour(36, 
				Colours.withAlpha(Colours.red, 0.5));
				Engine.setKeyColour(37, 
				Colours.withAlpha(Colours.red, 0.5));		
		break;
		
		
		
		
	}
}
 

That's what I was looking for!

Very late, after the editing process, I just realized that our mid-side microphones were exported as a single stereo file.

Is there a way in HISE to split these two microphones to their own respective, new channels—while also flipping the phase/polarity of the side microphone?

I'm guessing this would probably be easiest to do in script node?

Hello everyone,

I currently have two samplers that I need to crossfade between when the sustain pedal is down and another note is played. (I have effectively disabled the sustain pedal functionality for this purpose, so it is purely acting as a trigger at this point).

I have tried modifying the release time of the AHDSR Envelope once a note has played and the sustain pedal is down, but I noticed that the release time is set during the NoteOn event, so I'm unable to modify the release value for the already playing note.

Any recommendations on how to manually deal with this? I'm sure I'll need to make it artificial since I'll have to kill the note as well.

What's the memory usage/impact of using the same audio file in separate sample map locations/groups?

For instance, I'd rather not render unique release samples, but have the sustain referenced again, in its own location with a unique start, so that I can graft releases that occur before the end of the natural length of the sample.

I'm hoping this can save on disk space of raw samples, and then leverage the parameters within the sampler module.

@d-healey

Awesome. Thanks David!

@d-healey

This question had more to do with corrective EQ and dynamic adjustments: not necessarily cutting the samples.

We are premixing everything so that any move that would be done from an engineering standpoint is already done from the get-go, as it'll save us a lot of time down the road when using these instruments.

The thing is, a lot of these moves are mic specific and or unique to each note, so I was hoping to be able to do some of this within HISE in an attempt to keep unprocessed audio within the instrument as well, should we need that.

Based on the amount of round robins and samples that were recorded, let alone the number of mics from the studio, it'd be a bit of a slog to do item or track based fx for each note.