Thank you for your kind words on the library..!
I apologize for the download issues. We rely on Fastspring which uses the Amazon S3 Platform. Usually it's really fast, but in some cases (and randomly) it can be spotty for some countries. Other systems from other developers are based on same platform too, so it can be an occasional problem. A downloader might help, to just load the files and find them on your PC after a bit.
About the extraction we usually asks our user to use UNRARX, WinRAR or 7zip because on default they extract the libraries inn the right way. Other tools often don't support multipart rar (like stuffit or the unrachiver) and also they tend to create very strange folder structures.
We have to make a video to show accurately how to extract the libraries, but some info can be found on our FAQ page.
Basically you should have just the patch files in a folder and the samples files in a subfolder of it, let's say Dominus Choir Samples folder.
So the file structure is
MAIN FOLDER \ Dominus Choir Samples <- THIS IS A FOLDER :-)
MAIN FOLDER \ Dominus Choir.nki
MAIN FOLDER \ Dominus Choir.nkr
MAIN FOLDER \ Dominus Choir.nkc
MAIN FOLDER \ Quick Reference Manual.pdf
So you won't have any missing file. With a common Windows extractor you just can right click on the patch named rar file and the first of the samples.part1 files and select Extract Here. With UnRarX you can just open those files (or drag them into UNRARX window) and they will be automatically extracted.
It seems clumsy but this procedure is the very same for all our products and a lot of other products from different developers. We considered alternative easier solutions, but at the moment, neither seems ideal for us (we risk just to end with other different problems).
So maybe a video would be helpful.
About the library, I don't precisely understand your issue. If you get releases that are longer than wanted on the last syllable, it's possible that one of more of the keys are not released at the same time. This is done, because we want that for example the release S of DOMINUS would be heard when you release all the keys, but also that if you move an entire chord to another position on the last U you get a legato transition to the new notes. This behaviour can be adjusted by lowering the release / legato knob, but in general if you have recorded a sweet midi part, you can fix this by making the ending part of the released notes a bit more coincident with editing (like in a 300 ms timeframe), or be more "precise" when releasing a chordal part.
I realize that this may not be an ideal workflow for everyone and I'll look into this further to come up with a better solution (I have one in mind but I have to test it). We have something in mind for this library. I hate to promise things, but I enjoyed so much working on it and it has been having so warmly welcomed that it will be nice to add some useful things soon. We tried to stay simple, because the simpler it is the more "magic" it feels, to me :-)