@Lindon
I agree with you! I think the bug I mentioned is also a regression.

@Christoph-Hart Considering my post right above about the issues and limitation of the scriptnode table, could the upgraded UI table be ported to scriptnode with at least a default behaviour if a customisable one isn't convenient to add?

Linking a UI table for each one we want in scriptnode is not really an option so much it is cumbersome during development...

@Gab I'm on the Community version.

CleanShot 2026-03-02 at 10.33.11@2x.png

@l4ch If you're on Mac, try opening the XML in TextEdit then go to File > Revert To... > Browse all versions.

It might have some version history saved by macOS that you can restore from.

@pcs800 Or an array of buffers for stero/multichannel

I’m so absent-minded 😰 The issue was that I forgot you need to enable compilation in the main container. Thank you for your help, guys! @David-Healey @Christoph-Hart @dannytaurus

@David-Healey said in Best way to structure a multi-mic, multi-output drum library in HISE?:

@versusjona

1 sampler per instrument seems reasonable here.

You can merge samples with different numbers of channels, but the lengths must match.

A couple of videos you might find helpful regarding multi-mics.

https://www.youtube.com/watch?v=sV9aMTphmDE

https://www.youtube.com/watch?v=tvQUNsCc6Mw

Thanks a lot for the quick reply, David.
I’ll check both videos right away!

@Chazrox Hey everyone, I am currently running into the same issue with this setup. HISE crashes on Index 1 or 2, but works fine on Index 0. Even on a fresh project.
Did you anyone of you get this running the with other options? Would love to incorporate an oscilloscope into my plugin :)

@Ben-Catman
I don't plan to distribute it right now. For now, I just want the plugin to work without any problems. If the VST works well, I'd like to make it public (something like making a YouTube video and leaving a Google Drive link where it can be downloaded). And it will be ABSOLUTELY FREE.

If you'd like, I can credit you as the coder. Or leave a link to your social media accounts.

In any case, I don't currently plan to release it publicly for now. As I said before, I just want it to work well.

@Christoph-Hart

Hallo Christoph ;)
grüße aus Österreich :)

I was thinking about doing a little python script that creates the loop point meta data Hise needs for user samples. TBH i have never looked that much into your sample engine. Are there any specific metadata that hise needs? Would such a little project help the community ?

cheers

@David-Healey ahh, no they don't
this might be the issue (I'll try)

Okay, it's working now!
Thank you!

@Lindon ok more investigation..it really doesnt matter what you attach the LFO to its making nasty noises in the audio stream.....

@David-Healey said in Compile DSP networks as DLL keeps launching Export Setup Wizard:

@versusjona Yeah it's super annoying. We're waiting for @Christoph-Hart to remove it.

Close HISE Find the HISE app data folder on your system, in there find compilerSettings.xml and open it in a text editor. Add <ExportSetup value="Yes"/> below the <EnableLoris> entry. Save the file Reopen HISE

Thanks a lot for the quick reply, that did it!

Cheers,
Jon

@David-Healey @griffinboy @ustk Claude Code has done it :)

Whether it lives up to Christoph's coding standards we will have to see, but I did have the new Agents.md doc in the repo so hopefully Claude referenced that when making changes....

@Straticah yup checkout @resonant ’s link, someone already calculated the latency for you. So you just need an if/else statement to set the latency based on the octave amount.