Re: Dynamics, spacers, and partcombine used at once.

[Dominic]

Hi Carl,
I tried that and it does indeed work (at least in my small test example),
but it does seem like it destroys the semantic integrity of the code to have
notes and rests that are not really functioning as notes or rests.
Nevertheless, I'll keep it in mind as a solution to consider in the future
for one-off examples.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Dynamics-spacers-and-partcombine-used-at-once-tp149192p149200.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Dynamics, spacers, and partcombine used at once.

[Dominic]

Thanks Keith - this works brilliantly. Occasionally the part combiner will 
duplicate dynamics even though they are identical, so once in a while I have to 
force a 'partcombineChords' or 'partcombineUnisono' as necessary, but this is a 
small price to pay. Thanks again.

On 15 Aug 2013, at 06:11, Keith OHara [via Lilypond] 
 wrote:

> Dominic  gmail.com> writes: 
> 
> > My goal is to produce an orchestral score which both 
> > - uses *\partcombine* 
> > - has dynamics separately defined 
> 
> To make this go smoothly, you will probably need to keep in mind how 
> \partcombine works. \partcombine takes two music expressions and routes 
> each note into one of four Voices (depending on whether the players are 
> in unison, making chords, or soloI or soloII) and the system is a bit 
> fragile.  If you manage the voices in the expressions that go into 
> \partcombine, that can confuse the system. 
> 
> If you include the dynamics in the music for each player as it goes into 
> \partcombine, it will merge the dynamics and keep them attached to the 
> voice that is printing the notes so they are aligned to the notes. 
> 
> dd = {s4\p\< s s s\f s1 \bar "|."} 
> aa = << 
>   \dd 
>   {e4 f g a b\mf c' d' e'} >> 
> bb = << 
>   \dd 
>   {c4 d e f } >> 
> \new Staff { \transpose c c' \partcombine \aa \bb } 
> 
> 
> 
> 
> ___ 
> lilypond-user mailing list 
> [hidden email] 
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://lilypond.1069038.n5.nabble.com/Dynamics-spacers-and-partcombine-used-at-once-tp149192p149196.html
> To unsubscribe from Dynamics, spacers, and partcombine used at once., click 
> here.
> NAML





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Dynamics-spacers-and-partcombine-used-at-once-tp149192p149198.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Dynamics, spacers, and partcombine used at once.

[Carl Peterson]

On Wed, Aug 14, 2013 at 7:27 PM, Dominic  wrote:

>
> So my question is, how can I get the dynamics to align themselves
> 'correctly', i.e. as they would be if they were directly attached to the
> notes. Putting the dynamics in a Dynamics context is not really an option,
> since that will make them align themselves on one line, and I want the
> dynamics and hairpins to be snugly under the notes each time. Any ideas? I
> am aware that existing 'issues' exist to do with dynamic positioning, but
> many of them claim to be 'fixed' - yet they apparently are not.
>

What if you use rests or real notes instead of spacers and then hide the
notes and turn off the appropriate engravers so that the notes themselves
neither print nor impact the spacing of the score, but the dynamics are
attached to notes? Haven't tried this, but I use this technique with
partcombine to attach lyrics.

Cheers,
Carl
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Dynamics, spacers, and partcombine used at once.

[Keith OHara]

Dominic  gmail.com> writes:

> My goal is to produce an orchestral score which both
> - uses *\partcombine* 
> - has dynamics separately defined 

To make this go smoothly, you will probably need to keep in mind how 
\partcombine works. \partcombine takes two music expressions and routes 
each note into one of four Voices (depending on whether the players are
in unison, making chords, or soloI or soloII) and the system is a bit 
fragile.  If you manage the voices in the expressions that go into 
\partcombine, that can confuse the system. 

If you include the dynamics in the music for each player as it goes into 
\partcombine, it will merge the dynamics and keep them attached to the 
voice that is printing the notes so they are aligned to the notes.

dd = {s4\p\< s s s\f s1 \bar "|."}
aa = << 
  \dd
  {e4 f g a b\mf c' d' e'} >>
bb = << 
  \dd 
  {c4 d e f } >>
\new Staff { \transpose c c' \partcombine \aa \bb }




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Dynamics, spacers, and partcombine used at once.

[Dominic]

dynamic-positioning.ly
 
The following problem occurs with both 2.16.2 (stable) and 2.17.23
(unstable).

My goal is to produce an orchestral score which both
- uses *\partcombine* (e.g. to combine wind and brass instruments on shared
staves)
- has dynamics separately defined and attached to spacers, so that they can
be duplicated in several staves

Here are my observations:
- If the dynamic is attached directly to the note, it is positioned
correctly.
- If it is attached to a spacer, it is positioned too far to the left,
/unless/ the whole construction is explicitly wrapped in *\new Voice*. This
'solves' the problem in simple cases.
- However, when the music consists of *\partcombine*d material, (which mine
does) the dynamics are positioned wrongly, /even/ if I wrap the whole
construction in a *\new Voice*.

The incorrect positioning may seem small, but it causes great problems in a
real-life score, cutting into barlines and looking very odd especially at
the beginnings of bars.

So my question is, how can I get the dynamics to align themselves
'correctly', i.e. as they would be if they were directly attached to the
notes. Putting the dynamics in a Dynamics context is not really an option,
since that will make them align themselves on one line, and I want the
dynamics and hairpins to be snugly under the notes each time. Any ideas? I
am aware that existing 'issues' exist to do with dynamic positioning, but
many of them claim to be 'fixed' - yet they apparently are not.

I have attached a .ly file containing a series of minimal examples to
illustrate the observations I have made above.

Thanks everyone,

Dominic



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Dynamics-spacers-and-partcombine-used-at-once-tp149192.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: maintaining advanced power-user Scheme functions

[Pierre Perol-Schneider]

Hi Janek, Hi Harm,

2013/8/14 Thomas Morley 

>
> So I was annoyed by the lack of help/interest of others and I'm still
> pissed off.
>
>
Sorry for that, I think I totaly missed this discussion.



> Volunteers?
> Be sure that I'd grant support.
>

Sure !
Maybe give me some links where I can find how to do it.
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: maintaining advanced power-user Scheme functions

[Thomas Morley]

2013/8/14 Janek Warchoł :
> Hi,
>
> Harm and David N. (and some other people) write lots of very advanced
> (and very helpful!) Scheme functions.  These funcitons are improved
> over time, and there is a problem related to that: it's easy to get
> lost in all the email threads about them, and it's not always obvious
> where the most recent version is.
>
> I think that such functions should be tracked by version control, and
> i see two approaches:
> - include them in official LilyPond source as soon as they are
> created.  Upside: there's bigger chance that they will be updated when
> there are some changes. Downside: one has to write documentation and
> go through official patch submitting channels.
> - use another repository.  What about OpenLilyLib? http://www.openlilylib.org/
>
> At any rate, we better do something about it - at current state, all
> these funcitons can easily become lost or forgotten, and that would be
> a grave loss.
>
> Thoughts?
>
> Janek

Hi Janek,

well, if I think one of my functions, definitions etc is worth a
patch, I do so, but ofcourse there's the risk I'm distracted by other
tasks and forget about it or I've no time or ...

The idea of version-control for such functions might be nice. But
because I'm still not very familiar with git I'm feeling kind of
ambivalent.
Otoh, it might be an idea to do so for the LSR.

Though, a lot of my functions, definitions etc are too special-cased,
written to fit some users needs or they are workarounds not worth a
patch.
The right place for them would be the LSR, _if_ the LSR would be able
to compile them and not use a LilyPond-version far too old for many of
my ideas.

There were some insinuations on the list the last months (or was it a
year already?) to upgrade the LSR and yes, one should do so.
But I hesitate to volunteer again for this task.
I initiated the last ugrade and did perhaps the major work, supported
by several developers and the great David Nalesnik.
Though there was only one, I repeat _one_, other user who tried to help:
Philippe Hezaine

@Philippe
Thanks a lot for trying to help. And let me say: You didn't waste my time!

So I was annoyed by the lack of help/interest of others and I'm still
pissed off.

After my experience from doing it once, let me say: _Every_ user can
start the LSR-upgrade. The relevant CG-chapter is in far better state
than it was the last time. Ok, there will be snippets which need some
(perhaps advanced) scheme-knowledge and there may be some which need
advice from an experinced developer. Some tasks will need to be done
by people, who have the permission (from the LSR-maintainer) to do so.
But let me repeat:

_Every_ user can start the LSR-upgrade.

Volunteers?
Be sure that I'd grant support.

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Create different pdf layers

[Marek Klein]

Hello,

2013/8/1 Urs Liska 

> I have brought this up before without success. But as my interest
> reappeared I'll try it again with a slightly more specific question.
>

there is an existing issue based on your request:
http://code.google.com/p/lilypond/issues/detail?id=2542

Do you believe, it is a good Idea to discus your Ideas on bug-list?

Marek,
one of the very few bug squad members
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Tempo mark more than once

[Peter Toye]

Thomas,

Thanks. Works a treat.

Best regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

-
Tuesday, August 13, 2013, 4:47:42 PM, you wrote:

> 2013/8/13 Peter Toye :
>> I want to put a tempo marking (e,g, Allegro) into a song above both the
>> piano part and the vocal part. (I'm one of those people who believes in
>> making life easier for the pianist). And I can't see how to do it.

>> With the code as it is the "\tempo" indication is ignored.

>> If I move the "\tempo" above the "\new Staff" or outside the "<<" I get a
>> new staff with n o lines, and still no tempo indication.

>> How do I do it, please? I can't see it in the snippets.


>> Regards,

>> Peter Toye
>> mailto:lilyp...@ptoye.com
>> www.ptoye.com

>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user


> Hi,

> how about:

> \version "2.16.2"

> \layout {
> \context {
> \Score
> \remove "Metronome_mark_engraver"
> }
> \context {
> \Staff
> \consists "Metronome_mark_engraver"
> }
> }

> <<
>  \new Staff { \tempo 4=80 c1 }
>  \new PianoStaff
>  <<
>  \new Staff { \tempo 4=80 c1 }
>  \new Staff {  \clef bass c1 }



> HTH,
>   Harm___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: change the key signature

[Givaldo de Cidra]

Hi Thomas Morley

This code fully solved the problem...


Thanks very much.

Givaldo de Cidra




2013/8/14 Thomas Morley 

> 2013/7/28 Givaldo de Cidra 
> >
> >
> > \set Staff.keySignature '= # (((1. 0.), SHARP) ((1. 3.), natural))
> >
> > I want the key signature have a natural sign of caution.
> >
> > Is it possible?
>
>
> Hi,
>
> I'm a bit ashamed not having found a better method.
> It's Fischer-Technik/Tinkertoy at it's worst.
>
> Anyway, here it is:
>
> \version "2.16.2"
>
> #(define NEARNULL 1/10)
> #(define OTHERNEARNULL -1/10)
>
> very-kludgy-method-to-get-parenthesized-accidentals-in-key-signature =
> \override Staff.KeySignature #'before-line-breaking =
>   #(lambda (grob)
>  (let* ((glyph-name-alist (ly:grob-property grob 'glyph-name-alist))
> (lst (list (cons NEARNULL  "accidentals.leftparen")
>(cons OTHERNEARNULL  "accidentals.rightparen"
>
> (ly:grob-set-property! grob 'glyph-name-alist
> (append lst glyph-name-alist
>
> \layout {
>   \context {
> \Staff
> \very-kludgy-method-to-get-parenthesized-accidentals-in-key-signature
>   }
> }
>
> \new Staff {
> \set Staff.keySignature =
>   #`(((1 . 0) . ,SHARP)
>  ((1 . 3) . ,NEARNULL)
>  ((1 . 3) . ,NATURAL)
>  ((1 . 3) . ,OTHERNEARNULL)
>  ((1 . -1) . ,NEARNULL)
>  ((1 . -1) . ,FLAT)
>  ((1 . -1) . ,OTHERNEARNULL)
>  )
>  a'
> }
>
>
> Cheers,
>   Harm
>



-- 
Abraços,

Givaldo de Cidra
"Ser e Pensar Sempre no Objetivo é o Caminho para Alcançar o Sucesso"
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: change the key signature

[Thomas Morley]

2013/7/28 Givaldo de Cidra 
>
>
> \set Staff.keySignature '= # (((1. 0.), SHARP) ((1. 3.), natural))
>
> I want the key signature have a natural sign of caution.
>
> Is it possible?


Hi,

I'm a bit ashamed not having found a better method.
It's Fischer-Technik/Tinkertoy at it's worst.

Anyway, here it is:

\version "2.16.2"

#(define NEARNULL 1/10)
#(define OTHERNEARNULL -1/10)

very-kludgy-method-to-get-parenthesized-accidentals-in-key-signature =
\override Staff.KeySignature #'before-line-breaking =
  #(lambda (grob)
 (let* ((glyph-name-alist (ly:grob-property grob 'glyph-name-alist))
(lst (list (cons NEARNULL  "accidentals.leftparen")
   (cons OTHERNEARNULL  "accidentals.rightparen"

(ly:grob-set-property! grob 'glyph-name-alist
(append lst glyph-name-alist

\layout {
  \context {
\Staff
\very-kludgy-method-to-get-parenthesized-accidentals-in-key-signature
  }
}

\new Staff {
\set Staff.keySignature =
  #`(((1 . 0) . ,SHARP)
 ((1 . 3) . ,NEARNULL)
 ((1 . 3) . ,NATURAL)
 ((1 . 3) . ,OTHERNEARNULL)
 ((1 . -1) . ,NEARNULL)
 ((1 . -1) . ,FLAT)
 ((1 . -1) . ,OTHERNEARNULL)
 )
 a'
}


Cheers,
  Harm
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Text in front of Staves

[Kale Good]

Well that's the simple solution to defining right hand fingers that I 
was looking for. Thanks.


Your example, like Thomas's, throws an error for me with the \override 
VerticalAxisGroup using 2.16.2 Also throws an error for tuplet command, 
but both work once I take these out. Also, there's the issue of page 
breaks; right now the 20 exercise I have done are all crammed on one page.


Here is my code for the 2 we're looking at. Please pardon me if my 
minimum example isn't as minimum as possible; this is by far the biggest 
lily project I've undertaken.


\version "2.16.2"


 recurring themes %

staffset = {

\new Voice

\clef "G_8"

\key c

\major

\time 4/4

\mergeDifferentlyHeadedOn

\mergeDifferentlyDottedOn

\bar "|:"

}


cchord = {

\relative c' {

\bar ":|"

1

\bar "|."

}

}


rh = #rightHandFinger


strokesdown =

{

\set strokeFingerOrientations = #'(down)

\override StrokeFinger #'add-stem-support = ##t

}


strokesup = {

\set strokeFingerOrientations = #'(up)

\override StrokeFinger #'add-stem-support = ##t

}


%%% bass lines %%%

basslineOne = {

\strokesdown {

c,4\rh #1 e g c, | b d g b,

}

}


studies =

<<


%%%

%Number 3

%%%

\new Staff \with { instrumentName = "N° 3." }

<<

\staffset

\relative c' {

\bar ".|:"

\voiceOne

\scaleDurations #'(2 . 3) {

\strokesup

c,8 e'\rh #3 c\rh #2 e, e' c g e' c c, e' c

b, f'' d d, f' d g, f' d b, f'' d


}

\cchord

}

\new Voice

\relative c' {

\voiceTwo

\basslineOne

}

>>

%%%

%Number 4

%%%

\new Staff \with { instrumentName = "N° 4." }

<<

\staffset

\relative c' {

\bar ".|:"

\voiceOne

\scaleDurations #'(2 . 3) {

\strokesup

c,8 e\rh #2 g\rh #3 e g c g c e c, c' e

b, d g d g d' g, d' f b,, d' f

}

\cchord

}

\new Voice

\relative c' {

\voiceTwo

\basslineOne

}

>>

>>

\score {

<<

\studies

>>

\midi {

}


\layout {

ragged-right = ##f

\context {

\Voice

\override TupletBracket #'bracket-visibility = ##f

\override TupletNumber #'stencil = ##f

}

\context {

\Staff

}

\context {

\Score

\override SystemStartBar #'stencil = ##f

\override NoteColumn #'force-hshift = #0

}

}

}


\paper {

}


Best,
Kale






On 08/14/2013 09:44 AM, Pierre Perol-Schneider wrote:

Hi Harm, Hi Kale,

2013/8/14 Thomas Morley >



  \relative c' {


Two small remarks :
1) because of its tessitura, \relative is not needed for the guitar
2) better use \clef "G_8"

Here's Harm's code with "modern" fingerings and an alternative for the 
"no left hand finger" in the exercise no.4


\version "2.17.23"
%\version "2.16.2"

%%% Right hand fingerings %%
rhp = -\rightHandFinger #1
rhi = -\rightHandFinger #2
rhm = -\rightHandFinger #3
rha = -\rightHandFinger #4
rhx = -\rightHandFinger #5

 Aletrnate "No Left hand" fingering %
lnf =
#(let ((finger (make-music 'FingeringEvent)))
   (set! (ly:music-property finger 'tweaks)
   (acons 'text #{\markup\stencil #(make-circle-stencil 0.45 0.2 #f)#}
(ly:music-property finger 'tweaks)))
   finger)

%%% score 

\layout {
  ragged-right = ##f
  \context {
\Voice
\override TupletBracket #'bracket-visibility = ##f
\override TupletNumber #'stencil = ##f
  }
  \context {
\Staff
\override VerticalAxisGroup.default-staff-staff-spacing =
#'((basic-distance . 15)
 (minimum-distance . 10)
 (padding . 1))
  }
  \context {
\Score
\override SystemStartBar #'stencil = ##f
\override NoteColumn #'force-hshift = #0
  }
}

<<
  \new Staff \with { instrumentName = "N° 3" }
<<
  \new Voice
  \clef "G_8"
  {
\voiceOne
\set fingeringOrientations = #'(left)
\set strokeFingerOrientations = #'(up)
\override StrokeFinger #'add-stem-support = ##t
\bar ".|:"
\repeat volta 2 {
\tupletSpan 4
\times 2/3 {
%mes. 1
  c8   e e'\rhm c'\rhi
  g e'\rhm c'\rhi c e'\rhm c'\rhi |
  %mes. 2
  b,   d f'\rhm d'\rhi
  g f'\rhm d'\rhi b, f'\rhm d'\rhi |
}
}
% mes. 3
1 |
\bar "|."
  }
  \new Voice
  {
 \voiceTwo
   \set fingeringOrientations = #'(left)
   \set strokeFingerOrientations = #'(down)
 \override StrokeFinger #'add-stem-support = ##t
4   c\rhp
   b,\rhp
% mes. 3
1 |
  }
>>
  \new Staff \with { instrumentName = "N° 4" }
<<
  \new Voice
  \clef "G_8"
  {
\voiceOne
\set fingeringOrientations = #'(left)
\set strokeFingerOrientations = #'(up)
\override StrokeFinger #'add-stem-support = ##t
\bar ".|:"
\repeat volta 2 {
\tupletSpan 4
\times 2/3 {
 c8   e g\rhi 
 g c'\rhi  c c'\rhi e'\rhm
b,   d g\rhi 
g d'\rhi  b, d'\rhi f'\rhm
}
}
1
\bar "|."
  }
  \new Voice
  {
 \voiceTwo
   \set fingeringOrientations = #'(left)
   \set strokeFingerOrientations = #'(down)
 \override StrokeFinger #'add-stem-support = ##t
4 e\rhp g\rhp c\rhp
 d\

Re: text to the *right* of staves?

[Robin Bannister]

Adam Spiers-5 wrote
How can I put text *after* a staff?  
 I.e. directly to the right of the final barline?  



And here is another way: 


\version "2.16.2"
{
 \repeat unfold 44 R1
 \bar "|."
 % after final barline:
 \stopStaff 
 \once \override TextScript #'Y-offset = #-0.5 
 s1^"text at the right"

}

The -0.5 value centres it vertically; feel free to change this. 



Cheers, 
Robin



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Text in front of Staves

[Kale Good]

forgot to mention, i'm running 2.16.2

On 08/13/2013 07:56 PM, Thomas Morley wrote:




2013/8/14 mailto:k...@kalegood.com>>

I see that lilypond supports a cool-looking No. glyph, which is
great. I'd like to get in in front of each stave in order to
number a series of exercises. See attached png for an example.

I'm working on making a version of Giuliani's 120 right hand
studies for clasical guitar.

Hi,

I've typesetted the first two exercises of your png, though without 
fingerings.

This should give you a starting-point.
Btw, I hope you are _not_ going to rebuild these fossil 
right-hand-fingering-symbols. ;)



\version "2.17.24"

\layout {
  ragged-right = ##f
  \context {
\Voice
\override TupletBracket #'bracket-visibility = ##f
\override TupletNumber #'stencil = ##f
  }
  \context {
\Staff
\override VerticalAxisGroup.default-staff-staff-spacing =
  #'((basic-distance . 12)
 (minimum-distance . 7)
 (padding . 1))
  }
  \context {
\Score
\override SystemStartBar #'stencil = ##f
  }
}

<<
  \new Staff \with { instrumentName = "N° 3" }
<<
  \new Voice
  \relative c' {
\bar ".|:"
\repeat volta 2 {
\voiceOne
\tupletSpan 4
\times 2/3 {
c8 e' c e, e'c g e' c c, e' c
b, f'' d d, f' d g, f' d b, f'' d
}
}
1
\bar "|."
  }
  \new Voice
  \relative c' {
\voiceTwo
c4 e g c,
b d g b,
c1
  }
>>

  \new Staff \with { instrumentName = "N° 4" }
<<
  \new Voice
  \relative c' {
\bar ".|:"
\repeat volta 2 {
\voiceOne
\tupletSpan 4
\times 2/3 {
  c8 e g e g c g c e c, c' e
  b, d g d g d' g, d' f b,, d' f
}
}
1
\bar "|."
  }
  \new Voice
  \relative c' {
\voiceTwo
c4 e g c,
b d g b,
c1
  }
>>
>>

HTH,
  Harm



--
Kale Good: Guitar Instructor
phillyguitarlessons.com 
k...@kalegood.com 
phone: (215)260-5383

 * 4705 Baltimore Ave, Phila, PA 19143 -mailing & lessons
 * 1867 Frankford Ave. Phila, PA 19125 -lessons

Google+ 
Facebook 
Read my article "The Seven Secrets to Six String Success 
" at 
GuitarNoise.com 

Leading the Journey from No-Skills-Guitarist to Talented Musician!

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Text in front of Staves

[Kale Good]

Hi Thomas,
Thanks; it works like a charm* until I need a page break; right now its 
just crowding everything on one page. I put it a \pageBreak and nothing 
happened, so I'm guessing that lilypond won't break simultaneous music 
over a page (makes sense). Any overrides for this?


*works like a charm except for your \override VerticalAxisGroup command, 
which I'm not super familiar with (looks right to me). Won't compile 
with it, will compile without it.


wasn't planning on bringing back 19th century guitar fingering notation, 
but now that you mention it... =)


Thanks again,
Kale
On 08/13/2013 07:56 PM, Thomas Morley wrote:




2013/8/14 mailto:k...@kalegood.com>>

I see that lilypond supports a cool-looking No. glyph, which is
great. I'd like to get in in front of each stave in order to
number a series of exercises. See attached png for an example.

I'm working on making a version of Giuliani's 120 right hand
studies for clasical guitar.

Hi,

I've typesetted the first two exercises of your png, though without 
fingerings.

This should give you a starting-point.
Btw, I hope you are _not_ going to rebuild these fossil 
right-hand-fingering-symbols. ;)



\version "2.17.24"

\layout {
  ragged-right = ##f
  \context {
\Voice
\override TupletBracket #'bracket-visibility = ##f
\override TupletNumber #'stencil = ##f
  }
  \context {
\Staff
\override VerticalAxisGroup.default-staff-staff-spacing =
  #'((basic-distance . 12)
 (minimum-distance . 7)
 (padding . 1))
  }
  \context {
\Score
\override SystemStartBar #'stencil = ##f
  }
}

<<
  \new Staff \with { instrumentName = "N° 3" }
<<
  \new Voice
  \relative c' {
\bar ".|:"
\repeat volta 2 {
\voiceOne
\tupletSpan 4
\times 2/3 {
c8 e' c e, e'c g e' c c, e' c
b, f'' d d, f' d g, f' d b, f'' d
}
}
1
\bar "|."
  }
  \new Voice
  \relative c' {
\voiceTwo
c4 e g c,
b d g b,
c1
  }
>>

  \new Staff \with { instrumentName = "N° 4" }
<<
  \new Voice
  \relative c' {
\bar ".|:"
\repeat volta 2 {
\voiceOne
\tupletSpan 4
\times 2/3 {
  c8 e g e g c g c e c, c' e
  b, d g d g d' g, d' f b,, d' f
}
}
1
\bar "|."
  }
  \new Voice
  \relative c' {
\voiceTwo
c4 e g c,
b d g b,
c1
  }
>>
>>

HTH,
  Harm



--
Kale Good: Guitar Instructor
phillyguitarlessons.com 
k...@kalegood.com 
phone: (215)260-5383

 * 4705 Baltimore Ave, Phila, PA 19143 -mailing & lessons
 * 1867 Frankford Ave. Phila, PA 19125 -lessons

Google+ 
Facebook 
Read my article "The Seven Secrets to Six String Success 
" at 
GuitarNoise.com 

Leading the Journey from No-Skills-Guitarist to Talented Musician!

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Text in front of Staves

[Pierre Perol-Schneider]

Hi Harm, Hi Kale,

2013/8/14 Thomas Morley 

>
>   \relative c' {
>

Two small remarks :
1) because of its tessitura, \relative is not needed for the guitar
2) better use \clef "G_8"

