No way to save Kontakt instruments using a script, that's the biggest lack in automation, and it won't change.
Simple mode does not affect the structure at all, so the samples remain all here at the same location (folder, NKX...). This way, the instruments still find samples where there supposed to be and are not affected by 24->16 bits conversion. That's why I call it simple mode, because it avoids any operation in Kontakt.

It won't help for your previous conversions, but if you make a new full conversion using simple mode, you shouldn't have any issue with Kontakt when loading patches. Downside is that you cannot remove microphones or affect library structure in this mode, that would require some instruments changes in Kontakt.

 

I don’t need to remove microphones generally but I could possibly download the libraries I’ve shrunk again and have them reprocessed, I just want to know if I can put multiple in the input folder and they’ll all be separated and processed before coming out with their original structures

 

Yes, you can either create a txt file with the paths of the libraries you want to process (one per line) and choose menu "3", or put a "batch" folder in your source directory, and put your libraries in it. It would batch process the libraries.
Refer to the manuel in help folder if you want more details.

 

Cool script, I have a few questions:

1. Can the script create log files which only detail errors? I've tested it out a bit and can only see errors by sifting through the huge amount of console information it displays.

2. Is there any reason you shouldn't minify libraries other than keeping a 1:1 archive of the original? For example does 24bit -> 16bit result in an audible loss in quality? I've tried looking into this subject and there's a lot of conflicting information.

3. Which dither setting would you recommend for the most transparent quality? I've chosen 6 based on the information in the pdf but I'm unsure, I just want smaller libraries whilst keeping the sound quality as close to the original version.

4. Is it possible to make the script use less system resources? it causes my system to hang at certain points even with a relatively good PC, I tried messing with the process affinity and threads but no luck so far.

Feel free to point me to another post if this has already been asked.

Overall it looks like it's worthwhile converting libraries given the insane cost of hard drives and particularly SSDs these days.

Thanks yodadl & anyone who responds

 

Last edited: Jul 21, 2026 at 5:36 PM

There’s always a reason to keep the libraries shrunk, you’ll have more room for more libraries or other things… unfortunately some fail to shrink so they probably get kept at their 1:1 ratio, I usually just compress to 7z the ones I don’t use much that fail to shrink… the only reason I can think of to leave a library at full size if you’ve held onto the files for years and don’t want to tamper the date modified or something, like I have Kontakt libraries from 2020 I have not reached yet but I’ll probably just make a copy and use Mac to replace the samples with newly created shrunk versions either redownloaded or copied from the original folder.

 

That's true, based on the couple I've tested so far there's an impressive amount of space to be gained. Although I'm unsure what the downsides are to making everything 16bit, have you noticed any?

 

24 bit to 16 why would you want to? I reckon we're not getting the quality of product we think we are, ok if your just testing libraries and samples but not for serious productions.

 

I did 200 gig of stuff I never use! Saved 100gig!

 

The log should contains all the script errors, but there is a limitation to the script errors, not tools error.
I capture tools output to display one screen but logging everything would create huge logs and I didn't want to.
Not sure I can filter error from tools outputs so maybe I can add a parameter to enable log of all outputs but it will grow fast especially for big libraries.
If you encoutered errors, I am curious to know what they are, feel free to report anything that might be interesting.

Simple mode makes a 1:1 archive, mainly to remain simple for all users and allows to minify a lib without having to make any change in Kontakt, which could be a real pain, I made it for small to medium size libs (10 GB to 5GB is not so bad) and beginners.
Of course you can use advanced mode to make lighter libs by stripping microphone or instruments but you will have to work manually in Kontakt after.
Dithering is a process needed when you reduce depth to avoid distortion, it adds a light background noise, that is not noticable for most humans beings. If you feel concerned about sound alteration, you should do some research, you can find very good videos on Youtube and forum posts on the subject, if I can remember I will put a link here.
I set autoblank option in the script to avoid background noise when a sample is silent so the noise is only present melted with the sound, making it barely audible.
So at the cost of a noise you will probably never hear in your music work, you can seriously reduce size, this is interesting, and doing this you also reduce memory footprint by almost 2, which is even more interesting especially if you don't have a workhorse computer.

I set the dither profile to 1 by default because it is the most all around and "flat" curve of noise shaping, but 6 is the new recommended value by the author of Resampler. As the noise shape curve is slightly pronounced, I was afraid to build an audible noise when applying to library samples, but I never tried and without sound analysis you probably won't be able to hear the difference. When using Izoptope RX to analyse, the profile 1 is the most "neutral" so I decided to set it by default. But I can be wrong and maybe it's better to use 6.
I guess depending on the library you process you also might get some benefits to use one value or another.

I think you can always shrink a lib, but sometimes tools like conncw fails to unpack samples but there is always a way by collect samples in kontakt, save 24bits wave from Kontakt, then convert to 16 bites and compress back in ncw. You can use lite converter for some steps, but yes, you have to make some steps manually.

 

Last edited: Jul 22, 2026 at 6:44 AM

If you find errors just skip it and try another.

 

No, other than having to locate samples but I think the new version should fix that

 

Yes, but using simple mode only. If structure is modified in any way, you may be prompted for missing samples.

 

When I run "LiTE_Converter_Config" it just opens and closes (I tried running as admin as well). I'm using Windows 10 and also installed .NET Framework 10

I get this message for a split second

 

Last edited: Jul 22, 2026 at 4:46 PM

Oups, I don't know why it closes the script, I have to fix this, but here is a simple fix: go in the scripts folder inside Lite Converter directory, edit variables.ps1 with a simple text editor (notepad is fine) and replace the drive letter "G" in this line with one that exists on your system:

Code:

$liteLibDir = 'G:\LiTE_Converter\LiTE_Library'

If you have a drive D: you may set it like this, but any real letter will be fine.

Code:

$liteLibDir = 'D:\LiTE_Converter\LiTE_Library'

Save the changes, you will then be able to start the config script and set exactly the folders you want with the utility.

 

Now it opens correctly and displays the interface!

 

Nice, I fixed it in the config script, it will be included in the next update.

 

I guess I wouldn’t have used G:\ because I changed the paths variables immediately upon updating to the ones I used previously and I don’t think any of my drives used “G”