Ottavation markups

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Ottavation markups

Jean ABOU SAMRA
   Hi,

   The recent possibility to define ottavation markups introduced a bug
   when exporting to MIDI.

   For example,
   \version "2.21.0" % compiled with HEAD being
   ede0457988716a5e6fa0dd1757db0ebd96107bbc
   \score {
   { \ottava 1 c'1 }
   \midi { }
   }
   will trigger the warning
   Could not find ottavation markup for 1 octaves up.
   CCing Malte Meyne since he's the author of the patch that introduced
   the warning -- see
   http://lilypond.1069038.n5.nabble.com/Add-user-definable-ottavation-mar
   kups-issue-568970043-by-lilypond-maltemeyn-de-tc223988.html

   The MIDI output is fine though.

   Regards,

   Jean Abou Samra
_______________________________________________
bug-lilypond mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Reply | Threaded
Open this post in threaded view
|

Re: Ottavation markups

Thomas Morley-2
Am Mo., 2. März 2020 um 21:28 Uhr schrieb Jean Abou Samra <[hidden email]>:

>
>    Hi,
>
>    The recent possibility to define ottavation markups introduced a bug
>    when exporting to MIDI.
>
>    For example,
>    \version "2.21.0" % compiled with HEAD being
>    ede0457988716a5e6fa0dd1757db0ebd96107bbc
>    \score {
>    { \ottava 1 c'1 }
>    \midi { }
>    }
>    will trigger the warning
>    Could not find ottavation markup for 1 octaves up.
>    CCing Malte Meyne since he's the author of the patch that introduced
>    the warning -- see
>    http://lilypond.1069038.n5.nabble.com/Add-user-definable-ottavation-mar
>    kups-issue-568970043-by-lilypond-maltemeyn-de-tc223988.html
>
>    The MIDI output is fine though.

Not sure whether it's a proper fix.
For now you could do:

\version "2.21.0"

\score {
  { \ottava 1 c'1 }
  \midi {
    \context {
      \Staff
      ottavationMarkups = #ottavation-numbers
    }
  }
}

HTH,
  Harm

_______________________________________________
bug-lilypond mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Reply | Threaded
Open this post in threaded view
|

Re: Ottavation markups

Malte Meyn-3
In reply to this post by Jean ABOU SAMRA


Am 02.03.20 um 21:27 schrieb Jean Abou Samra:

> \version "2.21.0" % compiled with HEAD being
> ede0457988716a5e6fa0dd1757db0ebd96107bbc
>
> \score {
> { \ottava 1 c'1 }
> \midi { }
> }
>
> will trigger the warning
> Could not find ottavation markup for 1 octaves up.
>
> CCing Malte Meyne since he's the author of the patch that introduced the
> warning -- see
> http://lilypond.1069038.n5.nabble.com/Add-user-definable-ottavation-markups-issue-568970043-by-lilypond-maltemeyn-de-tc223988.html 
>
>
> The MIDI output is fine though.

Thanks for the report. I’ll try to find some time to have a look at this
(and issue 5611 which should be for now my last ottavation improvement
but has waited for completion for some weeks or months now).

_______________________________________________
bug-lilypond mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Reply | Threaded
Open this post in threaded view
|

Re: Ottavation markups

Jean ABOU SAMRA
In reply to this post by Thomas Morley-2
   Hi,

   Le 2 mars 2020 à 22:30, Thomas Morley < [1][hidden email]> a
   écrit :

   Not sure whether it's a proper fix.

   For now you could do:

   \version "2.21.0"

   \score {

   { \ottava 1 c'1 }

   \midi {

   \context {

   \Staff

   ottavationMarkups = #ottavation-numbers

   }

   }

   }

   HTH,

   Harm

   This does the trick. Thanks!

   So, apparently, MIDI performers lack a default value

   for ottavationMarkups. It could be provided, but the real

   fix would be to make performers just ignore ottavas ...

   Regards,

   Jean Abou Samra

References

   1. mailto:[hidden email]
_______________________________________________
bug-lilypond mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/bug-lilypond