Thanks - that sorts out a lot (and exposes another issue I'll write
about separately!).
In my many decades of programming I always had reservations about
"syntactic sugar" - different ways of expressing the same thing. When
the alternatives do not have the same behaviour at all times, they can
The reason for it breaking is that in the code you posted there are vertical
lines ” || " instead of backslashes ” \\ ” separating the voices.
The bracket issue is that the override needs to go in a context where the
tuples sees it. By default it goes into the Voice context here, and the << … \
In the following code, the first expression does more or less what I
want; but I also want tuplet brackets. However, specifying that they
are wanted, as in the second expression, seems to break stuff, and I
have no idea why.
In fact, it is simply the presence of the override which causes the
