Hi, found this because I run into this issue sometimes. I once showed a piece I was working on to a composition teacher, where I had marked flutes with f.t. (which Dorico defaults to when I type fluttertongue). My teacher is a sibelius user for whatever that’s worth, but they told me they had never seen f.t. in a score before, and felt certain woodwind players would be confused by this. When I explained that my intent is fluttertongue, they remarked I should use either unmeasured tremolo (3 marks) or a Z-stem, either of which a woodwind player would immediately recognize as fluttertongue (it’s basically a wind player’s version of tremolo).
The other issue I have with Dorico’s playback treatment of f.t. is that by default it is assigned as direction and not attribute:
Meaning that it will remain in fluttertongue until you tell it otherwise; in order to reset to normal, you have to use ‘nat.’ Another thing my teacher told me a woodwind player might be thrown off by. I personally find this an odd decision since IMHO f.t. is typically a short-term special effect that most composers only want on specific notes and not entire passages (of course if one does want it across entire passages, just like tremolo you would manually notate it on the notes). This seems to be cleaner and what most woodwind players will expect to see, but there will always be exceptions to the rule.
I recently discovered a workaround - go the expression map used by your playback template (in my case I’m using NotePerformer) and with that expression map selected look for in the list Base: Flutter-tongue. Duplicate this so you have the same settings of whatever it triggers (keyswitches or control change etc). Then double-click the duplicate and this list will pop-up, scroll down and select Tremolo (make sure it does not say flutter-tongue + tremolo).
Now whenever you add 3-stroke tremolo, it should trigger the actual flutter-tongue playback.
The issue I’m discovering here is that I cannot figure out a way of saving the expression map in such a way that it will load this way by default in the future (so it’s a step I have to take every single time), unless I save as a project template manually.
Lastly I believe if you want tremolo to be combined with other techniques (legato, muted, etc) you’ll have to duplicate those labelled flutter-tongue + [technique] and do this process again but combined with tremolo instead.
You can also test to make sure it’s working by viewing the key editor to make sure the technique is loading like so:
It should say tremolo but your ears should be hearing flutter-tongue.
I’ve found it to work great on all wind and brass, and it does not appear to interfere with instruments which do not have flutter-tongue (strings, perc etc.)
Lastly this tremolo only works with 3-stroke. I cannot figure out how to find ‘z on stem’ to trigger flutter-tongue. I feel this is likely less common as it is a little more of a percussion notation, but my teacher tells me wind players will recognize it and some prefer it (I haven’t gotten a second opinion on that, so I’ll stick with 3-stroke since I think that’s more common).
As one final step, if you want to remove any ambiguity for players, you can also just add ‘fluttertongue’ as a regular staff text. My teacher recommends against f.t. because not everyone will know what that stands for.
Hope that helps, and if anyone has any idea how to make an expression map change permanent please let us know. Ideally in the future Dorico will make tremolo and flutter-tongue useably interchangeable in the context of winds & brass, since 3-stroke tremolo is a common notation for this.