Re: Breaking Ties to Avoid Time Signature Changes

Hi Brian, does this snippet help? http://lilypond.org/doc/v2.18/Documentation/snippets/editorial-annotations#editorial-annotations-using-the-whiteout-property Best, Joram ___ lilypond-user mailing list lilypond-user@gnu.org

Breaking Ties to Avoid Time Signature Changes

Hi All, How do I break ties from a chord (single voice) that overlap a changed time signature in the next measure? Thanks, Brian ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re:Unterminated Crescendo Issue

Most of the other help you've been given has been techniques to combine two voices. A more straightforward approach is to avoid splitting up the music in the first place, and include all the music up until the terminal dynamic within the first parallel music expression. This is not as scalable

Re: Accidentals and thickness

Simon Albrecht-2 wrote > On 28.08.2017 22:49, SoundsFromSound wrote: >> Hello list, >> >> Can someone tell me the easiest way to adjust the thickness / thinness of >> accidentals in LilyPond? >> >> Not the size of the accidentals, just the actual thickness level for >> them. >> I've tried a few

Re: Accidentals and thickness

On 28.08.2017 22:49, SoundsFromSound wrote: Hello list, Can someone tell me the easiest way to adjust the thickness / thinness of accidentals in LilyPond? Not the size of the accidentals, just the actual thickness level for them. I've tried a few overrides w/ regards to contexts but nothing

Accidentals and thickness

Hello list, Can someone tell me the easiest way to adjust the thickness / thinness of accidentals in LilyPond? Not the size of the accidentals, just the actual thickness level for them. I've tried a few overrides w/ regards to contexts but nothing does what I had hoped it would...thank you!

Re: \breathe sign to be inline with alto

On 28.08.2017 21:49, Bernhard Kleine wrote: Am 28.08.2017 um 21:24 schrieb David Kastrup: Does { c'1 \tweak Y-offset -2 \breathe c'1 } help? It does! thank you. BTW: What do I to do to make it the variable \breathedown at the beginning of the setting? That’s just a simple variable

Re: \breathe sign to be inline with alto

Am 28.08.2017 um 21:24 schrieb David Kastrup: > Bernhard Kleine writes: > >> I try to set Verleih uns Frieden, a motette from Heinrich Schütz. >> sopranoII and alto are in the same staff. The \breathe sign for >> sopranoII is easy, simple \breathe and it moves to top of

Re: Unterminated Crescendo Issue

Thank you to all that responded. I very much appreciate the support of this list. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: \breathe sign to be inline with alto

Bernhard Kleine writes: > I try to set Verleih uns Frieden, a motette from Heinrich Schütz. > sopranoII and alto are in the same staff. The \breathe sign for > sopranoII is easy, simple \breathe and it moves to top of the staff. But > I could not find any help for the

Re: Unterminated Crescendo Issue

Ivan Kuznetsov writes: > And that does work ! > > It does appears to be a subtle variation > of Mr. Kastrup's solution. > > tisimst wrote: >> >> Instead of this: >> >> >> << >> { 8 8\< } >> \\ >> { f,4 } >>

\breathe sign to be inline with alto

Hi, I try to set Verleih uns Frieden, a motette from Heinrich Schütz. sopranoII and alto are in the same staff. The \breathe sign for sopranoII is easy, simple \breathe and it moves to top of the staff. But I could not find any help for the corresponding breathing sign for alto which should go

Re: Unterminated Crescendo Issue

Ivan Kuznetsov writes: > David Kastrup wrote: >> >> Ivan Kuznetsov writes: >>> >>> Is the only solution to define the problem measure as >>> a macro (themusic) and then insert that >>> macro at the appropriate place in the

Re: Unterminated Crescendo Issue

And that does work ! It does appears to be a subtle variation of Mr. Kastrup's solution. tisimst wrote: > > Instead of this: > > > << > { 8 8\< } > \\ > { f,4 } >>> > > > Do this: > > > << > { \voiceOne 8

Re: Unterminated Crescendo Issue

