@David-Healey Thank you for doing this. It really helps me in my Hise Sampler quest!

@Christoph-Hart Ok so thanks (or not) to Claude I could implement it fully after fixing many bugs. Obviously, this certainly has some AI non sense and I would be interested in your insight 😉

But it works a treat in context!

Here's the PR: https://github.com/christophhart/HISE/pull/1055

And a more readable bug fix report than the MarkDown: https://gold-reggie-20.tiiny.site/

@Sounddiy the warning icon is telling you what the problem is. the doc says:
https://docs.hise.dev/scriptnode/list/core/extra_mod.html

Note that these two modes are mutually exclusive and you cannot connect a root parameter to a target while having a extra_mod node connected to the same index. If you do so, you'll be greated with this aggressive warning icon:

In fact the connection is happening behind the scene. So just disconnect your parameter and connect the extra_mod node to your FAUST parameter. The index of the node becomes you selector.
So 4 parameters = 4 extra_mod nodes, and indexes 0 to 3.

@dannytaurus Voted, I don't see a per-currency breakdown in Moonbase though so not 100% sure about the split.

@dannytaurus Thank you so much Danny 👏
Sure.
I'll post what happened with you 👏

@AlienXY I'm very sus of popup AI generated sites. It might be totally legit but I'd need to be convinced.

The problem with Kontakt was never really the software. It was the ecosystem (native access), NI's licensing, ads in the home screen, and the proprietary source code meaning developers had no control over the software.

Koda might solve some of those issues, but it seems to me that the main one - control - is why most of the big developers left Kontakt to create their own samplers, and Koda won't solve that. Others have tried, Gorilla engine, Decent Sampler, Falcon, etc. Developers want control and you either use an open system like HISE or you build your own proprietary system.

FOUN IT . thanks.

Nice... Congrats !👍
But how can we export looped samples ? Piano/ pluck sampling is very easy.

@tobbentm Great to hear! 🙌

@gp_ it seems to happen when you disconnect or change an interface Hise had in memory when it’s close, then when you start it again it doesn’t find it and throws this warning.

Since when Hise has an issue or crashes it doesn’t rewrite the memory, it will happen next time again and again. The same thing happens with the window configuration since it is saved only with a proper close without issues, recalling an old window configuration (this time without a warning like the audio interface one)

Instead, Hise should save the configuration (audio, midi, windows, etc) as they change and not when closing the app.

But usually for the interface if the configuration doesn’t change between Hise sessions the warning should just go away

@shashwatshukla I think I'm the only person using this feature so the info I gave you is probably all there is.

@dannytaurus I don't know, I was just told Golden Gate, it's not my customer it's a third-party's

@marceau-dng said in Not finding LoadNAMModel:

I installed the latest version with the launcher btw

Build from source

@David-Healey Thanks ,appreciate it!

Wow congrats bro! I can't wait to try it

@cartemtune Thanks, none of these are ai btw 😊
But I get it AI is all over the place...

So in the end is this fixed with HISE_COMPLAIN_ABOUT_ILLEGAL_BUFFER_SIZE=0 or the issue persists?

If this flag becomes mandatory then it should simply be the default behaviour...

Came here trying to learn something about instrument design and somehow ended up learning about decompiling laws and the current state of Claude