Yes, I hope to manage to do so. I'm trying to write a script that will handle all scenarios, nkx, ncw, wav files... If I cannot do it, I will provide a script for wav files based library at least as I already made one for my own use.

 

LiTE Converter 2.0 is released! See first post for download

- NKX unpack added (no compression support)
- WAV support
- Lots of improvements

Set your variables, just drop your library in source folder and enjoy your lite version

Please submit any bug or error found here.

 

Can I just use the previous settings file from the previous version? That way I can just drag and drop the new one and not need to set the variables and directories?

 

Almost but no. Some essential variables names changed, so I recommand you keep the new file and copy your previous path into the new file.
$ncwdir is now named $sourceDir and there is a new $nkxTemp path to edit for handling NKX libraries.
Unless you use SSD only, you should keep 2 differents letters for path that are on different drive on default settings.
Let's say C: is disk 1 and G: disk 2, you should use disk 1 for $sourceDir and $16bDir, and use disk 2 for other paths.

If you really want to keep old file, you must at least rename $ncwDir variable to $sourcedir, and you won't be able to handle NKX based library until you use the new variables file.

 

I just copied the paths over and made a new one for nkx, the actual text format was different so I couldn’t replace it entirely, I actually have everything done internally so it’s quicker and I just make sure there’s room for the tool to work. Haven’t tried everything just yet but once it comes up I’ll get to see how well it works!