Re: Printing Title Pages; has it been a thought?
> > I think that this would be an interesting feature, but the issue with this > is > giving a default title page. It would require a user to adjust the title > page to fit the needs of the user. I have created a personal "title page > template," if you will. I'll attach it in the email to see what you think. > Note that my title page has my logo on it, so you'll have to change the .ly > file accordingly. Ryan McClure ryanmichaelmccl...@gmail.com Music Education Major, Shepherd University Luna Music Engraving I tried the template, and I was very pleased with the results. It is a most excellent I think we can learn a lot from Sibelius here... They seem to have an idea of how to organize a title page. We could also look at (who would have thought...?) old Baerenreiter editions, and figure out the consensus. I mean: If LaTeX can figure it out, why cannot we?? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Paper variables in scheme function
Am 28.03.2014 20:44, schrieb David Kastrup:
Simon Albrecht writes:
Hello,
I'm just creating a style sheet and want to create a scheme function
which sets the paper margins. However it seems the paper variables
aren't bound and I don't know why. A simple example would be:
\version "2.19.3"
test =
#(define-scheme-function (parser location num) (number?)
#{ \paper {
top-margin = #(* num paper-height)
}
#}
)
\test 0.1
{ c'1 }
Help is very much appreciated :-)
It is a scoping problem: the scope of # inside of #{ ... #} is that of
the embedding. Try something like
test =
#(define-scheme-function (parser location num) (number?)
#{ \paper { top-margin
$(* num (module-ref (current-module) 'paper-height)) } #})
\paper { \test 0.9 }
{ c'1 }
I am somewhat irritated that a plain
\test 0.9
does not work just as well. I thought I had done something to make that
work at one point of time, but apparently not so.
Attached you find the resulting function with a test score; the
'portrait version now works perfectly, only I can’t get the 'landscape
version to work as well (but I don’t need it for current work).
All the best,
Simon
% copyright by Simon Albrecht 2014
% licensed as Creative Common (BY-SA)
\version "2.19.3"
%% use inside \paper {}
typeArea =
#(define-scheme-function
;; size: optional paper size specification as defined in scm/paper.scm
;; orientation: 'portrait or 'landscape
;; ratio: typeAreaWidth/typeAreaHeight
examples:
portrait: standard 3/2, smaller would be 8/5 and 5/3
landscape: standard 5/4, smaller would be 6/5, larger 4/3
(parser location sz orientation ratio)
((string? "a4") symbol? rational?)
(_i "Calculate paper margins for DIN A paper formats so that:
â the width-to-height ratio of the type area is @var{ratio}
â the upper corners of the type area are on the diagonals of imaginary double pages
â the lower corners of the type area are on the diagonals of the page
which is supposed to make a pleasant visual appearance")
(cond
((and (eq? orientation 'portrait) (< ratio (sqrt 2)))
(ly:warning "Type area ratio has to be larger than square root
of 2 (1,414â¦). Using default margins"))
((and (eq? orientation 'landscape) (> ratio (sqrt 2)))
(ly:warning "Type area ratio has to be smaller than square root
of 2 (1,414â¦). Using default margins"))
(else
(cond ((eq? orientation 'portrait)
#{ \paper {
#(set-paper-size sz)
top-margin = $(*
(module-ref (current-module) 'paper-height)
(/ (- (numerator ratio)
(* (denominator ratio) (sqrt 2)))
(- (* 4 (numerator ratio))
(* 3 (denominator ratio) (sqrt 2))) ))
bottom-margin = #(* (module-ref (current-module) 'top-margin) 2)
left-margin = #(* (module-ref (current-module) 'top-margin) (sqrt 2))
right-margin = #(* (module-ref (current-module) 'top-margin) (sqrt 2)) }
#} )
((eq? 'orientation 'landscape)
#{ \paper {
#(set-paper-size sz orientation)
left-margin = $(*
(module-ref (current-module) 'paper-width)
(/ (- (numerator ratio)
(* (denominator ratio) (sqrt 2)))
(- (* 1.5 (numerator ratio))
(* 2 (denominator ratio) (sqrt 2))) ))
right-margin = #(module-ref (current-module) 'left-margin)
bottom-margin = #(* 0.5 (module-ref (current-module) 'left-margin) (sqrt 2))
top-margin = #(* (module-ref (current-module) 'bottom-margin) 0.5) }
#} )))
))
\paper {
\typeArea #'landscape #5/4
}
{ c'1 }___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Paper variables in scheme function
Simon Albrecht writes:
> Hello,
>
> I'm just creating a style sheet and want to create a scheme function
> which sets the paper margins. However it seems the paper variables
> aren't bound and I don't know why. A simple example would be:
>
> \version "2.19.3"
>
>
> test =
>
> #(define-scheme-function (parser location num) (number?)
>
> #{ \paper {
>
> top-margin = #(* num paper-height)
>
> }
>
> #}
>
> )
>
>
> \test 0.1
>
>
> { c'1 }
>
>
>
> Help is very much appreciated :-)
It is a scoping problem: the scope of # inside of #{ ... #} is that of
the embedding. Try something like
test =
#(define-scheme-function (parser location num) (number?)
#{ \paper { top-margin
$(* num (module-ref (current-module) 'paper-height)) } #})
\paper { \test 0.9 }
{ c'1 }
I am somewhat irritated that a plain
\test 0.9
does not work just as well. I thought I had done something to make that
work at one point of time, but apparently not so.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Paper variables in scheme function
Hello,
I'm just creating a style sheet and want to create a scheme function
which sets the paper margins. However it seems the paper variables
aren't bound and I don't know why. A simple example would be:
\version "2.19.3"
test =
#(define-scheme-function (parser location num) (number?)
#{ \paper {
top-margin = #(* num paper-height)
}
#}
)
\test 0.1
{ c'1 }
Help is very much appreciated :-)
Regards, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RSS/Atom news feed?
2.18.3 doesn't exist, so announcing it might be problematic. 2.18.2: er, yes. -- Phil Holmes - Original Message - From: Federico Bruni To: Phil Holmes Cc: Tobias Braun ; lilypond-user Mailinglist Sent: Friday, March 28, 2014 6:08 PM Subject: Re: RSS/Atom news feed? Il 28/mar/2014 19:01 "Phil Holmes" ha scritto: > > - Original Message - From: "Tobias Braun" > To: > Sent: Friday, March 28, 2014 4:29 PM > Subject: RSS/Atom news feed? > > > >> Hi, >> >> I was wondering whether there was any such thing as an RSS/Atom news feed for the news items on the LilyPond homepage. I remember there used to be one way back on the old web site, but now I can't seem to find one. >> >> Right now, I am using a web service that polls the LilyPond homepage, tries to parse the HTML for news items and generates an RSS feed from that. But it doesn't work very reliably. >> >> I'd really like to keep up with LilyPond news. There has to be a better solution than the hack I just mentioned! >> >> Tobias > > > > Generally, anything that's posted on the news is also sent to lilypond.announce. Is that of use? > Did you forget to announce 2.18.3? He can use Ben's method on that list: https://lists.gnu.org/mailman/listinfo/info-lilypond ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RSS/Atom news feed?
Il 28/mar/2014 19:01 "Phil Holmes" ha scritto: > > - Original Message - From: "Tobias Braun" < lists.tob...@braun-abstatt.de> > To: > Sent: Friday, March 28, 2014 4:29 PM > Subject: RSS/Atom news feed? > > > >> Hi, >> >> I was wondering whether there was any such thing as an RSS/Atom news feed for the news items on the LilyPond homepage. I remember there used to be one way back on the old web site, but now I can't seem to find one. >> >> Right now, I am using a web service that polls the LilyPond homepage, tries to parse the HTML for news items and generates an RSS feed from that. But it doesn't work very reliably. >> >> I'd really like to keep up with LilyPond news. There has to be a better solution than the hack I just mentioned! >> >> Tobias > > > > Generally, anything that's posted on the news is also sent to lilypond.announce. Is that of use? > Did you forget to announce 2.18.3? He can use Ben's method on that list: https://lists.gnu.org/mailman/listinfo/info-lilypond ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RSS/Atom news feed?
- Original Message - From: "Tobias Braun" To: Sent: Friday, March 28, 2014 4:29 PM Subject: RSS/Atom news feed? Hi, I was wondering whether there was any such thing as an RSS/Atom news feed for the news items on the LilyPond homepage. I remember there used to be one way back on the old web site, but now I can't seem to find one. Right now, I am using a web service that polls the LilyPond homepage, tries to parse the HTML for news items and generates an RSS feed from that. But it doesn't work very reliably. I'd really like to keep up with LilyPond news. There has to be a better solution than the hack I just mentioned! Tobias Generally, anything that's posted on the news is also sent to lilypond.announce. Is that of use? -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: avoiding collisions between rest and stems when writing multiple expressions
Am 28.03.2014 18:04, schrieb Jordan B:
Hello - When writing multiple expressions, I find the rest collides
with the stem of notes. Like so:
\version "2.14.2"
Please consider upgrading to the current stable version, 2.18.2. There
are many and great improvements in there.
\relative c' {
\clef bass
%the quarter rest is bumping against the dotted half note
b1
<< fis2. { r4 <> <>} >>
}
Is there a better way to write this so this does not happen?
The reason is that you have only one voice. If you read the logfile,
you'll see it complains about rests and noteheads being on one stem,
which is forbidden. In this case, you need something like
\relative c' {
\clef bass
b1
<<
{ r4 q }
\\
{ fis,2. }
>>
}
For more information, consult the learning manual and other introductory
texts on lilypond.org, especially I'm hearing voices
.
Thanks!
Jordan
Have fun with Lilypond!
Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: avoiding collisions between rest and stems when writing multiple expressions
Jordan B writes:
> Hello - When writing multiple expressions, I find the rest collides with
> the stem of notes. Like so:
>
> \version "2.14.2"
>
>
> \relative c' {
>
> \clef bass
>
> %the quarter rest is bumping against the dotted half note
>
> b1
>
> << fis2. { r4 <> <>} >>
>
> }
>
> Is there a better way to write this so this does not happen?
You probably mean something like
\version "2.14.2"
\relative c' {
\clef bass
b1
<< { r4 } \\ fis,2. >>
}
You really should take a look at least at LilyPond's tutorial pages to
figure out how to arrange your input.
And 2.14.2 is rather ancient. 2.16 was released almost two years ago,
and 2.18.2 is current.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
edition-engraver and templates
Hello list, today I want to announce the edition-graver and lalily-templates in openLilyLib: https://github.com/openlilylib/snippets/tree/master/templates/lalily https://github.com/openlilylib/snippets/tree/master/editorial-tools/edition-engraver I invite you to test it. The examples compile with lily 2.18 (stable) and 2.19.3 (devel). As with all snippets, you have to add the path to the openSnippetLib to the include paths either via CLI-option -Ipath/to/snippets or for example in frescobaldi in the preferences. Then you can type \include "templates/lalily/definitions.ily" or \include "editorial-tools/edition-engraver/definitions.ily" Then you can start using it. This is a work in progress. The list of predefined templates is far from complete, but it might be usefull. If you have comments or questions, don't hesitate to contact me. Cheers, Jan-Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RSS/Atom news feed?
Tobias Braun wrote > Hi, > > I was wondering whether there was any such thing as an RSS/Atom news feed > for the news items on the LilyPond homepage. I remember there used to be > one way back on the old web site, but now I can't seem to find one. > > Right now, I am using a web service that polls the LilyPond homepage, > tries to parse the HTML for news items and generates an RSS feed from > that. But it doesn't work very reliably. > > I'd really like to keep up with LilyPond news. There has to be a better > solution than the hack I just mentioned! > > Tobias > > > ___ > lilypond-user mailing list > lilypond-user@ > https://lists.gnu.org/mailman/listinfo/lilypond-user Apologies I just realized that I misread your post. You were not looking for an RSS feed for the mailing list, but only the lilypond.org home page blurbs. That's different, that's the web side of things. Sorry if I confused you! Ben - composer | sound designer LilyPond Tutorials (for beginners) --> http://bit.ly/bcl-lilypond -- View this message in context: http://lilypond.1069038.n5.nabble.com/RSS-Atom-news-feed-tp160908p160911.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: RSS/Atom news feed?
Tobias Braun wrote > Hi, > > I was wondering whether there was any such thing as an RSS/Atom news feed > for the news items on the LilyPond homepage. I remember there used to be > one way back on the old web site, but now I can't seem to find one. > > Right now, I am using a web service that polls the LilyPond homepage, > tries to parse the HTML for news items and generates an RSS feed from > that. But it doesn't work very reliably. > > I'd really like to keep up with LilyPond news. There has to be a better > solution than the hack I just mentioned! > > Tobias > > > ___ > lilypond-user mailing list > lilypond-user@ > https://lists.gnu.org/mailman/listinfo/lilypond-user I have Firefox set up with the LilyPond RSS feed and it's working just fine. All you have to do is add this "bookmark" to your Live Bookmarks/Feed and it will auto-refresh and bring you to the Nabble full mailing list interface and archive. That may or may not be what you prefer but it does work, just an fyi. Hope this helps. Add this --> http://lilypond.1069038.n5.nabble.com/User-ft3.xml - composer | sound designer LilyPond Tutorials (for beginners) --> http://bit.ly/bcl-lilypond -- View this message in context: http://lilypond.1069038.n5.nabble.com/RSS-Atom-news-feed-tp160908p160910.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
avoiding collisions between rest and stems when writing multiple expressions
Hello - When writing multiple expressions, I find the rest collides with
the stem of notes. Like so:
\version "2.14.2"
\relative c' {
\clef bass
%the quarter rest is bumping against the dotted half note
b1
<< fis2. { r4 <> <>} >>
}
Is there a better way to write this so this does not happen?
Thanks!
Jordan
J.Z. Burdge
www.existentialistcafe.wordpress.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RSS/Atom news feed?
Hi, I was wondering whether there was any such thing as an RSS/Atom news feed for the news items on the LilyPond homepage. I remember there used to be one way back on the old web site, but now I can't seem to find one. Right now, I am using a web service that polls the LilyPond homepage, tries to parse the HTML for news items and generates an RSS feed from that. But it doesn't work very reliably. I'd really like to keep up with LilyPond news. There has to be a better solution than the hack I just mentioned! Tobias ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics: \set associatedVoice
Simon Albrecht writes:
>>You can just add
>>
>> makeOctaves =
>> #(define-music-function (parser location oct mus) (integer? ly:music?)
>>(make-relative (mus) mus
>> #{ << \transpose c' $(ly:make-pitch oct 0 0) $mus $mus >> #}))
> Excellent! This seems to be just as powerful as LSR 445 while being
> far less complicated… or do I overlook something?
It will differ in its treatments of accents etc (one would probably want
to filter them from one of the music copies). The real work here is
actually in the make-relative macro available as of 2.18.0.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics: \set associatedVoice
Am 28.03.2014 03:57, schrieb David Kastrup:
Simon Albrecht writes:
Hello,
I've got a problem: I'm typesetting a Brahms lied where some melismata
are only for one stanza and not for the other. Now look at the
following example (output attached):
\version "2.19.3"
<< \new Staff <<
\new Voice = "one" { \voiceOne c'4 c' c'8 c' c'4 }
\new Voice = "two" { \voiceTwo s4 s c' s }
\new Lyrics \lyricsto "one" {
foo \set associatedVoice = "two"
foo \set associatedVoice = "one"
bar
bar
}
The associated voice has to be set one syllable early, which I did,
only the lyrics "come back" to voice "one" one note early: it should
be for the last quaver and not for the second crotchet. It seems to me
that the roots of this problem lie very deep. An optimal fix would of
course be to make the effect of \set associatedVoice enter immediately
rather than one syllable later, but this is probably far away.
Can anyone think of a workaround?
Just keep the same associated voice throughout for the variant with most
syllables, flipping it between \voiceOne, \voiceTwo and \oneVoice as
needed.
I lean towards not using \lyricsto here but just placing the durations
in the lyrics. That makes the timing unproblematic and robust against
slurs/beams/whatever, saving a lot of fiddling.
Maybe a cute LSR entry would be a Lyric_time_translator which is placed
in a lyricsto-governed context and then writes out the source file with
proper durations in all its lyrics so that you can then use this and
drop the lyricsto.
Then you need to get only one stanza synchronized at a time...
Associated voices still are good for not just aligning on the time but
note values.
In case someone might ask why this is necessary, I attach what I
already have of the entire lied also. The \makeOctaves function is
from LSR 445 and I added
it to scm/music-functions.scm or a similar one in order to always have
it at hand.
Non-compilable examples are a nuisance.
Sorry for that.
You can just add
makeOctaves =
#(define-music-function (parser location oct mus) (integer? ly:music?)
(make-relative (mus) mus
#{ << \transpose c' $(ly:make-pitch oct 0 0) $mus $mus >> #}))
Excellent! This seems to be just as powerful as LSR 445 while being far
less complicated… or do I overlook something?
to the code. As opposed to LSR445, it should work fine with chords and
also absolute music.
And many thanks for the explanations.
Yours, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Replacing glyph visuals with arbitrary unicode character
2014-03-23 17:10 GMT+01:00 Joey Di Nardo : > Works beautifully for clefs Pierre; how would I adjust the code to alter > *only* the 32nd and 64th rests? > I ask because neomensural notation uses the classical rests for 32nd and > 64th notes, and I'd like to replace them with unicode characters I've found. > > Hi Joey, 'Seems I've forgot to answer ... You can adapt this snippet : http://lsr.di.unimi.it/LSR/Item?id=548 to reach what you want. HTH ~Pierre ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extra Staff length
Hi Conor,
On Thu, Mar 27, 2014 at 10:14 PM, Conor Cook wrote:
>
> On Mar 27, 2014, at 10:15 AM, David Nalesnik
> wrote:
> > You might move the text to where you want it by first placing it where
> the staff length is unaffected, then overriding TextScript.extra-offset.
> This leaves the layout unchanged.
>
> I’m not entirely sure I follow (I’ve only been using this since February,
> which also explains the embarrassing file structure).
>
>
See attached. I took out the \halign and added
\once \override TextScript.extra-offset = #'(4 . 0)
The only drawback with this method is that extra-offset moves things
blindly without regard for collisions with other objects, so it could be an
annoyance using it before other details of the layout are fixed.
You can read more about it here:
http://www.lilypond.org/doc/v2.16/Documentation/learning/moving-objects
Hope this helps,
David
\version "2.18.2"
roundP = \markup {
\halign #-0.25 \lower #4 \concat { \bold { \italic ( }
\dynamic p \bold { \italic ) } } }
mezzoP = \markup {
\halign #-0.3 \lower #4 \dynamic mp
}
mezzoF = \markup {
\halign #0 \lower #4 \dynamic mf
}
forte = \markup {
\halign #0 \lower #4 \dynamic f
}
tenuto = \markup { \italic ten. }
tenutoH = \markup { \raise #2.5 \italic ten. }
\score {
\midi {}
\layout {
indent = #0
%line-width = #120
ragged-right = ##f
}
\new PianoStaff \with {
\override StaffGrouper.staffgroup-staff-spacing.basic-distance = #20
} {
<<
\new Staff \relative c' {
\key g \major
\set Score.currentBarNumber = #8
\bar ""
{4-._\roundP -. -.
<<
{ b'8( a | g2) }
\\
{ c,4 | r4 }
>>
d4_\mezzoF d | ^\(\arpeggio \< \arpeggio |
\arpeggio
\once \override TextScript.extra-offset = #'(4 . 0)
\!\)_\markup { \lower #4 { \italic etc... } }\arpeggio
}
}
\new Staff \relative c {
\clef "bass"
\key g \major
<<
{ r4 g'!2( fis4) | r d d d | r2 d4 r | r fis }
\\
{ a,2( d |
<<
{ g,) r | \arpeggio g' | }
\new PianoStaff {
<<
\new Staff \with {
\remove "Time_signature_engraver"
}
\relative c' {
\key g \major
<<
{ g'2 }
\\
{ r4 }
>>
4^\tenuto(_\mezzoF\arpeggio |
\override TextScript.avoid-slur = #'inside
\override TextScript.outside-staff-priority = ##f
\>\arpeggio ^\tenutoH\arpeggio \arpeggio |
\! \once \override TextScript.extra-offset = #'(4 . 0) )_\markup { \lower #4 { \italic etc... } }
}
\new Staff \with {
\consists "Span_arpeggio_engraver"
\remove "Time_signature_engraver"
}
\relative c {
\clef "bass"
\key g \major
\set Staff.connectArpeggios = ##t
<<
{ r4 d d\arpeggio e | r2 r4 \arpeggio | r4 }
\\
{ g,2 g\arpeggio (\arpeggio \arpeggio | )\arpeggio }
>>
}
>>
}
>>
}
>>
}
>>
}
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aligning parenthesized chords
Perfect! Thank you, Pierre!
Mark
On Fri, Mar 28, 2014 at 4:53 AM, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> wrote:
> 2014-03-28 8:07 GMT+01:00 Mark Mathias :
>
> May I please have some help aligning the parenthesized chords so that the
>> letter names align vertically with the unparenthesized chords below them?
>> Thank you!
>> Mark
>>
>>
>
> #(define (parenthesis-ignatzek-chord-names in-pitches bass inversion
> context)
> (markup #:hspace -1 #:line ("(" (ignatzek-chord-names in-pitches bass
> inversion context) ")")))
>
>
> HTH,
>
> ~Pierre
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: acciaccatura before barline
On Thu, Mar 27, 2014 at 1:22 PM, David Kastrup wrote: > Urs Liska writes: > > > Hi all, > > > > consider the attached image. > > Apart from the problematic slur which I don't want to deal with right > > now, how can I typeset the acciaccatura _before_ the barline. > > > > I was thinking of hacking something with \afterGrace, but that's not > > what it is. > > Well, here is a bit of a cheat: > > -- > David Kastrup Wonderful, David! Thanks so much. I've been trying to get \afterGrace to work nicely on acciaccaturas before a bar line for a long time, but \afterGrace always leaves too much space before the barline. Your cheat is perfect. Thanks again, Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aligning parenthesized chords
2014-03-28 8:07 GMT+01:00 Mark Mathias :
> May I please have some help aligning the parenthesized chords so that the
> letter names align vertically with the unparenthesized chords below them?
> Thank you!
> Mark
>
>
#(define (parenthesis-ignatzek-chord-names in-pitches bass inversion
context)
(markup #:hspace -1 #:line ("(" (ignatzek-chord-names in-pitches bass
inversion context) ")")))
HTH,
~Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Aligning parenthesized chords
May I please have some help aligning the parenthesized chords so that the
letter names align vertically with the unparenthesized chords below them?
Thank you!
Mark
\version "2.18.0"
#(define (parenthesis-ignatzek-chord-names in-pitches bass inversion
context)
(markup #:line ("(" (ignatzek-chord-names in-pitches bass inversion
context) ")")))
chordNames = \chordmode { c1 g }
chordNamesCapo = \chordmode {
\transpose c' a {
\set chordNameFunction = #parenthesis-ignatzek-chord-names
c1 g
}
}
chordsPart = \new ChordNames \chordNames
chordsPartCapo = \new ChordNames \chordNamesCapo
soprano = \relative c' { c4 c c c b b b b }
\score {
<<
\chordsPartCapo
\chordsPart
\soprano
>>
\layout { }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
