I've been getting hundreds of these warnings in each of my music files:

warning: MIDI channel wrapped around
warning: remapping modulo 16

These warnings begin to accumulate as I add calls to set the minimumFret.
It seems to be related to the transposition calls I'm doing as well, since
removing them makes the warning go away.

I've included a minimal example that demonstrates the problem
with just one warning.   In the real music I never set the minimum fret
to the same value twice in a row, but doing it here simplified the example.

I make an effort to try to keep my music files warning free, so it pains me
to see hundreds of these scroll by on every compile.  If I'm structuring my
files wrong (e.g. the way I'm instantiating the staffs or doing the
transpositions)
I'm happy to change them.  But this was the only way I could manage to
force the tabs and the MIDI output both into the correct octaves.

Thanks,

-steve

\version "2.13.10"
music = {
  <<
    \relative c' {
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
      \set TabStaff.minimumFret = #1 c
    }
  >>
}
\score {
  {
    <<
      \new Staff { \music }
      \new TabStaff { \transpose c c, { \music } }
    >>
  }
}
\score {
  {
    \transposition c \music
  }
  \midi {
    \context {
      \Score
    }
  }
}
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to