Packaging Instruments Guide?
-
Hi, I'm new to HISE (from Kontakt) and just trying to package my first free small instrument..I've been scraping around for info and have starting making the dmg file, but thought I'd ask if there's a good guide on best practises for packaging for both mac and pc? A walkthrough video from @David-Healey would be the ideal thing! I realise I need to use things like Inno / Packages, but would be great to get help with setting these up, as well as things I need to know such as licensing, encryption (for when I release something commercial) etc. I've also seen people say they've create custom scripts for eg. automating sample file installation along with the vst3/au files..things like that would be great to know. I'm more a musician who learnt to code in Kontakt so all this is a bit new to me. Thanks in advance for any help!
-
@jonalexander23 I prefer Packages (pkg) to dmg, but either is fine. I have a couple of video on YouTube/Patreon about using Packages.
On MacOS you'll also need a developer account so you can codesign and notarize your plugins. Otherwise users won't be able to run it on their system.
@jonalexander23 said in Packaging Instruments Guide?:
things I need to know such as licensing, encryption (for when I release something commercial)
If you're releasing an open source plugin then it should be under the GNU GPL. If it's proprietary then you'll need a HISE and a JUCE license. The price you charge makes no difference here.
@jonalexander23 said in Packaging Instruments Guide?:
ve also seen people say they've create custom scripts for eg. automating sample file installation along with the vst3/au files
Simplest solution is to use HISE's built in sample installer. You ship the data/installer and the samples as separate files. Then in future when you need to update the instrument's data the user doesn't have to redownload all the samples again. This also makes it easy for the user to choose where they want to install the samples.
-
Great thanks! I just saw your YT vid 'Automated Exporter Script for Mac OS'..but I think you mentioned in another post it's now a bit outdated, or can I use this instead of Packages? For PC I guess I will try Inno Setup. Thanks again.
-
@jonalexander23 said in Packaging Instruments Guide?:
or can I use this instead of Packages
The script uses Packages. Don't use the script though until you can do all the steps manually.
-
After spending all day trying to manual package, codesign and notarize, I've got as far as notarizing..I've been following the Notarising For Dummies thread and it seems some of it is out of date as altool no longer works (I get an error in Terminal 'ERROR: [altool.600001C484C0] ArgumentParsingFailure("Missing or no command argument specified.') - someone on the net said it became unusable about a year ago.
I'm pretty disillusioned regarding being able to use HISE even though I love creating in it - due to this crazy OS packaging process which seems to change from year to year by the looks of things...maybe there's plans for HISE to handle this part for non-experienced bash coders like me?
-
@jonalexander23 This is the guide I used: https://www.kvraudio.com/forum/viewtopic.php?t=531663
Free HISE Bootcamp Full Course for beginners.
YouTube Channel - Public HISE tutorials
My Patreon - HISE tutorials -
@David-Healey thanks for that, I will try again tomorrow!
-
@David-Healey It would be great if we had HISE-approved guides for creating installers for all platforms. Everyone can reference them, and as soon as something stops working we can report back, fix it and update the guide.
Your videos are great but as soon as the info goes out of date they're more confusing than helpful.
If we had written docs they would be much easier to update, and can be timestamped to give the reader some amount of certainty that they're up to date.
-
@jonalexander23 said in Packaging Instruments Guide?:
I'm pretty disillusioned regarding being able to use HISE even though I love creating in it - due to this crazy OS packaging process which seems to change from year to year by the looks of things...maybe there's plans for HISE to handle this part for non-experienced bash coders like me?
this is an issue with Apple not HISE, - welcome to plugin development - where eventually you end up hating Apple Corp.
