@lijas90

Highjacking, sorry for that, but i am really frustrated:

I want to route Sampler 1 to Output 1/2 and Sampler 2 to Output 3/4. My problem is, even in the plugin version of my drum sampler, i see only 2 outputs on my main Output container. In my sampler routing matrix i see all the outputs and can route them, but when i load the hise vst in cubase, it only gives me stereo out. I can do screeenshots later, but do you guys have any idea? I hust want to have a routing choice for snare, kick and so on ?

Do i need to compile HISE itself with some other flags or so?

Cheers
Ben

@David-Healey ah i see.

ill keep trying that from here on out

@voxuer1 Hi everyone,
I’ve been trying to get RNBO 1.4.2 to compile with HISE on macOS for an entire day, but unfortunately without success.
What I already tried:
Clean reinstall of HISE
Regenerating the JUCE project multiple times
Fresh builds in Xcode
No custom modifications to the generated project

Create files
Sorting include dependencies
Copying third party files
Compiling dll plugin
Re-saving file: /Users/thomaszalud/Documents/HISE Projects/0/DspNetworks/Binaries/AutogeneratedProject.jucer
Finished saving: Visual Studio 2022
Finished saving: Xcode (macOS)
Finished saving: Linux Makefile
Compiling 0 ...
** BUILD FAILED **

The following build commands failed:
CompileC /Users/thomaszalud/Documents/HISE\ Projects/0/DspNetworks/Binaries/Builds/MacOSX/build/0.build/Debug/0\ -\ Dynamic\ Library.build/Objects-normal/arm64/Main.o /Users/thomaszalud/Documents/HISE\ Projects/0/DspNetworks/Binaries/Source/Main.cpp normal arm64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target '0 - Dynamic Library' from project '0')
(1 failure)

@dannytaurus Yes I had tried those but to no avail...but seeing your example working made me look back at the project and there was a conflict which is why it wasn't changing anything visually, Thanks for your help it is much appreciated and shows me that I am not going mad at least haha

@David-Healey I finally managed to get a successful VST3 export! "BUILD SUCCEEDED" in the terminal.

What fixed the SDK error: The issue was indeed the VST3 SDK path. I had to point it exactly to the folder containing the base, public.sdk, and pluginterfaces directories. After correcting this in the Projucer Global Paths, the "SDK missing" error disappeared.

Bumpy bump

@Jaytove True, but the videos I mentioned are about file and file system APIs, combined with the steps I gave you above should point you in the right direction

@ulrik Thanks for checking! That makes sense.
I'll wait for @Christoph-Hart to take a look.

@David-Healey Fascinating stuff! Big takeaway for me is keep your business model simple.

@David-Healey doing it right now

@Lindon
Thanks Lindon, I'll try this (I guess I need to operate in onNoteOn).
@David-Healey Ok, tried also to set PreLoad size to -1 but the voice killing still happens.

@David-Healey said in this one looks interesting:

built lots of little projects

100% this! That's what I did over the last year or so.

Folks who jump straight in with a large project are asking for trouble. Even if they're seasoned in other languages or environments. For example, I'm well-versed in building web applications in Ruby On Rails but I wouldn't jump straight over to ASP.NET and try to build a massive project right off the bat.

The ideas for the first 4 HISE plugins I'm developing all came from a very simple concept for each one - focus on one single sound type. The first one is sub bass. Even keeping it simple like this has it's challenges.

@GUJIAN Choose the Export as Instrument option from the Export menu.

CleanShot 2026-01-28 at 10.56.28@2x.png

@Lindon Haha, allmost exactly as I do it

// ============= SET SAMPLE START MOD LENGTH =================== inline function onSampleLengthControl(component, value) { // Select all samples local selected = Sampler.createSelection(""); for (s in selected) s.set(Sampler.SampleStartMod, s.get(Sampler.SampleEnd) * value); } SampleLength.setControlCallback(onSampleLengthControl);