Just throwing my 2c in - I've just moved from Payhip to a more dedicated stack (Github Pages + Cloudflare for frontend, Polar as MoR / processor).

I've had a positive experience so far, very easy to setup and the API lets me run sales by just pushing an update to a config.json file - the Github actions & Cloudflare workers take it from there. They use Stripe for payment processing so it's pretty straightforward.

Payhip was a great alternative to Gumroad, but over time I found their load speeds were getting slower and slower. I'm not sure what the reason is, but I had page loads of up to 20 seconds (simple home pages, it wasn't a content issue). This included checkout and was likely inflating bounce rates like crazy. They also have limited metrics / analytics, and my entire site was basically HTML injected so I didn't need the page editor / designer tools.

Now everything is hosted on Cloudflare and I get sub 1s page loads, the Polar checkout is just an iframe.

When it comes to Trustpilot reviews - be aware that a lot of people try and use Polar, Payhip etc to sell lazy, low-effort products like e-books, .pdfs etc. They then promptly get banned from the platforms and then leavy a crybaby negative review saying they got scammed.

This was a very recent move, so I haven't completed a payout yet through Polar, but I've been in contact with their support (had to verify my ID and the Stripe ID checker wasn't working on my old ass Australian ID card) - they replied within 48 hours both times and the communication was crystal clear.

@dannytaurus said in Payment providers compared:

Whether Polar charge their 50¢ on a free ($0) download. None of them says. If you give away a lot of free products, ask first.

I've had a few hundred free product downloads over the last week or so - no fees from what I can tell. There's not even a payment form for free products or 100% discount codes: free is free.

The one sort of "downside" I guess is there's only checkout embeds, no cart / add-to-cart (you'd have to roll your own). And no Paypal from what I can tell, I'm not sure how big of a deal that is - Amazon doesn't use Paypal.

If I do come across any negative experience I'll update this post, but so far Polar has been great all around. I've just requested my first payout (only $50) and their docs say they can take up to 2 weeks which isn't a big deal really. Larger payouts might take longer.

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.

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