Re: Beaming across rests

Try this code snippet: A function to repeatedly print a given pattern with different notes -- View this message in context: http://lilypond.1069038.n5.nabble.com/Beaming-across-rests-tp196586p196588.html Sent from the User mailing list archive at

Slur not accepting \shape corrections

Hi, everyone, I'm new to LilyPond, and to the forum here. After trying several different options and looking around the documentation, I can't seem to find a solution to my problem. I'm working on a piano piece that has an extended slur at the end over the remaining notes. However, the slur's

Re: Slur not accepting \shape corrections

Not sure how I missed that. Thank you, it works now. :) -- View this message in context: http://lilypond.1069038.n5.nabble.com/Slur-not-accepting-shape-corrections-tp196581p196585.html Sent from the User mailing list archive at Nabble.com. ___

Beaming across rests

Good evening, all. When typesetting march music in 6/8, I very frequently have the figure \version "2.18.2" \relative c'' { \time 6/8 b8[ r b] b[ r b] } Obviously, I can get the effect I want, with two beamed groups of 3, as above. Is there anyway to force Lilypond to automatically beam

Re: Slur not accepting \shape corrections

The \shape command, if I remember correctly, functions like a "\once \override", so it needs to immediately precede the note to which the slur is attached, thus: /\stemUp r8 \shape #'((0 . 0)(0 . 0)(0 . 0)(0 . 0)) Slur c( g' c e g / -- View this message in context:

Re: Error code -1073741819 with tie and tenuto

Am 13.11.2016 um 23:16 schrieb David Kastrup: > Bernhard Kleine writes: > >> Am 13.11.2016 um 22:51 schrieb Simon Albrecht: >>> On 13.11.2016 22:49, Noeck wrote: Both \relative c { 1~-- | | } and \relative {

Re: Error code -1073741819 with tie and tenuto

Bernhard Kleine writes: > Am 13.11.2016 um 22:51 schrieb Simon Albrecht: >> On 13.11.2016 22:49, Noeck wrote: >>> Both >>> >>> \relative c { >>>1~-- | >>> | >>> } >>> >>> and >>> >>> \relative { >>>1~-- | >>> | >>> } >>> >>> are compiled without

Re: Error code -1073741819 with tie and tenuto

… and I confirm the crash with 2.19.47 on the same system. Segfault, return code 139. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Error code -1073741819 with tie and tenuto

Am 13.11.2016 um 22:51 schrieb Simon Albrecht: > On 13.11.2016 22:49, Noeck wrote: >> Both >> >> \relative c { >>1~-- | >> | >> } >> >> and >> >> \relative { >>1~-- | >> | >> } >> >> are compiled without problems here (2.19.49, Ubuntu 16.10, 64bit). > > OK, so it’s a bug

Re: Error code -1073741819 with tie and tenuto

On 13.11.2016 22:49, Noeck wrote: Both \relative c { 1~-- | | } and \relative { 1~-- | | } are compiled without problems here (2.19.49, Ubuntu 16.10, 64bit). OK, so it’s a bug already fixed. Best, Simon ___ lilypond-user

Fwd: Re: Error code -1073741819 with tie and tenuto

Forwarded Message Subject:Re: Error code -1073741819 with tie and tenuto Date: Sun, 13 Nov 2016 21:33:02 - From: Phil Holmes To: Simon Albrecht Semi bisected. Occurs between 19.41 and 19.47. -- Phil

Re: Error code -1073741819 with tie and tenuto

Both \relative c { 1~-- | | } and \relative { 1~-- | | } are compiled without problems here (2.19.49, Ubuntu 16.10, 64bit). ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Error code -1073741819 with tie and tenuto

Here, windows 7, amd64, it compiles well, the actual version is 2.19.49. Your code being rather simple that the origin of that spurious error message could be sorted out, I hope. Regards Bernhard Am 13.11.2016 um 22:26 schrieb Simon Albrecht: > On 13.11.2016 22:12, Michael Rivers wrote: >> I

Re: Error code -1073741819 with tie and tenuto

On 13.11.2016 22:12, Michael Rivers wrote: I was setting a song by Lior Novak and got an error message 1073741819 with these chords: Can confirm on Ubuntu. Here’s a smaller example: \version "2.19.47" \relative { 1~-- | | } Necessary conditions are the outside-chord tie, the

Error code -1073741819 with tie and tenuto

I was setting a song by Lior Novak and got an error message 1073741819 with these chords: \version "2.19.47" \relative c { 1~-- | | } If I remove either the tie or the tenuto on the first chord, it compiles fine. I got around the problem by tying the notes individually ( ),

Re: alternative notehead style breaks cross-staff stem

2016-11-13 15:45 GMT+01:00 Urs Liska : > Hi all, > > I'm trying to build something like similar to an automated harmonic > display on two staves, and it seems that alternative note head styles > break the cross staff stems: > > Is this known (at least not said in the NR)? Is

Re: alternative notehead style breaks cross-staff stem

Am 13.11.2016 um 15:45 schrieb Urs Liska: I'm trying to build something like similar to an automated harmonic display on two staves, and it seems that alternative note head styles break the cross staff stems: Is this known (at least not said in the NR)? Is there a way around this issue? I

programming error: no solution found for Bezier intersection

Hi I have a real piece where I get the following error (printed 6 times): programming error: no solution found for Bezier intersection continuing, cross fingers The PDF looks fine, but I'd like to avoid this error in the logs, if possible. By commenting some code I found, by trial and error,

Re: Getting the direction when defining a new markup command

Hi David, I guess I cut a bit too much out. Your example is exactly what I was trying to do; many thanks! Best wishes, Kevin ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: alternative notehead style breaks cross-staff stem

- Original Message - From: "Urs Liska" To: "lilypond-user" Sent: Sunday, November 13, 2016 2:45 PM Subject: alternative notehead style breaks cross-staff stem Hi all, I'm trying to build something like similar to an automated harmonic

alternative notehead style breaks cross-staff stem

Hi all, I'm trying to build something like similar to an automated harmonic display on two staves, and it seems that alternative note head styles break the cross staff stems: Is this known (at least not said in the NR)? Is there a way around this issue? Note that the example code isn't

Re: Pedal cautionary continuations and other bracket decorations

2016-11-13 1:39 GMT+01:00 Andrew Bernard : > Hi Harm, > > When there is a sustain on event followed by a sustain off event, the label > 1/2 ped should not occur - it's only for the start of the lines, and when > these events occur very close together with short notes