Re: Strange error from \new Voice

2020-04-10 Thread David Wright
On Fri 10 Apr 2020 at 09:58:57 (+0200), Michael Gerdau wrote: > > When working with addlyrics it was outside the \new staff construct like > > here: > > > > tenorVoicePart = \new Staff \with { > >   instrumentName = "Tenor" > >   midiInstrument = "choir aahs" > > } { \clef "treble_8" \tenorVoice }

Re: Strange error from \new Voice

2020-04-10 Thread David Wright
On Thu 09 Apr 2020 at 18:41:40 (+0200), Noeck wrote: > Am 09.04.20 um 18:18 schrieb Bernhard Kleine: > > This would be worth mentioning in the manual! > > glad it works. What exactly would you mention in the manual? > > 1) How to use the \lyricsto construct? It is explained here: > > https://lil

Re: Get current staff size

2020-04-10 Thread Valentin Villenave
On 4/10/20, Kevin Barry wrote: > As it happens, I found another solution Good job! Now, if you’ve found a solution with which you’re happy, could you try and build a nice snippet for the LSR? (Explaining why this is useful, and why it’s tricky to achieve.) It may help people who’d stumble upon

Re: Get current staff size

2020-04-10 Thread Kevin Barry
Hi All, Thank you for your suggestions. I did try using the StaffSymbol's staff-height, but that seems to be in staff spaces (with a little added on for the staff lines), so it's always just a little above 4. Timothy's suggestions works (I never would have found ly:pt). As it happens, I found an

Re: Proposal: Changing tremolo beam gap implementation

2020-04-10 Thread Torsten Hämmerle
Thomas Morley-2 wrote > https://sourceforge.net/p/testlilyissues/issues/704/#64b9 > has an image of the relevant Gould-page. > > ölkjh > > > […] > > Though, I'll not start the work if Torsten will present a proper fix > within the next two weeks. > > […] > > Torsten, what do you think? Hi Ha

Re: Proposal: Changing tremolo beam gap implementation

2020-04-10 Thread Thomas Morley
Am Fr., 10. Apr. 2020 um 14:34 Uhr schrieb Valentin Villenave : > > On 4/9/20, Thomas Morley wrote: > > https://lists.gnu.org/archive/html/lilypond-user/2020-04/msg00160.html > > It's ofcourse a workaround, but usable, afaict. > > Could it be worth mentioning on the tracker page for > #704/#3143/

Re: Get current staff size

2020-04-10 Thread Timothy Lanfear
On 10/04/2020 13:24, Noeck wrote: Am 10.04.20 um 14:12 schrieb Valentin Villenave: (* 4 (ly:output-def-lookup This yields 16 for a default staff here. Should the factor be 5? Cheers, Joram Try this instead, which displays the staff height in mm and pt \version "2.20.0" \paper {    #(l

Re: Proposal: Changing tremolo beam gap implementation

2020-04-10 Thread Valentin Villenave
On 4/9/20, Thomas Morley wrote: > https://lists.gnu.org/archive/html/lilypond-user/2020-04/msg00160.html > It's ofcourse a workaround, but usable, afaict. Could it be worth mentioning on the tracker page for #704/#3143/#318/whichever? Cheers, V.

Re: Get current staff size

2020-04-10 Thread Noeck
Am 10.04.20 um 14:12 schrieb Valentin Villenave: > (* 4 (ly:output-def-lookup This yields 16 for a default staff here. Should the factor be 5? Cheers, Joram

Re: Coda / split staff

2020-04-10 Thread Valentin Villenave
On 4/9/20, Pierre Perol-Schneider wrote: > Dear Harm et all, > Would you mind putting the following snippet to the LSR? > Originally: > http://lilypond.1069038.n5.nabble.com/Appending-coda-on-last-line-td44971.html#a44972 Or some version of the latest update: http://lilypond.1069038.n5.nabble.com

Re: Get current staff size

2020-04-10 Thread Valentin Villenave
On 4/9/20, Kevin Barry wrote: > Is there a way to obtain the current value of the staff size as set > with set-global-staff-size (or the layout version)? Would something like that help? %%% \applyOutput Staff.StaffSymbol #(lambda (grob org cur) (ly:message "\nCurrent staff size is: ~a\n\n"

Re: Text placement above the staff

2020-04-10 Thread Aaron Hill
On 2020-04-10 1:39 am, Bernhard Kleine wrote: Thanks a lot! You have seen the image of the last mail. Do you have also a way to align VerseTenorVoiceI and VerseTenorVoiceII that they are placed on the same line? There is not any conflict in the rest of the score. Put lyrics into the same Lyri

Re: Markup-Command shortcut

2020-04-10 Thread foxfanfare
Aaron Hill wrote > > \version "2.20.0" > > #(define-markup-command (subUp layout props f1 f2) (markup? markup?) >(interpret-markup layout props > #{ \markup \overtie \concat { #f1 \hspace #0.15 #f2 } #})) > > subst = #(define-music-function (f1 f2) (markup? markup?) >#{ \finger

Re: Text placement above the staff

2020-04-10 Thread Bernhard Kleine
Am 10.04.2020 um 10:22 schrieb Aaron Hill: > On 2020-04-10 12:46 am, Bernhard Kleine wrote: >> I wonder : >> >> Tenor = \new Staff \with { >>   instrumentName = "tenor" >>   \clef "treble_8" >> } << >>   \new Voice = "TI" { \voiceOne \TenorVoiceI } >>   \new Voice = "TII" { \voiceTwo \TenorVoiceII

Re: Text placement above the staff

2020-04-10 Thread Aaron Hill
On 2020-04-10 12:46 am, Bernhard Kleine wrote: I wonder : Tenor = \new Staff \with {   instrumentName = "tenor"   \clef "treble_8" } <<   \new Voice = "TI" { \voiceOne \TenorVoiceI }   \new Voice = "TII" { \voiceTwo \TenorVoiceII }   \new Voice = "TIII" { \voiceOne \TenorVoiceIII }   \new Lyrics

Re: Strange error from \new Voice

2020-04-10 Thread Michael Gerdau
> When working with addlyrics it was outside the \new staff construct like > here: > > tenorVoicePart = \new Staff \with { >   instrumentName = "Tenor" >   midiInstrument = "choir aahs" > } { \clef "treble_8" \tenorVoice } > \addlyrics { \verseVoice } > > Now, it is within > > Soprano = \new Sta

Text placement above the staff

2020-04-10 Thread Bernhard Kleine
I wonder : Tenor = \new Staff \with {   instrumentName = "tenor"   \clef "treble_8" } <<   \new Voice = "TI" { \voiceOne \TenorVoiceI }   \new Voice = "TII" { \voiceTwo \TenorVoiceII }   \new Voice = "TIII" { \voiceOne \TenorVoiceIII }   \new Lyrics \with { alignAboveContext = "tenor" } \lyricsto

Crash due to internal memory limits (?) in lilypond (was: Crash with bars-per-line-engraver as of LSR snippet id=838)

2020-04-10 Thread Michael Gerdau
> I doubt it's caused by any custom-engraver. > At least on my machine this code: > > \paper { > systems-per-page = #5 > } > > music = \absolute { > \repeat unfold 2000 { > d'8 f' a' g' d' f' b' d' d'8 f' a' g' d' f' b' d' \break > } > } > > \new Staff { \music } > > already f