Here's Harm's code with "modern" fingerings and an alternative for the "no
left hand finger" in the exercise no.4

\version "2.17.23"
%\version "2.16.2"

%%% Right hand fingerings %%
rhp = -\rightHandFinger #1
rhi = -\rightHandFinger #2
rhm = -\rightHandFinger #3
rha = -\rightHandFinger #4
rhx = -\rightHandFinger #5

 Aletrnate "No Left hand" fingering %
lnf =
#(let ((finger (make-music 'FingeringEvent)))
   (set! (ly:music-property finger 'tweaks)
   (acons 'text #{\markup\stencil #(make-circle-stencil 0.45 0.2 #f)#}
(ly:music-property finger 'tweaks)))
   finger)

%%% score 

\layout {
  ragged-right = ##f
  \context {
\Voice
\override TupletBracket #'bracket-visibility = ##f
\override TupletNumber #'stencil = ##f
  }
  \context {
\Staff
\override VerticalAxisGroup.default-staff-staff-spacing =
  #'((basic-distance . 15)
 (minimum-distance . 10)
 (padding . 1))
  }
  \context {
\Score
\override SystemStartBar #'stencil = ##f
\override NoteColumn #'force-hshift = #0
  }
}

<<
  \new Staff \with { instrumentName = "N° 3" }
<<
  \new Voice
  \clef "G_8"
  {
  \voiceOne
  \set fingeringOrientations = #'(left)
  \set strokeFingerOrientations = #'(up)
  \override StrokeFinger #'add-stem-support = ##t
\bar ".|:"
\repeat volta 2 {
\tupletSpan 4
\times 2/3 {
%mes. 1
c8   e e'\rhm c'\rhi
g e'\rhm c'\rhi c e'\rhm c'\rhi |
%mes. 2
b,   d f'\rhm d'\rhi
g f'\rhm d'\rhi b, f'\rhm d'\rhi |
}
}
% mes. 3
1 |
\bar "|."
  }
  \new Voice
  {
  \voiceTwo
  \set fingeringOrientations = #'(left)
  \set strokeFingerOrientations = #'(down)
  \override StrokeFinger #'add-stem-support = ##t
4   c\rhp
   b,\rhp
% mes. 3
1 |
  }
>>

  \new Staff \with { instrumentName = "N° 4" }
<<
  \new Voice
  \clef "G_8"
  {
\voiceOne
  \set fingeringOrientations = #'(left)
  \set strokeFingerOrientations = #'(up)
  \override StrokeFinger #'add-stem-support = ##t
  \bar ".|:"
\repeat volta 2 {
\tupletSpan 4
\times 2/3 {
  c8   e g\rhi 
  g c'\rhi  c c'\rhi e'\rhm

  b,   d g\rhi 
  g d'\rhi  b, d'\rhi f'\rhm
}
}
1
\bar "|."
  }
  \new Voice
  {
  \voiceTwo
  \set fingeringOrientations = #'(left)
  \set strokeFingerOrientations = #'(down)
  \override StrokeFinger #'add-stem-support = ##t
4 e\rhp g\rhp c\rhp
 d\rhp g\rhp b,\rhp
1
  }
>>
>>

Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Different figures on one bass (y-offset question)

[Francois Planiol]

Hello,

I join a pict. With lines separators would be best.
Actually, I did it manually with lines of figures full of

<\markup {" "}>2.
<\markup {" "}>2.
<\markup {" "}>2.

but thats not very smart... Then if the <7 4 2> has no glyph {" "}
directly under it, it lowers itself in the figures of the lower line
(look pic: false)

Thanks in advance,

Frank

2013/8/13, Phil Holmes :
> - Original Message -
> From: "Francois Planiol" 
> To: "lilypond-user" 
> Sent: Monday, August 12, 2013 9:45 PM
> Subject: Different figures on one bass (y-offset question)
>
>
>> Hello,
>>
>> I am working at material for harmony-lectures and need different
>> figures one the same bass (showing different chords-possibilities).
>> I need some Y-spacing between the figures lines to make clear for the
>> students, this doesnt belong together. This depends of course of the
>> line-numbers of the more complex figure.
>>
>> And I didnt found a way to do that.
>> Is this possible?
>> Thanks in advance,
>> Frank
>
>
> Could you provide an image of what you're trying to do, please?
>
> --
> Phil Holmes
>
<><>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: can someone convert a tux guitar to lilypond to PDF for me

[Pierre Perol-Schneider]

2013/8/14 Christopher Reed 

> hey I tried but I lost the drum section could someone email me and I'll
> send you the .Tg file
>
Done,
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Steinberg's progress report on new notation software

[Janek Warchoł]

Lol, indeed!
Thanks for letting me know, Jacques! Corrected.

Janek

2013/8/14 Andrew Bernard 

>
> An absolutely marvellous typo in our particular context. :-)
>
> Andrew
>
>   Jacques Menu 
>  14 August 2013 7:25 PM
>
> Typo: algorythmic
>
>
>
>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Steinberg's progress report on new notation software

[Andrew Bernard]

An absolutely marvellous typo in our particular context. :-)

