@dannytaurus the only thing I'd add is that the 3% conversion fee is carried by the buyer by default, so you don't technically pay that.
This is the alternative to listing in EUR for example, where the buyer would still pay the conversion fee, just through their card provider instead.
The end result should be that you get the same net amount in either case.
If you hard-code a GBP price, you should include the conversion rates in that price to get the same effect.

I totally get this is not great if you expect GBP in your account at the end of the day, so I hope we can add support for more holding currencies by the end of the year.

@AlienXY I'm very sus of popup AI generated sites. It might be totally legit but I'd need to be convinced.

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

@David-Healey Great info. Thanks!

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.

@Christoph-Hart Great, thanks.

Where do I get a copy of the current licence? I was never sent one when I started paying.

@dannytaurus said in No-argument sort() is a no-op on strings - bug?:

So you think the docs are wrong, rather than it being a bug?

Could be either

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...

@ustk Yeah, good idea. I asked Claude if the version reports as an invalid number, or just as 0.0.0.

The AU plist has AudioComponents.version = 0. Pluginval decoded that as v0.0.0. JUCE’s decoder explicitly formats the packed integer 0 as 0.0.0.

0.0.0 is valid as a semantic version, but AU metadata uses a packed UInt32, not a SemVer string.

In practice, hosts treat raw value 0 as “version unset.” Logic therefore labels it invalid, while pluginval merely displays the decoded value.

For 0.0.30, the AU field should contain integer 30. The bundle’s separate CFBundleVersion can remain the string 0.0.30.

@dannytaurus agreed about Claude, has become unusable in my opinion, deep dives and minutes of ruminations for simple questions, eats tokens like crazy.

I use cursor for everything now.

@Lindon

Sorry yes my typo...

Glad you weren't being charged 5% 😂

PRs for fixes here:

#1024 Make the "Default" font honour the requested size and measure consistently

#1025 Fix out-of-bounds read in the string width table for non-ASCII characters

@dannytaurus Interesting, looks like they are also phasing out Intel support when they eventually limit the minimum deployment to 27.0 - probably a few years yet.

I'll just stick with my existing build system for now until it no longer works.

@David-Healey Yours always seems to be more generally useful than mine though 😂

This one is pretty niche but I'll likely be using single column preset browsers in most of my plugins, so it's really useful for me.

@Orvillain said in Why I'm not making a Windows installer (nor code-signing):

Interesting, I wasn't aware of that. More details would be lovely! Private message if you need to :-)

https://forum.hise.audio/topic/14949/why-i-m-not-making-a-windows-installer-nor-code-signing/13?_=1785506496174

Update: Claude-generated gist here of the suggested patch: https://gist.github.com/weavermedia/3fc4a419920fcda8de389a89d7aec68d

@Christoph-Hart I've merged the new commit and it no longer crashes, just shows some ugly errors. Is this intended as a stop-gap solution? Because isDefined() still returns true for the none-existent function.

Edit: Oh I see, it just stops the execution at the "error"

Tried your suggestion and appears to be working here, maybe a preprocessor definition (default true) to protect older buggy projects?

I found when unloading a Full Instrument Expansion the automation xml was getting wiped. Made a little PR to fix it.

@David-Healey Makes sense 👍