Re: N.C. No Chord poll
Hi David, all, >1. How many Lilyponders think that "N.C." is elegant? It's the standard, and that's good enough for me. >2. How many guitar teachers instruct their students to keep strumming when >they see a rest? It depends what's on the staff. If the vocal/melody line is notated, it makes good sense to keep strumming in the rests between vocal phrases. Not every rest is a break! It makes sense to suppress N.C. only when the strumming pattern is expressly notated on the staff. >3. In what genres is it normative for guitars to continue strumming through >every rest? As noted above, not through any, but through many. >4. If genres exist where it is normative for guitar players to strum >throughout a rest, in these genres is it also normative for the other >musicians to sustain or fiddle throughout a rest? You're obviously confusing a rest within a voice with a general pause. The two are not the same. 5-6 are too silly to answer. >7. The decision with every LilyPond iteration not to allow a third option, >namely, normative blank over the rest, i.e. suppress the "N.C." gimmick -- >what are the reasons which LilyPond insiders have found so persuasive over the >years? Blank should be an option among many. And to my knowledge, it exists. >8. How many people feel that LilyPond is being clueless when it comes to >making "N.C." the default setting? If we take our clues from standard notation conventions, then questioning "N.C." is either clueless or willful ignorance of standard practice. >How can it be otherwise? Why should it be? Just my 2 cents, Amy -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Re: Bug in Completion_heads_engraver ?
Sorry! sent that reply from an address that was not subscribed to the list.
Re-sending.
> On 21 May 2023, at 14:53, Graham King ... wrote:
>
> Thanks Jean, both for the solution and for the education.
>
>> On 21 May 2023, at 13:58, Jean Abou Samra wrote:
>>
>>
>> Le dimanche 21 mai 2023 à 12:09 +0100, Graham King a écrit :
>>
>>> In the following code, I would expect the tie between the final two notes
>>> to be dotted. The actual output is a solid tie. Not sure whether this is
>>> a bug or just my doing something wrong...
>>>
>>> \version "2.25.0"
>>>
>>> { c''2
>>> \once \tieDotted
>>> \set melismaBusyProperties = #'()
>>> 1 ~ 2
>>> }
>>>
>>> \layout {
>>> \context {
>>> \Voice
>>> \remove "Note_heads_engraver"
>>> \consists "Completion_heads_engraver"
>>> }
>>> }
>>> I can work around this pretty easily, but I'd rather preserve the note
>>> durations of the original mensural notation if possible.
>>>
>> That the second tie is not dotted is perfectly normal since \once makes a
>> command apply only at the current moment, and that tie starts later.
>>
> I feared that this might be the case. I'll have to be much more circumspect
> when using the Completion_heads_engraver, in case a change of barline
> distribution triggers this unexpectedly.
>> What is more surprising is that the first tie is not dotted; this is harder
>> to explain simply, it's caused by shenanigans in the internals of
>> Completion_heads_engrver (it creates ties “retroactively”, later than when
>> they start).
>>
>> Try
>>
>> \version "2.24.1"
>>
>> { c''2
>> \once \override Tie.color = red
>> \set melismaBusyProperties = #'()
>> 1 \single \tieDotted ~ 2
>> }
>>
>> \layout {
>> \context {
>> \Voice
>> \remove "Note_heads_engraver"
>> \consists "Completion_heads_engraver"
>> }
>> }
> That works! I didn't know about \single (and I hadn't thought of using a
> tweak). I might convert all my dotted-tie instances to this mechanism, to
> avoid the impression that the decisions of the Completion_heads_engraver are
> changing the semantics of the .ly file.
Re: N.C. No Chord poll
I usually use an m-dash "—" as the noChordSymbol as it is more language agnostic. But N.C. is reasonable default IMHO.
Re: Bug in Completion_heads_engraver ?
Thanks Jean, both for the solution and for the education.
> On 21 May 2023, at 13:58, Jean Abou Samra wrote:
>
>
>>
>> Le dimanche 21 mai 2023 à 12:09 +0100, Graham King a écrit :
>>
>> In the following code, I would expect the tie between the final two notes to
>> be dotted. The actual output is a solid tie. Not sure whether this is a
>> bug or just my doing something wrong...
>>
>> \version "2.25.0"
>>
>> { c''2
>> \once \tieDotted
>> \set melismaBusyProperties = #'()
>> 1 ~ 2
>> }
>>
>> \layout {
>> \context {
>> \Voice
>> \remove "Note_heads_engraver"
>> \consists "Completion_heads_engraver"
>> }
>> }
>> I can work around this pretty easily, but I'd rather preserve the note
>> durations of the original mensural notation if possible.
>>
> That the second tie is not dotted is perfectly normal since \once makes a
> command apply only at the current moment, and that tie starts later.
>
I feared that this might be the case. I'll have to be much more circumspect
when using the Completion_heads_engraver, in case a change of barline
distribution triggers this unexpectedly.
> What is more surprising is that the first tie is not dotted; this is harder
> to explain simply, it's caused by shenanigans in the internals of
> Completion_heads_engrver (it creates ties “retroactively”, later than when
> they start).
>
> Try
>
> \version "2.24.1"
>
> { c''2
> \once \override Tie.color = red
> \set melismaBusyProperties = #'()
> 1 \single \tieDotted ~ 2
> }
>
> \layout {
> \context {
> \Voice
> \remove "Note_heads_engraver"
> \consists "Completion_heads_engraver"
> }
> }
That works! I didn't know about \single (and I hadn't thought of using a
tweak). I might convert all my dotted-tie instances to this mechanism, to
avoid the impression that the decisions of the Completion_heads_engraver are
changing the semantics of the .ly file.
Re: Bug in Completion_heads_engraver ?
Le dimanche 21 mai 2023 à 12:09 +0100, Graham King a écrit :
> In the following code, I would expect the tie between the final two notes to
> be dotted. The actual output is a solid tie. Not sure whether this is a bug
> or just my doing something wrong...
>
> ```
> \version "2.25.0"
>
> { c''2
> \once \tieDotted
> \set melismaBusyProperties = #'()
> 1 ~ 2
> }
>
> \layout {
> \context {
> \Voice
> \remove "Note_heads_engraver"
> \consists "Completion_heads_engraver"
> }
> }
> ```
>
> I can work around this pretty easily, but I'd rather preserve the note
> durations of the original mensural notation if possible.
That the second tie is not dotted is perfectly normal since `\once` makes a
command apply only at the current moment, and that tie starts later.
What is more surprising is that the *first* tie is not dotted; this is harder
to explain simply, it's caused by shenanigans in the internals of
`Completion_heads_engrver` (it creates ties “retroactively”, later than when
they start).
Try
```
\version "2.24.1"
{ c''2
\once \override Tie.color = red
\set melismaBusyProperties = #'()
1 \single \tieDotted ~ 2
}
\layout {
\context {
\Voice
\remove "Note_heads_engraver"
\consists "Completion_heads_engraver"
}
}
```
signature.asc
Description: This is a digitally signed message part
LilyPond 2.25.5
We are happy to announce the release of LilyPond 2.25.5. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.1, the current stable release. Please refer to the Installing section in the Learning Manual for instructions how to set up the provided binaries: https://lilypond.org/doc/v2.25/Documentation/learning/installing signature.asc Description: This is a digitally signed message part
Re: Using Variables
Johannes Roeßler writes:
> Hi Group,
>
> I try to define this:
>
> neo = {\once \override NoteHead.style = #'neomensural}
>
> but it leads to errors in the following parts (no error message
> regarding the variable definition though...)
>
> What am I doing wrong?
You are not posting your actual code and your actual error messages.
The above will fail because of a missing space after neomensural alone.
Please try to come up with a complete small example exhibiting your
problem.
--
David Kastrup
Using Variables
Hi Group,
I try to define this:
neo = {\once \override NoteHead.style = #'neomensural}
but it leads to errors in the following parts (no error message
regarding the variable definition though...)
What am I doing wrong?
Best regards
Joei
Bug in Completion_heads_engraver ?
In the following code, I would expect the tie between the final two notes to be
dotted. The actual output is a solid tie. Not sure whether this is a bug or
just my doing something wrong...
\version "2.25.0"
{ c''2
\once \tieDotted
\set melismaBusyProperties = #'()
1 ~ 2
}
\layout {
\context {
\Voice
\remove "Note_heads_engraver"
\consists "Completion_heads_engraver"
}
}
I can work around this pretty easily, but I'd rather preserve the note
durations of the original mensural notation if possible.
-- Graham
Re: Fonts and Tempo
For Unicode in Windows my preference is a little program called Wizkey - not
free, but extremely ergonomic, both for searching and blind typing (in the case
of ö, I just keyed: ctrl-: o).
https://antibody-software.com/wizkey/
For the tempo example, I just use markup in the \tempo command.
For the equality, I use something like:
^\markup \left-align \concat { " ← " \smaller \note-by-number #2 #0 #0.8 "
=" \smaller \note-by-number #2 #0 #0.8 " →" }
with alignment and offset trimmed as required (in my case to get the = over the
bar-line).
Regards,
Paul
From: Greg Lindstrom
To:
Sent: 21/05/2023 3:42
Subject: Fonts and Tempo
Good evening -
Let me start off by saying I'm loving working with lilypond to engrave music.
Well Done!!
Questions. How can I do this (an umlaut over the o??)
And on tempo markings (the "ca." after the equal sign. I could do it as all
text but wanted to know if there's a more "lilypond" way to do it).
And as long as I'm asking (and you're still reading). How about this (a half
note = a quarter note. I'd be happy to do it without the arrows -- which I
think borders on silly -- but I'll give extra credit):
Thanks for any help you can provide. I have the Lilypond 2.12 Notation
Reference so if you even point me to the section to reference I'll work it out.
Kind Regards,
--greg
Re: Fonts and Tempo
Le samedi 20 mai 2023 à 23:30 -0400, William Rehwinkel via LilyPond user
discussion a écrit :
> My apologies for double-posting...after writing I looked some more and found
> that you can use **\char ##x** to enter unicode characters in a markup
> block as in here
> [https://lilypond.org/doc/v2.25/Documentation/notation/unicode](https://lilypond.org/doc/v2.25/Documentation/notation/unicode)
Now that we are on Guile 2, you can also use the built-in Guile syntax:
```
\version "2.25.4"
\markup { ft #"S\xf6rent" }
```
More info here:
https://www.gnu.org/software/guile/manual/html_node/String-Syntax.html
signature.asc
Description: This is a digitally signed message part
Re: Fonts and Tempo
Le samedi 20 mai 2023 à 23:24 -0400, William Rehwinkel via LilyPond user
discussion a écrit :
> For the third I hacked together the following, which you can tinker with to
> your liking
>
> ```
> % --
> \version "2.25.4"
>
> \relative c' {
> c4 d e f | \mark \markup \smaller {\super\combine \draw-line #'(2 . 0)
> \arrow-head #X #LEFT ##t \rhythm {2 } = \rhythm { 4 } \super\combine
> \draw-line #'(-2 . 0) \arrow-head #X #RIGHT ##t} g4
> }
> % --
> ```
`\mark \markup` is soft-deprecated though (by which I mean that it will keep
working in the foreseeable future for backwards compatibility, but is no longer
recommended). Better use
```
\version "2.25.4"
\relative c' {
c4 d e f |
\tweak self-alignment-X #CENTER \textMark \markup \smaller {
\super \combine \draw-line #'(2 . 0) \arrow-head #X #LEFT ##t
\rhythm { 2 } = \rhythm { 4 }
\super \combine \draw-line #'(-2 . 0) \arrow-head #X #RIGHT ##t
}
g4
}
```
Best,
Jean
signature.asc
Description: This is a digitally signed message part
