@ILIAM I asked Claude:

Apple says a purchase can take up to 48 hours to process, so past that point it's usually stuck rather than slow, and waiting longer rarely fixes it.

The "Agreement signed: Apple Developer Agreement" email is sent for the free developer account, before any payment. Getting only that one, with no "Your order is being processed" email, suggests the purchase itself never registered, not that Apple is slow to activate it.

Things to check:

Account status: at developer.apple.com/account, see whether it says the enrolment is pending, or still offers a button to complete the purchase. Payment: check whether the card was actually charged or only shows a pending authorisation. A declined or held payment often fails silently. Identity mismatch: the legal name on the Apple ID must match the payment card and ID. Mismatches send the enrolment into manual review, sometimes with a request for a government ID. Enrolment type: if they enrolled as an organisation rather than an individual, Apple verifies the D-U-N-S number and signing authority, and days to weeks is normal.

The fix is to contact Apple Developer Support at developer.apple.com/contact, under Membership and Account. Asking for a phone call is far faster than email, and they can usually see what's blocking it straight away.

If the payment turns out never to have gone through, enrolling again via the Apple Developer app on iPhone or Mac tends to be smoother than the web. It does the ID verification in the app and bills as an in-app purchase.

This is from general knowledge rather than a fresh look at Apple's current documentation.

Videos:

https://youtu.be/4fBXh-8Lcgw

https://youtu.be/6qVCOTuVx3s

@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

@dannytaurus SoundSync can currently receive information related to the product’s operation and the customer journey, including:

When the plugin is opened or connects to SoundSync Activation, validation, restoration, and deactivation activity The installed plugin version The product and license associated with the activation A hashed installation/device identifier for managing activations Interactions with SoundSync-provided areas such as activation, account, store, support, and update interfaces Timestamps showing recent validation or connection activity

This can be combined with information already created elsewhere in SoundSync, such as purchases, products owned, downloads, customer accounts, support activity, email engagement, and marketing consent.

That makes practical things possible. For example, a developer could notify customers using an outdated version, help somebody who purchased but never activated, exclude existing owners from a promotion, or create a re-engagement flow based on meaningful customer activity, cart recovery, etc, etc.

SoundSync does not inspect or collect the customer’s audio, MIDI, presets, parameter changes, DAW projects, filenames, or what they are creating. We are interested in product lifecycle events that help with licensing, updates, support, and relevant communication, not the customer’s creative activity.

We also try to keep the principle fairly simple, collect the minimum information needed for the feature, be clear about how it is used, and give developers the controls they need to handle consent and privacy properly.

Some of this varies by integration. For example, the HISE package can report plugin-open and SoundSync interface events, while licensing integrations naturally generate activation and validation events whenever they communicate with SoundSync.

@David-Healey Of course, just don't draw most of the meter. Nice.

Converted the timer approach to LAF and it works exactly the same, except with 1.2s hard-coded hold instead of 1.5s, which actually feels better.

Thanks!