German bar lines documentation

2020-04-05 Thread Noeck
Hi,

tl;dr

- Zusätzlich kann noch "||:" verwendet werden, dass sich genauso wie
- "|:" verhält
+ Zusätzlich kann noch ".|:-||" verwendet werden, dass sich genauso wie
+ ".|:" verhält
___

the German docs read
http://lilypond.org/doc/v2.20/Documentation/notation/bars.de.html

> Zusätzlich kann noch "||:" verwendet werden, dass sich genauso wie "|:" 
> verhält

which does not work:

\version "2.20.0"

{
  a1 \bar  ".|:-||" \break   % works as expected
  a1 \bar  "||:" \break  % does not work
  a1
}

The bar should be as in the English docs:

> In addition, you can specify ".|:-||", which is equivalent to ".|:"

I guess this is from some ancient version when barline nomenclature was
different.

Well, there is a lot more which is not up to date, examples are
different or missing etc. Does it make sense to get into translating if
I can only contribute from time to time, let's say 2 paragraphs and then
2 months nothing? I could imagine that even small changes add up over
time. If that makes sense, I would read through the contributors manual
(translations) and come back to the dev list in case of questions.

Cheers,
Joram



Re: German bar lines documentation

2020-04-05 Thread Torsten Hämmerle
Noeck wrote
> [...] verwendet werden, dass sich genauso wie […]


Hi Joram,

No problems as to the bar lines, but it definitely has to be "*das*", not
"*dass*".

I'd also prefer "sich /genau so/ wie […] verhält" over "sich /genauso/ wie
[…] verhält" in this case.

Cheers,
Torsten



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html



Re: German bar lines documentation

2020-04-05 Thread Noeck
Hi Torsten,

well, there are various other issues. That's why I wanted to clarify
*how* to address them before I list all I found.

> has to be "*das*", not "*dass*".

Of course.

> I'd also prefer "sich /genau so/ wie […] verhält" over "sich /genauso/ wie
> […] verhält" in this case.

If this¹ is correct, I'd use "genauso".

¹: https://www.julianetopka.de/zwei-minuten-archiv/juli-2014

Cheers,
Joram



Fingering and slurs

2020-04-05 Thread Noeck
Hi,

I am transcribing piano music and I see a lot of ugly situations with
fingering and slurs.

Lilypond seems to draw the slur and then puts the fingering on the
inside if there is space and on the outside if not. From the score, I am
reading, I deduce these rules:

- fingering above the slur at slur tips
- fingering inside the slur otherwise
- fingering is above the staff for c'' and higher notes and
  inside the staff for lower notes

Is this a general practice or just happens to be what I see here?

I can regularly switch from avoid-slur between inside and outside and
set staff-padding to ##f and revert it by hand. But can you give me some
hints how to implement the rules above? I.e.

1. change avoid-slur based on slur beginnings and endings and
2. change staff-position based on the pitch of the note?

MWE:

\relative {
  \time 3/4
  \tempo "default"
  b'4.-2( a8-1 cis-2 e-4) |

  \tempo "inside"
  \override Fingering.avoid-slur = #'inside
  b4.-2( a8-1 cis-2 e-4) |
  \revert Fingering.avoid-slur

  \tempo "what I want"
  b4.-2(
  \once \override Fingering.staff-padding = ##f
  \override Fingering.avoid-slur = #'inside
  a8-1
  % I know this looks bad, but I that is the best rule I could find
  % \override Fingering.staff-padding = ##f  % manual override
  cis-2
  \revert Fingering.avoid-slur
  e-4) |
}

Thanks in advance.
Joram



Unwanted warnings/errors on pedals for multiple voices

2020-04-05 Thread Paolo Prete
Hello,

I still experience unwanted warnings (and, consequently, unwanted behavior
on midi) with pedals on PianoStaff with multiple voices.
Consider this example (tested on 2.19.84):



\version "2.19.84"

