@justmull I asked claude to impliment this fix on my project and it said:

The generic forum patch would actually break UI-driven automation in HISE since its getValue() updates before notifying the DAW. I'll apply the narrower fix that only affects the DAW-to-plugin path instead.

and instead did:

I applied the fix in ScriptComponentWrappers.cpp:3137. When Ableton sets a value, HISE now records it, so the later update matches and nothing gets sent back to Ableton. Values that change from the plugin's own UI still get reported, so recording automation by turning knobs still works. It's the only change in that file, and git checkout -- hi_scripting/scripting/api/ScriptComponentWrappers.cpp in the HISE folder undoes it. I left your existing uncommitted changes to the .jucer and AppConfig.h alone. You don't need to rebuild HISE.app for the plugin. The exported Xcode project compiles HISE's source folders directly, so re-running ./build_mac.sh (with the version bumped) builds the fix into the VST3 and AU.

I'm about to test and see if it worked. I mainly just wanted to chime in as I've been trying to figure out this issue for weeks now, as Ableton is my main daw and I have been trying EVERYTHING I could inside HISE and my scripts to troubleshoot. And for some reason I didn't think to search the forum for Ableton specific issues until I did some searching on google and its AI told me that it was likely ableton specific issue.

I am also curious if this is new behavior due to a change in ableton? Because I could swear I had this working fine in an old version of my plugin last year.

@cartemtune thanks folks! So Australia, New Zealand, and Japan seem to be the countries that I need to take a look at. I actually can easily unblock these countries on my store and set up custom tax rates on my store so I can at least collect the taxes, but I definitely need to do more research on how to remit them correctly. maybe after that then I'll start thinking about moving to an MOR if I need to. I'm just already so cozy here lol migrating platforms is so much work :')

@dannytaurus Thank you so much!

Started the process and Whish me LUCK :)

@resonant Yes sir im using A1, A2 isn't working for me at all it just crashes everytime when i try to load it, apparently its something to do with the top level architecture of A2 being SlimmableContainer which HISE isn't liking and A1 being top level WaveNet which works fine! Any ideas if im doing something wrong there?

@dannytaurus Haha, well I looked into it anyway. Seems like I have to use Wise assets to get the interest thingy, I checked with the bank I use for my savings account and if I open a new account I get 4% there, so that's what I did :)

@David-Healey Thank :)

@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/

@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.

@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...