Ah, yes, a single keybank can, itself, internally have multiple velocity-switched samples, whose velocity transition points are invisible to the user. AFAIK, this is always indicated by the presence of "Sw" in the name of the Waveform... so the process I described would not work to easily create a properly velocity-mapped SR-sampled version of a Performance that includes an element so named. (Obviously, sampling 127 velocity levels for each sampled note is not realistic!)Thus a single 'waveform' can contain many banks and WAV samples. But it is a 'waveform' that is assigned to an element - not an individual 'sample'.
The individual banks and their parameters are INTERNAL to the 'waveform' and can't be seen on an edit screen or by SampleRobot.
It is this 'internal' data I was referring to that I said SampleRobot can't access. Those internal parameter values are READ ONLY for preset waveforms and are HIDDEN from view.
So although you can see the Vel Limit, Note Limit and Center Key values on the element edit screen you can NOT assume they are the same as the values INSIDE the waveform banks. They might be the same as the values for ONE bank of the waveform but the waveform could contain many other banks with different parameters.
The "note limit" variable again I don't see as much of an issue, because one can always sample every key (or if memory consumption is a concern, use that "pitch bend" technique to listen for whether an adjacent key is stretched or is its own sample, to probably at least get close without too much difficulty).
I couldn't find that reference, maybe I was checking p.13 of the wrong manual? But again, assuming we avoid the performances with "Sw" elements, wouldn't all of that come in when you sample a given key at its highest indicated velocity within the performance?SampleRobot can NOT access the...Volume, Pan, Tune coarse or Tune Fine parameters (which can also turn you upside down) you also see on page 13 of the doc.
Statistics: Posted by anotherscott — Sun Feb 11, 2024 3:09 pm