@tobbentm Yeah I just noticed it in my account :) I don't the pricing can compete with SES but it's nice to have it integrated, and a lot of people can't get on SES it seems. Would it be possible to use our own SES subscription with Moonbase's mailer?

7949224b-45a2-4f8f-a23e-d77a5760736d-image.png

@tobbentm said in Payment providers compared:

There's certainly a difference in price, but also a massive difference in features and mindset behind the platforms, so I hope you all also consider everything else you need when selecting each, vs what is included in these prices.

By switching to Moonbase I massively reduced my costs elsewhere.
I no longer pay for hosting/data transfer costs, this means I'm able to have a cheaper VPS for my website, this was about a £30/month saving.

I was also paying annual fees for several wordpress plugins:

WooCommerce tax calculations Software licensing Amazon S3/Bunny A plugin that sends WooCommerce data to my accounting software Currency conversion plugin There's probably a few others I'm forgetting.

I also don't have the quarterly headache of dealing with VATMoss.

It looks like several of the other options would also offer some of these features too. I'm very happy with Moonbase though, it was easy to integrate. I've been able to add custom functionality with a few PHP/JS snippets. The support is very good and I actually get to talk to a real person! And new features are being added all the time.

Also, is anyone here running macOS Golden Gate who could test one of my installers for me? I’d really appreciate it!

@donto it does not open just delete build folder

@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

has anyone tried KODA more comprehensively? would love a more in depth review!

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