Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

2024-01-16 Thread Knute Snortum 
On Mon, Jan 15, 2024 at 10:57 AM Hans Aikema 
wrote:

>
> I've created an issue for Frescobaldi and I should be able to start work
> on it today.
>
> https://github.com/frescobaldi/frescobaldi/issues/172
>
>
> Knute, you've missed a digit while copying the link and without doubt
> intended to refer to
> https://github.com/frescobaldi/frescobaldi/issues/1728
>

Thanks!  The Issue is now fixed in the repository.

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

2024-01-15 Thread Hans Aikema 
On 15 Jan 2024, at 19:40, Knute Snortum  wrote:On Mon, Jan 15, 2024 at 7:47 AM David Kastrup  wrote:

Calling

git grep "override[^=]*#'[a-z]"

in the current Frescobaldi source tree delivers _way_ too many hits.  I
don't consider it sane that the current Frescobaldi will pump out
pre-2.18 syntax in droves in its templates.

And I suspect that it also splits overrides into multiple lines, making
it harder to recognize them.I've created an issue for Frescobaldi and I should be able to start work on it today.https://github.com/frescobaldi/frescobaldi/issues/172Knute, you've missed a digit while copying the link and without doubt intended to refer tohttps://github.com/frescobaldi/frescobaldi/issues/1728--Knute Snortum 

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

2024-01-15 Thread Knute Snortum 
On Mon, Jan 15, 2024 at 7:47 AM David Kastrup  wrote:

>
> Calling
>
> git grep "override[^=]*#'[a-z]"
>
> in the current Frescobaldi source tree delivers _way_ too many hits.  I
> don't consider it sane that the current Frescobaldi will pump out
> pre-2.18 syntax in droves in its templates.
>
> And I suspect that it also splits overrides into multiple lines, making
> it harder to recognize them.
>

I've created an issue for Frescobaldi and I should be able to start work on
it today.

https://github.com/frescobaldi/frescobaldi/issues/172


--
Knute Snortum

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

2024-01-15 Thread David Kastrup 
Knute Snortum  writes:

> On Mon, Jan 15, 2024 at 5:28 AM David Kastrup  wrote:
>
>> Bernhard Kleine  writes:
>>
>> > Dear David,
>> >
>> > the file was created this morning from frescobaldi with the
>> > Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
>> > Nothing was done be myself apart from wrinting notes and lyrics.
>>
>> If the "Partitur-Assistent" creates those overrides, it needs to get fixed.
>>
>
> It has been:
>
> https://github.com/frescobaldi/frescobaldi/commit/fb79df399056ddd8ce2fa2b48ac36fc37bdc0588

Well, it's a start.  See my note about

git grep "override[^=]*#'[a-z]"

I get

