Re: [Lyric+Chords project] required engravers

[Thomas Morley]

Am Fr., 14. Dez. 2018 um 17:57 Uhr schrieb Kieren MacMillan
:
>
> Hi Harm,
>
> > Any idea how to tackle:
> > (1) ligatures
> > \lyricmode { f -- i }
>
> Can you give me a real world situation — in a "regular" score (i.e., with 
> notes) — in which you would want both a ligature *and* chords on both 
> elements of the ligature? I can’t comprehend what that would look like…
>
> Thanks,
> Kieren.

Hi Kieren,

I can't imagine such a score either, though isn't it the challenge to
transform a score with chords/notes/lyrics there into a leadsheat?
Then you may have hyphenated text in such a score which should be
transformed into one word in the text of a leadsheet.

Look at the german children song:
https://cdn.familie.de/bilder/die-affen-rasen-durch-den-wald-1200-235512.jpg

In the last meaure of second line the chords could be done like
E/E   E/BE/Gis  E/E
Af -- fen -- ban -- de
(No ligature, every syllable with it's own chord-symbol)

In a leadsheet I'd then expect
E/E E/B E/Gis E/E
Affenbande
with ligature at "ff" and reasonable distributed chord-symbols.

Or are my expextations wrongly?


Cheers,
  Harm

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

Re: Problem with accidentals.ly and Lilypond 2.19.82

[Thomas Morley]

Am Fr., 14. Dez. 2018 um 17:12 Uhr schrieb Luca Danieli :
>
> Hi Thomas,
>
> your analysis has been very good.
> I have almost solved the issue.
> I just don't know what's the glyph name for the SEMI-SHARP and SEMI-FLAT
>
> In the following code, I should add the ones for SEMI-SHARP and SEMI-FLAT.
> Do you know what's the name of the glyph? I already tried (e.g. SEMI-SHARP) 
> "accidentals.semi-sharp", "accidentals.semisharp" and 
> "accidentals.sharp.semi".

Well, you change the note-names, scales, accidental-glyphs etc. So
it's up to you to decide which glyph you want to assign to a which
alteration.
Available are:
http://lilypond.org/doc/v2.19/Documentation/notation/the-emmentaler-font#accidental-glyphs

Cheers,
  Harm

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

Re: [Lyric+Chords project] required engravers

[Johan Vromans]

On Sat, 15 Dec 2018 10:08:05 +0100, Thomas Morley
 wrote:

> In the last meaure of second line the chords could be done like
> E/E   E/BE/Gis  E/E
> Af -- fen -- ban -- de
> (No ligature, every syllable with it's own chord-symbol)
> 
> In a leadsheet I'd then expect
> E/E E/B E/Gis E/E
> Affenbande
> with ligature at "ff" and reasonable distributed chord-symbols.

For a lead sheet it is crucial that the chord is placed exactly on top of
the syllable. Since the chords are wider than the syllables, it would
become something similar to
http://www.squirrel.nl/pub/xfer/uploads/3CSdG2lqsGIQZwZdizzYr3Eg.png

Some seem to like an alternative format that put the chords after
the line, and underscore the syllable
http://www.squirrel.nl/pub/xfer/uploads/3CzvTW10rCuZmRgnnMzwBhAQ.png

-- Johan

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

Re: [Lyric+Chords project] required engravers

[Kieren MacMillan]

Hi Harm,

> isn't it the challenge to transform a score with chords/notes/lyrics there 
> into a leadsheat?

Yes.

> Then you may have hyphenated text in such a score which should be
> transformed into one word in the text of a leadsheet.

Yes… *but only after chord-spacing is complete*!

> In the last meaure of second line the chords could be done like
> E/E   E/BE/Gis  E/E
> Af -- fen -- ban -- de
> (No ligature, every syllable with it's own chord-symbol)
> 
> In a leadsheet I'd then expect
> E/E E/B E/Gis E/E
> Affenbande
> with ligature at "ff" and reasonable distributed chord-symbols.
> 
> Or are my expextations wrongly?

In the "chords directly above lyrics" format, I think most people expect the 
chords to be precisely aligned with their respective syllables. Thus, if the 
chord names are too wide, they must force the syllables apart (including 
ligatures).

Cheers,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: [Lyric+Chords project] required engravers

[Kieren MacMillan]

Hi Johan,

> For a lead sheet it is crucial that the chord is placed exactly on top of
> the syllable. Since the chords are wider than the syllables, it would
> become something similar to
> http://www.squirrel.nl/pub/xfer/uploads/3CSdG2lqsGIQZwZdizzYr3Eg.png

Exactly.

> Some seem to like an alternative format that put the chords after
> the line, and underscore the syllable
> http://www.squirrel.nl/pub/xfer/uploads/3CzvTW10rCuZmRgnnMzwBhAQ.png

Yes! It would be very interesting to eventually include multiple different 
formats in the framework. However, my first target is the most common format 
(i.e., the "chords exactly on top of syllable" format you mentioned above).

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: [Lyric+Chords project] required engravers

[Johan Vromans]

On Sat, 15 Dec 2018 09:19:25 -0500, Kieren MacMillan
 wrote:

> Yes! It would be very interesting to eventually include multiple
> different formats in the framework.

The ChordPro reference implementation currently supports
* chords above lyrics
* chords under lyrics
* chords within lyrics
* chords at the right

And then there are chord diagrams...
E.g. https://www.chordpro.org/chordpro/images/style_modern3.pdf

-- Johan

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

Re: [Lyric+Chords project] required engravers

[Kieren MacMillan]

Hi Johan,

> The ChordPro reference implementation currently supports
> * chords above lyrics
> * chords under lyrics
> * chords within lyrics
> * chords at the right
> And then there are chord diagrams...
> E.g. https://www.chordpro.org/chordpro/images/style_modern3.pdf

Very nice!
I am hoping my LilyChordPro framework will eventually allow all of that within 
Lilypond.

Thanks!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: feathered beam calculations

[Reggie]

N. Andrew Walsh wrote
> Hi List,
> 
> I'm trying to use the \featherDurations command on a brief passage:
> 
> \relative c' {
> a,,^\markup { \italic "subito meno mosso" }\( b cis dis eis8\)
>  \override Beam.grow-direction = #LEFT
>   \featherDurations #(ly:make-moment 2/1)
>  { a,32[\( b cis dis eis]\)\fermata }
>  \override Beam.grow-direction = #'()
>  < a, cis e >16 < a cis e >
> 
> }
> 
> What I want is for that feathered group on the fourth line to occupy the
> duration of exactly one eighth note. As there are five notes, I'm
> struggling with the math, and thus what to put after ly:make-moment.
> 
> Can you advise as to what the numbers should be?
> 
> Cheers,
> 
> A
> 
> ___
> lilypond-user mailing list

> lilypond-user@

> https://lists.gnu.org/mailman/listinfo/lilypond-user

Did you solve this? I cannot find anywhere in documentation an exact
information about how to explicitly tell lilypond how many beats should be
in a group of feather beamed notes. Like you say 1 eighth note what about a
dotted quarter or a half note. No idea how to force the duration of feathers
to be X beats in order for bar check success. Did you find the answer?



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Combine these segments for same score

[Reggie]

I cannot use LilyPond for large scores it takes hours to compile. Nowhere in
the documentation does it teach me how to merge. Can someone please show me
how to make a seamless score from these multiple "segments" name? Every time
I compile I get broken scores and not one piece together. Do I need to
include currentBars or some kind of Scorecode? Please help. Please create a
dummy file so I can merge into a larger score thank you.

badSegmenttt.png
  

My score file is this code

\version "2.19.82"
% current bar number?
\include "segment1.ly"
\include "segment2.ly"
\include "segment3.ly"

My other files are this code respectively 1 2 3

\new Staff = "mystaff" \relative c' { \repeat unfold 50 {c2 c2} }
\new Staff = "mystaff" \relative c' { \repeat unfold 50 {e2 e2} }
\new Staff = "mystaff" \relative c' { \repeat unfold 50 {g'2 g'2} }




--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Re: Handbell mallets

[Rick Kimpel]

On 2018-12-15 12:46 pm, Aaron Hill wrote:
 
On 2018-12-14 9:58 pm, Rick Kimpel wrote:
>> All,
>> In handbell music, there is an articulation for playing the bell with
>> a mallet while it is on the table. It looks like a "stopped" symbol
>> near the note head, with a "staccato" articulation just beyond that. I
>> can get reasonable results for notes near the top and bottom of the
>> staff, but when I have something like
>> 
>> {f8'-+-.[ f''-+-.]}
>> 
>> one of the two will always look bad. Ideally, the + will be in the
>> staff near the note head. Any ideas on how to achieve this without
>> tweaking each articulation? I have half a mind to just use staccato
>> and a note in the score.
>> 
>> >https://www.handbellworld.com/images/HandbellNotation/MalletWithHandbellOnTable>.jpg
>
>Creating a custom articulations is probably the best option, however you 
>can also easily redefine the stencil for an existing one:
>
>
>\version "2.19.82"
>
>% handbell mallet
>hbm = \tweak stencil #(lambda (grob)
>   (grob-interpret-markup grob #{ \markup \combine
>   \raise #1 \musicglyph #"scripts.stopped"
>   \musicglyph #"scripts.staccato"
> #})) \stopped

Thanks, Aaron. 
You made me take a closer look at my scores. Other publishers put 
the + over the . no matter the orientation. Something I had never 
noticed before. So your first solution was close (although I find the 
directional one more interesting). All I did was change the final 
\stopped to \staccato. I will have to look up this custom articulation 
thing one of these days, though.

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