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.

Hello,

I'm currently in the middle of editing a ton of legato samples, and while I am getting ready to go through and edit every mic on a per item basis in Reaper, it also hit me that I may be able to do some of this within HISE.

Is it possible to add effects, like a dynamic eq, on a per sample/region basis?

I'm not quite sure, yet, how I'm going to be laying these out within HISE, so I figured if I can adjust and chase some of these pesky fundamentals on a per sample basis, not necessarily the actual note on event, I could go through and set this up without having to re-render "cleaned" audio.

It's been awhile since I have dug around in HISE, so I'm excited to check out all the shiny new features.

Hello,

A few friends were asking me about HISE, and since I have no clue about this answer, I figured I would ask here.

How does HISE handle repitching samples, and would there be any benefit to using 96khz or above to fend off digital artifacting with extreme changes?

In my regular work experience, I frequently use high sample rate sources for sound design, but I have never really considered this when making something for a VI. I have always just worked with 48khz samples in 48khz sessions.

How does HISE handle this, and how does HISE handle source samples with a different rate than a host DAW?

@d-healey Good to know about the .hr format!

I just tried building a few other things. It does look like the automated system is hit or miss at choosing to build with 2017 rather than 2019—regardless of settings. Hopefully if people run into this as I did, this should save some headaches. Fairly easy work around of just going to the jucer file.

It was able to build via this method, so there may be a problem with having multiple VS versions installed. Unfortunately, I need 2019 for other things.

Furthermore, the newer version of IPP appears to still be problematic... After all that time and when I finally believed to have gotten IPP working.

With ipp enabled:

1>...\hise-scriptnode\hi_streaming\hi_streaming.h(69): fatal error C1083: Cannot open include file: 'ipp.h': No such file or directory (compiling source file ....\JuceLibraryCode\include_stk_wrapper.cpp)
1>Done building project "Oboe QuickTest_SharedCode.vcxproj" -- FAILED.
2>------ Build started: Project: Oboe QuickTest_VST, Configuration: Release x64 ------
2>include_juce_audio_plugin_client_VST2.cpp
2>LINK : fatal error LNK1181: cannot open input file 'Oboe QuickTest x64.lib'
2>Done building project "Oboe QuickTest_VST.vcxproj" -- FAILED.

With Ipp Disabled:

2>...\hise-scriptnode\juce\modules\juce_core\text\juce_charpointer_ascii.h(43): warning C4702: unreachable code
2>Finished generating code
2>Oboe QuickTest_VST.vcxproj -> ...\Oboe Sample Library_POC\HISE Project\Binaries\Builds\VisualStudio2017.....\Compiled\VST\Oboe QuickTest x64.dll
2>Done building project "Oboe QuickTest_VST.vcxproj".
========== Build: 2 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

Luckily, I dont use internal reverbs in anything I make; however, I did run into an odd quirk when I loaded the vst.

It kept asking for a .hr1 archive file, but it doesnt appear to have ever made one. Everything turns up blank when doing a system-wide search. I'm assuming this is because I am redirecting the samples to another folder. But it appears to have worked after just telling to physically look at said folder.

For me, it isnt a big deal at the moment, but is this intended? This is the first time I have tried working with HISE where all of my assets are not in the root project hierarchy.

That's what I initially thought as well, but it says it is using Visual Studio 2017.

Same error.

Not entirely sure at this point.

Finished saving: Visual Studio 2017
Finished saving: Xcode (MacOSX)
Finished saving: Xcode (iOS)
Finished saving: Linux Makefile
Compiling 64bit Instrument plugin Oboe QuickTest ...
The system cannot find the path specified.
Press any key to continue . . .

I recompiled HISE yesterday to the Scriptnode branch, and today, none of my exports are working. It says the system cannot find the path specified; however, I have it set correctly to the HISE root directory within the preferences.

I have visual studio 2017 and 2019 installed, but the latter did not cause issues before.

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

Does HISE have a facsimile to Kontakt's Flexible envelope?