Over the past few months, several people have asked me if I could add microtuning support to Decent Sampler. This week, after purchasing a çifteli (pictured above) at a local thrift shop and discovering its unique scale, I finally decided to roll up my sleeves and see what I could do.
There is a new version (1.8.0) of Decent Sampler available here. It will be officially released on Monday, February 27th. This new version introduces the Tuning menu. This menu allows you load Scala (.scl) and Keyboard Mapping (.kbm files). It also allows you to specify a non-440Hz frequency for MIDI Note 69:
In order to use the microtuning functionality, you will need to get ahold of the .scl and .kbm files for the scale you are interested in. A great place to download a bunch of scales is here (look for the Download them all link in the Tuning Files section). Once you have those, you can load them using the Load .kbm Keyoard Mapping… and/or the Load.scl Scale… menu options.
When you specify a scale or keyboard mapping, your scale and keyboard mapping will get saved along with the DAW session. However, if you create a new track and put Decent Sampler on that track, the new track will revert back to the classic twelve-tone scale that most DS users expect. This is by design, but if someone thinks this behavior should be changed, let me know.
Sample creators can also embed scales in their instruments by adding a “tuningSclFile” and/or “tuningKbmFile” attributes to their top-level <DecentSampler> elements.
I want to thank the kind developers over at Surge synth for making their microtuning library available to all developers and for licensing it so generously. Without this, I would not have added microtuning support.
This is very much my first foray into the world of microtuning, so I expect that users will have suggestions. There will doubtless be a version 1.8.1 and a version 1.8.2. Let me know what you think!
EDIT: I’ve updated the screenshot above to show the new version of the Tuning menu.
5 thoughts on “Microtuning Support for Decent Sampler”
Hi hi! Checked 1.8.0 and 1.8.1. First of all, retuning per se seems without any issue. At least if checking with just an ear.
But alas the sample map, like in sforzando, stays fixed as it was, so when using a tuning with 7 or 17 notes per octave, samples at ends of the playing range get retuned too much, with effect on timbre and sample length (too long and muffled on one end, too short and bright on another, which being which depends on if there are more or fewer notes than 12).
As I said in comments to that other older post (in probably hardly a clear way—but I’ll try better this time) it can be fixed quite readily—barring some issues which are probably not fixable in an automatic way and better left to the user (more about that below).
The actual keymap in the .dspreset file stays the same, with MIDI notes for starts and ends of each sample’s range. But it’s interpreted differently when retuned: when you got a new frequency F for each MIDI note N, you also calculate “an actual MIDI note” Ñ (which would generally be fractional now), looking what MIDI note would give F in standard tuning. (See the formula below if I’m too wordy here.) You then use this Ñ to determine if a note lies in a range of a particular sample (or group; I haven’t yet looked too much into the format).
Let’s say if a range of sample S1 is from 60 to 64, then range of sample S2 is from 65 to 68. They are with no gap when we use standard tuning, so we want them be without a gap in any other tuning; the natural thing to do then is to use S1 for Ñ ranging from 60 − ½ to 64 + ½, and S2 for Ñ from 65 − ½ to 68 + ½. We have a slight collision at the border 64 + ½ = 65 − ½, and I think it should be okay to resolve this ambiguity in any way: always using a sample with the lower range, or always using one with the higher range—or any simple way you deem convenient.
If you precompute which sample is used for which MIDI note (N → sample-id), you’d probably be good with precomputing this new “concrete map” each time frequencies of notes change, computing N → Ñ → sample-id. (And if Ñ is out of any defined range, it’s unplayable.)
If playing ranges grow outside our meager MIDI1 note range of 0…127, then so be it; musicians using keyboard retuning method are already accustomed to this (and it can be made okay when using KBM files which allow to focus on a part of a range, so it’s nice the Surge library allowed you to already have both 👏 👍). So you don’t even need to check which range from .dspreset maps to which range in retuned MIDI notes (maybe only to show a warning somewhere in a log if you wish!).
[Calculating Ñ in terms of F]
As one calculates the frequency of a MIDI note N in standard tuning as F = 440 Hz × 2^((N − 69) / 12), then reversing this (and using Ñ in place of N) gives this:
Ñ = 69 + 12 × log2(F / 440 Hz)
(just in case C++ math library doesn’t have log2(x), it’s log(x) / log(2) but you probably already know).
About keyswitches (this is that problem I think is better left for a user to solve): now as ranges would sometimes grow, they can intersect one or more keyswitches. Which are probably should stay in place on the keyboard for their convenience! But if you want to experiment, you can add a checkbox for shifting keyswitches too as if they were normal notes. But I’d make this an opt-in because it seems a weird behavior. Staying in place is not conveinent too when the range grows, but this is that case I think only the user would know where to place the keyswitch to make themselves content. So again, probably flashing a warning somewhere—“beware this keyswitch redefines one of notes now in playing range, you may want to edit the preset file!”—and hoping they would be ready for that occasion as they used a scale with many notes per octave and probably knew what to expect from that!
At least that’s the best I came up with.
Again, thank you David very much for working on this feature! 🎈 Believe or not, this is in a sense history because, well, when ever would Plogue be able to patch sforzando? They said they’ll first make a successor to ARIA and then make sforzando use that new engine and it could support MPE. As of better sample mapping, I probably was too cryptic and wordy and they haven’t yer answered about that at all. (They are cool, I’m just stating the state of affairs.) Another one sampler, TX16Wx can be retuned by MTS-ESP but again the sample mapping issue is the same. And there are probably no other freeware samplers sophisticated enough and supporting major formats (as input or import).
Another thing: how is the state of things with FLAC, do you have time×motivation for that? For some reason I expected importing SFZ libraries with FLAC samples would work and was a bit surprised what the errors were about (I thought there was something with file paths and edited them two times before getting a clue). But this is another issue; and I already added a little comment on the QA question about FLAC so no worries. I think I have space for WAV for now. 😀
Let me know if I forgot to elaborate anything I said here I would and then forgot. I hope the trick with “actual MIDI note” Ñ is understandable because I may be explaining it in a weird way.
Version 1.8.3 added a new menu option: “Select samples based on scale tuning.” Is this what you were hoping for?
Aaaaah!! That’s so cool!! 🙌 Yep that’s exactly it.
Thank you yet again!
BTW a little cosmetic fix which you probably already noted can be added to note colors in the on-screen piano keyboard to reflect the new range of playing when this switch is on. If it wouldn’t be too hard, as it’s more than fine already. (I think.)
I downloaded the .scl and .kbl files that I wanted from my computer and put them in an iCloud Drive folder, but when I try to load them in IOS, they appear greyed out. Is there something I am doing wrong, or is microtonality not possible in IOS? When I use Decent Sampler on my Mac, it all works fine.
Hi! yes, you should be able to load them via the “File > Tuning > Load SCL File…” menu option. 🙂