Re: aftergrace consistently close to the next bar line

On Sun, May 5, 2024 at 1:19 AM wrote: > Good day, > > > > I use afterGrace notes to mark the end of a glissando. At the moment > lilypond places these afterGrace notes somehow depending on the note's > length. > I want the glissando to be played over the entire length of the time unit, > so the

Re: afterGrace, glissando, and hidenotes

Am Donnerstag, 11. April 2024, 19:11:45 CEST schrieb Walt North: > Hello, I would appreciate some help with this music function. > > The end goal is have a define function produce a glissando after a note > going either up or down to > > undetermined second note. For example a guitar slide down

Re: afterGrace, glissando, and hidenotes

Hi Walt, On 4/11/24 13:11, Walt North wrote: > Hello, I would appreciate some help with this music function. > > The end goal is have a define function produce a glissando after a > note going either up or down to undetermined second note. For > example a guitar slide down off the note. If I'm

Re: `\afterGrace` and clef problem

Jean Abou Samra writes: > Le lundi 13 février 2023 à 18:08 +0100, David Kastrup a écrit : >> That begs the question whether it would make sense to restrict >> afterGrace scales to values below 1.  But I think that making syntactic >> decisions based on values rather than types is really

Re: `\afterGrace` and clef problem

Le lundi 13 février 2023 à 18:08 +0100, David Kastrup a écrit : > That begs the question whether it would make sense to restrict > afterGrace scales to values below 1.  But I think that making syntactic > decisions based on values rather than types is really icky.  It is > probably a bad

Re: `\afterGrace` and clef problem

Lukas-Fabian Moser writes: > Hi Werner, > >>> Alternatively you may try to use \afterGrace to insert the \clef >>> before the bar line, although this would probably require some >>> manual spacing too. >> This doesn't work at all: `\afterGrace` doesn't accept a clef, as the >> image shows. > >

Re: `\afterGrace` and clef problem

> That is because you are using 1 instead of a note name such as c'1. after- > grace does not handle this mechanism. Thanks (and thanks to Lukas, too)! > Instead of manually extra-offsetting the Clefs you might also do > something along the lines of [...] Nice! I will use that. Werner

Re: `\afterGrace` and clef problem