Andrew

   	   
   	Jacques Menu  
  14 August 2013 
7:25 PM
  Typo: algorythmic

  


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Steinberg's progress report on new notation software

[Jacques Menu]

Hello Janek,

Very interesting post, thanks!

Typo: algorythmic

JM

Le 14 août 2013 à 10:54:17, Janek Warchoł  a écrit :

> [lots of discussion about LilyPond vs other notation software]
> 
> Hi people,
> 
> it seems that i've missed an important discussion.  After reading it
> (and reading comments on the Steinberg blog), i decided to add my
> comment in the form of a blog post:
> http://lilypondblog.org/2013/08/honestly-is-lilypond-good-enough/
> I'd be interested in hearing your opinions in the comments!
> 
> best,
> Janek
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Steinberg's progress report on new notation software

[Janek Warchoł]

[lots of discussion about LilyPond vs other notation software]

Hi people,

it seems that i've missed an important discussion.  After reading it
(and reading comments on the Steinberg blog), i decided to add my
comment in the form of a blog post:
http://lilypondblog.org/2013/08/honestly-is-lilypond-good-enough/
I'd be interested in hearing your opinions in the comments!

best,
Janek

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: text to the *right* of staves?

[Eluze]

Adam Spiers-5 wrote
> How can I put text *after* a staff?  I.e. directly to the right of the
> final barline?  I've searched high and low but can't find anything
> close ...

here's one simple way:

\markup \fill-line {
  \score {
\new Voice \repeat unfold 4 \relative {a' b c d}
\layout{
  line-width=#166 
  ragged-right = ##f 
}
  }
  "text at the right"
}
Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/text-to-the-right-of-staves-tp149126p149138.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Getting rid of space above lyrics...I'm completely stumped.

[Eluze]

John S.L. wrote
> Here's the log
> %
> Starting lilypond-windows.exe 2.16.2 [ForumAug8.ly]...
> Processing
> `c:/users/johnla~1/appdata/local/temp/frescobaldi-pgntlt/tmpxiwiz4/ForumAug8.ly'
> Parsing...
> c:/users/johnla~1/appdata/local/temp/frescobaldi-pgntlt/tmpxiwiz4/ForumAug8.ly:40:16:
> error: Grob name should be alphanumeric
>   \override 
> LyricText.font-size = #-1 

the culprit is in line 40 column 16 where in upgraded versions (2.17.4 and
up) we can use 

\override LyricText.font-size 

instead of 

\override LyricText #'font-size


sorry I overlooked that - but it also brings out the importance to reduce
sample code to a minimum

Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Getting-rid-of-space-above-lyrics-I-m-completely-stumped-tp149021p149134.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user