Last modifiedby & filed under KSP Scripting (NI Kontakt) - Tutorials, KSP: Basics.

Please note that this article is not about choosing the best and cheapest server for your needs nor is it about any marketing strategies!

At the latest when all the work is done and your instrument is finally ready to be published, you probably start thinking about a best way to distribute everything including upcoming updates.

One of the best solution (probably for everyone) is to separate the samples from the nki and resources. Which means offering at least two separate download files to your customers/users. One zip for the samples and one for the rest (nki, nkc, nkr etc).

In this way, we save a lot of time by not constantly uploading several GB to our web server/cloud. Because usually updstes only affect the nki not the samples. So there is no need to also upload the samples. But exactly this happens if using one zip file for everything (or if using Kontakt’s monolith mode).

And don’t worry, if there are updates to be made to any of your samples you can still update them individually. Either by offering a third file or by adding them to the smaller nki zip.

This introduced practice here also reduces the server bandwidth. Imagine if thousands of users/customers download the update with all the samples instead of just a tiny update file (the nki zip). It probably even saves you lots of web space .. in case you want to keep an update history, which can be very useful.

 

Distributing your Kontakt Instruments & Updates

Basically there are two variants which are not that different. One or the other may be suited better, depending on your or your customers preferences. Of course the variants can be mixed.

VARIANT A – 2 files in total

ksp-best-update-practise-zip-samples

upload & initial downloads

  • create 2 zip files:
    > One for your samples (the whole sample folder, including all sub folders).
    > One for your nki file plus nkr & nkc files also data folder (and resource folder if you wanna publish that one, learn more).
  • Upload both zips to your server.
  • When doing updates only upload and exchange the 2nd zip with your nki, nkr & nkc files
  • initial customers: offer both files for downloading. The large sample pack plus the latest update file with the nki, nkr & nkc. The customers marry the files again by extracting both zips to the same folder.

nki or nkr updates

  • simply offer only the nki zip-file.
  • tell your customers to overwrite all files

note: if you are only updating your ksp code and if you are working with externals script files (but not using the script tabs), you could just distribute the nkr file.

ksp-best-update-practise-zip-samplesA
  • only put all updated samples into your sample folder
    make sure you keep the correct file structure, which means adding the complete sample folder plus sub folders to your zip. But only add the updated samples of course.
  • add the sample folder to the nki update file
  • tell your customers to overwrite the sample folder with the new one.

Note: of course you can also create an extra third file for the updated samples, like described in Variant B.

VARIANT B – multiple zip files

ksp-best-update-practise-zip-samples ksp-best-update-practise-zip-all

upload & initial downloads

  • create 3 zip files:
    > One for the samples (including the whole sample folder structure + sub folders).
    > One for the nki file, nkc and nkr file.
    > One Major Zip File, containing everything: samples and nki, nkr, nkc files
  • Upload all 3 zips to your server.*
  • initial customers: offer the major zip file containing everything.

*) note: the first “sample only” zip is actually not required but you should still upload it to your server. Just in case!

nki, nkc or nkr updates

  • initial customers: offer the major zip file + the update file
    don’t forget to give instructions: the users must now overwrite the old nki, nkc,..  etc again!
  • recurring customers / updates only:  like Method A simply offer the small updated “nki-zip”

note: if you are only updating your ksp code and if you are working with externals script files (but not using the script tabs), you could just distribute the nkr file.

sample updates

ksp-best-update-practise-zip-all
  • create a 4th file for all updated samples only and offer it separately.
  • make sure you keep the correct file structure, which means adding the complete sample folder plus sub folders to your zip. But only add the updated samples of course.
  • tell your customers to overwrite the sample folder with the new one. The old samples should remain intact

 

 

How useful was this article?

Average rating / 5. Vote count:

No votes so far! Be the first to rate this post.

We are sorry that this post was not useful for you!

NOTE: highly negative votes may be removed without any reasonable given feedback!

Tell us how we can improve this post?

Leave a Reply

use <pre></pre> to wrap code blocks

use <code></code> to wrap small code snippets

Your email address will not be published. Required fields are marked *