Menu
What's new
By:
Filters

Why "Batch Resave" in 2023?!

whinecellar

whinecellar

Jim Daneker
Seriously... been wondering forever... why does this exist? Why can't Kontakt be smart enough to

(1) assume the necessary files are in the containing folder that's the norm for pretty much every Kontakt library (which it kinda does, but then...)
(2) load everything as fast as it does after doing a Batch Resave... why not just default to fastest load times
(3) allow a batch-Batch Resave... in other words, allow you to select a whole bunch of Kontakt libraries and batch resave them all at once

I'm on the tail end of installing a new Mac from scratch, and I loathe the thought of having to do this yet again for 100 or so Kontakt libraries. I could leave it alone, but knowing the increased speed will add up over the next few years, it's worth trudging through molasses in January, I guess.

But again, WHY???
Click to read more...
 
I believe you can actually batch resave multiple libraries, but problems occur if there are samples that share names in different libs. Never tried it myself.
Beyond it being necessary at all, what really bugs me is how often it's prone to failure when doing it within KK, often taking S1 down with it.
 
whinecellar said:
why does this exist?
Click to expand...
The original purpose was (and mostly still is) to convert pre-Kontakt 4.2 patches to the new binary format, which is way faster to load.

whinecellar said:
(2) load everything as fast as it does after doing a Batch Resave... why not just default to fastest load times
Click to expand...
Complicated topic. It has to do with your OS caching files for faster access. In this regard batch resave is useless today, because after you turn off your computer and do a cold boot, those same patches you batch resaved would be back to a bit slower loading times. It's just how modern computers are.

Another reason is that there is a bit of a slowdown when loading a library that has been created with a Windows machine on a Mac and vice versa. There's some pathing issue that affects .nkc (sample file path cache) files where batch resave helps somehow. So to me this suggests that if you're moving from old NMac to new Mac, you don't have to bother with batch resaving at all.

whinecellar said:
3) allow a batch-Batch Resave... in other words, allow you to select a whole bunch of Kontakt libraries and batch resave them all at once
Click to expand...
You can but it's not advised as mentioned in a prior post, if two libraries by some stroke of accident use the same sample names, this won't be easily resolvable. There actually are cases of this out there, so it's generally just better avoided.

Akoustecx said:
Beyond it being necessary at all, what really bugs me is how often it's prone to failure when doing it within KK, often taking S1 down with it.
Click to expand...
TBH it should only ever be done from standalone. Maybe we should even hide the option in plugin mode...
 
EvilDragon said:
The original purpose was (and mostly still is) to convert pre-Kontakt 4.2 patches to the new binary format, which is way faster to load.


Complicated topic. It has to do with your OS caching files for faster access. In this regard batch resave is useless today, because after you turn off your computer and do a cold boot, those same patches you batch resaved would be back to a bit slower loading times. It's just how modern computers are.

Another reason is that there is a bit of a slowdown when loading a library that has been created with a Windows machine on a Mac and vice versa. There's some pathing issue that affects .nkc (sample file path cache) files where batch resave helps somehow. So to me this suggests that if you're moving from old NMac to new Mac, you don't have to bother with batch resaving at all.


You can but it's not advised as mentioned in a prior post, if two libraries by some stroke of accident use the same sample names, this won't be easily resolvable. There actually are cases of this out there, so it's generally just better avoided.


TBH it should only ever be done from standalone. Maybe we should even hide the option in plugin mode...
Click to expand...
Ahhhhh THANK YOU - i've always wondered about the technicalities of this. Appreciate the info!
 
I don't agree with that, personally. You do this batch resave once, ideally, too. And either way anything related to batch resave is unlikely to change I think...
 
I never batch resave.
Am I wrong ? (On an MBP, libraries on TB4 NVME).
I don't feel like my libraries take much time to load.
 
I feel like this is one of those topics I've always read and heard about but never really dived in to understand properly. Like side-chaining! But with modern NVME speeds I find libraries load pretty quick anyway, and I'm worried about breaking something.
 
Wondering this exact thing today as I reinstall on a new system. Why isn’t there Quick-Load speeds (and thus, I assume caching) as default? Does anyone actually want slower loading times than the fastest available?

Is there any reason why I shouldn’t load everything I enjoy using into Quick Load?
 
Sorry to bring this up again. I am right now in the midst of installing my Kontakt Library from scratch on my new Mac Studio. Do I get it right that I do NOT have to do this Batch Resave additionaly for ALL libraries when I just made a clean install (no copying from my old computer)? Thanks ... :)
 
You must log in or register to reply here.
Top Bottom