Re: In TabVoice - how to avoid: "programming error: side-axis not set for grob StrokeFinger"

2020-03-10 Thread Thomas Morley
Am Di., 10. März 2020 um 00:07 Uhr schrieb Torsten Hämmerle : > > Thomas Morley-2 wrote > > Any hints why this error is generated and how to avoid? > > > Hi Harm, > > Unfortunately, applying \consists "New_fingering_engraver" does not quite do > the trick yet, because there's a problem of

Re: Unexpected "Merge_rests_engraver" behavior

2020-03-10 Thread Torsten Hämmerle
Павел Буданов-2 wrote > See the vertical position of multimeasure rest. > > ```lilypond > \version "2.19.83" > [...] Hi Pavel, Yes, that's a bug, but it has been fixed in 2.19.84 and current stable 2.20.0 is OK, too. Regards, Torsten -- Sent from:

Re: stanza numbers at the beginning of every system

2020-03-10 Thread Karlin High
On 3/10/2020 2:55 PM, Benjamin Bloomfield wrote: I would like the stanza numbers lined up more like StanzaNumber than InstrumentName so there is that problem with using \set shortVocalName. However, this thread was from 2013, so I am wondering whether anyone knows of a better way to have

stanza numbers at the beginning of every system

2020-03-10 Thread Benjamin Bloomfield
I just read through this old thread from 2013 about repeating stanza numbers at the beginning of every system, because there isn't much more I've been able to find about doing this. The scheme engraver given in that

Re: Exited with return code -1073741819

2020-03-10 Thread Samuel Burt
Just wanted to reply so that anyone searching will have some idea of how to approach this problem. I couldn't figure out how to get MSYS, which I already had installed, to install Lilypond, so I installed Ubuntu for Windows. Lilypond was fairly easy to install from the Lilypond website.

Unexpected "Merge_rests_engraver" behavior

2020-03-10 Thread Павел Буданов
See the vertical position of multimeasure rest. ```lilypond \version "2.19.83" \new Staff \with { \consists "Merge_rests_engraver" } << { R1 r1 } \\ { R1 r1 } >> ```

Re: Getting started with music functions

2020-03-10 Thread David Kastrup
Aaron Hill writes: >>> => David K., do you know why the parser balks at such a top-level >>> ly:book? > >> How can a book be distinguished from a bookpart? > > Are they both ly:book? behind the scenes? If so, I can see the problem. > > >> Without an answer to >> that question, we cannot

Re: parenthesizing by parentheses or brackets

2020-03-10 Thread Pierre Perol-Schneider
Hi Niels, See: --- http://lsr.di.unimi.it/LSR/Item?id=318 --- http://lsr.di.unimi.it/LSR/Item?id=564 HTH, cheers, Pierre Le mar. 10 mars 2020 à 11:57, Niels a écrit : > Dear all, > > I want to parenthesize some notes by regular parentheses () and other by > brackets []. One for composers

parenthesizing by parentheses or brackets

2020-03-10 Thread Niels
Dear all, I want to parenthesize some notes by regular parentheses () and other by brackets []. One for composers instructions and one for publisher corrections. Could anyone help me in achieving this? Niels

Re: In TabVoice - how to avoid: "programming error: side-axis not set for grob StrokeFinger"

2020-03-10 Thread Torsten Hämmerle
Werner LEMBERG wrote > Interesting. Is it documented somewhere that the order of `\consists` > calls is relevant (sometimes)? Hi Werner, I couldn't find anything about that in the documentation. When experimenting with Voice and TabVoice, I noticed that Voice worked without a problem and, most

Re: Getting started with music functions

2020-03-10 Thread Aaron Hill
=> David K., do you know why the parser balks at such a top-level ly:book? How can a book be distinguished from a bookpart? Are they both ly:book? behind the scenes? If so, I can see the problem. Without an answer to that question, we cannot implement this. But have you tried explicitly

Re: In TabVoice - how to avoid: "programming error: side-axis not set for grob StrokeFinger"

2020-03-10 Thread Werner LEMBERG
> In order to avoid this problem of sequence, I've first removed > Script_column_engraver and appended it again /after/ > New_fingering_engraver. Looks funny but actually solves the > problem. > > [...] > \remove "Script_column_engraver" > \consists "New_fingering_engraver" % *before*