tremolo placement in crimped staves
Hey all,
I’m working on a piece where staff space is used to indicate intervals.
In a staff where the distance between lines is halved, I need to double stem
lengths (which are calculated in staff spaces) so that stems are comfortably
readable.
However, tremolos are shifted up on these stems compared to their usual
placement. Is there any not-too-hackish way to bump the tremolo down to an
aesthetically nicer place?
\version "2.19.0"
{
\override Staff.StaffSymbol.staff-space = #0.5
\override Stem.details.lengths = #'(7.0 7.0 7.0 8.5 10.0 12.0)
g'4:32
}
Cheers,
MS
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning LilyPond, comments invited
Carl Sorensen-3 wrote > Your music has some durations that cross bar lines. These durations mess > up the bar checks. Is there a reason you don't separate them into tied > groups so there are bar line breaks? Ah, let me explain. The composer, Philippe Verdelot, lived somewhere around 1500, and back then they didn't use bar lines yet. Please consult the following entry from the LilyPond documentation: http://www.lilypond.org/doc/v2.17/Documentation/notation/working-with-ancient-music_002d_002dscenarios-and-solutions#mensurstriche-layout It's a compromise. The ancient notation isn't copied, but some characteristics are allowed to shine through, particularly the fact that renaissance music has no concept of measures. That poses a challenge, of course. Can the music typesetting software handle that requirement? It may be, I don't know, that graphically oriented software is rigidly dependent on bar checks at _every_ bar. The LilyPond developers are aware of all this, of course. LilyPond must be able to reproduce a wide range of typesetting styles. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Learning-LilyPond-comments-invited-tp156969p157002.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: Learning LilyPond, comments invited
Colin Tennyson schrieb: >Carl Sorensen-3 wrote >> Your music has some durations that cross bar lines. These durations >mess >> up the bar checks. Is there a reason you don't separate them into >tied >> groups so there are bar line breaks? > > >Ah, let me explain. > >The composer, Philippe Verdelot, lived somewhere around 1500, and back >then >they didn't use bar lines yet. > >Please consult the following entry from the LilyPond documentation: >http://www.lilypond.org/doc/v2.17/Documentation/notation/working-with-ancient-music_002d_002dscenarios-and-solutions#mensurstriche-layout > >It's a compromise. The ancient notation isn't copied, but some >characteristics are allowed to shine through, particularly the fact >that >renaissance music has no concept of measures. I didn't follow the thread so far. But this sounds like you should simply drop the barchecks. If the music doesn't have a notion of measures, why check for them? Urs > >That poses a challenge, of course. Can the music typesetting software >handle >that requirement? It may be, I don't know, that graphically oriented >software is rigidly dependent on bar checks at _every_ bar. > >The LilyPond developers are aware of all this, of course. LilyPond must >be >able to reproduce a wide range of typesetting styles. > > > >-- >View this message in context: >http://lilypond.1069038.n5.nabble.com/Learning-LilyPond-comments-invited-tp156969p157002.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 -- Urs Liska openlilylib.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tremolo placement in crimped staves
On Fri, Jan 3, 2014 at 9:01 AM, Mike Solomon wrote: > However, tremolos are shifted up on these stems compared to their usual > placement. Is there any not-too-hackish way to bump the tremolo down to an > aesthetically nicer place? I assume this is the sort of thing you’d refer to as hackish? http://lsr.dsi.unimi.it/LSR/Snippet?id=374 (Then: I’ve got nothin’ :-) Cheers, Valentin. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tremolo placement in crimped staves
On Jan 3, 2014, at 10:23 AM, Valentin Villenave wrote: > On Fri, Jan 3, 2014 at 9:01 AM, Mike Solomon wrote: >> However, tremolos are shifted up on these stems compared to their usual >> placement. Is there any not-too-hackish way to bump the tremolo down to an >> aesthetically nicer place? > > I assume this is the sort of thing you’d refer to as hackish? > http://lsr.dsi.unimi.it/LSR/Snippet?id=374 > > (Then: I’ve got nothin’ :-) > I think a better option would be a Y-offset function for the tremolo that put it farther down the stem - how far down I’m not sure… ~Mike ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
how to update an olp piece of code
Dear community, I have an old piece of code, initially written by Rune Zedeler. I would like to update it to version 2.18.0, but I don't know what is wrong with it. Here is the code: \version "2.17.97" motiv = #(define-music-function (parser location name pattern) (symbol? ly:music?) (letrec ((trans-rec (lambda (pitches) (lambda (music) (let* ((es (ly:music-property music 'elements)) (e (ly:music-property music 'element)) (p (ly:music-property music 'pitch))) (if (pair? es) (ly:music-set-property! music 'elements (map (trans-rec pitches) es))) (if (ly:music? e) (ly:music-set-property! music 'element ((trans-rec pitches) e))) (if (ly:pitch? p) (let* ((o (ly:pitch-octave p)) (n (ly:pitch-notename p)) (i (+ (* 7 o) n)) (pes (ly:music-property (list-ref pitches i) 'elements)) (pnew (ly:music-property (car pes) 'pitch)) ) (ly:music-set-property! music 'pitch pnew) )) music) (primitive-eval `(define ,name (define-music-function (parserb locationb pitchseq) (ly:music?) (let* ((pitches (ly:music-property pitchseq 'elements)) (n (ly:music-property pitchseq 'name))) (if (not (equal? n 'SequentialMusic)) (ly:warning "2nd arg of transform must be SequentialMusic, got ~a" n) ((,trans-rec (map event-chord-wrap! pitches)) (ly:music-deep-copy ,pattern))) (make-music 'SequentialMusic 'void #t))) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to update an olp piece of code
Stefan Thomas writes: > Dear community, > I have an old piece of code, initially written by Rune Zedeler. > I would like to update it to version 2.18.0, but I don't know what is wrong > with it. > Here is the code: You failed to mention what it is supposed to do, give an example for using it, and point out what goes wrong now. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning LilyPond, comments invited
Hi Carl,
You have pointed out something very interesting:
This is the the way I had written the nesting structure in my first message:
addKey = { \key c \major \time 4/4 }
\score {
\new StaffGroup
<<
\new Staff
<<
\set Staff.instrumentName = #"Superius "
\new Voice = "staffOne" << \addKey \staffOneNotes >>
\lyricsto "staffOne" \new Lyrics \staffOneWords
>>
\new Staff
<<
\set Staff.instrumentName = #"Contratenor "
\new Voice = "staffTwo" << \addKey \staffTwoNotes >>
\lyricsto "staffTwo" \new Lyrics \staffTwoWords
>>
>>
}
The LillyPond parser accepts this, there is no error, and the score _is
rendered correctly_.
But as you point out:
this:
<< \addKey \staffOneNotes >>
is better written as:
{ \addKey \staffOneNotes }
\score {
\new StaffGroup
<<
\new Staff
<<
\set Staff.instrumentName = #"Superius "
\new Voice = "staffOne" { \addKey \staffOneNotes }
\lyricsto "staffOne" \new Lyrics \staffOneWords
>>
\new Staff
<<
\set Staff.instrumentName = #"Contratenor "
\new Voice = "staffTwo" { \addKey \staffTwoNotes }
\lyricsto "staffTwo" \new Lyrics \staffTwoWords
>>
>>
}
While the { ... } notation is better, LilyPond accepts both: { \addKey
\staffTwoNotes } and << \addKey \staffTwoNotes >>. In this case both are
rendered the same.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Learning-LilyPond-comments-invited-tp156969p157008.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: Learning LilyPond, comments invited
Colin Tennyson writes:
> The LillyPond parser accepts this, there is no error, and the score _is
> rendered correctly_.
> But as you point out:
> this:
> << \addKey \staffOneNotes >>
> is better written as:
> { \addKey \staffOneNotes }
>
>
> While the { ... } notation is better, LilyPond accepts both: { \addKey
> \staffTwoNotes } and << \addKey \staffTwoNotes >>. In this case both are
> rendered the same.
But that's not a given. Take, for example, the output of
addKey = { \key g \major \time 4/4 }
staffOneNotes = { \grace { d'16 g' b' } d''8 8 8 8 fis'8 8 g'4 }
\score {
\new StaffGroup <<
\new Staff \new Voice = "staffOne" << \addKey \staffOneNotes >>
\new Staff \new Voice = "staffOne" { \addKey \staffOneNotes }
>>
}
Also, if you have something like
\new StaffGroup
{
<< \key c\major { c' c' c' c' } >>
}
you'll likely be surprised by the results...
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning LilyPond, comments invited
David Kastrup schrieb:
>Colin Tennyson writes:
>
>> The LillyPond parser accepts this, there is no error, and the score
>_is
>> rendered correctly_.
>> But as you point out:
>> this:
>> << \addKey \staffOneNotes >>
>> is better written as:
>> { \addKey \staffOneNotes }
>>
>>
>> While the { ... } notation is better, LilyPond accepts both: {
>\addKey
>> \staffTwoNotes } and << \addKey \staffTwoNotes >>. In this case both
>are
>> rendered the same.
>
>But that's not a given. Take, for example, the output of
>
>
>
>
>
>Also, if you have something like
>
>\new StaffGroup
>{
> << \key c\major { c' c' c' c' } >>
>}
>
>you'll likely be surprised by the results...
Colin, your example works because you have exactly one music expression inside
the angled brackets.
These let you enter multiple expressions that are interpreted in parallel. And
if there is just one expression inside it just does nothing.
HTH
Urs
--
Urs Liska
openlilylib.org
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning LilyPond, comments invited
Urs Liska writes:
> David Kastrup schrieb:
>>Colin Tennyson writes:
>>
>>> The LillyPond parser accepts this, there is no error, and the score
>>_is
>>> rendered correctly_.
>>> But as you point out:
>>> this:
>>> << \addKey \staffOneNotes >>
>>> is better written as:
>>> { \addKey \staffOneNotes }
>>>
>>>
>>> While the { ... } notation is better, LilyPond accepts both: {
>>\addKey
>>> \staffTwoNotes } and << \addKey \staffTwoNotes >>. In this case both
>>are
>>> rendered the same.
>>
>>But that's not a given. Take, for example, the output of
>>
>>
>>
>>
>>
>>Also, if you have something like
>>
>>\new StaffGroup
>>{
>> << \key c\major { c' c' c' c' } >>
>>}
>>
>>you'll likely be surprised by the results...
>
> Colin, your example works because you have exactly one music
> expression inside the angled brackets.
\addKey \staffOneNotes are _two_ music expressions. I used exactly the
same template for demonstrating things that don't work.
> These let you enter multiple expressions that are interpreted in
> parallel. And if there is just one expression inside it just does
> nothing.
But that's not what we had here.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to update an olp piece of code
Ok, I use it in the following way:
\motiv #'something {c'4 c' d' d' e' d' c'2 }
\new Staff \relative { \something { c d e } }
2014/1/3 David Kastrup
> Stefan Thomas writes:
>
> > Dear community,
> > I have an old piece of code, initially written by Rune Zedeler.
> > I would like to update it to version 2.18.0, but I don't know what is
> wrong
> > with it.
> > Here is the code:
>
> You failed to mention what it is supposed to do, give an example for
> using it, and point out what goes wrong now.
>
> --
> David Kastrup
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning LilyPond, comments invited
David Kastrup schrieb:
>Urs Liska writes:
>
>> David Kastrup schrieb:
>>>Colin Tennyson writes:
>>>
The LillyPond parser accepts this, there is no error, and the score
>>>_is
rendered correctly_.
But as you point out:
this:
<< \addKey \staffOneNotes >>
is better written as:
{ \addKey \staffOneNotes }
While the { ... } notation is better, LilyPond accepts both: {
>>>\addKey
\staffTwoNotes } and << \addKey \staffTwoNotes >>. In this case
>both
>>>are
rendered the same.
>>>
>>>But that's not a given. Take, for example, the output of
>>>
>>>
>>>
>>>
>>>
>>>Also, if you have something like
>>>
>>>\new StaffGroup
>>>{
>>> << \key c\major { c' c' c' c' } >>
>>>}
>>>
>>>you'll likely be surprised by the results...
>>
>> Colin, your example works because you have exactly one music
>> expression inside the angled brackets.
>
>\addKey \staffOneNotes are _two_ music expressions. I used exactly the
>same template for demonstrating things that don't work.
>
>> These let you enter multiple expressions that are interpreted in
>> parallel. And if there is just one expression inside it just does
>> nothing.
>
>But that's not what we had here.
Ok, sorry for not having looked close enough.
--
Urs Liska
openlilylib.org
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning LilyPond, comments invited
David Kastrup wrote
> Take, for example, the output of
>
> addKey = { \key g \major \time 4/4 }
> staffOneNotes = { \grace { d'16 g' b' } d''8 8 8 8 fis'8 8 g'4 }
>
> \score {
> \new StaffGroup <<
> \new Staff \new Voice = "staffOne" << \addKey \staffOneNotes >>
> \new Staff \new Voice = "staffOne" { \addKey \staffOneNotes }
> >>
> }
>
>
> Also, if you have something like
>
> \new StaffGroup
> {
><< \key c\major { c' c' c' c' } >>
> }
>
> you'll likely be surprised by the results...
Given these concerns the following templates in the documentation need to be
updated:
http://www.lilypond.org/doc/v2.18/Documentation/learning/satb-on-four-staves
The template uses the ill advised << ... >> grouping
This is just one of the templates, presumably _all_ the vocal ensenble
templates are using << ... >>
How many different versions of the documentation do you keep?
I'm mostly encountering v2.16 and v2.17, but sometimes a google search gives
me a result in v2.14
(For google searches in the lilypond documentation I generally add the
following specifiation in the Google search bar:
site:lilypond.org/doc/v2.17/Documentation/)
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Learning-LilyPond-comments-invited-tp156969p157015.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: how to update an olp piece of code
Stefan Thomas writes:
> 2014/1/3 David Kastrup
>> Stefan Thomas writes:
>>
>> > Dear community,
>> > I have an old piece of code, initially written by Rune Zedeler.
>> > I would like to update it to version 2.18.0, but I don't know what is wrong
>> > with it.
>> > Here is the code:
>>
>> You failed to mention what it is supposed to do, give an example for
>> using it, and point out what goes wrong now.
>
> Ok, I use it in the following way:
> \motiv #'something {c'4 c' d' d' e' d' c'2 }
>
> \new Staff \relative { \something { c d e } }
Which does not raise an error. You failed to mention what it is
supposed to do and point out what goes wrong now.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Learning Lilypond, comments invited - part 2
I'm creating a new thread because the previous one has become somewhat
cluttered.
My template is much better now, thank you for your suggestions.
As emphasized by David Kastrup, the keyword \new instructs Lilypond to
create a new instance of a class.
\new StaffGroup creates an instance of the StaffGroup object.
In this template several properties of the Score class are modified, such
as:
\hide Score.SystemStartBracket
\override Score.BarNumber.font-size = #1.5
I surmise that the StaffGroup object inherits from the Score object, similar
to inheritence in object oriented programming.
Again, this is the first 10 measures and the upper 2 staffs of a 100
measure, 4 staff score.
I'm pleased with the separations in this template.
- The declaration of the nesting structure now contains only the nesting of
the elements
- Properties of the elements are all declared in \layout
One thing remains: the property "forbid_line_break_engraver" is a property
of the element Voice
If possible I want to avoid repeating commands. I don't want to put in the
\remove "forbid_line_break_engraver" four times, for every voice in the
score.
For the other properties I was able to use a dot notation access. Examples:
\hide Score.SystemStartBracket
\override Staff.InstrumentName.self-alignment-X = #RIGHT
The accessor \context allows the property to be set centrally:
\context { \Voice \remove "Forbid_line_break_engraver" }
But is just a side effect? Is \context meant for something else entirely?
Can the property "forbid_line_break_engraver" also be accessed using a dot
notation?
\version "2.18.0"
\language "english"
% 't' as in 'test' or 'transcribing an existing score'
tBreak = { \break }
ficta = { \once \set suggestAccidentals = ##t }
addKey = { \key c \major \time 4/4 }
barSetup = {
\hide Staff.BarLine %{ for the Mensurstriche: inside the staff hide the
barline %}
s1 | s1 | s1 | \tBreak s1 | s1 | %05
s1 | s1 | s1 | \tBreak s1 | s1 | %10
\undo \hide Staff.BarLine \bar "||" % final barline visible
}
staffOneNotes = \relative c'' {
g1 | g2 a2 | b2 g2 | r2 a2 | d2. c4 | %005
b2 a2 | r4 d4 d4 b4 | c4. b8 a8[ g8] a4. g8[ f8 e8] d4 a'2 g2 \ficta
fs4 | %010
}
staffOneWords = \lyricmode {
San -- cta Ma -- ri -- a, San -- cta Ma -- %005
ri -- a, suc -- cur -- re mi- _ _ _ _ _ _ _ _ _ _ %010
}
staffTwoNotes = \relative c' {
%\clef "G_8"
g2 c2. d4 a2 | g4. a8 b8[ c8] d2 cs4 d2 | r4 d2 d4 | %005
e2 f2 | d2 r2 | c2 f2. d4 f2 | e2 d4. c8 | %010
}
staffTwoWords = \lyricmode {
San -- cta Ma -- ri -- _ _ _ _ _ _ a, San -- cta %05
Ma -- ri -- a, suc -- cur -- re mi -- se- _ _ %10
}
#(set-global-staff-size 18)
\header {
title = "Sancta Maria, succurre miseris"
composer = "Philippe Verdelot"
tagline = ""
}
\score {
\new StaffGroup
<<
\new Staff
<<
\set Staff.instrumentName = #"Superius "
\new Voice = "staffOne" { \addKey \staffOneNotes }
\lyricsto "staffOne" \new Lyrics \staffOneWords
\barSetup
>>
\new Staff
<<
\set Staff.instrumentName = #"Contratenor "
\new Voice = "staffTwo" { \addKey \staffTwoNotes }
\lyricsto "staffTwo" \new Lyrics \staffTwoWords
\barSetup
>>
>>
\layout
{
indent = 6\cm
\hide Score.SystemStartBracket
\override Score.BarNumber.font-size = #1.5
\override Score.BarNumber.break-visibility = #end-of-line-invisible
\override Score.BarNumber.self-alignment-X = #LEFT
\set Score.barNumberVisibility = #(every-nth-bar-number-visible 5)
\override Staff.InstrumentName.self-alignment-X = #RIGHT
\context { \Voice \remove "Forbid_line_break_engraver" }
%#(layout-set-staff-size 18)
}
%\midi { }
}
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Learning-Lilypond-comments-invited-part-2-tp157019.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: Learning Lilypond, comments invited - part 2
> Can the property "forbid_line_break_engraver" also be accessed using a dot > notation? I am not the only one ;) (David will understand what I want to say) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning LilyPond, comments invited
>From what I've seen, \cadenzaOn seems to be the preferred way of writing >unmeasured music. On Jan 3, 2014, at 3:14 AM, Colin Tennyson wrote: > Carl Sorensen-3 wrote >> Your music has some durations that cross bar lines. These durations mess >> up the bar checks. Is there a reason you don't separate them into tied >> groups so there are bar line breaks? > > > Ah, let me explain. > > The composer, Philippe Verdelot, lived somewhere around 1500, and back then > they didn't use bar lines yet. > > Please consult the following entry from the LilyPond documentation: > http://www.lilypond.org/doc/v2.17/Documentation/notation/working-with-ancient-music_002d_002dscenarios-and-solutions#mensurstriche-layout > > It's a compromise. The ancient notation isn't copied, but some > characteristics are allowed to shine through, particularly the fact that > renaissance music has no concept of measures. > > That poses a challenge, of course. Can the music typesetting software handle > that requirement? It may be, I don't know, that graphically oriented > software is rigidly dependent on bar checks at _every_ bar. > > The LilyPond developers are aware of all this, of course. LilyPond must be > able to reproduce a wide range of typesetting styles. > > > > -- > View this message in context: > http://lilypond.1069038.n5.nabble.com/Learning-LilyPond-comments-invited-tp156969p157002.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 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \include "*.ly" for only part of a score
In general it's best practice to keep includes at the top of the file, so I
would do it like this:
%file custom.ly
varA = %letter paper; can't check syntax on my ipod so not going to try
varB = %ragged right
%your file
\version "2.18.0"
\include "custom.ly"
\paper{ \varB }
etc.
On Jan 2, 2014, at 9:11 PM, Jay Anderson wrote:
> On Thu, Jan 2, 2014 at 6:55 PM, guocuozuoduo wrote:
>> I would like to know how to use the \include command for only part of a
>> score.
>> It is not described in the manual.
>
> sectionA.ily:
> \relative c' {\time 4/4 c1 |}
>
> sectionB.ily:
> \relative c' {e1 |}
>
> score.ly:
> \score {
> \new Staff {
>\include "sectionA.ily"
>\include "sectionB.ily"
> }
> }
>
> (I haven't tested the above, but this shows the idea.)
>
> Alternatively you could assign the sections to variables and use those
> instead of using \include directly:
>
>
> sectionA.ily:
> sectionA = \relative c' {\time 4/4 c1 |}
>
> sectionB.ily:
> sectionB = \relative c' {e1 |}
>
> score.ly:
> \include "sectionA.ily"
> \include "sectionB.ily"
>
> \score {
> \new Staff {
>\sectionA
>\sectionB
> }
> }
>
> -Jay
>
> ___
> 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: Learning LilyPond, comments invited
Alex Loomis-2 wrote > From what I've seen, \cadenzaOn seems to be the preferred way of writing > unmeasured music. Well, the availability of "\hide \BarLine" and "\undo \hide \BarLine" is relatively recent. I think I saw a place where it was described in the v2.17 documentation, but not in the v2.16 documentation As to \cadenzaOn, from the LilyPond documentation: http://www.lilypond.org/doc/v2.17/Documentation/notation/displaying-rhythms "Inserting a \bar command within a cadenza does not start a new measure, even if a bar line is printed. So any accidentals – which are usually assumed to remain in force until the end of the measure – will still be valid after the bar line printed by \bar." In the case of typesetting renaissance (choral) music you do want the modern conventions for accidentals. With \cadenzaOn you would lose the automated handling of accidentals. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Learning-LilyPond-comments-invited-tp156969p157031.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
Slur position
Is it me, or is this slur too far away from the noteheads?
\version "2.18.0"
\relative c''' {
c4.( c8~ c4 c)
}
DR
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Numbers over double percent repeats
> -Original Message- > From: Marc Hohl [mailto:m...@hohlart.de] > Sent: Friday, January 03, 2014 2:49 AM > To: lilypond-user@gnu.org > Subject: Re: Numbers over double percent repeats > > Am 03.01.2014 06:51, schrieb Daniel Rosen: > > How can I modify the code below so that it produces output more along > the lines of the attachment (regarding the numbers over the percent > repeats)? I want the number to express how many measures are being > repeated, not how many repetitions. > > > I think > > \set countPercentRepeats = ##t > > will do the job. > > HTH, > > Marc Nope, that gives me a 2 over the first percent and a 3 over the second. I need both of them to have a 2. DR ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
Colin Tennyson writes:
> I'm creating a new thread because the previous one has become somewhat
> cluttered.
>
> My template is much better now, thank you for your suggestions.
>
> As emphasized by David Kastrup, the keyword \new instructs Lilypond to
> create a new instance of a class.
> \new StaffGroup creates an instance of the StaffGroup object.
When you blindly exchange words and terms to the names of concepts of
which you have an understanding, that does not mean that stuff will
magically start behaving according to those concepts. And it does not
facilitate communication.
> In this template several properties of the Score class are modified, such
> as:
> \hide Score.SystemStartBracket
> \override Score.BarNumber.font-size = #1.5
>
> I surmise that the StaffGroup object inherits from the Score object,
> similar to inheritence in object oriented programming.
See, now you've muddled up your terminology to a degree where it does
not make any sense.
You call contexts "objects", but those don't inherit anything, and most
certainly not in the sense of object oriented programming. In OOP, you
have a _type_ hierarchy based on inheritance.
However, the parent relationship of contexts is not a type hierarchy:
every context is created from its context description and _nothing_
else.
The parent relationship comes into play if we are looking at
_properties_: when looking up a property (context/grob), looking up in
some context a property that is not defined will instead get looked up
in the parent context.
The parent relationship is only established when a context is created.
While some guidelines are in the context definition (namely the types of
subcontexts that would be acceptable, and a default type to create and
delegate the subcontext creation to in case a context of the given type
can' be found or created otherwise).
> One thing remains: the property "forbid_line_break_engraver" is a property
> of the element Voice
No, it isn't. Your use of "property" and "element" does not make any
sense.
> If possible I want to avoid repeating commands. I don't want to put in the
> \remove "forbid_line_break_engraver" four times, for every voice in the
> score.
So do it in the layout definition.
> For the other properties I was able to use a dot notation access. Examples:
> \hide Score.SystemStartBracket
> \override Staff.InstrumentName.self-alignment-X = #RIGHT
>
> The accessor \context allows the property to be set centrally:
> \context { \Voice \remove "Forbid_line_break_engraver" }
Again, you are wildly throwing terms around that have no sensible
relation or meaning. \context is no "accessor". It is a reserved word
that will, inside of a layout definition, start a context definition.
> But is just a side effect? Is \context meant for something else entirely?
> Can the property "forbid_line_break_engraver" also be accessed using a dot
> notation?
I don't understand what you are trying to talk about.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Another time model (related to the usability thread)
Hi Keith, > I think the automatic-rest-length idea will be easier to use if it is > independent of \pushToTag. Yes, sorry, I misspoke: I didn’t mean to LITERALLY extend \pushToTag. I simply meant that, to the user, it appears that \pushToTag puts music at a certain tag point only, whereas your function puts music at a certain tag point **and fills the rests in “behind” it**, so in that sense it is [to the user’s mind] an “extension” of \pushToTag. Regardless of how this functionality gets implemented, it will be very welcome! That being said, I do hope we get several opinions on the matter, so that we end up with the most intuitive, flexible, and robust implementation. Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
Hi Colin,
I will try to answer in a way that helps you.
> the keyword \new instructs Lilypond to create a new instance of a class.
You clearly come from a programming background, which will help you scale the
Lilypond learning curve in some ways.
However, don’t push that analogy too far, or you might find (as I did) that it
can confuse matters. =)
> \new StaffGroup creates an instance of the StaffGroup object.
In the way you’re thinking, \new StaffGroup does indeed “create” a new context
("instance of an object”) which matches the StaffGroup definition.
> I surmise that the StaffGroup object inherits from the Score object, similar
> to inheritence in object oriented programming.
Here, David does [with my judicious editing ;)] do a good job of explaining the
situation:
> the parent relationship of contexts is not a type hierarchy:
> every context is created from its context description […]
> the parent relationship comes into play if we are looking at _properties_:
> when looking up a property (context/grob), looking up in some context
> a property that is not defined will instead get looked up
> in the parent context.
>
> The parent relationship is only established when a context is created.
> While some guidelines are in the context definition (namely the types of
> subcontexts that would be acceptable, and a default type to create and
> delegate the subcontext creation to in case a context of the given type
> can' be found or created otherwise).
Is anything in there unclear?
> the property "forbid_line_break_engraver" is a property of the element Voice
More accurately, the Voice context, as defined by default, includes the
forbid_line_break_engraver.
> If possible I want to avoid repeating commands. I don't want to put in the
> \remove "forbid_line_break_engraver" four times, for every voice in the score.
Correct — you can simply “redefine” or “extend” the definition of voice:
\layout {
\context {
\Voice
\remove "forbid_line_break_engraver"
}
}
Now, in any scores which use that layout definition, \new Voice [or \context
Voice] will give you a Voice context [“instance”] which does not include the
forbid_line_break_engraver.
> The accessor \context allows the property to be set centrally:
> \context { \Voice \remove "Forbid_line_break_engraver” }
The **reserved word** \context can indeed be used to add or remove an engraver
in an abstracted (“central”) way.
> But is just a side effect? Is \context meant for something else entirely?
To the user’s eye, \context does two different things when used in two
different places:
1. Inside a \layout definition, it starts the definition of a context.
2. Inside a score, it will look for an existing “instance” (by name) and create
a new one (if not found).
Perhaps this is what you’re referring to?
> Can the property "forbid_line_break_engraver" also be accessed using a dot
> notation?
Not that I’m aware of: engravers can only be added (\consists) or removed
(\remove) in a context definition.
There is no mechanism (e.g.) “Voice.forbid_line_break_engraver.foo”.
Hope this helps!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
Kieren MacMillan writes:
>> Can the property "forbid_line_break_engraver" also be accessed using
>> a dot notation?
>
> Not that I’m aware of: engravers can only be added (\consists) or
> removed (\remove) in a context definition.
No, they can also be added or removed in a context _modification_, as in
\new Voice \with { \remove "..." \consists "..." }
{ ... }
The presence/absence of engravers is established when a context is
created and is static over its lifetime, or iteration would not be able
to work consistently.
Dot syntax is used for navigating to an existing (or implicitly created)
context during music execution. So it's not useful with engravers.
That dot syntax is reinterpreted in the context of _music_ expressions
in a layout definition to affect a subset of context definitions is just
a courtesy
http://code.google.com/p/lilypond/issues/detail?id=2358>. As
opposed to inside of context definitions and modifications,
\override/\revert are not specifically supported in the syntax of layout
definitions. They just happen to be music expressions that can be
sensibly reinterpreted. That would not work for engravers.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning LilyPond, comments invited
David Kastrup wrote
> [...]
> Take, for example, the output of
>
> addKey = { \key g \major \time 4/4 }
> staffOneNotes = { \grace { d'16 g' b' } d''8 8 8 8 fis'8 8 g'4 }
>
> \score {
> \new StaffGroup <<
> \new Staff \new Voice = "staffOne" << \addKey \staffOneNotes >>
> \new Staff \new Voice = "staffOne" { \addKey \staffOneNotes }
> >>
> }
isn't that the well-known issue with grace notes at the begin of
simultaneous music - if you don't have grace notes in staffOneNotes or you
add corresponding grace notes in addKey like
addKey = { \key g \major \time 4/4 \grace s8. }
then it works correctly, doesn't it?
this said, I also prefer the form
{ \addKey \staffOneNotes }
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Learning-LilyPond-comments-invited-tp156969p157038.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: Learning LilyPond, comments invited
Eluze writes:
> David Kastrup wrote
>> [...]
>> Take, for example, the output of
>>
>> addKey = { \key g \major \time 4/4 }
>> staffOneNotes = { \grace { d'16 g' b' } d''8 8 8 8 fis'8 8 g'4 }
>>
>> \score {
>> \new StaffGroup <<
>> \new Staff \new Voice = "staffOne" << \addKey \staffOneNotes >>
>> \new Staff \new Voice = "staffOne" { \addKey \staffOneNotes }
>> >>
>> }
>
> isn't that the well-known issue with grace notes at the begin of
> simultaneous music - if you don't have grace notes in staffOneNotes or you
> add corresponding grace notes in addKey like
>
> addKey = { \key g \major \time 4/4 \grace s8. }
>
> then it works correctly, doesn't it?
I'm not saying that it works incorrectly. Parallel music is
synchronized at the time point 0. Sequential music is executed in
sequence.
The behavior in this case is quite logical.
It would make some sense to move context creation backward in time
before simultaneous grace music in order to maintain top-down order in a
<< \new ... \new ... \new ... >> construct.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
Hi David,
> No, they can also be added or removed in a context _modification_, as in
>
> \new Voice \with { \remove "..." \consists "..." }
> { … }
Thank you for the clarification/correction: engravers can be added or removed
in a context definition or modification.
Cheers,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
when is 2.19 going to be released?
Hello all, Now that 2.18 has been released (kudos, by the way!!!), when is the unstable branch going to be updated? I like to be on the bleeding edge… ;) Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: when is 2.19 going to be released?
- Original Message - From: "Kieren MacMillan" To: "Lilypond-User Mailing List" Cc: "Lilypond Dev" Sent: Friday, January 03, 2014 4:24 PM Subject: when is 2.19 going to be released? Hello all, Now that 2.18 has been released (kudos, by the way!!!), when is the unstable branch going to be updated? I like to be on the bleeding edge… ;) Thanks, Kieren. ___ Well, you need to compile your own version then :-) Unless anyone complains, probably this weekend. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Slur position
It does seem a bit far on 2.18. Is this a regression? I dumped my
earlier versions and therefore can't check it out at the moment.
Shane
On Fri, Jan 3, 2014 at 10:10 AM, Daniel Rosen wrote:
> Is it me, or is this slur too far away from the noteheads?
>
> \version "2.18.0"
> \relative c''' {
> c4.( c8~ c4 c)
> }
>
> DR
>
>
>
> ___
> 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: when is 2.19 going to be released?
Hi Phil, > Well, you need to compile your own version then :-) I have VirtualBox and Lilybuntu and Janek’s script installed. The problem is, there are 437.5 “versions of Lilypond" in git, and I don’t know which I should compile. :-p > Unless anyone complains, probably this weekend. Thanks. =) Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: when is 2.19 going to be released?
Kieren MacMillan schrieb: >Hello all, > >Now that 2.18 has been released (kudos, by the way!!!), when is the >unstable branch going to be updated? >I like to be on the bleeding edge… ;) Then you should build your own LilyPonds ;-) -- Urs Liska openlilylib.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: when is 2.19 going to be released?
Kieren MacMillan schrieb: >Hi Phil, > >> Well, you need to compile your own version then :-) > >I have VirtualBox and Lilybuntu and Janek’s script installed. >The problem is, there are 437.5 “versions of Lilypond" in git, and I >don’t know which I should compile. :-p As long as you don't want to try out a specific feature that someone develops you should simply checkout master and run build-lilypond. This will give you the "mainstream bleeding edge" in a "current" subdir. HTH Urs > >> Unless anyone complains, probably this weekend. > >Thanks. =) >Kieren. >___ >lilypond-user mailing list >lilypond-user@gnu.org >https://lists.gnu.org/mailman/listinfo/lilypond-user -- Urs Liska openlilylib.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Weirdness With Fonts and Font Tree Snippet
> The function `ly:font-config-display-fonts' (available via the `-dshow-available-fonts' command line option of lilypond) I don't even know how to access that. I don't see an option from the GUI to be able to do that. I tried doing some of the things aforementioned through Frescobaldi's command line option (in the GUI), but I could never type in any characters, let alone a full line command. IC, Josh On Fri, Jan 3, 2014 at 12:50 AM, Werner LEMBERG wrote: > > > Indeed, I have found that on Mac OS X, the system is very picky > > about what it sees and doesn't see. For instance, I use the > > SkyFonts program to install fonts from the Google Fonts site. > > Apparently, it doesn't install them as system fonts, so if I want to > > use them in LilyPond (and PT Sans Narrow, one of the fonts in that > > collection, is the font I currently use for LilyPond), I have to go > > ahead and download the ZIP file and install them through FontBook, > > but almost every other program I use has no issue with it. I think > > Inkscape might be picky as well, but I don't do enough stuff with > > those fonts in that program to remember. > > Hmm. The function `ly:font-config-display-fonts' (available via the > `-dshow-available-fonts' command line option of lilypond) shows > exactly which directories lilypond's fontconfig is looking into, > besides a list of fonts it recognizes. It also lists the > configuration files together with the directories fontconfig is > searching for configuration files. Doesn't this work as expected? > > > Werner > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Slur position
- Original Message -
From: "Shane Brandes"
To: "Daniel Rosen"
Cc:
Sent: Friday, January 03, 2014 4:37 PM
Subject: Re: Slur position
It does seem a bit far on 2.18. Is this a regression? I dumped my
earlier versions and therefore can't check it out at the moment.
Shane
On Fri, Jan 3, 2014 at 10:10 AM, Daniel Rosen wrote:
Is it me, or is this slur too far away from the noteheads?
\version "2.18.0"
\relative c''' {
c4.( c8~ c4 c)
}
DR
It appears unchanged since 2.16.0
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Weirdness With Fonts and Font Tree Snippet
2014/1/3 Joshua Nichols > > The function `ly:font-config-display-fonts' (available via the > `-dshow-available-fonts' command line option of lilypond) > > I don't even know how to access that. I don't see an option from the GUI > to be able to do that. > I tried doing some of the things aforementioned through Frescobaldi's > command line option (in the GUI), but I could never type in any characters, > let alone a full line command. > open the terminal of Mac and write: lilypond -dshow-available-fonts ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Weirdness With Fonts and Font Tree Snippet
On Fri, Jan 3, 2014 at 10:53 AM, Federico Bruni wrote: > open the terminal of Mac and write: > > lilypond -dshow-available-fonts > I got: -bash: lilypond: command not found IC, Josh ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
Kieren MacMillan wrote > You clearly come from a programming background, which will help you scale > the Lilypond learning curve in some ways. > However, don’t push that analogy too far, or you might find (as I did) > that it can confuse matters. =) Hi Kieren, To use another analogy: our choir conductor sometimes asks in mild exasparation: "Sing _something_ , never mind you're not sure. If you sing the wrong note I can correct it, but if you don't sing at all I'm dead in the water." So, in asking questions here on this forum I allow myself to err on the side of pushing. (I'm not a programmer, but as you can tell from the terminology I picked up I have been reading up on general principles of programming.) In order to learn the LilyPond environment, I feel I need to know the concepts that have guided how Lilypond is implemented. The opportunity for parent-child relationships is obvious. Systems consist of staffs, staffs are filled with notes. So, is all the typesetting organized according to parent-child and sibling-group relationships, or only some things and other things not? Why do I see side by side two keywords for setting properties: \set and \override. I have seen environments where every property that is by nature ON/OFF is controlled with a boolean variable. That is straightforward, that helps to make the enviroment learnable. Why do I see side by side several ways of toggling ON/OFF? I see "\hide" "\undo \hide" I see "consists" "\remove" I see "##t" and "##f" I wonder, how did the development of LilyPond end up with the syntax and keyword set that it now has? -- View this message in context: http://lilypond.1069038.n5.nabble.com/Learning-Lilypond-comments-invited-part-2-tp157019p157057.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: Weirdness With Fonts and Font Tree Snippet
On 1/3/14 9:57 AM, "Joshua Nichols" wrote: > >On Fri, Jan 3, 2014 at 10:53 AM, Federico Bruni >wrote: > >open the terminal of Mac and write: > >lilypond -dshow-available-fonts > > > > >I got: >-bash: lilypond: command not found On the mac, lilypond is not in a directory that's part of your path. Instead, it's in a subdirectory of your LilyPond application. The command you would use is /Applications/your-Lilypond-version.app/Contents/Resources/bin/lilypond -dshow-available-fonts where you replace your-Lilypond-version.app with the file name of your lilypond application. (Of course, this assumes that your Lilypond.app is in the /Applications folder. If not, you'll need to change the path accordingly.) HTH, Carl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: when is 2.19 going to be released?
Kieren MacMillan writes: > Hi Phil, > >> Well, you need to compile your own version then :-) > > I have VirtualBox and Lilybuntu and Janek’s script installed. > The problem is, there are 437.5 “versions of Lilypond" in git, and I > don’t know which I should compile. :-p Verified bleeding edge is called master. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: when is 2.19 going to be released?
Kieren MacMillan writes: > Hello all, > > Now that 2.18 has been released (kudos, by the way!!!), when is the > unstable branch going to be updated? What do you mean, "updated"? There are a lot of changes in the unstable branch already. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
Colin Tennyson writes: > To use another analogy: our choir conductor sometimes asks in mild > exasparation: "Sing _something_ , never mind you're not sure. If you sing > the wrong note I can correct it, but if you don't sing at all I'm dead in > the water." > > So, in asking questions here on this forum I allow myself to err on the side > of pushing. > > (I'm not a programmer, but as you can tell from the terminology I picked up > I have been reading up on general principles of programming.) > > > In order to learn the LilyPond environment, I feel I need to know the > concepts that have guided how Lilypond is implemented. Contexts, properties and engravers are described in the Usage manual. Be sure to read the latest version as there have been quite a few improvements. > Why do I see side by side two keywords for setting properties: \set > and \override. That is explained in the manual. > I have seen environments where every property that is by nature ON/OFF is > controlled with a boolean variable. That is straightforward, that helps to > make the enviroment learnable. > > Why do I see side by side several ways of toggling ON/OFF? > I see "\hide" "\undo \hide" If you prefer, you can override the transparency property of a grob with #t and #f. \hide is just a convenience function. > I see "consists" "\remove" > I see "##t" and "##f" > > I wonder, how did the development of LilyPond end up with the syntax and > keyword set that it now has? The change log files are available, and so are the archives of the developer and user lists. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: when is 2.19 going to be released?
On 1/3/14 9:26 AM, "David Kastrup" wrote: >Kieren MacMillan writes: > >> Hello all, >> >> Now that 2.18 has been released (kudos, by the way!!!), when is the >> unstable branch going to be updated? > >What do you mean, "updated"? There are a lot of changes in the unstable >branch already. I believe that the question might be better stated as "When will a new development release be made?" Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Numbers over double percent repeats
Am 03.01.2014 16:17, schrieb Daniel Rosen: -Original Message- [...] Nope, that gives me a 2 over the first percent and a 3 over the second. I need both of them to have a 2. Ah, ok, sorry, I misunderstood your request completely. Perhaps http://lsr.dsi.unimi.it/LSR/Item?id=883 is of some use? HTH, Marc ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Weirdness With Fonts and Font Tree Snippet
On 1/3/14 10:33 AM, "Carl Sorensen" wrote: > > >On 1/3/14 9:57 AM, "Joshua Nichols" wrote: > >> >>On Fri, Jan 3, 2014 at 10:53 AM, Federico Bruni >>wrote: >> >>open the terminal of Mac and write: >> >>lilypond -dshow-available-fonts >> >> >> >> >>I got: >>-bash: lilypond: command not found Another way to do it is to create a lilypond file that contains #(ly:font-config-display-fonts) and typeset it. You will get a list of the fonts in the log window. HTH, Carl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Another time model (related to the usability thread)
Hi Keith, Would \combineAt (measure moment/fraction) \base-music \new-music be a more intuitive — and ultimately useful — syntax? You could also have a \insertAt (measure moment/fraction) \base-music \new-music which would insert something (instead of simultaneous-ing it). The big downside, of course, would be that if the number of measures before that point changed, you’d have to update all of those references; using \tag would avoid that problem. The big downside with \tag is that you need to fill up the content with \tag locations for every possible addition/insertion; this ultimately eliminates the possibility of real content-presentation separation, which \addAt would allow. Of course, having both would be great — but for my money, the ability to \addAt something post-hoc (i.e., without “a priori” \tag-ging) is the power tool. Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Weirdness With Fonts and Font Tree Snippet
> Another way to do it is to create a lilypond file that contains > > #(ly:font-config-display-fonts) > > and typeset it. You will get a list of the fonts in the log window. Nice. The OP talked about `GUI'; I assume he means Frescobaldi. Maybe such a command could be added to its menu system, to aid people having problems with fonts. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
>> Why do I see side by side two keywords for setting properties: \set >> and \override. > > That is explained in the manual. With the promising caption "\set versus \override" and no content: http://www.lilypond.org/doc/v2.18/Documentation/notation/set-versus-override The preceding sections are helpful though. Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: why you don't contribute to Mutopia
Am 03.01.2014 07:56, schrieb Frédéric Bron: >> I'd like to have some feedback from you. Which change in the Mutopia >> interface/decisions would make you start contributing or contributing more? > > I wanted to contribute with the 4th symphony of Schumann which was > ready to be submitted. I had spent some time to adjust the page layout > for A4 paper format and was not ready to spend more time to target the > letter paper format. The requirement to not specify the paper format and have both A4 and letter supported is nice in theory. And it is good that LP has good defaults for both. In practice, for almost every score, the layout settings depend on the paper format to make it really looking good. Therefore, IMHO, both A4 and letter contributions could be accepted by Mutopia without the other. If I (as a user) really want a score which is available as US letter only, I can do the tweaks myself to fit nicely on my A4 paper (and vice versa) and I am better off if it exists in the other format than starting from scratch. Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Numbers over double percent repeats
Am 03.01.2014 18:32, schrieb Marc Hohl: Am 03.01.2014 16:17, schrieb Daniel Rosen: -Original Message- [...] Nope, that gives me a 2 over the first percent and a 3 over the second. I need both of them to have a 2. Ah, ok, sorry, I misunderstood your request completely. Perhaps http://lsr.dsi.unimi.it/LSR/Item?id=883 is of some use? D'oh, I should read the details, this doesn't work either :-( Marc ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: when is 2.19 going to be released?
> I believe that the question might be better stated as > "When will a new development release be made?” Yes. That. =) Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
Noeck writes: >>> Why do I see side by side two keywords for setting properties: \set >>> and \override. >> >> That is explained in the manual. > > With the promising caption "\set versus \override" and no content: > http://www.lilypond.org/doc/v2.18/Documentation/notation/set-versus-override Having spent quite a bit of time writing this section and making it as accurate as I can, I consider the sweeping characterization as "no content" rather impolite. Please try offering more constructive criticism. It has been on review as http://code.google.com/p/lilypond/issues/detail?id=3649>. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
Am 03.01.2014 19:20, schrieb David Kastrup: Noeck writes: Why do I see side by side two keywords for setting properties: \set and \override. That is explained in the manual. With the promising caption "\set versus \override" and no content: http://www.lilypond.org/doc/v2.18/Documentation/notation/set-versus-override Having spent quite a bit of time writing this section and making it as accurate as I can, I consider the sweeping characterization as "no content" rather impolite. Please try offering more constructive criticism. Well, clicking at the link above loads a page with a caption only and no content, at least in the german version. Marc It has been on review as http://code.google.com/p/lilypond/issues/detail?id=3649>. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
Hi David and Phil, I now realize that this is an issue with the translation. My browser redirects me automatically to the German version: http://www.lilypond.org/doc/v2.18/Documentation/notation/set-versus-override.de.html I now see that the English version of that page indeed has content that I will read now. Sorry for the misunderstanding! Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning LilyPond, comments invited
Hi Colin, Am 03.01.2014 15:35, schrieb Colin Tennyson: > Alex Loomis-2 wrote >> From what I've seen, \cadenzaOn seems to be the preferred way of writing >> unmeasured music. > > Well, the availability of "\hide \BarLine" and "\undo \hide \BarLine" is > relatively recent. > I think I saw a place where it was described in the v2.17 documentation, but > not in the v2.16 documentation But please be aware that hiding just means that the barline is not visible. It still takes space and the timing is still in place and checked. To really leave out the barline, you can \omit it (or BarLine.stencil = ##f). Even then this only affects the optical output. And you still have your 4/4 measure (or what ever) that needs to be satisfied. \cadenzaOn only affects the timing: cadenzaOn = \set Timing.timing = ##f cadenzaOff = \set Timing.timing = ##t And I think this what you want. You don't loose the accidental handling - it is just adapted. Remembering the accidentals until the barline just does not make sense without a barline. How long would you like to remember it? Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
Am 03.01.2014 19:20, schrieb David Kastrup: > Noeck writes: > Why do I see side by side two keywords for setting properties: \set and \override. >>> >>> That is explained in the manual. >> >> With the promising caption "\set versus \override" and no content: >> http://www.lilypond.org/doc/v2.18/Documentation/notation/set-versus-override > > Having spent quite a bit of time writing this section and making it as > accurate as I can, I consider the sweeping characterization as "no > content" rather impolite. Please try offering more constructive > criticism. I didn't want to offend you. For me this page is *really empty*! With no content I mean literally no content. Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
Marc Hohl writes: > Am 03.01.2014 19:20, schrieb David Kastrup: >> Noeck writes: >> > Why do I see side by side two keywords for setting properties: \set > and \override. That is explained in the manual. >>> >>> With the promising caption "\set versus \override" and no content: >>> http://www.lilypond.org/doc/v2.18/Documentation/notation/set-versus-override >> >> Having spent quite a bit of time writing this section and making it as >> accurate as I can, I consider the sweeping characterization as "no >> content" rather impolite. Please try offering more constructive >> criticism. >> > Well, clicking at the link above loads a page with a caption only and > no content, at least in the german version. The German translation is probably at least a year behind, some parts more. The translations that seem to have kept up with 2.18 reasonably well are the Spanish, Italian and French translations, probably in that order. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Numbers over double percent repeats
Am 03.01.2014 19:08, schrieb Marc Hohl:
Am 03.01.2014 18:32, schrieb Marc Hohl:
Am 03.01.2014 16:17, schrieb Daniel Rosen:
-Original Message-
[...]
Nope, that gives me a 2 over the first percent and a 3 over the
second. I need both of them to have a 2.
Ah, ok, sorry, I misunderstood your request completely.
Perhaps
http://lsr.dsi.unimi.it/LSR/Item?id=883
is of some use?
D'oh, I should read the details, this doesn't work either :-(
A bit hackish, but it works:
\version "2.19.0"
\score {
\new Staff {
\set countPercentRepeats = ##t
\override PercentRepeatCounter.stencil = #(lambda (grob)
(grob-interpret-markup grob (markup "1")))
\override DoublePercentRepeatCounter.stencil = #(lambda (grob)
(grob-interpret-markup grob (markup "2")))
\repeat percent 5 { e4 e e e } |
\repeat percent 5 { f4 f f f |
d4 d d d } |
}
}
Marc
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Weirdness With Fonts and Font Tree Snippet
> > Nice. The OP talked about `GUI'; I assume he means Frescobaldi. > Maybe such a command could be added to its menu system, to aid people > having problems with fonts. Yes, I was talking about Frescobaldi, but also LilyPond's native interface, more specifically. The drop down menus do not contain anything beyond the "typeset file" and "edit" features. IC, Josh On Fri, Jan 3, 2014 at 11:58 AM, Werner LEMBERG wrote: > > > Another way to do it is to create a lilypond file that contains > > > > #(ly:font-config-display-fonts) > > > > and typeset it. You will get a list of the fonts in the log window. > > Nice. The OP talked about `GUI'; I assume he means Frescobaldi. > Maybe such a command could be added to its menu system, to aid people > having problems with fonts. > > > Werner > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Weirdness With Fonts and Font Tree Snippet
> > Another way to do it is to create a lilypond file that contains > #(ly:font-config-display-fonts) This was very helpful. That is a nice tip. IC, Josh On Fri, Jan 3, 2014 at 11:53 AM, Carl Sorensen wrote: > > > On 1/3/14 10:33 AM, "Carl Sorensen" wrote: > > > > > > >On 1/3/14 9:57 AM, "Joshua Nichols" wrote: > > > >> > >>On Fri, Jan 3, 2014 at 10:53 AM, Federico Bruni > >>wrote: > >> > >>open the terminal of Mac and write: > >> > >>lilypond -dshow-available-fonts > >> > >> > >> > >> > >>I got: > >>-bash: lilypond: command not found > > > Another way to do it is to create a lilypond file that contains > > #(ly:font-config-display-fonts) > > and typeset it. You will get a list of the fonts in the log window. > > HTH, > > Carl > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Weirdness With Fonts and Font Tree Snippet
On 1/3/14 10:58 AM, "Werner LEMBERG" wrote: > >> Another way to do it is to create a lilypond file that contains >> >> #(ly:font-config-display-fonts) >> >> and typeset it. You will get a list of the fonts in the log window. > >Nice. The OP talked about `GUI'; I assume he means Frescobaldi. >Maybe such a command could be added to its menu system, to aid people >having problems with fonts. I assumed he meant the LilyPad editor that shows up on the Mac when you click on the LilyPond icon. Carl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
fernapp: for accessing Linux desktop applications in a web browser
Off-topic: I recently came across fernapp[1] which lets you run Linux desktop applications (like LibreOffice) in a web browser. The code is Java and is licensed under the GPL. Perhaps it might be of interest to anyone wanting to set up something like LilyBin[2] (by making Frescobaldi usable through a browser?) in order to make it easy for people to try out LilyPond without installing anything, or to use it on a tablet, etc... Or possibly for some future version of the LSR or the LilyPond website? [1] http://www.fernapp.com/ [2] http://lilybin.com/ -Paul ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
the "ly" tool (was Re: code formatting)
Op Thu, 02 Jan 2014 08:16:15 +0100 Noeck schreef: > is the lilypond code formatting that Frescobaldi does also available > as a commandline tool? Not yet, but it is being actively worked on these days, by me. It will become a Python library named 'python-ly' with a commandline tool called 'ly' that can perform many of the tasks that Frescobaldi provides. Such as indent, format, but also transpose, translate, etc. It will also be possible to import ly from other Python applications to get access to everything just as inside Frescobaldi. The python-ly module will only depend on Python itself. Best regards, Wilbert (Frescobaldi author and main developer) -- Wilbert Berendsen (http://www.wilbertberendsen.nl) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: the "ly" tool (was Re: code formatting)
Cool. I am looking forward to it. Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Learning Lilypond, comments invited - part 2
- Original Message - From: "Noeck" To: "David Kastrup" ; Cc: Sent: Friday, January 03, 2014 6:30 PM Subject: Re: Learning Lilypond, comments invited - part 2 Hi David and Phil, I now realize that this is an issue with the translation. My browser redirects me automatically to the German version: http://www.lilypond.org/doc/v2.18/Documentation/notation/set-versus-override.de.html I now see that the English version of that page indeed has content that I will read now. Sorry for the misunderstanding! Joram If you're a native German speaker and want to contribute to LilyPond development, you could help by translating pages like this. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: the "ly" tool (was Re: code formatting)
On Fri, 3 Jan 2014, Wilbert Berendsen wrote: The python-ly module will only depend on Python itself. And frescobaldi will depend on the python-ly module I guess? Will it be "shipped" separately, or together? Anyway, the idea sounds promising. -- MT ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: the "ly" tool (was Re: code formatting)
Martin Tarenskeen writes: > On Fri, 3 Jan 2014, Wilbert Berendsen wrote: > >> The python-ly module will only depend on Python itself. > > And frescobaldi will depend on the python-ly module I guess? > Will it be "shipped" separately, or together? > > Anyway, the idea sounds promising. Hm. If it is an independent, standalone module, I wonder whether it would not make more sense to develop the independent, standalone module in GUILE running inside of a copy of LilyPond. Of course, the downside is that this is not robust against partially correct input. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Weirdness With Fonts and Font Tree Snippet
> > I assumed he meant the LilyPad editor that shows up on the Mac when you > click on the LilyPond icon. This is what I meant. Sorry for the weird (typing quickly and on the fly). IC, Josh On Fri, Jan 3, 2014 at 1:18 PM, Carl Sorensen wrote: > > > On 1/3/14 10:58 AM, "Werner LEMBERG" wrote: > > > > >> Another way to do it is to create a lilypond file that contains > >> > >> #(ly:font-config-display-fonts) > >> > >> and typeset it. You will get a list of the fonts in the log window. > > > >Nice. The OP talked about `GUI'; I assume he means Frescobaldi. > >Maybe such a command could be added to its menu system, to aid people > >having problems with fonts. > > I assumed he meant the LilyPad editor that shows up on the Mac when you > click on the LilyPond icon. > > Carl > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Numbers over double percent repeats
> -Original Message-
> From: Marc Hohl [mailto:m...@hohlart.de]
> Sent: Friday, January 03, 2014 1:25 PM
> To: Daniel Rosen; lilypond-user@gnu.org
> Subject: Re: Numbers over double percent repeats
>
> Am 03.01.2014 19:08, schrieb Marc Hohl:
> > Am 03.01.2014 18:32, schrieb Marc Hohl:
> >> Am 03.01.2014 16:17, schrieb Daniel Rosen:
> -Original Message-
> >> [...]
> >>>
> >>> Nope, that gives me a 2 over the first percent and a 3 over the
> >>> second. I need both of them to have a 2.
> >>
> >> Ah, ok, sorry, I misunderstood your request completely.
> >>
> >> Perhaps
> >>
> >> http://lsr.dsi.unimi.it/LSR/Item?id=883
> >>
> >> is of some use?
> >
> > D'oh, I should read the details, this doesn't work either :-(
>
> A bit hackish, but it works:
>
> \version "2.19.0"
>
> \score {
>\new Staff {
>\set countPercentRepeats = ##t
>\override PercentRepeatCounter.stencil = #(lambda (grob)
> (grob-interpret-markup grob (markup "1")))
>\override DoublePercentRepeatCounter.stencil = #(lambda (grob)
> (grob-interpret-markup grob (markup "2")))
>\repeat percent 5 { e4 e e e } |
> \repeat percent 5 { f4 f f f |
> d4 d d d } |
>}
> }
>
>
> Marc
Works for me. Thanks!
DR
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: the "ly" tool (was Re: code formatting)
Il 03/gen/2014 20:39 "Wilbert Berendsen" ha scritto:. > > It will become a Python library named 'python-ly' with a commandline > tool called 'ly' that can perform many of the tasks that Frescobaldi > provides. Such as indent, format, but also transpose, translate, etc. > Code highlight also? (for lilypond-book) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
\override NoteHead.style in drummode
How can I get just the whole note in the example below to use the xcircle
style? \once \override NoteHead.style = #'xcircle doesn't work.
\version "2.18.0"
#(define mydrums '((crashcymbal cross #f6)))
\drums {
\set drumStyleTable = #(alist->hash-table mydrums)
cymc4 cymc cymc cymc |
cymc1 |
}
DR
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: \override NoteHead.style in drummode
> -Original Message-
> From: Daniel Rosen
> Sent: Friday, January 03, 2014 7:48 PM
> To: lilypond-user@gnu.org
> Subject: \override NoteHead.style in drummode
>
> How can I get just the whole note in the example below to use the xcircle
> style? \once \override NoteHead.style = #'xcircle doesn't work.
>
> \version "2.18.0"
> #(define mydrums '((crashcymbal cross #f6)))
> \drums {
> \set drumStyleTable = #(alist->hash-table mydrums)
> cymc4 cymc cymc cymc |
> cymc1 |
> }
>
> DR
>
Please disregard the above--figured it out on my own.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Changing the thickness of clusters
I am currently typesetting a piece that has a pre-recorded track, and I'm cuing things via the track. I decided to use \makeCluster to form a continuous line... Is there a way to make the line thinner? I tried using \teeny in both the \score block and my pre-existing variables (one named cluster and the other clusters), but alas... no change. Thanks! Sincerely, Josh ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Changing the thickness of clusters
I am absolutely baffled by this question. And after writing an extensive reply it occurred to me that it might be simplest to reduce the note head sizes. Tried it that does not work either. But it does work to reduce the interval width down to a single note. That is as simple as it gets with out some other trickery. Anyway best of luck. What on earth are clusters good for anyway? Aleatoric strangeness. Shane On Fri, Jan 3, 2014 at 9:37 PM, Joshua Nichols wrote: > I am currently typesetting a piece that has a pre-recorded track, and I'm > cuing things via the track. > > I decided to use \makeCluster to form a continuous line... > > Is there a way to make the line thinner? I tried using \teeny in both the > \score block and my pre-existing variables (one named cluster and the other > clusters), but alas... no change. > > Thanks! > > Sincerely, > > Josh > > ___ > 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: Changing the thickness of clusters
> > I am absolutely baffled by this question. Tell me about it. ...it might be simplest to reduce > the note head sizes. Tried it that does not work either. Same here. What on earth are clusters good for anyway? Aleatoric strangeness. You are right, and I am definitely not a fan nor in agreement with clusters and other types of graphical notation, but I am working for people who do favor them, and I need to be able to do at least some of it (I draw the line at hand-drawn graphs like Crumb and Cage, where even the publishers wouldn't touch it). But, this kind of notation is really useful for outlining general cues in pre-recorded tracks (hence my email). But, I understand if this has "never" been asked before; It would be cool to see where LilyPond takes in that direction. We definitely have competition; Finale 2014 can apparently "do it all" and can compose stuff like George Crumb stuff. Has anyone thought about this? About advanced Contemporary Music? What about our (somewhat) competitive brother "Belle, Bonne, Sage"? On Fri, Jan 3, 2014 at 11:38 PM, Shane Brandes wrote: IC, Josh ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
