Re: v2.23.8: \fine seems to break \midi

[Jean Abou Samra]

Le 09/05/2022 à 20:11, Nikolai Hedler a écrit :

Windows 10, 64-bit

I discovered the new \fine feature and looked to implement it in a project
of mine, and I believe I've discovered a bug in its interaction with \midi
blocks. The following appears to be a minimal example which produces the
error for me:

\version "2.23.8"
\score {
   \unfoldRepeats
   \relative f' {
 \repeat segno 2 {
   c1 \volta 2 \fine
   c
 }
   }
   \midi { }
}

The expected result is 3 notes played, but it inexplicably produces 4. The
log includes the following inscrutable error in duplicate:

programming error: asked to compute volume at +3.00 for dynamic span of
duration 3.00 starting at 0
continuing, cross fingers

Not sure what other info may be helpful.


Thanks, opened

https://gitlab.com/lilypond/lilypond/-/issues/6345

Best,
Jean


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Lilypond 2.22 & 2.23 return 0 when a Scheme error occurs.

[Jean Abou Samra]

Le 02/05/2022 à 08:50, Stéphane SOPPERA a écrit :

Hi,

This very basic program reproduce the issue:

#(error "test")

\relative {
  c'1 |
}

With Lilypond 2.20, the compilation produces:

Processing `scheme_err.ly'
Parsing...
scheme_err.ly:1:2: error: GUILE signaled an error for the expression 
beginning here

#
 (error "test")
scheme_err.ly:1: warning: no \version statement found, please add

\version "2.20.0"

for future compatibility
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `/tmp/lilypond-Cgqpyv'...
Converting to `scheme_err.pdf'...
Deleting `/tmp/lilypond-Cgqpyv'...
test
fatal error: failed files: "scheme_err.ly"

and the//`lilypond` process returns 1.

With Lilypond 2.22 & 2.23, the compilation produces:

Processing `scheme_err.ly'
Parsing...
scheme_err.ly:1:2: error: GUILE signaled an error for the expression 
beginning here

#
 (error "test")
scheme_err.ly:1: warning: no \version statement found, please add

\version "2.22.2"

for future compatibility
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Converting to `scheme_err.pdf'...
test
Success: compilation successfully completed

and the `lilypond` process returns 0.

Note that if the `-V` flag is used, then all versions of Lilypond fail 
and in that case no PDF is generated at all.

Here is a quick summary of the outputs of the different versions:

| version | -V  | rc | PDF |
|-+-++-|
|  2.23.8 | no  |  0 | yes |
|  2.23.8 | yes |  1 | no  |
|    2.22 | no  |  0 | yes |
|    2.22 | yes |  1 | no  |
|    2.20 | no  |  1 | yes |
|    2.20 | yes |  1 | yes |

Is this intentional that the newer versions don't fail anymore on some 
Scheme errors?

What is the rationale for this change?

Thanks!


Thanks, opened

https://gitlab.com/lilypond/lilypond/-/issues/6344

Best,
Jean



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond