Re: Unwanted warnings/errors on pedals for multiple voices

Hi Paolo, > Why do you say they are visually distracting? Because as a pianist, it’s easier for me to read _/\ _/\ _/\ than _/\ _/\ _/\ (I hope my ASCII art demonstrates my

Unwanted warnings/errors on pedals for multiple voices

On Tuesday, April 7, 2020, Kieren MacMillan wrote: > Hi Paolo, > > > I don't think it would be useful to assign a layer to the pedal > information. It doesn't add any benefit in terms of visual clarity, it > doesn't save space and it adds redundancy (which is hard to manage when the > score

Re: Unwanted warnings/errors on pedals for multiple voices

Hi Paolo, > I don't think it would be useful to assign a layer to the pedal information. > It doesn't add any benefit in terms of visual clarity, it doesn't save space > and it adds redundancy (which is hard to manage when the score becomes bigger > and bigger). And I never saw a score in

Re: Unwanted warnings/errors on pedals for multiple voices

On Tue, Apr 7, 2020 at 1:46 AM Kieren MacMillan wrote: > Hi Paolo, > > > All this considered, IMHO (and considered that I really got crazy with > this warnings for weeks): > > > > 1) The "Dynamics line" solution should be discouraged in the > documentation. I can be wrong but I really don't

Re: Unwanted warnings/errors on pedals for multiple voices

Hi Paolo, > All this considered, IMHO (and considered that I really got crazy with this > warnings for weeks): > > 1) The "Dynamics line" solution should be discouraged in the documentation. I > can be wrong but I really don't understand in which cases it could be useful. > And redundancy is

Re: Unwanted warnings/errors on pedals for multiple voices

Hi Carl (et al.), > To me, the ideal default is PianoStaff. +1 This will cover the vast majority of "real world" cases. The ones where pedals apply to individual voices on a single staff, or to individual staves within the full piano staff, will be (I strongly believe) a very small fraction

Re: Unwanted warnings/errors on pedals for multiple voices

On Mon, Apr 6, 2020 at 8:02 PM Carl Sorensen wrote: > > > > > *From: *Paolo Prete > *Date: *Monday, April 6, 2020 at 11:25 AM > *To: *Carl Sorensen > *Cc: *Thomas Morley , Kieren MacMillan < > kie...@kierenmacmillan.info>, Lilypond-User Mailing List < > lilypond-user@gnu.org> > *Subject: *Re:

Re: Positioning a segno relative to an alternative line

Hello David, >> No, I need it above the first staff, but below the 2. line. > > Won't that raise the 2 line?—I would shorten it, so that the segno > and coda match in height. I thought of that, but I thought that maintaining the regularity of the first and second alternatives was an asset. A

Re: Default accidental style with timing off

I’ve been playing with this further and have come up with the attached. Now, can someone tell me how I might combine \test and \bar into a redefined \bar (so that I don’t have to have both \test and \bar in all bar locations)? My naive expectation would have been `bar = \test \bar \etc` but

Re: Positioning a segno relative to an alternative line

On Mon 06 Apr 2020 at 19:41:14 (+0200), Jacques Menu wrote: > > Le 6 avr. 2020 à 19:37, Thomas Morley a écrit : > > Am Mo., 6. Apr. 2020 um 18:33 Uhr schrieb Jacques Menu > > mailto:imj-muz...@bluewin.ch>>: > > > Thanks for you help. > > > This produces the following, though: > > [...] > > > >

Re: Unwanted warnings/errors on pedals for multiple voices

From: Paolo Prete Date: Monday, April 6, 2020 at 11:25 AM To: Carl Sorensen Cc: Thomas Morley , Kieren MacMillan , Lilypond-User Mailing List Subject: Re: Unwanted warnings/errors on pedals for multiple voices On Mon, Apr 6, 2020 at 6:17 PM Carl Sorensen mailto:c_soren...@byu.edu>>

Re: Positioning a segno relative to an alternative line

> Le 6 avr. 2020 à 19:37, Thomas Morley a écrit : > > > > Am Mo., 6. Apr. 2020 um 18:33 Uhr schrieb Jacques Menu >: > > Thanks for you help. > > This produces the following, though: > [...] > > Maybe I misunderstood. Isn't it what you wanted? No, I need it

Re: Positioning a segno relative to an alternative line

Am Mo., 6. Apr. 2020 um 18:33 Uhr schrieb Jacques Menu < imj-muz...@bluewin.ch>: > Thanks for you help. > This produces the following, though: [...] Maybe I misunderstood. Isn't it what you wanted? Cheers, Harm

Re: Unwanted warnings/errors on pedals for multiple voices

On Mon, Apr 6, 2020 at 6:17 PM Carl Sorensen wrote: > > To me, the ideal default is PianoStaff. > > > 1) (another example) In a 4 hands piano score this would be undesirable, because it would logically assign the pedal to *one* performer, while it can switch from performer1 to performer2. For

Re: Unwanted warnings/errors on pedals for multiple voices

On 06/04/2020 17:17, Carl Sorensen wrote: *From: *Paolo Prete *Date: *Monday, April 6, 2020 at 9:15 AM *To: *Thomas Morley *Cc: *Kieren MacMillan , Lilypond-User Mailing List *Subject: *Re: Unwanted warnings/errors on pedals for multiple voices On Mon, Apr 6, 2020 at 4:25 PM Thomas Morley

Re: Positioning a segno relative to an alternative line

Hello Thomas, Thanks for you help. This produces the following, though: > Le 6 avr. 2020 à 16:47, Thomas Morley a écrit : > > Hi Jacques, > > try > \override Score.RehearsalMark.direction = #DOWN > > Cheers, > Harm

Re: Unwanted warnings/errors on pedals for multiple voices

From: Paolo Prete Date: Monday, April 6, 2020 at 9:15 AM To: Thomas Morley Cc: Kieren MacMillan , Lilypond-User Mailing List Subject: Re: Unwanted warnings/errors on pedals for multiple voices On Mon, Apr 6, 2020 at 4:25 PM Thomas Morley mailto:thomasmorle...@gmail.com>> wrote: Am Mo.,

Horizontal placement of first LyricText on a system

I'm having an issue with the first lyric syllable of a line colliding with the shortVocalName, which I've set to be engraved to the right of the system start (by using \override InstrumentName.direction = #RIGHT) and I can't find in the manual how to configure how far to the left the first lyric

Re: Unwanted warnings/errors on pedals for multiple voices

On Mon, Apr 6, 2020 at 4:25 PM Thomas Morley wrote: > Am Mo., 6. Apr. 2020 um 16:03 Uhr schrieb Paolo Prete < > paolopr...@gmail.com>: > > > > > > > > On Mon, Apr 6, 2020 at 3:08 PM Kieren MacMillan < > kie...@kierenmacmillan.info> wrote: > >> > >> Hi all, > >> > >> > You could move the

Re: Positioning a segno relative to an alternative line

Am Mo., 6. Apr. 2020 um 16:38 Uhr schrieb Jacques Menu : > > Hello folks, > > In the attached, I’d like the segno to be below the second alternative line > in the third system. > > I tried: > > \once \override TextScript.extra-offset = #'( 0 . -5.0 ) > \mark \markup { \musicglyph

Re: Unwanted warnings/errors on pedals for multiple voices

Am Mo., 6. Apr. 2020 um 16:03 Uhr schrieb Paolo Prete : > > > > On Mon, Apr 6, 2020 at 3:08 PM Kieren MacMillan > wrote: >> >> Hi all, >> >> > You could move the Piano_pedal_performer from Voice to Staff level. >> > Add or remove the \consists command to hear the difference. >> >> Is there some

Re: Unwanted warnings/errors on pedals for multiple voices

On Mon, Apr 6, 2020 at 3:08 PM Kieren MacMillan wrote: > Hi all, > > > You could move the Piano_pedal_performer from Voice to Staff level. > > Add or remove the \consists command to hear the difference. > > Is there some reason this shouldn’t be the default? > I can’t imagine Voice-independent

Re: Unwanted warnings/errors on pedals for multiple voices

Hi all, > You could move the Piano_pedal_performer from Voice to Staff level. > Add or remove the \consists command to hear the difference. Is there some reason this shouldn’t be the default? I can’t imagine Voice-independent pedalling is a feature of more than a miniscule fraction of “real

Re: incomplete tuplets in non-standard time signatures

Am So., 5. Apr. 2020 um 19:59 Uhr schrieb 98123981293 1293812397123 : > > Dear list, > > In the following example, I would like to: > 1) In the first voice: make the tuplet line to the right of the number into a > dashed straight line. > 2) In the second voice: fix the appearance of the last

Re: Ties between Fingerings

Am Mo., 6. Apr. 2020 um 10:49 Uhr schrieb Noeck : > > Wow. Thanks Harm! That makes sense and looks good. > > I never thought of a glissando here. But it actually makes sense. Now I > wonder if a straight glissando line would even be more appropriate than > a slur … I would read it more easily. > >

Re: Ties between Fingerings

> Hm. Can it be made breakable in a way that the glissando line appears on > both ends? Found it: \override Glissando.after-line-breaking = #'()

Re: Ties between Fingerings

Hm. Can it be made breakable in a way that the glissando line appears on both ends? Joram

Re: Ties between Fingerings

Wow. Thanks Harm! That makes sense and looks good. I never thought of a glissando here. But it actually makes sense. Now I wonder if a straight glissando line would even be more appropriate than a slur … I would read it more easily. Joram

Re: Ties between Fingerings

Am Mo., 6. Apr. 2020 um 10:27 Uhr schrieb Noeck : > > Hi, > > can Lilypond draw ties between fingerings? > I can fake it by using a slur and putting it above the fingering: > > \version "2.20.0" > { > % fake what I want > \override Fingering.avoid-slur = #'inside > cis''-4( c''-4) r > %

Ties between Fingerings

Hi, can Lilypond draw ties between fingerings? I can fake it by using a slur and putting it above the fingering: \version "2.20.0" { % fake what I want \override Fingering.avoid-slur = #'inside cis''-4( c''-4) r % ties possible on one note c''^\markup \finger \overtie "43" } Is that