Holy cow! Thank you for such a comprehensive comparison. I wanted to provide some additional info as well as a little bit of correction based on my own experience. I used to be on gumroad, migrated to payhip, and then subsequently reached out to payhip's support team after danny's post on another separate thread and I thought I'd share:

Migration from other platforms: Payhip does offer help with moving product listings over from Gumroad. In my case, they used my Gumroad store URL to recreate the listings on Payhip for free. My understanding is that they copied the text and images from the public pages. You still need to upload the actual product files yourself so this isn’t a full account migration with customers & order data. They actually even offered to "fully furnish" my store too (for free), but I decided to do that myself

Sales taxes: I am aware that Payhip automatically collects and remits sales tax/VAT for the US, Canada, UK and EU as a marketplace facilitator (not MOR). Outside those regions, you’d need to work out your obligations and handle any required collection and remittance yourself. You can configure custom tax rates in your payhip dashboard, but that doesn’t take care of registration or filing for you.
Is this set up accountant-proofed? Yes, but I’m in Canada so I can't speak for other countries. I’ve checked my own setup with my accountant, everything is a okay.
I’ve only opened my store to the US, Canada, UK and EU so far, so the payhip automatic tax handling coverage hasn’t been an issue for me yet. But Danny's point about 15% of sales coming from elsewhere definitely makes me curious about what I might be missing xD I would love some extra $$$$ and I'm looking to see if I can just open up a few extra countries with my current set up so I don't have to do a full migration elsewhere

Marketplace facilitator vs MOR: If you're like me and your head is spinning with all these jargons, I also asked Payhip’s support team about the tradeoffs between their setup and an MoR. Obviously their answer would be biased, but here's what they said: An MOR handling refunds and disputes doesn’t necessarily mean the seller avoids all the costs. You'd still to check each provider’s refund fees, chargeback terms, payout schedule and reserve policy.
My personal finding on this is that: e.g. Gumroad has a $100 minimum payout balance. This is likely because they are an MoR and need to cover their sellers' refunds and chargebacks when they happen. I also noticed that Paddle also has a minimum payout of $100 and the payouts aren't instant either i.e. only on the 2nd and 15th of every month

Lemon Squeezy: I agree. I think this company is being phased out. I have been following with them when I was first looking to move away from gumroad and their Twitter/X account is filled with only motivational quotes for YEARS now xD I don't see any notable new features at all since the acquisition. That's definitely not a good sign. I would AVOID!

You’ve got me curious about Polar and Moonbase now. Would be interested to hear how the actual checkout and customer experience compares once you’ve tried them. Please update 🙏

@cartemtune thanks folks! So Australia, New Zealand, and Japan seem to be the countries that I need to take a look at. I actually can easily unblock these countries on my store and set up custom tax rates on my store so I can at least collect the taxes, but I definitely need to do more research on how to remit them correctly. maybe after that then I'll start thinking about moving to an MOR if I need to. I'm just already so cozy here lol migrating platforms is so much work :')

@dannytaurus Thank you so much!

Started the process and Whish me LUCK :)

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

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

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.

@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

@David-Healey Thanks ,appreciate 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.