[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Notation manual - 1.3.3 Expressive marks as lines - glissandi

From: Simon Albrecht
Subject: Re: Notation manual - 1.3.3 Expressive marks as lines - glissandi
Date: Sat, 23 Apr 2016 09:03:36 +0200

Sorry, but what are you playing at with such an e-mail on the -devel list?
First, it’s a little bit offensive considering that – as you very well know – all people bringing Lily to you are only volunteers who do their very best to make her as good as possible. Second, this is a _developers’_ list. So if you have a technical question at developing LilyPond, or want to propose a patch, then you can come here. For a documentation suggestion as this the bug list is the right place. And you’ll be wise to provide a more precise description of the problem with that example in the docs and why your proposal solves that problem. ‘side effects have buggered everything else up’ and ‘mess up royally’ are so vague expressions that you basically expect others to figure out themselves what exactly these side effects are, and why the snippet doesn’t apply to your use case. The whole story of your pain with this issue may go to the user list then – maybe you can get some advice there.

Best, Simon

On 22.04.2016 22:30, Anthonys Lists wrote:
Arghh! Tweaks and workarounds!

"For a contemporary glissando from a note, you can use hideNote and cadenzaOn/Off". Except I've tried it and the side effects have buggered everything else up !!!

As soon as you start combining voices - like I separate markups, time signatures, etc from notes - as soon as you put a cadenza in one voice and not the others, they get out of sync and mess up royally.

So I tried to use a chord with a hidden note, except that it appears you can't put a rest into a chord ...

What I've done, which works for me, is to use a tuplet instead. imho this is much better, not least because it doesn't have nasty side effects.

I attach my little example below, if someone would care to put it in the manual instead of the one that's there.

  \once \override TupletBracket.bracket-visibility = ##f
  \once \hide TupletNumber
  \times 2/3 { r4 \hideNotes c'8\glissando \unHideNotes } c''2->

Okay, my example is to a note, not from, but when you're trying to do a score, or multiple instruments where some have "contemporary glissandi" and others don't, the example in the manual is going to cause grief. This version doesn't have side-effects.


lilypond-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]