upper = {

<<
{c'8\sustainOn c' c'}
\\
{r8 r r}
>>

<<
{c'8 c' r}
\\
{r8 r c'\sustainOff}
>>

}

lower = { }

\score {
  \new PianoStaff <<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>
  \layout { }
  \midi { }
}



The output says "warning: cannot find start of piano pedal: `Sustain'"

The warning disappears if I put \sustainOff on the first voice of the
second expression. And it disappears as well If I don't use a PianoStaff,
but I simply compile this:



{
<<
{c'8\sustainOn c' c'}
\\
{r8 r r}
>>

<<
{c'8 c' r}
\\
{r8 r c'\sustainOff}
>>
}



I don't understand if this is a bug (it seems so). But, anyway, is there a
way to fix the issue in the first example, *without* having to write all
the pedals in the voices that are put at the same level (which I think is
not only pointless, but also uncomfortable)?

Thanks
P


Re: Fingering and slurs

2020-04-05 Thread Martin Tarenskeen




On Sun, 5 Apr 2020, Noeck wrote:


I am transcribing piano music and I see a lot of ugly situations with
fingering and slurs.


+1

following.



Re: Unwanted warnings/errors on pedals for multiple voices

2020-04-05 Thread Timothy Lanfear

On 05/04/2020 15:11, Paolo Prete wrote:

Hello,

I still experience unwanted warnings (and, consequently, unwanted 
behavior on midi) with pedals on PianoStaff with multiple voices.

Consider this example (tested on 2.19.84):



\version "2.19.84"

upper = {

<<
{c'8\sustainOn c' c'}
\\
{r8 r r}
>>

<<
{c'8 c' r}
\\
{r8 r c'\sustainOff}
>>

}

lower = { }

\score {
  \new PianoStaff <<
    \new Staff = "upper" \upper
    \new Staff = "lower" \lower
  >>
  \layout { }
  \midi { }
}



You could move the Piano_pedal_performer from Voice to Staff level. Add 
or remove the \consists command to hear the difference.


\version "2.20.0"

\midi {
    \context { \Voice \remove Piano_pedal_performer }
    \context { \Staff \consists Piano_pedal_performer }
}

upper = {
  <<
    {c'8\sustainOn r r}
  \\
    {r8 r r}
  >>

  <<
    {r8 r r}
  \\
    {r8 r c'\sustainOff}
  >>
}

lower = { s1 }

\score {
  %{ \new PianoStaff %} <<
    \new Staff = "upper" \upper
    \new Staff = "lower" \lower
  >>
  \layout { }
  \midi { }
}


--
Timothy Lanfear, Bristol, UK.




Re: Unwanted warnings/errors on pedals for multiple voices

2020-04-05 Thread Paolo Prete
On Sun, Apr 5, 2020 at 6:04 PM Timothy Lanfear  wrote:

>
> You could move the Piano_pedal_performer from Voice to Staff level. Add
> or remove the \consists command to hear the difference.
>
> \version "2.20.0"
>
> \midi {
>  \context { \Voice \remove Piano_pedal_performer }
>  \context { \Staff \consists Piano_pedal_performer }
> }
>
> upper = {
><<
>  {c'8\sustainOn r r}
>\\
>  {r8 r r}
>>>
>
><<
>  {r8 r r}
>\\
>  {r8 r c'\sustainOff}
>>>
> }
>
> lower = { s1 }
>
> \score {
>%{ \new PianoStaff %} <<
>  \new Staff = "upper" \upper
>  \new Staff = "lower" \lower
>>>
>\layout { }
>\midi { }
> }
>
>
>
Thanks, this helps a lot.
Together with this:
https://lists.gnu.org/archive/html/lilypond-user/2020-01/msg00119.html
it should be added to the *official* documentation. IMHO.


incomplete tuplets in non-standard time signatures

2020-04-05 Thread 98123981293 1293812397123
Dear list,

In the following example, I would like to:
1) In the first voice: make the tuplet line to the right of the number into
a dashed straight line.
2) In the second voice: fix the appearance of the last tuplet in the
measure so that the number does not clash with the bracket, and the bracket
is not horizontally flipped. Once this is accomplished, I would like to
apply the same appearance with dotted right lines from step one. I've
attached a .png drawing of roughly how I want it to look.

This thread (
https://www.mail-archive.com/lilypond-user@gnu.org/msg89110.html) addresses
these types of alterations, but affects the whole bracket; is there any way
to adjust the left and right sides of the bracket independently?  If this
has already been addressed elsewhere please let me know so that I may
consult the relevant documentation/snippet/archive.

Thank you for your time,
-Kyle

\version "2.18.2"

\header {
  subsubtitle = "incomplete tuplets in non-standard time sigs"
}

\score {
<<
\new Staff {
\clef treble
\key c \major
\set subdivideBeams = ##t
\set strictBeatBeaming = ##t
\override TupletBracket.bracket-visibility = ##t

\time 8/24
\times 2/3 {
bes'16[
 \set stemLeftBeamCount =2
 \set stemRightBeamCount =2
d''16
b'16]
}
\times 2/3 {
cis''8[
f''16]
}
\times 2/3 {
d''16[
e''16]
}
}


\new Staff {
 \clef bass
\key c \major
\set subdivideBeams = ##t
\set strictBeatBeaming = ##t
\override TupletBracket.bracket-visibility = ##t

 \time 8/24
a8~
\times 2/3 {
a8[
g16~]
}
\times 2/3 {
g8
}
}
>>
}


Edition engraver and upbeat

2020-04-05 Thread Noeck
Hi,

how can I address timesteps in an upbeat (partial) with the edition
engraver? Am I correct that this is still not possible?

https://lists.gnu.org/archive/html/lilypond-user/2017-04/msg00574.html

Best,
Joram



Re: Alignment issues of Time signature above the staff

2020-04-05 Thread Chen Leo
Hi,
Thank you for your responses.
I managed to solve the bar number problem by removing the "Bar_number_engraver" 
from the staff context and \consists "Bar_number_engraver" in the staff under 
the time signature.
For the time signature’s alignment, I found a simpler solution by using 
\override TimeSignature.break-align-symbol = #'staff-bar with \override 
MultiMeasureRest.spacing-pair = #'(clef . staff-bar). However, It still causes 
break-alignment issues from here to there.

Example:

\version "2.19.0"

timeSignatures = { \numericTimeSignature \tempo 4 = 80 \time 4/4 s1 \time 3/8 
s4.
\time 3/4 s2. \time 4/4 s1 }

\score {
  \layout {
  \context {
\type "Engraver_group"
\consists "Time_signature_engraver"
\consists "Axis_group_engraver"
\name "TimeSig"
\alias "Staff"
  \override TimeSignature.font-size = #8
  \override TimeSignature.break-align-symbol = #'staff-bar
  \override TimeSignature.X-offset =
  #ly:self-alignment-interface::x-aligned-on-self
  \override TimeSignature.self-alignment-X = #LEFT
  %\override TimeSignature.X-extent = #'(0 . 0)
  }
  \context {
\Score
\accepts TimeSig
\remove "Bar_number_engraver"
  }
  \context {
\Staff
\override MultiMeasureRest.spacing-pair = #'(clef . staff-bar)
\remove "Time_signature_engraver"
  }
  \context {
\Score
  }
}
  <<
\new TimeSig \with {
}
{
  \timeSignatures
}

\new StaffGroup \with {} <<
\new Staff \with {
\consists "Bar_number_engraver"
}
\relative c' {
\textLengthOn
c4 ( _\markup \column {
"← Objects failed to appear"
"below the time signature"
"when using \\textLengthOn"
}
\textLengthOff
d4 e4 f4 )
a''4 ( g8 ) R2. c1 }
\new Staff \relative c' {
R1
R4.
\clef bass
a2. \> \break
c2 _\markup \column {
"  "
"↑"
"Hairpin stops below the time signature"
}  c2\! }
\new Staff \relative c' { R1 R4. R2. c1 }
>>
  >>
}



On 3/29/2020 2:10 AM, Chen Leo wrote:

Hi Kevin,


Thank you for your reply.


For the first problem, you will have to set break-align-symbol to ##f to 
reproduce the problem. That is because by default break-align-symbol is set to 
#'time-signature. so commenting out the override shouldn't help.


Secondly, using \override TimeSignature.X-extent = #'(0 . 0) causes collisions 
when texts and notes are displayed above the staff because lilypond is not 
adding vertical spacing above the staff. And it seems like now all the time 
signatures are shifted a bit to the right instead of aligning right after the 
bar line.


Thirdly, the bar numbers are raised to align vertically with the 
time-signatures, which is not something I would like to have. It will be nice 
if you can share any ideas on how that can be solved.


Leo

Here's an example:

\version "2.20.0"

\layout {
  \context {
\type "Engraver_group"
\consists "Time_signature_engraver"
\consists "Axis_group_engraver"
\name "TimeSig"
\alias "Staff"
% original settings from 
"http://lsr.di.unimi.it/LSR/Snippet?id=272";
%{
  \override TimeSignature.font-size = #3
  \override TimeSignature.break-align-symbol = ##f
  \override TimeSignature.X-offset =
#ly:self-alignment-interface::x-aligned-on-self
  \override TimeSignature.self-alignment-X = #CENTER
  \override TimeSignature.after-line-breaking =
  #shift-right-at-line-begin
%}
% settings after adjustments
{
\override TimeSignature.font-size = #4
\override TimeSignature.X-offset =
  #ly:self-alignment-interface::x-aligned-on-self
\override TimeSignature.self-alignment-X = #LEFT
\override TimeSignature.X-extent = #'(0 . 0)
}
  }
  \context {
\Score
\accepts TimeSig
  }
  \context {
\Staff
\remove "Time_signature_engraver"
  }
}

timeSignatures = { \numericTimeSignature \time 4/4 s1 \time 3/8 s4. \time 3/4 
s2. \break \time 4/4 s1 }

\score {
  <<
\new TimeSig \timeSignatures
\new Staff \relative c' { c4 ^\markup \column {"a" "b" "c"} ( d4 e4 f4 ) 
a''4
  ^\markup \column {"a" "b" "c"} ( g8 ) R2. c1 }
\new Staff \relative c' { R1 R4. \clef bass a2. c1 }
\new Staff \relative c' { R1 R4. R2. c1 }
  >>
}




Hi Chen,

I was able to solve the second of your problems (the whole bar rests
being shifted by the time signatures in the TimeSig context) by
adding:
\override TimeSignature.X-extent = ##f
(You could also use the value #'(0 . 0) if the warnings are off
putting, but I noticed that that doesn't *quite* fix it fully.)

I tried to reproduce your description of the first problem (time
signatures aligning over cue clefs), but even commenting out the
break-align-symbol override didn't make it appear. I was able to
correct the alignment of the first time signature by removing the
line:
\override Tim