So one can have something like this:
I’m envisioning something like dynamics, where there are prefix/suffix properties.
Yes, I know using some of the notehead fonts foating around I could fake this in text, but I prefer not to.
1 Like
Semantically speaking, “the trailing text is more playing technique than tempo” is what the Dorico AI is likely thinking.
That said, I have not problem with your request to allow trailing text after the M.M. marking.
1 Like
Well, you don’t want to fake it with text, but it’s the only way to get all this marking formatted like this!
Can I plus one this as a feature request. It makes perfect sense to be able to enter:
“q = 57 or faster”
It is so common in scores, this sort of indication.
In the next version of Dorico it will be possible on a per-tempo basis to swap the order of the metronome mark and the following text, so you’ll be able to achieve simple markings with metronome marks followed by text easily.
8 Likes
Perhaps a most flexible option would be to add a token for the current mm, so one could turn off display of the MM, and then drop the token in exactly where desired?
In v6, I’d love the ability to add text before AND after a metronome marking! I want the ability to do things like “Quickly q=144 / 8 Free” (i.e. free clicks in a recording session). I can fake it now, but I wish I didn’t have to!
2 Likes
If the tempo object handling undergoes any revising by v6, I would wish for the following (in addition to JWink’s suggestion):
for the tempo “Text” property to recognize Markdown formatting and line break characters, like the fields in Project Info. (All the better, if the field would also recognize Music Symbol tokens, to write out metric modulations etc.)
Sometimes (and not at all seldom) due to space constraints, or for general project housekeeping, it would be handy to format the tempo markings in two lines. Also the ability to bold/italicize etc. the text inside the tempo text would be useful. If for programming reasons treating the tempo objects as WYSIWYG like a Paragraph Style is not feasible, that’s completely fine (for super involved tempo markings, faking them with System Text is not a problem) — but having a bit more flexibility with the actual Tempo feature / properties certainly wouldn’t hurt. Unless it’s impossible or hugely impractical to implement, that is.
Pretty sure I’ve requested the multiple lines thing myself. There are a fair number of existing editions with tempo markings in multiple languages, even.
Yes, it comes up from time to time. Though with the myriad of different “tempo indications” (sometimes including stage directions, poetry, other dramatic stuff, different languages, plethora of metric modulation à la Carter and so on and on and on) that can be encountered in different extant editions, and which might need to be reproduced, I feel that the System Text workaround is/should be the way for those cases. (I also suspect that any time that is the use case, the time frames to work on e.g. a new critical edition or a series of volumes is completely different than churning out session charts on weekly/daily basis.)
The Tempo feature of Dorico, which is basically formatted “non WYSIWYG” via the Properties, is a design choice that in my opinion works rather well. I also suspect (not a programmer) that revamping it completely after 5 versions might be a stretch and a half to ask, for compatibility and other reasons. That’s why my layman’s view and concrete suggestion would be simply (?) to implement the same kind of functionality to the free text field in tempo properties that already functions is quasi-similar fields in Setup mode (Project Info, Player Name…).