Re: Strange space between beam and slur

2019-06-24 Thread Pierre Perol-Schneider
So possible workarounds: #(set-global-staff-size 19.01) or using: \layout { #(layout-set-staff-size 19) } instead. Cheers, Pierre Le mar. 25 juin 2019 à 01:01, Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com> a écrit : > Hum, this staff-size 19 reminds me: >

Re: Strange space between beam and slur

2019-06-24 Thread Pierre Perol-Schneider
Hum, this staff-size 19 reminds me: http://lilypond.1069038.n5.nabble.com/misplacement-note-head-version-2-19-td211629.html Any posible relationship? Cheers, Pierre Le mar. 25 juin 2019 à 00:11, Thomas Morley a écrit : > Am So., 23. Juni 2019 um 11:59 Uhr schrieb Thomas Morley > : > [...] >

Re: Strange space between beam and slur

2019-06-24 Thread Thomas Morley
Am So., 23. Juni 2019 um 11:59 Uhr schrieb Thomas Morley : [...] Just reported in the german forum https://lilypondforum.de/index.php/topic,501.0.html \version "2.19.82" % problem occurs at staff-size 19, but does not occur at staff-size 18 or 20 #(set-global-staff-size 19) \new TabStaff \with

Re: Error message

2019-06-24 Thread Aaron Hill
On 2019-06-24 3:18 am, Craig Dabelstein wrote: Hi Aaron, Omitting the tuplet bracket doesn't help. I'm really at a loss at what to do now. Since your isolated measures involved tuplets, I had wondered if perhaps the issue came from the brackets. Maybe try \omit TupletNumber, both with

Re: Error message

2019-06-24 Thread Craig Dabelstein
Hi Aaron, Omitting the tuplet bracket doesn't help. I'm really at a loss at what to do now. Craig On Mon, 24 Jun 2019 at 16:57, Aaron Hill wrote: > On 2019-06-23 11:15 pm, Craig Dabelstein wrote: > > Thanks for the help everyone. > > > > I narrowed down the guilty bars. Here's a MWE,

Re: Help with tweaks

2019-06-24 Thread Robert Blackstone
Hi Evan, For what it’s worth. Since I am not yet an experienced user of “regular’ tweaks, I would have used a different solution to this problem, i.e. moving the Markup texts to a second voice with hidden notes. I give you my solution here but I have to warn you that I never use \relative c’

Re: Error message

2019-06-24 Thread Aaron Hill
On 2019-06-23 11:15 pm, Craig Dabelstein wrote: Thanks for the help everyone. I narrowed down the guilty bars. Here's a MWE, however, it doesn't reproduce the error in this MWE. When these two bars are replaced with s1.*2 the files produce no error. I really don't know where to go from here.

Re: Error message

2019-06-24 Thread Craig Dabelstein
Thanks for the help everyone. I narrowed down the guilty bars. Here's a MWE, however, it doesn't reproduce the error in this MWE. When these two bars are replaced with s1.*2 the files produce no error. I really don't know where to go from here. Any advice? Craig \version "2.19.82" \language