Solved Many small sample files VS one long sample file in Kontakt

I have a general question concerned with the efficiency by which Kontakt handles the situations mentioned in the title.
(1) I can import one long file with several notes, slice it in Kontakt's wave editor and drag the slices in a "slices mapped" group onto different zones, where Kontakt references the start and endpoints in the original file. (2)Alternatively, I can slice the long file in another audio editor, name and save individual slices as separate smaller sample files and load them onto different zones/groups in Kontakt.

At the same time, I could set the source to sampler (A) mode or DFD (B) mode.

Everything being equal, from the four combinations, which one is the best strategy for your average home computer? 1A, 1B, 2A or 2B?

Additionally, would the various options above make a difference if, in the end, one saves the instrument as a monolith, which creates one big file from all the underlying data?

I find that the perceived "playability" and "organic" nature of a Kontakt instrument is psychologically directly linked to the efficiency of sample playback. Most Kontakt libraries (including Spitfire Audio, which contains very clever but often misleading scripting and instrument group structures) use many samples files for each zone/group and set the source to DFD (2B). I, on the other hand, find that the opposite (1A) is better for a fluent performance experience (i.e. one long sample sliced in Kontakt and source set to sampler).

I will appreciate any insights into this subject.

Thank you.

 

2B would be more efficient RAM-wise (of course), and is usually generally preferred unless you need the full sample (i.e. for time stretching).

 

Thank you very much for the reply.
Yes, 2B should be the most RAM efficient, provided everybody uses SSDs and USB 3. For certain groups, I am using velocity to modulate sample start. So for that, I need to load the bulk of the sample.
Irrespective of that, does it make a difference if a recording session is separated into many small audio files or loaded as one big file and sliced in Kontakt? Is the disk streaming, RAM utilization different in an impactful way?

 

Well don't forget Kontakt is 20 years old and people used DFD just fine on old computers and 7200 RPM drives...

Personally I like properly trimmed and cut samples as that's also most efficient storage-wise. It makes no sense to use one big file in sampler mode since that also loads the unused cruft at all times.

Disk streaming doesn't really care either way, it just loads a chunk of specified DFD buffer size from the file and keeps that in RAM.

 

Perfect. Thanks! I appreciate your moderation. Your explanations are helpful and succinct.