I've been holding back to see the results of your sample rate testing, Russ. I can add to the reference link posted by kwgm above. It's difficult to give a
specific solution, because no specific presets were mentioned (beyond the Male Choir).
A general approach isn't all that difficult to detail, and it offers a permanent solution. I wouldn't go at this 'globally', using the Transpose parameter at the Element level.
It'd be prudent to back up any .sfz files that you're editing; at least until you're comfortable with the process and the results. ****************
****************
Call up the program file that's bothering you, and note the .sfz file name that serves as the core.
It's listed under the 'Load Multisamples' slot; just under the Program Browser slot at the top.
Click in the Load Multisamples slot, and navigate to the .sfz file that you've determined to be the editing target.
If it's one of the 'Real Basses' presets, for example, it'll be in the '13 - Electric Basses', or '14 - Acoustic Basses' folder.
Right-click on the file name, and select 'Open' or 'Edit'. A text editor will pop up, containing the .sfz file in question.
You'll see all sorts of sample definitions ("<region>"), usually with a Tune parameter at the tail end of each line.
If not, a Tune=
X opcode can be appended, with
X being the tuning offset in cents (positive or negative).
Now, you have to figure out which keys sound out-of-tune to you. Play a few scales and make notes of the offending ...
notes.
You can do all this with the Dimension Pro microhost open, alongside your open text editor. Nothing changes until you save the file.
****************
****************
.sfz files use the International Pitch Notation convention (
not the Acoustical Society of America notation adopted by Cakewalk host programs). That places middle C=C4 (MIDI Note 60). Here's a chart to use. All you have to be concerned with from this illustration is the Note name (or MIDI number) and the Keyboard column.
****************
Match the 'Note name' to what you're hearing, and adjust the Tune parameter in the sample <region> that contains it.
The 'key=' determines the central note, with 'lokey=' and 'hikey=' spreading the same sample over 2, 3, or possibly 4 keys.
Make adjustments to the Tune opcodes, Save the .sfz file, and reload it (or the parent preset) back into Dimension Pro.
If you're guessing at the number of cents "out of tune", it's going to take a few tries to get it right.
****************
****************
For more information,
see the
Sfz in the Grand Piano tutorial(s) [
dissecting the .sfz parameters of an existing preset].
If anyone is waiting on a perceived problem to be updated
for you, consider that Dimension Pro is soon to become part of Sonar8. I'm not certain that's the 'end of the line' for it, in terms of development, but you can review the history of that move and judge for yourself.