<![CDATA[Automatic license file placement, like user presets]]>Any interest in this as a PR? Or are you all handling license files in your installer?

I extended HISE to write the project's LICENSE.txt file into the AppData folder on first launch.

Same mechanism as the UserPresets system.

  1. When you compile the plugin VST/AU, it looks for a LICENSE.txt file in the project root
  2. If it finds one, it bundles into the embedded data
  3. On first plugin launch, it writes the LICENSE.txt to the user's AppData folder, next to UserPresets
  4. It respects the version number, same as UserPresets, and overwrites if the version has changed
]]>https://forum.hise.audio/topic/14864/automatic-license-file-placement-like-user-presetsRSS for NodeSat, 20 Jun 2026 13:57:30 GMTSat, 20 Jun 2026 10:29:13 GMT60<![CDATA[Reply to Automatic license file placement, like user presets on Sat, 20 Jun 2026 12:38:44 GMT]]>Why not just verify if it's on the disk or not and pull it from the server?
Assuming plugins are connect to the internet for your license system in the first place...

EDIT: or even simpler, pull it at the same time you pull the plugin's license...

]]>https://forum.hise.audio/post/121393https://forum.hise.audio/post/121393Sat, 20 Jun 2026 12:38:44 GMT<![CDATA[Reply to Automatic license file placement, like user presets on Sat, 20 Jun 2026 11:16:02 GMT]]>@David-Healey said in Automatic license file placement, like user presets:

the first page of the installer and it's on the website

Yeah, that's all I was going to do too. But then I thought some persisted version on the user's disk might be good too.

I think probably the best way is to show it in the plugin, even if it's a footer link in a settings/credits panel.

That's the only way to be sure that the license always travels with the plugin.

]]>https://forum.hise.audio/post/121392https://forum.hise.audio/post/121392Sat, 20 Jun 2026 11:16:02 GMT<![CDATA[Reply to Automatic license file placement, like user presets on Sat, 20 Jun 2026 11:03:45 GMT]]>@dannytaurus I show it in the first page of the installer and it's on the website. Adding it into the app data folder too seems like a good idea so I might do that.

]]>https://forum.hise.audio/post/121391https://forum.hise.audio/post/121391Sat, 20 Jun 2026 11:03:45 GMT<![CDATA[Reply to Automatic license file placement, like user presets on Sat, 20 Jun 2026 11:02:47 GMT]]>@David-Healey Gotcha. Problem with that method is keeping two separate copies/formats of the license text in sync, assuming you also want to display it on your website/elsewhere too.

I'm not even sure how I want to show/store the plugin license yet.

I looked at a bunch of other (well-known) plugins on my system and can't find any licenses/EULA files for most of them.

They either have it in a panel in the plugin, or it's just on their website.

]]>https://forum.hise.audio/post/121390https://forum.hise.audio/post/121390Sat, 20 Jun 2026 11:02:47 GMT<![CDATA[Reply to Automatic license file placement, like user presets on Sat, 20 Jun 2026 10:50:07 GMT]]>@dannytaurus I'd include the license in a .js file, then use File.writeString() to put it into a file in the app data folder.

]]>https://forum.hise.audio/post/121389https://forum.hise.audio/post/121389Sat, 20 Jun 2026 10:50:07 GMT<![CDATA[Reply to Automatic license file placement, like user presets on Sat, 20 Jun 2026 10:33:46 GMT]]>@David-Healey How would you do it with script?

]]>https://forum.hise.audio/post/121388https://forum.hise.audio/post/121388Sat, 20 Jun 2026 10:33:46 GMT<![CDATA[Reply to Automatic license file placement, like user presets on Sat, 20 Jun 2026 10:30:41 GMT]]>@dannytaurus I include this in my installer, you could also do it through a HISE script.

]]>https://forum.hise.audio/post/121387https://forum.hise.audio/post/121387Sat, 20 Jun 2026 10:30:41 GMT