Are smaller size sample chains less cpu-heavy than larger/longer slice chains?

[lesstalkmoredisco]

Question, maybe someone from 1010 can answer this: Are smaller size sample chains less cpu-heavy than larger/longer slice chains?

I use sample chains on more than half of my Bitbox Micro tracks (for example one track with a chain of many kicks, the next track with many longer synth stabs). Some have WAVs around 1-2mb, but other range beyond 30mb up to 90mb. Does it matter? Is it good practice to cut them up in two or more halfs? Will it help lower CPU or latency? Any other ups/downs? Or does it not matter?

Thanks! LTMD

[Steve]

It does not affect latency or CPU, necessarily. Our samplers load wav files from the microSD card to RAM buffers. Wav files are effectively streamed this way. If you load several, very large wav files it is possible to hit the buffers hard. Using 24/48 wav files is your best bet to not overwork the CPU.

[lesstalkmoredisco]

Perfect, thanks Steve I already indeed batch convert all my files to 24bit/48hz.

Don't want to overask, but what is your idea of "several, very large"? (Is 50-100mb very large or is 500mb very large?)

[Steve]

I would not consider 500MB to be too larger. When you start loading multiple, full-song stems where the files are in the GB range, you may experience a hiccup or two.

[lesstalkmoredisco]

Steve clear - thanks!