Re: Slurs in volta 2 and bend
The slur in Volta 2 can be achieved by adding \repeattie after the note. For the bend, you will need a hidden voice. 在 16/09/2014，7:01 pm，Marco Bagolin bagolin.ma...@gmail.com 写道： Hello, I can't find the way to reproduce the examples attached (the slur in volta 2 and the bend). I tried to search in the site and in the manuals but I did not find a solution. Someone can help me ? Thank you in advance. MB slurvolta.PNG bend.PNG ___ 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 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Can NoteNames in higher octaves be changed?
I'm not top posting.
David,
How I wish I could understand how you do what you do! It all looks like
magic to me. Is there a place that shows how to use all these functions?
I tried to adapt what you showed to my system. So far, all attempts have
resulted in syntax error or other error, mostly because I do not know
what the commands actually do.
Here is what I have - it prints the NoteNames as S R G M P D and N as
defined in the newnames variable. For the range of notes from low G to
high G, it prints P D N S R G M P D N S R G M P. What I would like to
see printed is: p d n S R G M P D N s̊ r̊ g̊ m̊ p̊ [where the
higher octave notes have a dot on top].
Jay
\version 2.18.2
music = {g2 a b c d e f g a b c d e f g}
newnames =
#`((c . S)
(d . R)
(e . G)
(f . M)
(g . P)
(a . D)
(b . N))
myNoteNames =
#(lambda (grob)
(let* (
;; bindings
(default-name (ly:grob-property grob 'text))
(new-name (assoc-get default-name newnames))
)
;; body
(ly:grob-set-property! grob 'text new-name)
(ly:text-interface::print grob)
)
)
\new Staff {
\relative c' \music
\context NoteNames {
\set printOctaveNames = ##t
\override NoteName.stencil = #myNoteNames
\music
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Can NoteNames in higher octaves be changed?
Hi Jay,
On Tue, Sep 16, 2014 at 6:52 AM, Jay Vara j...@diljun.com wrote:
I'm not top posting.
David,
How I wish I could understand how you do what you do! It all looks like
magic to me. Is there a place that shows how to use all these functions?
There is a list of Scheme functions (
http://lilypond.org/doc/v2.18/Documentation/notation/scheme-functions), the
Extending manual, and of course the Internals Reference. But there are a
lot of functions which you can only know about by looking through the code
base. scm/lily-library.scm has a number of useful Scheme functions, for
example.
As far as GUILE, I've gotten a lot from the 1.8 documentation (
http://www.gnu.org/software/guile/docs/docs-1.8/guile-ref/index.html).
Unfortunately, the LilyPond specific stuff is a bit harder to discover!
(And the documentation is certainly no tutorial, as you'll see from the
list of Scheme functions.)
Since you're new to the program, I hope you're not getting the impression
that it's impossibly arcane. Well, it can be, but for the vast amount of
typical usage, LilyPond is straightforward to use and admirably documented.
Questions like yours are great because they show areas where the program
might be improved. Easy change of NoteName pitches (whether it be for a
custom system, or scientific pitch notation--C4 and the like) would be a
useful addition, I think.
I tried to adapt what you showed to my system. So far, all attempts have
resulted in syntax error or other error, mostly because I do not know
what the commands actually do.
Here is what I have - it prints the NoteNames as S R G M P D and N as
defined in the newnames variable. For the range of notes from low G to
high G, it prints P D N S R G M P D N S R G M P. What I would like to
see printed is: p d n S R G M P D N s̊ r̊ g̊ m̊ p̊ [where the
higher octave notes have a dot on top].
Jay
\version 2.18.2
music = {g2 a b c d e f g a b c d e f g}
newnames =
#`((c . S)
(d . R)
(e . G)
(f . M)
(g . P)
(a . D)
(b . N))
myNoteNames =
#(lambda (grob)
(let* (
;; bindings
(default-name (ly:grob-property grob 'text))
(new-name (assoc-get default-name newnames))
)
;; body
(ly:grob-set-property! grob 'text new-name)
(ly:text-interface::print grob)
)
)
\new Staff {
\relative c' \music
\context NoteNames {
\set printOctaveNames = ##t
\override NoteName.stencil = #myNoteNames
Oh, such a simple and easy-to-miss problem! (It took me a while.) You
need another \relative c' before \music. (You could attach it to your
variable above, so you aren't liable to forget.)
\music
}
}
All you'd have to do to make your function work is add the
note-names-with-octaves to your newnames alist. If you're just dealing
with the limited range in your example, a simple extension seems reasonable.
Hope this helps!
David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Can NoteNames in higher octaves be changed?
Jay, One more thing. For chords, the note name text would be a single string a' cis' e'. Don't know if you need that extra ability, but that would of course require some string manipulation. --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Can NoteNames in higher octaves be changed?
David, That worked. I have now defined a 2.5 octave range that covers most of my music. I will try to learn the scm slowly - I should say it is a bit confusing with all the different levels of parenthesis. Thanks, Jay ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Can NoteNames in higher octaves be changed?
Jay, On Tue, Sep 16, 2014 at 11:03 AM, Jay Vara j...@diljun.com wrote: David, That worked. I have now defined a 2.5 octave range that covers most of my music. Nice to hear! I will try to learn the scm slowly - I should say it is a bit confusing with all the different levels of parenthesis. https://lists.gnu.org/mailman/listinfo/lilypond-user I'd be nowhere without a text editor with syntax highlighting. Frescobaldi makes it much easier. --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
How do you tell Lilypond not to jump strings when sliding?
I'm not top posting.
When you give lilypond a piece of music, it automatically generates the
music and guitar tabs for it. When there are glissandos in the music,
lilypod does show the slides automatically.
However, many times, it shows slides from one string to another, rather
than choosing frets on the same string. Is there a way to force it to
restrict slides to a single string?
The following code shows an example. The second measure shows the
automatically generated lilypod slides that go from the first string to
the second string. (This can not be played) In the third measure, I have
manually forced the notes to all be on the second string. I need a way
to do this automatically.
Also, I tried to avoid open strings by setting restrainOpenStrings to
true. It does not seem to work.
\version 2.18.2
musica = \relative c' {e2 e}
musicb = \relative c' {e2 e8\glissando (d16\glissando e16)}
musicc = \relative c' {e2 e8\2\glissando (d16\glissando e16\2)}
\score { \new StaffGroup
\new Staff {\musica \musicb \musicc}
\new TabStaff {
\set TabStaff.restrainOpenStrings = ##t
\tabFullNotation
\musica \musicb \musicc}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How do you tell Lilypond not to jump strings when sliding?
Il 16/set/2014 18:12 Jay Vara j...@diljun.com ha scritto: I'm not top posting. When you give lilypond a piece of music, it automatically generates the music and guitar tabs for it. When there are glissandos in the music, lilypod does show the slides automatically. However, many times, it shows slides from one string to another, rather than choosing frets on the same string. Is there a way to force it to restrict slides to a single string? AFAIK you must specify the string number either with the slash or with minimumFret. Same for slurs/hammer-on pull-off. The following code shows an example. The second measure shows the automatically generated lilypod slides that go from the first string to the second string. (This can not be played) In the third measure, I have manually forced the notes to all be on the second string. I need a way to do this automatically. Also, I tried to avoid open strings by setting restrainOpenStrings to true. It does not seem to work. Its use makes sense only when minimumFret is set ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How do you tell Lilypond not to jump strings when sliding?
Frederico, Yay! I added \set TabStaff.minimumFret = #1 and now it works! Who would have thought that minimumFret is related to restrainOpenStrings! Thanks, Jay ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
how to force shortened staff lines?
i want to generate a landscape score, but one where the staff lines
extend some percentage of the printable area - let's say, 70%. Leaving
30% width blank, on the right, for hand-written annotations (upon printout).
I've tried:
line-width = 70%
,
line-width = 7.0\in
, and
right-margin = 3.0\in
but all that is being ignored. At least in the \paper { } block.
Help?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How do you tell Lilypond not to jump strings when sliding?
I'm not top posting.
I spoke too soon. Setting the minimumFret does fix the
restrainOpenStrings issue, but not the jumping strings during slide
issue as seen in the code below.
There should be some way to tell lilypond not to jump strings during
slides.
\version 2.18.2
musica = \relative c'' {g8\glissando e8 g8\glissando (e16\glissando
g16)}
musicb = \relative c' {e2 e8\glissando (d16\glissando e16)}
musicc = \relative c' {e2 e8\2\glissando (d16\glissando e16\2)}
\score { \new StaffGroup
\new Staff {\musica \musicb \musicc \musica \musicb \musicc}
\new TabStaff {
\set TabStaff.restrainOpenStrings = ##t
\tabFullNotation
\musica \musicb \musicc
% setting minimumFret to a number, say #1, prevents the
jumping strings during sliding for the second measure (as seen in the
fourth measure) but
% introduces the jump problem for the 1st measure (as seen in
the 3rd measure)
\set TabStaff.minimumFret = #1
\musica \musicb \musicc}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Slurs in volta 2 and bend
Am 16.09.2014 um 09:03 schrieb guoguocuozuoduo:
The slur in Volta 2 can be achieved by adding \repeattie after the note.
For the bend, you will need a hidden voice.
I don't know whether it is the best way to achieve this, but the output
of this comes pretty close:
{
b'1\repeatTie
{ b'4\rest s2. } \\ {
\oneVoice \hideNotes e'4( \unHideNotes f'2.^^\fz ) }
b'1\bendAfter #5
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How do you tell Lilypond not to jump strings when sliding?
On 16.09.2014, at 20:42, pls p.l.schm...@gmx.de wrote:
Jay,
there is actually a way to achieve what you want. I am not sure if it’s
documented: pretend that your single notes are chords, put them in angled
brackets and use the command for string numbers after the closing brackets,
like so:
musicb = \relative c' {e2 e8\2\glissando (d16\glissando e16\2)}
This tells LilyPond to use the right strings in tablature and the string
numbers don’t appear in the score.
hth
patrick
On 16.09.2014, at 19:09, Jay Vara j...@diljun.com wrote:
I'm not top posting.
I spoke too soon. Setting the minimumFret does fix the
restrainOpenStrings issue, but not the jumping strings during slide
issue as seen in the code below.
There should be some way to tell lilypond not to jump strings during
slides.
\version 2.18.2
musica = \relative c'' {g8\glissando e8 g8\glissando (e16\glissando
g16)}
musicb = \relative c' {e2 e8\glissando (d16\glissando e16)}
musicc = \relative c' {e2 e8\2\glissando (d16\glissando e16\2)}
\score { \new StaffGroup
\new Staff {\musica \musicb \musicc \musica \musicb \musicc}
\new TabStaff {
\set TabStaff.restrainOpenStrings = ##t
\tabFullNotation
\musica \musicb \musicc
% setting minimumFret to a number, say #1, prevents the
jumping strings during sliding for the second measure (as seen in the
fourth measure) but
% introduces the jump problem for the 1st measure (as seen in
the 3rd measure)
\set TabStaff.minimumFret = #1
\musica \musicb \musicc}
}
___
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
Can not get '\override Score.BarNumber.break-visibility' to work
I'm trying to get bar numbers on every second bar get syntax error from
stuff straight out of the documentation.
/tmp/frescobaldi-qhLT9N/tmpOW4D8u/Le_vieux_chalet.ly:27:29: error: syntax
error, unexpected '.', expecting SCM_FUNCTION or SCM_IDENTIFIER or
SCM_TOKEN
\override Score.BarNumber
.break-visibility = ##(#t #t #t)
Unfortunately I have absolutely no idea where to look for a solution. I'm
sure it is something very basic.
Here the entire file:
\version 2.16.2
\header {
title = Le Vieux Chalet
composer = Joseph Bovet
poet = Joseph Bovet
tagline = \markup {
Engraved at
\simple #(strftime %Y-%m-%d (localtime (current-time)))
with \with-url #http://lilypond.org/;
\line { LilyPond \simple #(lilypond-version) (http://lilypond.org/) }
% from \sourcefilename
}
}
\score {
\new Staff = Tenor
\set Staff.midiInstrument = #acoustic grand
\set Staff.instrumentName = Tenor
\time 3/4 \key g \major
\partial 4
\relative c'
\new Voice = Tenor 1 {
\override Score.BarNumber.break-visibility = ##(#t #t #t)
% \set Score.currentBarNumber = #21
% % Permit first bar number to be printed
% \bar
\set Score.barNumberVisibility = #(every-nth-bar-number-visible 2)
\voiceOne
% Tenor 1
d4
\repeat volta 2 { d'4. c8 b8. c16 b4 a d, d'8. c16 b4 a4 }
\alternative { { g2 d4 } { g2 g4 } }
a4. b8 g a | b4. c8 a b | c4. d8 b c | d2 g,4 |
e'4. d8 c b | a8.( b16) a4 a | d8. c16 b4 a | g2
}
\addlyrics {
La | haut sur la mon -- | ta -- gne l'é -- | tait un vieux cha -- |
let. La | let. Murs |
blancs, toit de bar -- | deaux, de -- vant la | porte un veux bou -- |
leau. La |
haut sur la mon -- | tag -- ne l'é -- | tait un vieux cha -- | let.
}
\new Voice = Tenor 2 {
\voiceTwo
% Tenor 2
d4 b'4. a8 g8. a16 g4 fis d g8. e16 g4 fis4
g2 d4 g2 g4
fis4. d8 e fis | g4. e8 fis g | a4. fis8 g a |
g4 fis g | c4. b8 a g | fis8. g16 fis4 fis | g8. e16 d4 c | b2
}
\new Staff = Bass
\set Staff.instrumentName = Bass/Bar
\set Staff.midiInstrument = #acoustic bass
\clef bass \key g \major
\relative c
\new Voice = Bariton {
% Bariton
\set Voice.midiInstrument = #glockenspiel
\voiceThree
d4 | d4. d8 d8. e16 | d4 d d | d8. e16 e4 d8 c |
b2 d4 | b2 b8 d8 |
d4. d8 d d | d4. d8 d d | d4. d8 d d | d2 g4 |
g4. fis8 e d | e4 e d | d8. e16 d4 d8 c | b2
}
\relative c
\new Voice = Bass {
% Bass
\voiceFour
d4 | g,4. g8 g8. c16 | d4 d,4 d'8 c | b8. c16 e4 d,4 |
g2 d'4 | g,2 g8 b8 |
d4. d8 d d | d4. d8 d d | d4. d8 d d | g,2 g'4 |
c,4. gis8 a b | c4 c c | b8. c16 d4 d,4 g2
}
\layout {}
\midi {
\context {
\Score
tempoWholesPerMinute = #(ly:make-moment 270 8)
}
}
}
--
Markus Baertschi, Bas du Rossé 16, CH-1163, Etoy, Switzerland
mar...@markus.org, ++41 (79) 403 1186 (mobile)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How do you tell Lilypond not to jump strings when sliding?
- Original Message -
From: Jay Vara j...@diljun.com
To: lilypond-user@gnu.org
Sent: Tuesday, September 16, 2014 6:09 PM
Subject: Re: How do you tell Lilypond not to jump strings when sliding?
I'm not top posting.
I spoke too soon. Setting the minimumFret does fix the
restrainOpenStrings issue, but not the jumping strings during slide
issue as seen in the code below.
There should be some way to tell lilypond not to jump strings during
slides.
\version 2.18.2
musica = \relative c'' {g8\glissando e8 g8\glissando (e16\glissando
g16)}
musicb = \relative c' {e2 e8\glissando (d16\glissando e16)}
musicc = \relative c' {e2 e8\2\glissando (d16\glissando e16\2)}
\score { \new StaffGroup
\new Staff {\musica \musicb \musicc \musica \musicb \musicc}
\new TabStaff {
\set TabStaff.restrainOpenStrings = ##t
\tabFullNotation
\musica \musicb \musicc
% setting minimumFret to a number, say #1, prevents the
jumping strings during sliding for the second measure (as seen in the
fourth measure) but
% introduces the jump problem for the 1st measure (as seen in
the 3rd measure)
\set TabStaff.minimumFret = #1
\musica \musicb \musicc}
}
Jay,
You'll need to indicate string numbers. They can be hidden with \omit
StringNumber if you do not want the circled numbers to appear.
Btw, guitar music is usually written an octave higher than it sounds. You
should use \clef treble_8 in the \new Staff section.
Hope that helps.
Phil.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Can not get '\override Score.BarNumber.break-visibility' to work
Hi Markus, I'm trying to get bar numbers on every second bar get syntax error from stuff straight out of the documentation. /tmp/frescobaldi-qhLT9N/tmpOW4D8u/Le_vieux_chalet.ly:27:29: error: syntax error, unexpected '.', expecting SCM_FUNCTION or SCM_IDENTIFIER or SCM_TOKEN \override Score.BarNumber .break-visibility = ##(#t #t #t) Unfortunately I have absolutely no idea where to look for a solution. I'm sure it is something very basic. Here the entire file: \version “2.16.2 I believe you’re using too old a version of Lilypond for that syntax. Try instead \override Score.BarNumber #'break-visibility = ##(#t #t #t) Hope this helps! Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Can not get '\override Score.BarNumber.break-visibility' to work
Your problem comes from the fact that you use a syntax for a newer
version of LilyPond.
I suggest that you either update to LilyPond 2.18.2 (preferable) or have
a look at the documentation for 2.16 at
http://lilypond.org/doc/v2.16/Documentation/web/manuals
The dot-notation was introduced in 2.18, previously you had to write
\override Score.BarNumber #'break-visibility ...
(although I don't know if there have been other changes in that
break-visibility stuff as well.)
HTH
Urs
Am 16.09.2014 21:08, schrieb Markus Baertschi:
I'm trying to get bar numbers on every second bar get syntax error
from stuff straight out of the documentation.
/tmp/frescobaldi-qhLT9N/tmpOW4D8u/Le_vieux_chalet.ly:27:29: error:
syntax error, unexpected '.', expecting SCM_FUNCTION or SCM_IDENTIFIER
or SCM_TOKEN
\override Score.BarNumber
.break-visibility = ##(#t #t #t)
Unfortunately I have absolutely no idea where to look for a solution.
I'm sure it is something very basic.
Here the entire file:
\version 2.16.2
\header {
title = Le Vieux Chalet
composer = Joseph Bovet
poet = Joseph Bovet
tagline = \markup {
Engraved at
\simple #(strftime %Y-%m-%d (localtime (current-time)))
with \with-url #http://lilypond.org/;
\line { LilyPond \simple #(lilypond-version) (http://lilypond.org/) }
% from \sourcefilename
}
}
\score {
\new Staff = Tenor
\set Staff.midiInstrument = #acoustic grand
\set Staff.instrumentName = Tenor
\time 3/4 \key g \major
\partial 4
\relative c'
\new Voice = Tenor 1 {
\override Score.BarNumber.break-visibility = ##(#t #t #t)
% \set Score.currentBarNumber = #21
% % Permit first bar number to be printed
% \bar
\set Score.barNumberVisibility = #(every-nth-bar-number-visible 2)
\voiceOne
% Tenor 1
d4
\repeat volta 2 { d'4. c8 b8. c16 b4 a d, d'8. c16 b4 a4 }
\alternative { { g2 d4 } { g2 g4 } }
a4. b8 g a | b4. c8 a b | c4. d8 b c | d2 g,4 |
e'4. d8 c b | a8.( b16) a4 a | d8. c16 b4 a | g2
}
\addlyrics {
La | haut sur la mon -- | ta -- gne l'é -- | tait un vieux cha -- |
let. La | let. Murs |
blancs, toit de bar -- | deaux, de -- vant la | porte un veux bou -- |
leau. La |
haut sur la mon -- | tag -- ne l'é -- | tait un vieux cha -- | let.
}
\new Voice = Tenor 2 {
\voiceTwo
% Tenor 2
d4 b'4. a8 g8. a16 g4 fis d g8. e16 g4 fis4
g2 d4 g2 g4
fis4. d8 e fis | g4. e8 fis g | a4. fis8 g a |
g4 fis g | c4. b8 a g | fis8. g16 fis4 fis | g8. e16 d4 c | b2
}
\new Staff = Bass
\set Staff.instrumentName = Bass/Bar
\set Staff.midiInstrument = #acoustic bass
\clef bass \key g \major
\relative c
\new Voice = Bariton {
% Bariton
\set Voice.midiInstrument = #glockenspiel
\voiceThree
d4 | d4. d8 d8. e16 | d4 d d | d8. e16 e4 d8 c |
b2 d4 | b2 b8 d8 |
d4. d8 d d | d4. d8 d d | d4. d8 d d | d2 g4 |
g4. fis8 e d | e4 e d | d8. e16 d4 d8 c | b2
}
\relative c
\new Voice = Bass {
% Bass
\voiceFour
d4 | g,4. g8 g8. c16 | d4 d,4 d'8 c | b8. c16 e4 d,4 |
g2 d'4 | g,2 g8 b8 |
d4. d8 d d | d4. d8 d d | d4. d8 d d | g,2 g'4 |
c,4. gis8 a b | c4 c c | b8. c16 d4 d,4 g2
}
\layout {}
\midi {
\context {
\Score
tempoWholesPerMinute = #(ly:make-moment 270 8)
}
}
}
--
Markus Baertschi, Bas du Rossé 16, CH-1163, Etoy, Switzerland
mar...@markus.org mailto:mar...@markus.org, ++41 (79) 403 1186 (mobile)
___
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: Can not get '\override Score.BarNumber.break-visibility' to work
Thanks Gentlemen,
The 'old' version I'm using is probably the culprit. The syntax you guys
suggested works fine.
I'm using Ubuntu. It looks like the version in the standard Ubuntu
repositories is still 2.16.
I'm starting with it now and playing with music for my mens choir.
Any important things I'll be missing out on 2.16 ?
There is a PPA so I could upgrade quite easily, if necessary,
Thanks Markus
On Tue, Sep 16, 2014 at 9:13 PM, Urs Liska u...@openlilylib.org wrote:
Your problem comes from the fact that you use a syntax for a newer
version of LilyPond.
I suggest that you either update to LilyPond 2.18.2 (preferable) or have a
look at the documentation for 2.16 at
http://lilypond.org/doc/v2.16/Documentation/web/manuals
The dot-notation was introduced in 2.18, previously you had to write
\override Score.BarNumber #'break-visibility ...
(although I don't know if there have been other changes in that
break-visibility stuff as well.)
HTH
Urs
Am 16.09.2014 21:08, schrieb Markus Baertschi:
I'm trying to get bar numbers on every second bar get syntax error from
stuff straight out of the documentation.
/tmp/frescobaldi-qhLT9N/tmpOW4D8u/Le_vieux_chalet.ly:27:29: error: syntax
error, unexpected '.', expecting SCM_FUNCTION or SCM_IDENTIFIER or
SCM_TOKEN
\override Score.BarNumber
.break-visibility = ##(#t #t #t)
Unfortunately I have absolutely no idea where to look for a solution. I'm
sure it is something very basic.
Here the entire file:
\version 2.16.2
\header {
title = Le Vieux Chalet
composer = Joseph Bovet
poet = Joseph Bovet
tagline = \markup {
Engraved at
\simple #(strftime %Y-%m-%d (localtime (current-time)))
with \with-url #http://lilypond.org/;
\line { LilyPond \simple #(lilypond-version) (http://lilypond.org/) }
% from \sourcefilename
}
}
\score {
\new Staff = Tenor
\set Staff.midiInstrument = #acoustic grand
\set Staff.instrumentName = Tenor
\time 3/4 \key g \major
\partial 4
\relative c'
\new Voice = Tenor 1 {
\override Score.BarNumber.break-visibility = ##(#t #t #t)
% \set Score.currentBarNumber = #21
% % Permit first bar number to be printed
% \bar
\set Score.barNumberVisibility = #(every-nth-bar-number-visible 2)
\voiceOne
% Tenor 1
d4
\repeat volta 2 { d'4. c8 b8. c16 b4 a d, d'8. c16 b4 a4 }
\alternative { { g2 d4 } { g2 g4 } }
a4. b8 g a | b4. c8 a b | c4. d8 b c | d2 g,4 |
e'4. d8 c b | a8.( b16) a4 a | d8. c16 b4 a | g2
}
\addlyrics {
La | haut sur la mon -- | ta -- gne l'é -- | tait un vieux cha -- |
let. La | let. Murs |
blancs, toit de bar -- | deaux, de -- vant la | porte un veux bou -- |
leau. La |
haut sur la mon -- | tag -- ne l'é -- | tait un vieux cha -- | let.
}
\new Voice = Tenor 2 {
\voiceTwo
% Tenor 2
d4 b'4. a8 g8. a16 g4 fis d g8. e16 g4 fis4
g2 d4 g2 g4
fis4. d8 e fis | g4. e8 fis g | a4. fis8 g a |
g4 fis g | c4. b8 a g | fis8. g16 fis4 fis | g8. e16 d4 c | b2
}
\new Staff = Bass
\set Staff.instrumentName = Bass/Bar
\set Staff.midiInstrument = #acoustic bass
\clef bass \key g \major
\relative c
\new Voice = Bariton {
% Bariton
\set Voice.midiInstrument = #glockenspiel
\voiceThree
d4 | d4. d8 d8. e16 | d4 d d | d8. e16 e4 d8 c |
b2 d4 | b2 b8 d8 |
d4. d8 d d | d4. d8 d d | d4. d8 d d | d2 g4 |
g4. fis8 e d | e4 e d | d8. e16 d4 d8 c | b2
}
\relative c
\new Voice = Bass {
% Bass
\voiceFour
d4 | g,4. g8 g8. c16 | d4 d,4 d'8 c | b8. c16 e4 d,4 |
g2 d'4 | g,2 g8 b8 |
d4. d8 d d | d4. d8 d d | d4. d8 d d | g,2 g'4 |
c,4. gis8 a b | c4 c c | b8. c16 d4 d,4 g2
}
\layout {}
\midi {
\context {
\Score
tempoWholesPerMinute = #(ly:make-moment 270 8)
}
}
}
--
Markus Baertschi, Bas du Rossé 16, CH-1163, Etoy, Switzerland
mar...@markus.org, ++41 (79) 403 1186 (mobile)
___
lilypond-user mailing
listlilypond-user@gnu.orghttps://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
--
*Markus Baertschi*, Bas du Rossé 16, CH-1163, Etoy, Switzerland
mar...@markus.org, ++41 (79) 403 1186 (mobile)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Can not get '\override Score.BarNumber.break-visibility' to work
There is a PPA so I could upgrade quite easily, if necessary,
Even easier and much better is to just download it from Lilypond directly.
It is packaged in such a way as to make installation and upgrading on
Ubuntu (and all Linux distros) super duper easy. This way you can have the
latest versions without relying on a package maintainer to keep up to date.
On Tue, Sep 16, 2014 at 12:23 PM, Markus Baertschi mar...@markus.org
wrote:
Thanks Gentlemen,
The 'old' version I'm using is probably the culprit. The syntax you guys
suggested works fine.
I'm using Ubuntu. It looks like the version in the standard Ubuntu
repositories is still 2.16.
I'm starting with it now and playing with music for my mens choir.
Any important things I'll be missing out on 2.16 ?
There is a PPA so I could upgrade quite easily, if necessary,
Thanks Markus
On Tue, Sep 16, 2014 at 9:13 PM, Urs Liska u...@openlilylib.org wrote:
Your problem comes from the fact that you use a syntax for a newer
version of LilyPond.
I suggest that you either update to LilyPond 2.18.2 (preferable) or have
a look at the documentation for 2.16 at
http://lilypond.org/doc/v2.16/Documentation/web/manuals
The dot-notation was introduced in 2.18, previously you had to write
\override Score.BarNumber #'break-visibility ...
(although I don't know if there have been other changes in that
break-visibility stuff as well.)
HTH
Urs
Am 16.09.2014 21:08, schrieb Markus Baertschi:
I'm trying to get bar numbers on every second bar get syntax error from
stuff straight out of the documentation.
/tmp/frescobaldi-qhLT9N/tmpOW4D8u/Le_vieux_chalet.ly:27:29: error: syntax
error, unexpected '.', expecting SCM_FUNCTION or SCM_IDENTIFIER or
SCM_TOKEN
\override Score.BarNumber
.break-visibility = ##(#t #t #t)
Unfortunately I have absolutely no idea where to look for a solution. I'm
sure it is something very basic.
Here the entire file:
\version 2.16.2
\header {
title = Le Vieux Chalet
composer = Joseph Bovet
poet = Joseph Bovet
tagline = \markup {
Engraved at
\simple #(strftime %Y-%m-%d (localtime (current-time)))
with \with-url #http://lilypond.org/;
\line { LilyPond \simple #(lilypond-version) (http://lilypond.org/) }
% from \sourcefilename
}
}
\score {
\new Staff = Tenor
\set Staff.midiInstrument = #acoustic grand
\set Staff.instrumentName = Tenor
\time 3/4 \key g \major
\partial 4
\relative c'
\new Voice = Tenor 1 {
\override Score.BarNumber.break-visibility = ##(#t #t #t)
% \set Score.currentBarNumber = #21
% % Permit first bar number to be printed
% \bar
\set Score.barNumberVisibility = #(every-nth-bar-number-visible 2)
\voiceOne
% Tenor 1
d4
\repeat volta 2 { d'4. c8 b8. c16 b4 a d, d'8. c16 b4 a4 }
\alternative { { g2 d4 } { g2 g4 } }
a4. b8 g a | b4. c8 a b | c4. d8 b c | d2 g,4 |
e'4. d8 c b | a8.( b16) a4 a | d8. c16 b4 a | g2
}
\addlyrics {
La | haut sur la mon -- | ta -- gne l'é -- | tait un vieux cha -- |
let. La | let. Murs |
blancs, toit de bar -- | deaux, de -- vant la | porte un veux bou -- |
leau. La |
haut sur la mon -- | tag -- ne l'é -- | tait un vieux cha -- | let.
}
\new Voice = Tenor 2 {
\voiceTwo
% Tenor 2
d4 b'4. a8 g8. a16 g4 fis d g8. e16 g4 fis4
g2 d4 g2 g4
fis4. d8 e fis | g4. e8 fis g | a4. fis8 g a |
g4 fis g | c4. b8 a g | fis8. g16 fis4 fis | g8. e16 d4 c | b2
}
\new Staff = Bass
\set Staff.instrumentName = Bass/Bar
\set Staff.midiInstrument = #acoustic bass
\clef bass \key g \major
\relative c
\new Voice = Bariton {
% Bariton
\set Voice.midiInstrument = #glockenspiel
\voiceThree
d4 | d4. d8 d8. e16 | d4 d d | d8. e16 e4 d8 c |
b2 d4 | b2 b8 d8 |
d4. d8 d d | d4. d8 d d | d4. d8 d d | d2 g4 |
g4. fis8 e d | e4 e d | d8. e16 d4 d8 c | b2
}
\relative c
\new Voice = Bass {
% Bass
\voiceFour
d4 | g,4. g8 g8. c16 | d4 d,4 d'8 c | b8. c16 e4 d,4 |
g2 d'4 | g,2 g8 b8 |
d4. d8 d d | d4. d8 d d | d4. d8 d d | g,2 g'4 |
c,4. gis8 a b | c4 c c | b8. c16 d4 d,4 g2
}
\layout {}
\midi {
\context {
\Score
tempoWholesPerMinute = #(ly:make-moment 270 8)
}
}
}
--
Markus Baertschi, Bas du Rossé 16, CH-1163, Etoy, Switzerland
mar...@markus.org, ++41 (79) 403 1186 (mobile)
___
lilypond-user mailing
listlilypond-user@gnu.orghttps://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
--
*Markus Baertschi*, Bas du Rossé 16, CH-1163, Etoy, Switzerland
mar...@markus.org, ++41 (79) 403 1186 (mobile)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
markup on top staff of an orchestra piece
Hi, in a piece for large orchestra, I need text markup and tempo markings which only appear on the top staff of the score and each part. I defined an empty (invisible) staff with removed staff symbol, time signature, etc., using skips instead of rests, which works well. Unfortunately as soon as \RemoveEmptyBars is used in the score, the staff and all markup gets removed. Is there a way to persuade Lily never to remove that staff without adding any visual content to it (except for the markup of course...)? -- Orm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup on top staff of an orchestra piece
I found it.
For someone googling this: You have to put
\new Staff \with { \override VerticalAxisGroup.remove-empty = ##f }
into your staff definition.
Sorry for the noise...
--
Orm
Am Dienstag, den 16. September 2014 um 22:04:38 Uhr (+0200) schrieb Orm
Finnendahl:
Hi,
in a piece for large orchestra, I need text markup and tempo markings
which only appear on the top staff of the score and each part. I
defined an empty (invisible) staff with removed staff symbol, time
signature, etc., using skips instead of rests, which works well.
Unfortunately as soon as \RemoveEmptyBars is used in the score, the
staff and all markup gets removed.
Is there a way to persuade Lily never to remove that staff without
adding any visual content to it (except for the markup of course...)?
--
Orm
___
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: markup on top staff of an orchestra piece
There’s a much better solution which doesn’t need a piccolo (or whatever
is on top) staff that is always present, even if it’s only filled with
pauses: Put \tempo and \mark into a global variable and add this to all
staffs; see attachment. This also lets you change things like time
signature or key in all instruments simulatneously.
Am 16.09.2014 um 22:19 schrieb Orm Finnendahl:
I found it.
For someone googling this: You have to put
\new Staff \with { \override VerticalAxisGroup.remove-empty = ##f }
into your staff definition.
Sorry for the noise...
--
Orm
Am Dienstag, den 16. September 2014 um 22:04:38 Uhr (+0200) schrieb Orm
Finnendahl:
Hi,
in a piece for large orchestra, I need text markup and tempo markings
which only appear on the top staff of the score and each part. I
defined an empty (invisible) staff with removed staff symbol, time
signature, etc., using skips instead of rests, which works well.
Unfortunately as soon as \RemoveEmptyBars is used in the score, the
staff and all markup gets removed.
Is there a way to persuade Lily never to remove that staff without
adding any visual content to it (except for the markup of course...)?
--
Orm
___
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
\version 2.19.13
global = {
\time 3/4
s2.*4
\mark \default
s2.*4
\time 6/8
s2.*4
\tempo 4 = 90
s2.*4
\tempo Allegro
s2.*4
}
silentpiccolo = {
R2.*20
}
busyviolin = \relative c' {
\repeat unfold 20 c2.:32
}
\score {
\new Staff \with {
instrumentName = Piccolo
shortInstrumentName = Picc.
}
\global
\silentpiccolo
\new Staff \with {
instrumentName = Violin
shortInstrumentName = Vln.
}
\global
\busyviolin
\layout {
\context {
\Score
\RemoveEmptyStaves
}
}
}
\markup { Parts follow: }
\score {
\new Staff \with {
instrumentName = Violin
}
\global
\busyviolin
}
\score {
\new Staff \with {
instrumentName = Piccolo
}
\compressFullBarRests %optional
\global
\silentpiccolo
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How do you tell Lilypond not to jump strings when sliding?
Phil Burfitt phil.burfitt at talktalk.net writes: Jay, You'll need to indicate string numbers. They can be hidden with \omit StringNumber if you do not want the circled numbers to appear. Btw, guitar music is usually written an octave higher than it sounds. You should use \clef treble_8 in the \new Staff section. Hope that helps. Phil. Phil, Thanks. I was hoping that there was a way to tell lilypond not to jump between strings when sliding - that is logical and makes sense. You are saying that I have to specify the StringNumber, which is what I wanted to avoid. I think this situation does not make sense for such an advanced software as lilypond. Jay ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup on top staff of an orchestra piece
Hi Malte,
thanks for the recommendation. This isn't what I'm looking for as the
voice defined in the global variable included and repeated for each
staff results in the appearance of all markups like tempo and such on
all staffs. Defining a dedicated empty staff system (it's not the
piccolo) entirely for the purpose of these definitions and including
it once on top of the score, on top of some staffgroups and on top of
the part templates serves the same purpose as a global variable, but
makes them appear only at selected places, no matter, which staffs
have been removed.
The only thing I haven't figured out yet is, how I can make these
invisible staves disappear in case no staff of a certain staffgroup is
present at all. E.g. in large scores bar numbers normally get
displayed on top, but also above staff groups like the string
section. If there are no other instruments but strings, this makes the
bar numbers appear twice. If anybody knows how to get around this I'd
be glad to know... (but keep in mind that the score is sent to the
printer next Monday, so I'd need that information rather soon as the
score is in A2 and that costs about 100,- Euro for one copy).
Yours,
Orm
Am Dienstag, den 16. September 2014 um 22:35:20 Uhr (+0200) schrieb Malte Meyn:
There’s a much better solution which doesn’t need a piccolo (or whatever is
on top) staff that is always present, even if it’s only filled with pauses:
Put \tempo and \mark into a global variable and add this to all staffs; see
attachment. This also lets you change things like time signature or key in
all instruments simulatneously.
Am 16.09.2014 um 22:19 schrieb Orm Finnendahl:
I found it.
For someone googling this: You have to put
\new Staff \with { \override VerticalAxisGroup.remove-empty = ##f }
into your staff definition.
Sorry for the noise...
--
Orm
Am Dienstag, den 16. September 2014 um 22:04:38 Uhr (+0200) schrieb Orm
Finnendahl:
Hi,
in a piece for large orchestra, I need text markup and tempo markings
which only appear on the top staff of the score and each part. I
defined an empty (invisible) staff with removed staff symbol, time
signature, etc., using skips instead of rests, which works well.
Unfortunately as soon as \RemoveEmptyBars is used in the score, the
staff and all markup gets removed.
Is there a way to persuade Lily never to remove that staff without
adding any visual content to it (except for the markup of course...)?
--
Orm
___
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
\version 2.19.13
global = {
\time 3/4
s2.*4
\mark \default
s2.*4
\time 6/8
s2.*4
\tempo 4 = 90
s2.*4
\tempo Allegro
s2.*4
}
silentpiccolo = {
R2.*20
}
busyviolin = \relative c' {
\repeat unfold 20 c2.:32
}
\score {
\new Staff \with {
instrumentName = Piccolo
shortInstrumentName = Picc.
}
\global
\silentpiccolo
\new Staff \with {
instrumentName = Violin
shortInstrumentName = Vln.
}
\global
\busyviolin
\layout {
\context {
\Score
\RemoveEmptyStaves
}
}
}
\markup { Parts follow: }
\score {
\new Staff \with {
instrumentName = Violin
}
\global
\busyviolin
}
\score {
\new Staff \with {
instrumentName = Piccolo
}
\compressFullBarRests %optional
\global
\silentpiccolo
}
___
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
moving tweaks into markup-definition
Hi,
here is the next question:
Is there a way to move the tweaks in the following code into the
markup definition of secs so that they don't clutter up the score?
--
Orm
%
\version 2.19.5
#(define-markup-command (secs layout props numsecs)
(string?)
(interpret-markup layout props
(markup
#:fontsize -1
#:bold numsecs)))
{ r1 \fermata
-\tweak self-alignment-X #-0.5
-\tweak padding #4
^\markup \secs # 2\ }
%
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How do you tell Lilypond not to jump strings when sliding?
Il 16/set/2014 23:10 Jay Vara j...@diljun.com ha scritto: I was hoping that there was a way to tell lilypond not to jump between strings when sliding - that is logical and makes sense. You are saying that I have to specify the StringNumber, which is what I wanted to avoid. I think this situation does not make sense for such an advanced software as lilypond. Yes, you have to specify the string number. Lilypond tablature is not smart as you'd like to, it's basically a staff adapted to look like a tablature, I think. IIRC few years ago there was a discussion about introducing some more guitar-friendly input syntax (through fret/string numbers): such a system, if implemented, could handle the situation you are describing. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup on top staff of an orchestra piece
Am Dienstag, den 16. September 2014 um 23:29:14 Uhr (+0200) schrieb Orm Finnendahl: The only thing I haven't figured out yet is, how I can make these invisible staves disappear in case no staff of a certain staffgroup is present at all. E.g. in large scores bar numbers normally get displayed on top, but also above staff groups like the string section. If there are no other instruments but strings, this makes the bar numbers appear twice. If anybody knows how to get around this I'd be glad to know... Found that as well: Put an \omit Staff.BarNumber in the staff at the place where you don't want bar numbers and put \undo \omit Staff.BarNumber when they should reappear. -- Orm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup on top staff of an orchestra piece
Hi Orm, The only thing I haven't figured out yet is, how I can make these invisible staves disappear in case no staff of a certain staffgroup is present at all. Malte’s idea is the correct way to go, with a custom context (search for ScoreMarks or MarksLine in the list archives). To get it to disappear with the rest of a staff group, you use properties like keep-alive-together. I’m hoping to get a turn-key template uploaded to openlilylib someday, but in the meantime this information should help you find the right solution. Hope this helps! Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
wrong page-number position in 2.19.14
I noticed that in 2.19.14, page numbers in oddHeaderMarkup are center-aligned,
while in evenHeaderMarkup - left-aligned. This looks strange. Bug?
{
c'1
\pageBreak
c'1
\pageBreak
c'1
\pageBreak
c'1
\pageBreak
c'1
\pageBreak
}
-- Karol
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving tweaks into markup-definition
Hello,
On Tue, Sep 16, 2014 at 4:33 PM, Orm Finnendahl
orm.finnend...@selma.hfmdk-frankfurt.de wrote:
Hi,
here is the next question:
Is there a way to move the tweaks in the following code into the
markup definition of secs so that they don't clutter up the score?
The only way I can think of doing this is to add (property . value) pairs
to the contents of props. The following works for your tweaks, but it
won't work for every overridable property: 'color and 'transparent don't
work, for example.
I'd be interested to know if there's a better way to do this.
Anyway, I hope this is useful.
%
\version 2.19.5
#(define-markup-command (secs layout props numsecs)
(string?)
(let* ((immutable (car props))
(mutable (cadr props))
(font-defaults (caddr props)))
(set! mutable (assoc-set! mutable 'self-alignment-X -0.5))
(set! mutable (assoc-set! mutable 'padding 4))
;(set! mutable (acons 'padding 4 mutable)) ; this doesn't take--why
not?
(set! props (list immutable mutable font-defaults))
(interpret-markup layout props
(markup
#:fontsize -1
#:bold numsecs
{ r1 \fermata
^\markup \secs # 2\ }
%
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup on top staff of an orchestra piece
Hi Kieren, thanks for the note, I'll try to find that. Not sure whether it makes sense at this moment to change in the current score (although it's quite well modularized, the whole thing consists of about 600 files), especially since I seem to be able to get everything worked out quite well, but I will definitely consider that in the future. -- Orm Am Dienstag, den 16. September 2014 um 17:56:32 Uhr (-0400) schrieb Kieren MacMillan: Hi Orm, The only thing I haven't figured out yet is, how I can make these invisible staves disappear in case no staff of a certain staffgroup is present at all. Malte’s idea is the correct way to go, with a custom context (search for ScoreMarks or MarksLine in the list archives). To get it to disappear with the rest of a staff group, you use properties like keep-alive-together. I’m hoping to get a turn-key template uploaded to openlilylib someday, but in the meantime this information should help you find the right solution. Hope this helps! Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving tweaks into markup-definition
Hi David,
thanks a lot, that definitely helps! I tried to manipulate the assoc
list of props by consing to it but lacking the knowledge of the
structure of the prop variable didn't get me anywhere. I wonder
whether I could find that information without having to read through
and understand all of the sources of lilypond.
--
Orm
Am Dienstag, den 16. September 2014 um 17:52:47 Uhr (-0500) schrieb David
Nalesnik:
Hello,
On Tue, Sep 16, 2014 at 4:33 PM, Orm Finnendahl
orm.finnend...@selma.hfmdk-frankfurt.de wrote:
Hi,
here is the next question:
Is there a way to move the tweaks in the following code into the
markup definition of secs so that they don't clutter up the score?
The only way I can think of doing this is to add (property . value) pairs
to the contents of props. The following works for your tweaks, but it
won't work for every overridable property: 'color and 'transparent don't
work, for example.
I'd be interested to know if there's a better way to do this.
Anyway, I hope this is useful.
%
\version 2.19.5
#(define-markup-command (secs layout props numsecs)
(string?)
(let* ((immutable (car props))
(mutable (cadr props))
(font-defaults (caddr props)))
(set! mutable (assoc-set! mutable 'self-alignment-X -0.5))
(set! mutable (assoc-set! mutable 'padding 4))
;(set! mutable (acons 'padding 4 mutable)) ; this doesn't take--why
not?
(set! props (list immutable mutable font-defaults))
(interpret-markup layout props
(markup
#:fontsize -1
#:bold numsecs
{ r1 \fermata
^\markup \secs # 2\ }
%
___
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: moving tweaks into markup-definition
On Tue, Sep 16, 2014 at 6:19 PM, Orm Finnendahl orm.finnend...@selma.hfmdk-frankfurt.de wrote: Hi David, thanks a lot, that definitely helps! I tried to manipulate the assoc list of props by consing to it but lacking the knowledge of the structure of the prop variable didn't get me anywhere. I wonder whether I could find that information without having to read through and understand all of the sources of lilypond. Well, there is some information here: http://www.lilypond.org/doc/v2.19/Documentation/extending/new-markup-command-definition#on-properties But I only learned about the structure of props by poking around in C++ files :( I tried to show the structure of the props list-of-alists in the function, though. It's a list of the immutable properties alist of the TextScript grob, the mutable properties alist, and the font-defaults alist. As far as mutable/immutable properties, there's a description here: http://www.lilypond.org/doc/v2.19/Documentation/notation/technical-glossary though I don't think it's particularly clear... --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to force shortened staff lines?
This seems to work fine for me:
%% --- Begin
\version 2.18.2
\paper {
right-margin = 3.0\in
}
\score {
\relative c' {
\repeat unfold 32 { c4 d e f }
}
\layout {
}
}
%%--- End
Can you post a short example that shows us the problem?
Knute Snortum
(via Gmail)
On Tue, Sep 16, 2014 at 10:36 AM, Bric b...@flight.us wrote:
i want to generate a landscape score, but one where the staff lines extend
some percentage of the printable area - let's say, 70%. Leaving 30% width
blank, on the right, for hand-written annotations (upon printout).
I've tried:
line-width = 70%
,
line-width = 7.0\in
, and
right-margin = 3.0\in
but all that is being ignored. At least in the \paper { } block.
Help?
___
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: how to force shortened staff lines?
On 09/16/2014 08:44 PM, Knute Snortum wrote:
This seems to work fine for me:
%% --- Begin
\version 2.18.2
\paper {
right-margin = 3.0\in
}
\score {
\relative c' {
\repeat unfold 32 { c4 d e f }
}
\layout {
}
}
%%--- End
My profuse apologiesto the list.
I had overlooked the offending directive earlier; it was:
line-width = 13.5\in
so sorry. I have a different though related question; postingas a
separate thread.
thank you!
Can you post a short example that shows us the problem?
Knute Snortum
(via Gmail)
On Tue, Sep 16, 2014 at 10:36 AM, Bric b...@flight.us
mailto:b...@flight.us wrote:
i want to generate a landscape score, but one where the staff
lines extend some percentage of the printable area - let's say,
70%. Leaving 30% width blank, on the right, for hand-written
annotations (upon printout).
I've tried:
line-width = 70%
,
line-width = 7.0\in
, and
right-margin = 3.0\in
but all that is being ignored. At least in the \paper { } block.
Help?
___
lilypond-user mailing list
lilypond-user@gnu.org mailto: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
a column of text to the right of the score
earlier today I asked about creating blank margins for HAND-WRITTEN annotations (and got help - thanks). I would also like to know how one can include typed text in the same space, as a column of text to the right of the score, spanning the full height of the printable area - for comments, verses, pedagogical notes, etc. I have a hunch this is a page layout question that's already been addressed, but I couldn't find previous discussion. TIA ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
