While shifting from 3/4 to 9/8, I’m indicating to the performers both that (1) the length of an eighth note stays the same with “(e=e)”, and (2) telling them to play a tad faster with “Poco più moto”. Dorico doesn’t seem to want me to do this.
I can come up with a workaround (place one of them in a different measure and drag into place under Engrave mode), but wanted to see if there’s a better way of doing this, and also to ask about some other behavior that I don’t understand.
So if I try to change my own “Poco più moto” to “Poco più moto (e=e)”, Dorico deletes the verbal instruction and gives me just the “e=e” instead. For some reason, it also gets rid of my parentheses:
Also, if I input just “(e=e)”, the equation by itself is fine for the time being. If I double click it to make any alteration, what I get is the “e=e” without the parentheses, and I have to put them back. Not sure why this is happening, either.
You cannot at the moment combine both a tempo equation and another kind of tempo at the same position, I’m afraid. You’ll need to employ some kind of workaround, e.g. adding the written tempo at a slightly later rhythmic position and then adjusting it in Engrave mode.
Got it, thanks for confirming.
Just adding this here as something I hope can be taken as useful feedback, though I know has been iterated and reiterated in various ways before. A question I keep hearing discussed among my colleagues is: Why does it seem like there’s extra effort put into making Dorico inflexible? This is just one of countless examples. Someone needs to have spent time in order to make it so that I can’t just type in what I want here. And what I’m trying to input is totally standard notation.
Also, still wondering what the reason is my “(e=e)” gets constantly turned into “e=e” if I try to edit it.
That’s a complete misconception. Building software is not like sculpting from a block of marble, where you are taking things away by chiseling pieces away. Building software is more like growing a garden, cultivating plants from seeds and carefully tending them, paying attention to every shoot and branch. Even this analogy isn’t really correct, because plants grow on their own if you provide them with soil, water, and sunlight, whereas software never grows capabilities on its own: every point of functionality has to be conceived of, designed, implemented, and tested by the team.
So it is certainly not the case that we have put extra effort in to limiting the possibilities of the software. Instead, we carefully implement each functional area to best address the requirements as comprehensively as we can. But there will always be more things for us to add, in every area of the software.
When you edit an existing tempo equation, the popover isn’t paying attention to whether the tempo equation is parenthesised, so it’s losing the parentheses. I’ll make sure we take care of this in due course.
6 Likes
