Thanks for putting this together, it's the most useful comparison I've seen.

Full disclosure first: I make one of the options in the category you left out, self-hosted stores. It's called Alien XY (alienxy.com). So treat this as one view, not a neutral one.

To your "web app or plugins?" question, there's a middle path: run a ready-made store on your own server with your own Stripe account. Then the only fees are Stripe's, so close to your "Stripe on its own" row (about 4.3% on your mixed basket), with no revenue share on top. Alien XY costs $199 or $499 one-time, or $39/month if you want it hosted for you. It comes with licence keys and activation, file delivery, coupons and affiliates already built.

The catch, and it's a big one for you: it isn't a merchant of record. You'd be the seller, so VAT and sales tax stay your job, same as plain Stripe. Since you've said MoR is a must, it probably doesn't fit your case. I'm mentioning it for people who are already registered for VAT, or who sell mostly in places where that's manageable, and would rather not hand over 7 to 15% for good.

Happy to answer questions here.

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.

@ILIAM said in macOS Golden Gate! Compatibility Issues?:

My installers are currently not code-signed/notarized.

Get an Apple Developer account for $99/year. The process of code-signing and notarising is simple.

Installers work on your own machine because it's your machine. As soon as you use the installers on another machine, the gatekeeper kicks in.

It matters how you transfer files to your test machines. If you move stuff by USB stick, it doesn't get the 'scary downloaded from the internet' flag, and gatekeeper is more relaxed.

To test installers on another machine, they have to be downloaded from the internet, to simulate what a real end user would do.

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

@lijas90 said in Velocity layers overlapping issue:

I still get quite a noticeable jump between the different samples.

What kind of jump? Volume, tone, pitch, stereo field, something else?