Re: Fwd: Weird behaviour with TupletNumber.avoid-slur (beam disappears)

On 16.11.2016 11:42, Risto Vääräniemi wrote: Shall I just forward this thread to lily-bug Yes, see . The gmane interface is defunct, though. Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org

Fwd: Weird behaviour with TupletNumber.avoid-slur (beam disappears)

Hi Harm, Thanks for checking. I had a look at the file I am now porting to 2.19 and it seems it was made with 2.11.57. I attached an image showing how things were back in 2008/9. There the slur ends are on the same level. The effect was achieved with (old syntax shown): \once \override

Re: Weird behaviour with TupletNumber.avoid-slur (beam disappears)

2016-11-16 8:30 GMT+01:00 Risto Vääräniemi : > David's example shows the same issue, I'm having. > > @Mark: > I'm writing choir music with soprano & alto on one staff and tenor & bass on > another. So, basically I need to force slurs & ties on the "outer side" of > each staff.

Re: Weird behaviour with TupletNumber.avoid-slur (beam disappears)

David's example shows the same issue, I'm having. @Mark: I'm writing choir music with soprano & alto on one staff and tenor & bass on another. So, basically I need to force slurs & ties on the "outer side" of each staff. I also need to force stems up / down. I just deleted everything unnecessary

Re: Weird behaviour with TupletNumber.avoid-slur (beam disappears)

On Tue 15 Nov 2016 at 13:23:56 (-0800), Mark Stephen Mrotek wrote: > Not knowing the requirements/necessity of your putting the slur above the > beam, I would put the slur down – closer to the note heads. This would/does > avoid conflict with the number. Yes, that's what I thought, until I

RE: Weird behaviour with TupletNumber.avoid-slur (beam disappears)

:39 PM To: Mark Stephen Mrotek <carsonm...@ca.rr.com> Cc: Lilypond user <lilypond-user@gnu.org> Subject: Re: Weird behaviour with TupletNumber.avoid-slur (beam disappears) Hi Mark, I need a slur. It was quicker to write a bunch of same notes. I tested it again with different pitches

Re: Weird behaviour with TupletNumber.avoid-slur (beam disappears)

m:* lilypond-user [mailto:lilypond-user-bounces+carsonmark= > ca.rr@gnu.org] *On Behalf Of *Risto Vääräniemi > *Sent:* Tuesday, November 15, 2016 9:22 AM > *To:* Lilypond user <lilypond-user@gnu.org> > *Subject:* Weird behaviour with TupletNumber.avoid-slur (beam

RE: Weird behaviour with TupletNumber.avoid-slur (beam disappears)

: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Risto Vääräniemi Sent: Tuesday, November 15, 2016 9:22 AM To: Lilypond user <lilypond-user@gnu.org> Subject: Weird behaviour with TupletNumber.avoid-slur (beam disappears) Hi, I tried to keep the tuplet

Weird behaviour with TupletNumber.avoid-slur (beam disappears)

Hi, I tried to keep the tuplet number from colliding with a slur by using TupletNumber.avoid-slur = #'outside. It has worked before ~2.12.XX but with 2.19.49 something weid happened. The tuplet beam disappeared (actually was shortened and moved to the left of the staff, see the red circle). Even