Dorico in its wisdom puts in six fermatas here, due to excessive polyphonic zeal. So then one has to remove four of them in engrave mode. What I find weird is that you can’t delete them, you have to move them off the page area. Why is that? That is my question.
What is preventing the Dorico design from simply allowing one to delete unwanted fermatas? And as a secondary point, why add a fermata to every voice in a case like this, very common, where nobody to my knowledge would ever write six fermatas - it makes no sense. I officially name this disease fermatitis.
Yes, but why not allowed to simply delete unwanted instances? People say Dorico is logical, but I cant follow the logic in this - I think it is the only instance where you have to hide something in this manner.
For the time being it’s definitely worth creating a fermata playing technique as suggested by @LAE. It seems more elegant than dragging the unwanted second fermata out of the room and it’s even a little faster than the “one per voice” option in the properties if you want just one on each side.
I’d agree that being able to hide individual fermatas would be useful, rather than deleting them; despite hiding things being anathema.
One of the things that first attracted me to Dorico was the ability to add one fermata on staff, and get them ‘for free’ on all the others, compared to manually selecting every staff.
I know that Dorico treats various things hanging off the staff in different ways: like Chords, or like System Text: it may be that making exclusions to “this appears on every staff” is complex.
One of these days I will do a tour de force and go through all Engraving Options and I’m sure I’ll discover the most wondrous surprises. Or maybe it’s faster to make a suggestion here and then find out it can be made even easier?
Except, as has already been explained, in cases such as yours it’s just a case of either setting the global option correctly or setting the local property correctly. There are fairly limited circumstances in which fermate don’t apply simultaneously to all players (such as where one person plays a cadenza) and this isn’t well catered for.
The implementation of fermate as local, staff-attached objects in other programs, and the fact that their users didn’t/don’t necessarily understand that fermate should be added to every player’s part, has led to several hours of wasted rehearsal time and confusion in just my working life. Fermate that are system-attached prevent this issue from occurring.
There are existing feature requests for handling cadenzas and cadenza-like situations, but these haven’t been implemented as yet. No-one’s suggesting the software’s “finished”.
@pianoleo This is polyphonic keyboard music, not ensemble, so I suppose Dorico is not yet smart enough to understand you don’t need six fermatas on a polyphonic chord. On the other hand, the instrument is ‘harpsichord’ and there’s a faint possibility one day in the future it could figure this out!
My main gripe is this weird business of having to drag them out of sight. It’s fiddly and you have to do it only after the pages are all finally laid out or you risk having them appear on a page still. Surely simpler is better - just allow a fermata in a multiple set to be deleted. I submit this for consideration as a feature request.