Thought it might be useful to share some details about using muti-samples in quantum particle oscillator.
Auto-map (in timbre>actions menu for particle oscillator) will spread a group of already added multi-samples across the keyboard.
It can only do this if the samples contain embedded note data. It seems to look for an "unshifted note" value in the INST chunk of the sample - not all multi-samples contain this. I use wavelab to check if this is set to the correct note (tool windows > sample attributes > tune:key). Apple logic/mainstage auto-samplers add the note, as does MPC auto-sampling, and many commercial sample libraries have the note embedded eg some "samples from mars" samples do and the MPC instrument expansion samples I've tried do too.
The main limitation is that it will only set the note range for the first sample it finds for a note, and it assigns it to the full 0-127 velocity range. Other samples with the same note just get ranged to the single note and the full velocity range. This means it doesn't spread out the samples for velocity ranges or round robins.
They can be edited manually on the quantum but it's a bit of a pain.
Houhoura Fréderic on Facebook suggested editing the .map file directly on computer and it's the method I use - here are my notes on doing that (on mac but the principle should be same on windows):
Add multi-samples to the particle oscillator as normal (can select the parent folder rather than individual files to load the entire contents in one go)
actions > auto-map to get a starting point
actions > save map - save to usb or sd card
Open .map file on mac in textedit
copy and paste into excel
select columns : B E H I J L M O
format > cells > custom > 0.00000000 (8 decimals)
select column A > format > cells > custom > \"@\"
these are the column contents in excel for editing:
a = sample location (double quoted string)
b = pitch/note (8dec)
c = range start (int)
d = range end (int)
e = gain (8dec)
f = vel start (int)
g = vel end (int)
h = unknown - 0.50000000 (8dec)
i = sample start (8dec)
j = sample end (8dec)
k = loop mode 1=on / 0=off (int)
l = loop start (8dec)
m = loop end (8dec)
n = direction 0=forward / 1=backward (int)
o = xfade % (8dec)
attached is an image of an original auto-map file, loaded into excel with cells formatted as above. This is an MPC expansion where there are 3 samples for the C of each octave. (These are intended to be cycled through so it's not the exact same sample each time - I use "rule=random" on quantum for this).
there is also an image attached of the file after it has been edited so that the 3 samples for each octave have the same note/pitch, range start and range end values (see cols b, c and d).
copy the excel cells with content to the clipboard
paste back into textedit and save (make sure it saves as .map else rename the .txt to .map)
insert sd card/usb back into quantum and go actions>load map - when loading a map it does the samples "add" automatically, so it automatically works with samples already imported to internal storage on 2.0 firmware and on beta 3.0 it will work automatically with samples on usb/sd-card without being imported.
It's a lot easier after doing it once (and can save the excel file as a template to make it faster next time) - it only took a few minutes to map the MPC samples above from scratch for example (these were from the MPC jupiter rising expansion which I note is on offer at $19.99 at the moment at audiodeluxe.com. The patches aren't of any use in quantum, but the 3,700 samples make good patch starting points as almost all of them are in sets of 7 octaves with 3 round robins for the C. All the samples I've tried in that pack have the embedded note data, but I can't say for sure that they all do).