David Kastrup wrote: > > Ivan Kuznetsov writes: >> >> Is the only solution to define the problem measure as >> a macro (themusic) and then insert that >> macro at the appropriate place in the score? > > Good grief, no. A macro is completely equivalent

Re: Unterminated Crescendo Issue

Hi, Ivan! On Mon, Aug 28, 2017 at 12:38 PM, Ivan Kuznetsov [via Lilypond] < ml+s1069038n205320...@n5.nabble.com> wrote: > Mark Stephen Mrotek <[hidden email] > > wrote: > > > > Perhaps you could code a second voice with spacers and place the >

Re: Unterminated Crescendo Issue

Ivan Kuznetsov writes: > Thank you Mr. Kastrup. > > Whereas the snippet you provided works, I am still > having trouble implementing your solution into > the context of my composition. > > Is the only solution to define the problem measure as > a macro (themusic) and

Re: Unterminated Crescendo Issue

Mark Stephen Mrotek wrote: > > Perhaps you could code a second voice with spacers and place the beginning > and ending of the hairpin exactly. I have tried using an extra voice with spacers but have yet to come up with a solution.

Re: Unterminated Crescendo Issue

Thank you Mr. Kastrup. Whereas the snippet you provided works, I am still having trouble implementing your solution into the context of my composition. Is the only solution to define the problem measure as a macro (themusic) and then insert that macro at the appropriate place in the score? The

Re: Merge_rests_engraver and dotted rest problem

On 28 August 2017 at 17:57, Thomas Morley wrote: > 2017-08-27 12:58 GMT+02:00 Risto Vääräniemi : >> >> I just discovered the new Merge_rests_engraver that should merge the >> rests of two voices. It is an improvement to the LSR snippet 336 *) >>

Re: Unterminated Crescendo Issue

Ivan Kuznetsov wrote: > Kieren MacMillan wrote: >> >> You need to explicitly extantiate the voices, so that the >> first voice is the main one: > > That was a solution. Thanks. Actually, I spoke too soon. That solution fixed the

Re: Unterminated Crescendo Issue

Hi David, > here is a nicer way (given a recent enough version of LilyPond) I wondered if that \voices command had made it in yet. Really glad to see it! Now I can (I think?) finally get rid of all my "\split" macros… Thanks, Kieren. Kieren MacMillan, composer

Re: Unterminated Crescendo Issue

Kieren MacMillan wrote: > > You need to explicitly extantiate the voices, so that the > first voice is the main one: That was a solution. Thanks. I did have to add the command: \set Timing.beamExceptions = #'() to get rid of a bizarre default beaming though.

RE: Unterminated Crescendo Issue

Ivan, Perhaps you could code a second voice with spacers and place the beginning and ending of the hairpin exactly. Mark -Original Message- From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Ivan Kuznetsov Sent: Monday, August 28, 2017 10:24 AM

Re: Unterminated Crescendo Issue

Kieren MacMillan writes: > Hi Ivan, > >> I suspect the error message is because of the way >> the voices are laid out: Beat one is written >> as two lilypond-voices > > You need to explicitly extantiate the voices, so that the first voice is the > main one: > >

Re: Unterminated Crescendo Issue

Hi Ivan, > I suspect the error message is because of the way > the voices are laid out: Beat one is written > as two lilypond-voices You need to explicitly extantiate the voices, so that the first voice is the main one: SNIPPET BEGINS \version "2.19.64" \include "english.ly" themusic =

Unterminated Crescendo Issue

Hello All: I need a hairpin crescendo to start on the second eighth-note of beat one (underneath the B-flat/D-flat diad) and continue to the forte under the second eighth-note of beat two (underneath the D/B-flat/G triad). The error message I get is: post01.ly:18:23: warning: unterminated

Re: Merge_rests_engraver and dotted rest problem

2017-08-27 12:58 GMT+02:00 Risto Vääräniemi : > Hi, > > I just discovered the new Merge_rests_engraver that should merge the > rests of two voices. It is an improvement to the LSR snippet 336 *) > because it now combines the whole-measure rests. However, it fails to > merge