bug-lilypond
[Top][All Lists]
Advanced

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

Re: Barcheck warning with independent meters and midi


From: Thomas Morley
Subject: Re: Barcheck warning with independent meters and midi
Date: Sat, 30 Mar 2019 22:32:35 +0100

Am Sa., 30. März 2019 um 20:20 Uhr schrieb N Trocado <address@hidden>:
>
> The following produces a barcheck warning:
>
> \version "2.19.82"
>
> \layout {
>   \context {
>     \Score
>     \remove "Timing_translator"
>     \remove "Default_bar_line_engraver"
>   }
>   \context {
>     \Staff
>     \consists "Timing_translator"
>     \consists "Default_bar_line_engraver"
>   }
> }
>
> \score {
>   <<
>     \new Staff {
>       \time 4/4
>       a1 |
>     }
>     \new Staff {
>       \time 7/8
>       a4. a4 a |
>     }
>   >>
>   \layout { }
>   \midi { }
> }
>
> -> 21:10: warning: barcheck failed at: 1/8
>       a1
>          |
>
> There's no warning if I comment out the midi block.
> Despite the warning, the midi file plays correctly, following the time 
> signature of the lowest staff.
> AFAIK the midi standard may not allow for independent meters in different 
> channels. If this is the reason for the barcheck warning, maybe a more 
> specific (single) message would be appropriate? It took me a long time to 
> find out why the barcheck warnings were being produced...

You move engravers, this has _no_ impact on midi.
Instead you should do:

\score {
  <<
    \new Staff {
      \time 4/4
      c'1 |
    }
    \new Staff {
      \time 7/8
      a4. a4 a |
    }
  >>
  \layout {
    \context {
      \Score
      \remove "Timing_translator"
      \remove "Default_bar_line_engraver"
    }
    \context {
      \Staff
      \consists "Timing_translator"
      \consists "Default_bar_line_engraver"
    }
  }
  \midi {
    \context {
      \Score
      \remove "Timing_translator"
    }
    \context {
      \Staff
      \consists "Timing_translator"
    }
  }
}

So no bug in the source code.
Admittedly midi is highly underdocumented.
Which is the real problem here ...


Cheers,
  Harm



reply via email to

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