That is because you are using 1 instead of a note name such as c'1. after- grace does not handle this mechanism. You can see here that this does work, but it does produce less optimal spacing: \relative c' { << \new Staff { \afterGrace f1 { e16[ f] } | g1 } \new Staff { #(define

Re: `\afterGrace` and clef problem

Hi Werner, Alternatively you may try to use \afterGrace to insert the \clef before the bar line, although this would probably require some manual spacing too. This doesn't work at all: `\afterGrace` doesn't accept a clef, as the image shows. afterGrace is defined as #(define-music-function

Re: `\afterGrace` and clef problem

> [...] I'm rather inclined to count the behaviour of `space-alist` > for clefs as a buglet: It doesn't make sense allowing the clef to > move 'under' other notes in different staves while its `space-alist` > values are applied globally to all staves. This is now issue #6529.

Re: `\afterGrace` and clef problem

Hello Valentin, > My suggestion to getting around this would be the tell Lilypond that > the clef stencil is in fact narrower than it actually is, which will > allow the Clef stencil to protrude arbitrarily much: [...] Thanks! Interestingly, the clef still gets some extra horizontal space,

Re: `\afterGrace` and clef problem

Hello Werner, When doing \afterGrace internally something like << [music] { [some-skip] [graces] } >> is created. These graces will necessarily not fall onto the last timestep of the measure, which appears to be where the Clef stencil is limited to, which we can see here: \relative c' { <<

RE: AfterGrace

d-user Mailinglist <lilypond-user@gnu.org> Subject: Re: AfterGrace Hi Mark, On 6 June 2016 at 04:24, Mark Stephen Mrotek <carsonm...@ca.rr.com> wrote: > In the attached snippet I want the aftergrace positioned closer to the > subsequent bar line. > Hi Mark, > On 6 June 20

Re: AfterGrace

Hi Mark, On 6 June 2016 at 04:24, Mark Stephen Mrotek wrote: > In the attached snippet I want the aftergrace positioned closer to the > subsequent bar line. > Hi Mark, > On 6 June 2016 at 4:26:08 AM, Mark Stephen Mrotek (carsonm...@ca.rr.com) > wrote: > > In the

Re: \afterGrace control over stem length

Hi James, I was not able to reproduce the stem length shown on your picture. Please be so kind to send compilable example including the version you're using. Doc's here: http://www.lilypond.org/doc/v2.18/Documentation/learning/fixing-overlapping-notation#the-positions-property And here's two

Re: \afterGrace control over stem length

Pierre Perol-Schneider pierre.schneider.paris at gmail.com writes: I was not able to reproduce the stem length shown on your picture. Please be so kind to send compilable example including the version you're using. That might be awhile... time is short at the moment and I have a feeling that it

Re: afterGrace on Completion_heads_engraver layout

2015-05-16 13:58 GMT+02:00 Venus' Wink venuswi...@inbox.com: Hi, I've found this is a known bug: http://code.google.com/p/lilypond/issues/detail?id=2769 Thanks Venus' Wink I've updated issue 2769 http://code.google.com/p/lilypond/issues/detail?id=2769 with the workaround Thanks, Harm

Re: afterGrace on Completion_heads_engraver layout

2015-05-16 11:58 GMT+02:00 Venus' Wink venuswi...@inbox.com: Hi, I'm trying use \afterGrace on layout consists Completion_heads_engraver as: \version 2.18.2 \layout { \context { \Voice \remove Note_heads_engraver \consists Completion_heads_engraver } }

Re: afterGrace on Completion_heads_engraver layout

-Original Message- From: thomasmorle...@gmail.com Sent: Sat, 16 May 2015 12:40:02 +0200 To: venuswi...@inbox.com Subject: Re: afterGrace on Completion_heads_engraver layout 2015-05-16 11:58 GMT+02:00 Venus' Wink venuswi...@inbox.com: Hi, I'm trying use \afterGrace on layout

Re: afterGrace and slashedGrace

Hi Federico, There's a conflict between \afterGrace and \slashedGrace in your coding. How about : \version 2.19.15 \relative c'' { \afterGrace c1 { \once\override Flag.stroke-style = #grace d8 } } HTH, Pierre 2014-12-27 11:35 GMT+01:00 Federico Bruni fedel...@gmail.com: I think

Re: afterGrace and slashedGrace

Thanks Pierre! Just found my previous question: https://lists.gnu.org/archive/html/lilypond-user/2014-11/msg00261.html I see that if I change the direction of the slashed stem it appears a bit too long (I think) and I must tweak it, see commented line below: \version 2.19.15 \relative c'' {

Re: afterGrace and slashedGrace

2014-12-27 12:20 GMT+01:00 Federico Bruni fedel...@gmail.com: I see that if I change the direction of the slashed stem it appears a bit too long (I think) and I must tweak it, see commented line below: I totally agree. ___ lilypond-user mailing

Re: \afterGrace \glissando draws incorrect line?

On 17/06/14 19:43, st...@linuxsuite.org wrote: Howdy! I have a problem getting lilypond to draw the correct glissando line... Here is a pdf and lilypond source file http://gooeytar.com/projects/test/test.pdf http://gooeytar.com/projects/test/test.ly

Re: \afterGrace \glissando draws incorrect line?

2014-06-17 20:43 GMT+02:00 st...@linuxsuite.org: Howdy! I have a problem getting lilypond to draw the correct glissando line... Here is a pdf and lilypond source file http://gooeytar.com/projects/test/test.pdf http://gooeytar.com/projects/test/test.ly

Re: \afterGrace \glissando draws incorrect line?

voiceone = \relative c' { a''4 b,, dis a dis16 a fis' dis | a'4 dis,, a' b a'16 fis b( a) | dis4 fis, a dis %% changed input order: fis dis' a \glissando %% thanks to David K: \grace { \bar a fis'8 \bar | } a fis' 4 gis e' } This works!

Re: \afterGrace \glissando draws incorrect line?

I changed the \new Voice \voiceOne { \afterGrace fis4 \glissando a8 } \new Voice \voiceTwo { \stemUp a4 } \new Voice \voiceThree { \afterGrace dis4 \glissando fis8 } to \afterGrace dis'4 \glissando fis8 \\ \stemUp a,4 \\ \afterGrace fis4 \glissando

Re: afterGrace spacing

Daniel Rosen drose...@gmail.com writes: In the example below, how can I adjust the space between the second grace note and the barline? I'd like for the barline to be closer. \relative c'' { #(define afterGraceFraction (cons 15 16)) c1 \afterGrace d1 { c16[ d] } c1 } Don't have an

Re: afterGrace spacing

David Kastrup d...@gnu.org writes: Daniel Rosen drose...@gmail.com writes: In the example below, how can I adjust the space between the second grace note and the barline? I'd like for the barline to be closer. \relative c'' { #(define afterGraceFraction (cons 15 16)) c1 \afterGrace d1

Re: aftergrace with pitchedtrill

Dear community, thanks for Your code. I can't remember my mistake, but I see, that it works fine now! I tested: \new Staff { \afterGrace \pitchedTrill fis''2 \startTrillSpan gis'' { e''16[ fis''] } g''2 \stopTrillSpan } with 2.14.2, 2.16.0 and

Re: aftergrace with pitchedtrill

Stefan Thomas-5 wrote Dear community, I have the same problem like Trevor Bača, years ago. See at http://lists.gnu.org/archive/html/lilypond-user/2006-11/msg00265.html Is there a solution available? sure - what version are you using? Eluze -- View this message in context:

Re: aftergrace with pitchedtrill

Dear community, I'm using version 2.16.0 Subject: Re: aftergrace with pitchedtrill Message-ID: 1352647402382-136192.p...@n5.nabble.com Content-Type: text/plain; charset=UTF-8 Stefan Thomas-5 wrote Dear community, I have the same problem like Trevor Ba?a, years ago. See at http://lists.gnu.org

Re: aftergrace with pitchedtrill

Stefan Thomas-5 wrote Dear community, I'm using version 2.16.0 Trevor complained about: /But combining pitchedTrill with afterGrace gives a wide and varied array of warnings and errors, …/ is that still the case with 2.16.0? Eluze -- View this message in context:

Re: aftergrace with pitchedtrill

2012/11/11 Eluze elu...@gmail.com: Stefan Thomas-5 wrote Dear community, I'm using version 2.16.0 Trevor complained about: /But combining pitchedTrill with afterGrace gives a wide and varied array of warnings and errors, …/ is that still the case with 2.16.0? Eluze I tested: \new

Re: aftergrace with pitchedtrill

2012/11/12 Eric eric.schis...@gmail.com: I've had this problem for awhile but in 2.16.0 hit on something that worked once. Whether it can be generalized to a _solution_ I don't know. Here's a snippet, I hope it helps (it's from a cadenza-like passage in a violin part of a quartet (composed

Re: \afterGrace - afterGraceFraction [Lilypond 2.10.0 Windows]

Thanks Mats, Bertalan. I'll give it a try. Trent - Original Message - From: Mats Bengtsson [EMAIL PROTECTED] To: Trent J [EMAIL PROTECTED] Cc: lilypond-user@gnu.org Sent: Thursday, November 16, 2006 6:30 PM Subject: Re: \afterGrace - afterGraceFraction [Lilypond 2.10.0 Windows

Re: \afterGrace - afterGraceFraction [Lilypond 2.10.0 Windows]

No, it means just afterGraceFraction = #(cons 7 8) - if you look into music-functions-init.ly, you can find this declaration there. Bert ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: \afterGrace - afterGraceFraction [Lilypond 2.10.0 Windows]

Actually, afterGraceFraction is defined as an ordinary LilyPond identifier, in ly/music-functions-init.ly. So, one option for you if you want to change the setting globally for the full score is to add afterGraceFraction = #(cons 7 8) at the top level of the file (just as you can define

Re: afterGrace with a slur?

Simply add the slur as for any other notes: \version 2.6.0 \score{ \new Voice \relative c'' { \afterGrace a4 ( {b16 [ a ] ) } g4 } \layout{raggedright=##t} } /Mats Bodo wrote: Hi, I want to add two grace notes that are sung on the same syllable as the preceding note and are