Re: Multi-measure rests and mark collisions ...

[David Wright]

On Fri 22 Apr 2016 at 16:24:06 (+0100), Anthonys Lists wrote:
> On 22/04/2016 14:49, Paul Scott wrote:
> >>I assume Wol (like me) has the problem where the compressed rest happens
> >>>in the part, not in the full score — but one wants not to have to use
> >>>multiple \tag constructs just to handle this issue.
> >Me too.  I asked a long time ago and got the idea that I was the only
> >one concerned about this.  Essentially why is alignment different for
> >multi-measure rests than notes.
> And other things too? Try the following ...
> 
> f1->\fermata R1*3 R1\fermata
> 
> The first fermata prints fine. The second fermata prints
> "programming error: Object is not a markup." in the log and doesn't
> print. So that's another bug tracked down in my piece, but - from a
> musician's pov - it doesn't make sense that the first example on a
> note should work fine, and the second on a rest produces an error.
> (It never used to work on notes at all, iirc, only as a mark on
> barlines, so maybe I should be grateful for small mercies :-)
> 
> It's easy enough to fix - something like "\markup #symbol.fermata" -
> I'll have to look up the syntax - but it's just frustrating that
> it's not consistent.

That's because whole-bar and multimeasure rests are themselves not
consistent with music notation in general. They have the "wrong"
duration and the "wrong" alignment (placement). They're a convenience
for musicians (especially instrumentalists; singers often hate them)
and a pain for engraving programs.

AIUI I can anchor things horizontally to either barlines or to
notes/rests/spacers. Unfortunately once a whole-bar rest has
jumped to the middle of a bar, it's no longer a useful anchor
for most purposes.

I haven't tried to set your OP's snippet. It might be an idea to post
a sketch of what you want. Possibly you'll improve your chances of
suggestions.

Cheers,
David.