@dannytaurus

Okay, I finally got verified by Apple for the Developer Program! 🎉

From the moment I paid to getting fully verified, it took 4 days total — but 2 of those days were the weekend, so technically it was only 2 working days. That’s actually pretty reasonable!

I sent several emails but got no reply after 48 hours. Then I requested a call, and honestly, the call was quick, straightforward, and super easy.

The operator sent me an email, so I uploaded a scan of my passport. Then again… another day went by with no answer. 😅

Today I made another call, and while I was on the phone, the operator actually verified my account!

Funny thing — my name didn’t match the name on my government ID. He said, “We have a small problem here,” and I explained that it was my artistic/developer name. He changed it to my legal government name, and everything was sorted out in about a minute! 😂

Okay, I’m going to take a nap now… and then I’m starting the Mac signing marathon! 🚀

@dannytaurus Thank you SO much, Danny, for all your help! Really appreciate you! 🙏

@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 :)

@Mors If you used the current NAM training method (Tone3000, A2), it should work in Hise as well. Is your profile A1 architecture?
Yes training is under 48k but nam engine plays the model at 44.1k as well. Normally you shouldn’t do this.

I’m not using the current commit, but it does have NAM integration.

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

@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