ananmusatili
Member
Ok, so I've been messing about with Kontakt for long enough to notice things. And one thing, which annoys me, is that quite many of the developers who create the non-licensed libraries, don't utilize the snapshots at all but just give folders of NKIs.
While you can easily utilize the quick-load folders, it does make managing the libraries more hands-on than would be necessary if the snapshots were utilized.
And here I mean the kind of instruments where the multitude of NKIs utilize the same exact engine with just different settings.
My question here is --> Why don't many of the developers use the snapshots at all? Is it because a lot of users don't have a clue how to install them, or is there some other reason I'm missing?
Now I need to save them from scratch to make the workflow easier for myself to not have play with the quick-load structures so much.
This is pretty cumbersome as each NKI creates their own snapshot folder in the \User Content\Kontakt\ folder from which I then have to copy them to the main instrument folder. At least I've not found an easier way to handle this.
While you can easily utilize the quick-load folders, it does make managing the libraries more hands-on than would be necessary if the snapshots were utilized.
And here I mean the kind of instruments where the multitude of NKIs utilize the same exact engine with just different settings.
My question here is --> Why don't many of the developers use the snapshots at all? Is it because a lot of users don't have a clue how to install them, or is there some other reason I'm missing?
Now I need to save them from scratch to make the workflow easier for myself to not have play with the quick-load structures so much.
This is pretty cumbersome as each NKI creates their own snapshot folder in the \User Content\Kontakt\ folder from which I then have to copy them to the main instrument folder. At least I've not found an easier way to handle this.