TODO:  * drag an object to e.g. create an \override #'extra-offset command
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:\override 
DynamicLineSpanner #'staff-padding = #2.0
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:  \override 
BreathingSign #'text = \markup { \musicglyph #"scripts.rvarcomma" }
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:  \override 
TrillSpanner #'direction = #DOWN
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:  \override 
BreathingSign #'text = \markup { \musicglyph #"scripts.caesura.curved" }
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:  \override 
BreathingSign #'text = \markup { \musicglyph #"scripts.caesura.straight" }
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:  \override 
BreathingSign #'text = \markup { \musicglyph #"scripts.tickmark" }
frescobaldi_app/fonts/templates/musicfont-realbook.ly:\override Score.Clef 
#'break-visibility = #'#(#f #f #f)
frescobaldi_app/fonts/templates/musicfont-realbook.ly:\override 
Score.KeySignature #'break-visibility = #'#(#f #f #f)
frescobaldi_app/fonts/templates/musicfont-realbook.ly:\override 
Score.SystemStartBar #'collapse-height = #1
frescobaldi_app/scorewiz/scoreproperties.py:
ly.dom.Line(r"\override Staff.TimeSignature #'style = #'()", node)
frescobaldi_app/symbols/arpeggio_defaults.ily:\override StaffSymbol 
#'transparent = ##t
frescobaldi_app/symbols/arpeggio_defaults.ily:\override StaffSymbol #'width 
= #4
frescobaldi_app/symbols/arpeggio_defaults.ily:\override NoteHead 
#'no-ledgers = ##t
frescobaldi_app/symbols/arpeggio_defaults.ily:\override NoteHead #'stencil 
= #empty-stencil
frescobaldi_app/symbols/arpeggio_defaults.ily:\override Stem #'stencil 
=#empty-stencil
frescobaldi_app/symbols/bar_defaults.ily:\override StaffSymbol #'width = #'4
frescobaldi_app/symbols/bar_defaults.ily:\override StaffSymbol #'thickness 
= #1.2
frescobaldi_app/symbols/bar_kievan.ly:\override StaffSymbol #'width = #1.44
frescobaldi_app/symbols/bar_repeat_angled_double.ly:\override StaffSymbol 
#'width = #5.5
frescobaldi_app/symbols/bar_repeat_angled_end.ly:\override StaffSymbol 
#'width = #5.5
frescobaldi_app/symbols/bar_repeat_angled_start.ly:\override StaffSymbol 
#'width = #5.5
frescobaldi_app/symbols/bar_segno.ly:\override StaffSymbol #'width = #7
frescobaldi_app/symbols/bar_tick.ly:\override StaffSymbol #'staff-space = 
#(/ 7 8)
frescobaldi_app/symbols/clef_defaults.ily:\override StaffSymbol #'width = #4
frescobaldi_app/symbols/clef_tab.ly:\override StaffSymbol #'width = #4
frescobaldi_app/symbols/clef_tab.ly:\override StaffSymbol #'staff-space = #1
frescobaldi_app/symbols/clef_tab.ly:\override Clef #'font-size = #-3.5
frescobaldi_app/symbols/glissando_defaults.ily:\override StaffSymbol 
#'transparent = ##t
frescobaldi_app/symbols/glissando_defaults.ily:\override StaffSymbol 
#'width = #4
frescobaldi_app/symbols/glissando_defaults.ily:\override NoteHead #'stencil 
= #empty-stencil
frescobaldi_app/symbols/glissando_defaults.ily:\override Stem #'stencil = 
#empty-stencil
frescobaldi_app/symbols/glissando_defaults.ily:\override Stem #'length = #0
frescobaldi_app/symbols/glissando_defaults.ily:\override Glissando 
#'bound-details = #
frescobaldi_app/symbols/glissando_defaults.ily:  \override Glissando 
#'style = $style
frescobaldi_app/symbols/glissando_dotted.ly:\override Glissando #'thickness 
= #1.5
frescobaldi_app/symbols/spanner_beam16.ly:  \override NoteHead 
#'extra-spacing-width = #'(0 . 1.3)
frescobaldi_app/symbols/spanner_defaults.ily:\override StaffSymbol #'width 
= #4.4
frescobaldi_app/symbols/spanner_defaults.ily:\override StaffSymbol 
#'transparent = ##t
frescobaldi_app/symbols/spanner_melisma.ly:  \override Stem #'length = #3
frescobaldi_app/symbols/spanner_melisma.ly:  \override VerticalAxisGroup 
#'nonstaff-relatedstaff-spacing =
frescobaldi_app/symbols/spanner_phrasingslur.ly:\override Stem #'length = #0
frescobaldi_app/symbols/spanner_phrasingslur.ly:\override Stem #'direction 
= #DOWN
frescobaldi_app/symbols/spanner_phrasingslur.ly:\override Stem 
#'transparent = ##t
frescobaldi_app/symbols/spanner_phrasingslur.ly:\override Tie 
#'minimum-length = #4.4

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

2024-01-15 Thread David Kastrup 
Bernhard Kleine  writes:

> Am 15.01.2024 um 14:28 schrieb David Kastrup:
>> Bernhard Kleine  writes:
>>
>>> Dear David,
>>>
>>> the file was created this morning from frescobaldi with the
>>> Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
>>> Nothing was done be myself apart from wrinting notes and lyrics.
>> If the "Partitur-Assistent" creates those overrides, it needs to get fixed.
>
> It does create them. Any idea how to get is fixed in this particular case?

Calling

git grep "override[^=]*#'[a-z]"

in the current Frescobaldi source tree delivers _way_ too many hits.  I
don't consider it sane that the current Frescobaldi will pump out
pre-2.18 syntax in droves in its templates.

And I suspect that it also splits overrides into multiple lines, making
it harder to recognize them.

-- 
David Kastrup

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

2024-01-15 Thread Knute Snortum 
On Mon, Jan 15, 2024 at 5:28 AM David Kastrup  wrote:

> Bernhard Kleine  writes:
>
> > Dear David,
> >
> > the file was created this morning from frescobaldi with the
> > Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
> > Nothing was done be myself apart from wrinting notes and lyrics.
>
> If the "Partitur-Assistent" creates those overrides, it needs to get fixed.
>

It has been:

https://github.com/frescobaldi/frescobaldi/commit/fb79df399056ddd8ce2fa2b48ac36fc37bdc0588


--
Knute Snortum

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

2024-01-15 Thread Bernhard Kleine 


Am 15.01.2024 um 14:28 schrieb David Kastrup:

Bernhard Kleine  writes:


Dear David,

the file was created this morning from frescobaldi with the
Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
Nothing was done be myself apart from wrinting notes and lyrics.

If the "Partitur-Assistent" creates those overrides, it needs to get fixed.


It does create them. Any idea how to get is fixed in this particular case?

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

2024-01-15 Thread David Kastrup 
Bernhard Kleine  writes:

> Dear David,
>
> the file was created this morning from frescobaldi with the
> Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
> Nothing was done be myself apart from wrinting notes and lyrics.

If the "Partitur-Assistent" creates those overrides, it needs to get fixed.

-- 
David Kastrup

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

2024-01-15 Thread Bernhard Kleine 

Dear David,

the file was created this morning from frescobaldi with the
Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
Nothing was done be myself apart from wrinting notes and lyrics.

