Bowing mark not showing on condensed divisi staff

Looks like a bug: the downbow mark at the beginning of the divisi for the lower staff is not showing on the condensed staff. If you mov
Deleteme5.dorico (695.8 KB)
e it up a bit, it will.

Dorico 5.1.70.2200

What do you mean by ā€œmove it up a bitā€?

I mean, if you move it to the right by one grid-position (even if that’s a semidemiquaver, I think the lowest possible?) in write-mode, it will show in engrave mode. Meaning it must be related to it being at the very start of the divisi staff.

It’s not a bug.

  • Double-click the Condensing Change to open the dialog
  • Tick the Double Bass in the left-hand column
  • In the right-hand column, scroll down to Allow amalgamation for playing techniques
  • Activate and then deselect it

It’s possible to save this setting as default by going to the below section in Notation Options:

2 Likes

@JustusR, @DanielMuzMurray is right. Learn to set the correct options before you shout ā€œbugā€.

OT: Those bowings are entirely unnecessary and will be ignored by Bassists.

Oh, so it is! Many thanks! I was really wrong-footed there.

1 Like

Whoa! Easy, tiger. If you are from the Dorico team, please confirm you prefer me not to report suspected bugs, on the basis that I might be wrong and they aren’t.

Dorico Team members have the Dorico logo on their avatar.

If you merely report that you are having difficulty accomplishing something in the program, Daniel and the Development Team are happy to admit if they determine it is a bug, but if someone cannot accomplish something, too often someone will claim something is a bug when they really mean ā€œit’s not my fault.ā€

When I take the trouble of making a tailored file, to post on this forum with a clear description of what the issue is, I genuinely do that with the intent of helping the makers improve the product. Over the years, I’ve probably reported about 10 (?) ā€˜suspected bugs’, and yes - sometimes it turned out to be I was doing something wrong or wasn’t aware of a detail - but equally I’ve been able to highlight quite a few problems, for the greater good. If I just want to know how to do something, I’d post it on the Facebook forum instead. I just don’t think it’s good tactics to get angry at people who report bugs, even if turns out it was their mistake. Because all you do is discourage people from reporting them.

I’m not angry. I’m just not the boy who cries wolf.
I let the Development Team decide what’s a bug.
That is not to say you shouldn’t raise questions when something confuses you.

1 Like

Thanks for taking the trouble to make the file - and all the other people who do this as well, it helps all of us. Whenever I have post something like this, I try to use words like ā€œissueā€ or ā€œproblemā€ instead of ā€œbugā€, because like the others said above, it might not be a bug.

2 Likes

That is definitely a learning value I take away from this unexpected thread :slight_smile:

1 Like