bug-lilypond
[Top][All Lists]
Advanced

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

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


From: Nikolai Hedler
Subject: Re: v2.23.8: \fine seems to break \midi
Date: Mon, 27 Jun 2022 19:33:52 -0400

Copied from my comment on GitLab:

It seems that the programming error re: dynamics actually obscured some
other problems I encountered in my project. I had assumed that there was
only one fault at play here, but there's more to it than I thought.
MIDI ends late if \fine followed by a pitch.

\version "2.23.10"\score {  \unfoldRepeats  \repeat segno 2 {    c'1
\volta 2 \fine    2 2  }  \layout { }  \midi { }}

This produces correct sheet music but the MIDI file contains 4 notes
(ending one note *after* the \fine). No errors are logged. Changing the
second bar from 2 2 to r1 causes the MIDI output to behave as expected,
ending after the 2nd C without an extraneous rest.
Beaming and \fine

There's something funky going on with beaming: changing the 2nd bar from 2 2 to
8[ 8] 4 2 returns a couple of errors, but claims to compile successfully
and returns expected sheet music. Again, the MIDI output erroneously
includes the first note after the \fine on the 2nd repeat.
Log here:

Processing `[redacted]/document.ly'Parsing...Interpreting
music...[redacted]/document.ly:5:6: warning: unterminated beam  c'8
 [ 8] 4 2Preprocessing graphical objects...[redacted]/document.ly:5:3:
programming error: cyclic dependency: calculation-in-progress
encountered for Stem.direction    c'8[ 8] 4
2[redacted]/document.ly:5:3: continuing, cross
fingers[redacted]/document.ly:5:3: warning: direction of grob Stem
must be UP or DOWN; using UP    c'8[ 8] 4 2Interpreting music...MIDI
output to `document.mid'...Finding the ideal number of pages...Fitting
music on 1 page...Drawing systems...Converting to
`document.pdf'...Success: compilation successfully completed

Multi-measure rests

This one is very strange.

\version "2.23.10"\score {  \unfoldRepeats  \repeat segno 2 {    c'1
\volta 2 \fine    R1  }  \layout { }  \midi { }}

Errors in the log during MIDI processing, but the output seems correct
(MIDI file ends after \fine instead of including extraneous rest).

Log here:

Parsing...Interpreting music...Preprocessing graphical
objects...programming error: Multi measure rest seems
misplaced.continuing, cross fingersprogramming error: Object is not a
markup.continuing, cross fingersprogramming error: Multi measure rest
seems misplaced.continuing, cross fingersInterpreting music...MIDI
output to `document.mid'...Finding the ideal number of pages...Fitting
music on 1 page...Drawing systems...Converting to
`document.pdf'...This object should be a markup: ()Success:
compilation successfully completed

- Nikolai

On Tue, May 17, 2022 at 4:38 AM Jean Abou Samra <jean@abou-samra.fr> wrote:

>
>
> 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.000000 for dynamic span
> of
> > duration 3.000000 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
>
>


reply via email to

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