Am 15.01.2024 um 13:06 schrieb David Kastrup:

Bernhard Kleine  writes:


The following MWE gave a warning

C:/Users/bk/AppData/Local/Temp/frescobaldi-n7fp9iem/tmp_isr57mt/document.ly:52:25:
Warnung: deprecated: missing `.' in property path StaffSymbol.staff-space

I think maybe the frescobaldi is not aware of changes to this lilypond
version. What do I have change to make the score compile without this
warning?

Kind regards

Bernhard

\version "2.25.7"

Do _NOT_ update the version header by hand.  That is the job of
convert-ly when it also updates the syntax of your file to a newer
version.

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

2024-01-15 Thread David Kastrup 
Bernhard Kleine  writes:

> The following MWE gave a warning
>
> C:/Users/bk/AppData/Local/Temp/frescobaldi-n7fp9iem/tmp_isr57mt/document.ly:52:25:
> Warnung: deprecated: missing `.' in property path StaffSymbol.staff-space
>
> I think maybe the frescobaldi is not aware of changes to this lilypond
> version. What do I have change to make the score compile without this
> warning?
>
> Kind regards
>
> Bernhard
>
> \version "2.25.7"

Do _NOT_ update the version header by hand.  That is the job of
convert-ly when it also updates the syntax of your file to a newer
version.

-- 
David Kastrup

Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

2024-01-15 Thread Kevin Cole 
On Mon, Jan 15, 2024 at 6:26 AM Bernhard Kleine  wrote:

> The following MWE gave a warning
>
> C:/Users/bk/AppData/Local/Temp/frescobaldi-n7fp9iem/tmp_isr57mt/document.ly:52:25:
>  Warnung: deprecated: missing `.' in property path StaffSymbol.staff-space
>
> I think maybe the frescobaldi is not aware of changes to this lilypond 
> version. What do I have change to make the score compile without this warning?

I'm FAR from an expert, but the few times I've encountered errors like
that, the error message basically seems to tell me what I should do,
albeit not in the clearest way.

Does changing StaffSymbol #'staff-space to StaffSymbol.staff-space fix
the problem?

(Or am I misunderstanding your question?)

I note, as I often do, too many older versions of documentation --
apparently, from 2.13 to 2.24, with the documentation for 2.25 not
there yet. But this page for 2.24 suggests to me, the change that the
error message suggested...

https://lilypond.org/doc/v2.24/Documentation/snippets/spacing

Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0

2024-01-15 Thread Bernhard Kleine 

The following MWE gave a warning

C:/Users/bk/AppData/Local/Temp/frescobaldi-n7fp9iem/tmp_isr57mt/document.ly:52:25:
Warnung: deprecated: missing `.' in property path StaffSymbol.staff-space

I think maybe the frescobaldi is not aware of changes to this lilypond
version. What do I have change to make the score compile without this
warning?

Kind regards

Bernhard


\override StaffSymbol

#'staff-space = #(magstep -1)


\version "2.25.7"
\language  "deutsch"

global = {
  \key b \major
  \time 2/2
}

soprano = \relative c' {
  \global
    f1
}

alto = \relative c' {
  \global
    b1|
}

tenor = \relative c' {
  \global
    b1
}

bass = \relative c' {
  \global
  % Die Noten folgen hier.
  b1
}

sopranoVerse = \lyricmode {
  % Liedtext folgt hier.
  O mag -- num
}

altoVerse = \lyricmode {
  % Liedtext folgt hier.
  O mag -- num
}

tenorVerse = \lyricmode {
  % Liedtext folgt hier.
  O mag -- num
}

bassVerse = \lyricmode {
  % Liedtext folgt hier.
  O mag -- num
}

pianoReduction = \new PianoStaff \with {
  fontSize = #-1
\override StaffSymbol #'staff-space = #(magstep -1)
} <<
  \new Staff \with {
    \consists "Mark_engraver"
    \consists "Metronome_mark_engraver"
    \remove "Staff_performer"
  } {
    #(set-accidental-style 'piano)
    <<
  \soprano \\
  \alto
    >>
  }
  \new Staff \with {
    \remove "Staff_performer"
  } {
    \clef bass
    #(set-accidental-style 'piano)
    <<
  \tenor \\
  \bass
    >>
  }
>>

\score {
  <<
    \new ChoirStaff <<
  \new Staff \with {
    midiInstrument = "choir aahs"
  } { \soprano }
  \addlyrics { \sopranoVerse }
  \new Staff \with {
    midiInstrument = "choir aahs"
  } { \alto }
  \addlyrics { \altoVerse }
  \new Staff \with {
    midiInstrument = "choir aahs"
  } { \clef "treble_8" \tenor }
  \addlyrics { \tenorVerse }
  \new Staff \with {
    midiInstrument = "choir aahs"
  } { \clef bass \bass }
  \addlyrics { \bassVerse }
    >>
    \pianoReduction
  >>
  \layout { }
  \midi {
    \tempo 4=100
  }
}