Small Quality of Life Improvements Wishlist for Next Dorico

My wishlist for few minor things that might be low-hanging fruit but can help with productivity. (Sorry, I am just making an assumption that these are low-hanging fruits, but maybe they are harder to actually implement :D)

  1. Add indentation and bullet list support to the text tool.

  2. Text tool overlay window always appears at the top so if I am working with a large text frame and editing text in middle or bottom of the frame and am slightly zoomed in, I cannot see the text tool, so need to unselect, zoom out, and reselect the text frame to be able to edit text at the bottom of frame. Would be great if text tool can appear relative to the screen instead of the app.

  3. A new property option to parenthesize Playing Techniques similar to Dynamics. Current workaround is to create a duplicate object and add parenthesis to it manually. But this is not as easy for non-text objects.

  4. Option to scale Paragraph Styles (EDIT: meant Font Styles) in parts vs score. Example, big orchestra score so need large font for Tempo markings. But it carries over to parts and it looks too big. Currently need to manually select all tempos and scale them differently using the property panel for each part or in score, which is very time consuming. But if there was a layout option that would allow us to scale paragraph styles differently in Part Layouts, it would immensely save time.

  5. Automatically use the text “Tutti” instead of “unis.” for staff division of Solo + Gli Altri.

I might add more to this thread if I com across other things in the future.

Thank you Dorico team <3

For #4, I think you mean Font Styles, not Paragraph Styles (which already allow for different sizes in parts and score). There have been discussions elsewhere about this, and I think it’s somewhere on the todo list to migrate don’t styles to paragraph styles.

1 Like

You’re absolutely right, #4 is supposed to be font styles.

Engraving Options > Condensing > Text for unison indication of section players

2 Likes

I don’t see an option that specifies a solo(s) + gli altri situation. In a piece, one may need both unis. (after a passage where a section is equally divided into multiple groups) , and Tutti (which is the marking used after a section is divided into Solo(s) + Gli Altri)

The only workaround is to manually overriding the text using property panel.

I think that is correct, yes.

How is Dorico supposed to know the difference? What would you have for a divisi that splits into a solo and two divided groups? Is the return a tutti or a unis?

It is specified in the Change Divisi dialogue! So it shouldn’t be hard for Dorico to know what marking to use.

As for more nuance / complex divisions using both solos and multiple divided groups, I am not the expert on that so best to consult a notation guru but I personally would be ok with using unis. as long as there is at least two or more divided groups. In other words, solo(s) + gli altri is the only situation where I use Tutti.

No. That is for the split - not the return.

Sure but that does not mean Dorico does not know what kind of split it is combining.

What should the return sign be for …

Unis or Tutti?

I already answered this in my response with the picture.

No you did not. Unis or Tutti?

Copy pasting my answer :slight_smile:

“As for more nuance / complex divisions using both solos and multiple divided groups, I am not the expert on that so best to consult a notation guru but I personally would be ok with using unis. as long as there is at least two or more divided groups. In other words, solo(s) + gli altri is the only situation where I use Tutti.”

So in this case I’m ok with using unision.

Which is what Dorico does by default. So back to your original suggestion: you want Dorico to have a differential response in the special case of a solo/gli altri divisi, yet are unhappy with the current ability to customise that response?

You are misunderstanding my point. The current behavior is not correct for a solo+gli altri case. So one has to manually override the return text using the property panel after each time such a division is used.
My feature request is for Dorico to automatically recognize this case and use Tutti instead of unison.

And I think that is an unreasonable request to bake into Dorico’s behaviour, especially as you already have a simple route to deliver what you need.

1 Like

I disagree. It is a manual process, prone to errors and inconsistency, and time consuming. Not to mention it is incorrect for this case.
And it does not have to be “Baked in”. It can simply be a notation option, like many other variety of notation options that Dorico supports.