Re: TimeSignature Event
Thank you Neil,
now I created the following time-signature engraver:
--snip--
\version 2.14.2
#(define-public orff (lambda (context)
(let ((time-signature '())
(last-fraction #f))
`((process-music
. ,(lambda (trans)
(let ((frac (ly:context-property context
'timeSignatureFraction)))
(if (and (null? time-signature)
(not (equal? last-fraction frac))
(pair? frac))
(begin
(set! time-signature
(ly:engraver-make-grob trans 'TimeSignature '()))
(set! (ly:grob-property
time-signature 'fraction) frac)
(set! (ly:grob-property
time-signature 'stencil) ly:text-interface::print)
(set! (ly:grob-property
time-signature 'text)
(markup #:translate '(0 . 2)
#:concat (
#:bold (format ~a
(car frac))
#:translate '(-2 . -2)
#:draw-line '(3 . 3)
#:translate '(-2 . -3.5)
#:smaller #:smaller #:note (format ~a (cdr frac)) UP)
))
(and (not last-fraction)
(set! (ly:grob-property
time-signature 'break-visibility)
(ly:context-property
context 'implicitTimeSignatureVisibility)))
(set! last-fraction frac))
(stop-translation-timestep
. ,(lambda (trans)
(set! time-signature '()
)))
meta = {
\key bes \major \time 3/4 s2.*2
\key a \minor \time 5/8 s8*5
\key bes \major \time 3/4 s2.*2
}
mel = \relative c'' {
a8 bes c d c d | a bes c d c d | a c d c d | ees d c bes a bes | ees
d c bes a bes |
}
\score {
\new StaffGroup
\new Dynamics \with {
\consists \orff
\override TimeSignature #'extra-offset = #'(-1 . 0)
} { \meta }
\new Staff \with {
\remove Time_signature_engraver
}
\meta
\new Voice = mel { \mel } % e-mail-compatible line breaks ;-)
}
--snip--
I will optimize and use overrides for this engraver - the markup is a
first shot. If I have time and/or a need, I will look for another
context than Dynamics.
Cheers,
Jan-Peter
Am 13.08.2011 16:31, schrieb Neil Puttock:
On 13 August 2011 10:27, Jan-Peter Voigtjp.vo...@gmx.de wrote:
So my question is: How do I catch the right event and get the time sig probs to
display?
There's no event* for time signatures; they're generated when certain
context properties change.
See the scheme engraver I posted here for an idea:
http://lists.gnu.org/archive/html/lilypond-user/2011-05/msg00468.html
* there is a music object (TimeSignatureMusic), but that's only used
for iteration so the relevant settings are accessible by
\displayLilyMusic
Cheers,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Misleading autobeaming in 3/4
Ok, I'll keep LilyPond's default beaming since it's the usual notation. Thanks! Bertrand ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: font tree setting ignored
Am 2011-08-09 um 21:39 schrieb Matthew Collett:
LilyPond 2.14.x (tested .0 and .2) on OSX-Intel ignores my font
settings like
\paper {
#(define fonts (make-pango-font-tree TeX Gyre Schola LMSans10
LMTypewriter10 Regular (/ 14 20)))
}
The font names are exactly the same as I get with lilypond -dshow-
available-fonts any, and it used to work with 2.13.x. I can't
tell when it stopped.
Of course I tried a bunch of other fonts, it never changes.
Where do these fonts live? User library, main library or somewhere
else? As I reported to this list about a month ago, Lilypond
(2.14.1) is not aware of the fonts in the user library (Mac OS X
10.6.8). It seems to be a simple omission from fonts.conf, which
has entries for the shared library fonts (dir/Library/Fonts/dir)
and the system fonts (dir/System/Library/Fonts/dir) but not the
user fonts (dir~/Library/Fonts/dir).
I adapted fonts.conf to my needs, to include also FontExplorer and TeX
directories.
I tried only fonts that were reported by lilypond -dshow-available-
fonts any (others can’t work), and it doesn’t seem to depend on the
format (TrueType, OpenType; I don’t use PostScript any more). – Oh, in
an other project I'm using a Type1 font, and that does work!
I also have a slightly different font problem, perhaps closer to
yours, which is that requesting plain Helvetica gives me bold
Helvetica instead (only this one font as far as I know; others, e.g.
Helvetica Neue, are fine). I have no idea why this happens.
Are both in LilyPond’s (i.e. pango’s) list?
Am 2011-08-12 um 15:00 schrieb flup2:
I've the same problem. It doesn't seem to depend of the location of
the font
(mine are all in the same folder). I deleted OS X font cache as well
as
lilypond font cache.
When compiling, I have 3 situations, dependding the font I use :
- it works (TeX Gyre fonts or Futura, for instance)
- it doesn't, but without console message (Times New Roman, for
instance)
- it doesn't and shows a message échec de « (fondu -force
/Library/Fonts/[name of the font]) » (256)
I guess it's related to OS X Lion (knowing I also have problems with
XeLaTeX).
I’m on OSX 10.5.8 (Leopard), so it doesn’t seem to be a 10.7 (Lion)
problem (alone).
Greetlings from Lake Constance
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net
http://angerweit.tikon.ch/lieder/
https://www.cacert.org (I'm an assurer)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: TimeSignature Event
On 14 August 2011 08:48, Jan-Peter Voigt jp.vo...@gmx.de wrote: I will optimize and use overrides for this engraver - the markup is a first shot. If I have time and/or a need, I will look for another context than Dynamics. I don't think you need a new engraver for this; overriding the stencil should suffice since the time signature fraction is passed to TimeSignature via the property 'fraction: \override TimeSignature #'stencil = #(lambda (grob) (let ((frac (ly:grob-property grob 'fraction))) (grob-interpret-markup grob (markup #:translate '(0 . 2) #:concat ( #:bold (format ~a (car frac)) #:translate '(-2 . -2) #:draw-line '(3 . 3) #:translate '(-2 . -3.5) #:smaller #:smaller #:note (format ~a (cdr frac)) UP) Cheers, Neil ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: TimeSignature Event
Am 14.08.2011 um 12:52 schrieb Neil Puttock: I don't think you need a new engraver for this; overriding the stencil should suffice since the time signature fraction is passed to TimeSignature via the property 'fraction: Of course, I came via the scheme-engraver-street and didn't saw the simpler solution for this special case. Thanks again :-) Well, I have a feeling, that once I will need to write my own engraver ;-) Cheers, Jan-Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Font problem with fink compiled lilypond
Hi, I've been compiling lilypond with fink (MacOS X 10.6) for two years. Since a update about one year ago I didn't track down, I have some trouble with some unicode characters (in that case 0x266D which is a flat sign). The binary version works with the same chars. The advantage of the fink compiled version is that it is 2-4 times faster. I guess it's a fink, font cache, font library, font problem. May be you hint which library should I look into for this problem. Does anyone have a dependency list for lilypond? Here are the messages I get in the console: warning: no PostScript font name for font `/usr/X11R6/lib/X11/fonts/misc/10x20.pcf.gz' warning: FreeType face has no PostScript font name programming error: Improbable offset for stencil: -inf staff space Thanks, Jean-Alexis ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Misleading autobeaming in 3/4
On 8/13/11 2:55 PM, Bertrand Bordage bordage.bertr...@gmail.com wrote:
Hi everyone!
(I don't know if we can call this a defect, so I don't send it to bug-lilypond
for the moment)
I am working on a 3/4 score with this rhythmical pattern in the beginning :
4. 8 8 8.
It is repeated five times, but the rest of the score is clearly in 3/4 and not
6/8, contrary to what this pattern suggests.
It is therefore important to have a beaming that suggests 3/4, even if it's
already written at the beginning.
But here's what happens:
%%%
\markup This:
\relative c'' { \time 3/4 a4. b8 c d e d c b4. a8 b c d c b a2. }
\markup looks like 6/8:
\relative c'' { \time 6/8 a4. b8 c d e d c b4. a8 b c d c b a2. }
\markup but should be like this:
\relative c'' { \time 3/4 a4. b8\noBeam c d e d c\noBeam b4. a8 b c d c b a2.
}
%%%
IMO this *is* a bug for default beaming. The engraving sources (Stone,
Read, Gould) are pretty united in saying that you should not beam 3/4 to
look like 6/8.
I'm not sure what's going on with the Chopin and Brahms beaming that looks
like LilyPond's current default.
Please report to bug-lilypond.
Thanks,
Carl
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Misleading autobeaming in 3/4
Carl Sorensen c_soren...@byu.edu writes:
On 8/13/11 2:55 PM, Bertrand Bordage bordage.bertr...@gmail.com wrote:
Hi everyone!
(I don't know if we can call this a defect, so I don't send it to
bug-lilypond
for the moment)
I am working on a 3/4 score with this rhythmical pattern in the beginning :
4. 8 8 8.
It is repeated five times, but the rest of the score is clearly in 3/4 and
not
6/8, contrary to what this pattern suggests.
It is therefore important to have a beaming that suggests 3/4, even if it's
already written at the beginning.
But here's what happens:
%%%
\markup This:
\relative c'' { \time 3/4 a4. b8 c d e d c b4. a8 b c d c b a2. }
\markup looks like 6/8:
\relative c'' { \time 6/8 a4. b8 c d e d c b4. a8 b c d c b a2. }
\markup but should be like this:
\relative c'' { \time 3/4 a4. b8\noBeam c d e d c\noBeam b4. a8 b c d c b a2.
}
%%%
IMO this *is* a bug for default beaming. The engraving sources (Stone,
Read, Gould) are pretty united in saying that you should not beam 3/4 to
look like 6/8.
I'm not sure what's going on with the Chopin and Brahms beaming that looks
like LilyPond's current default.
Please report to bug-lilypond.
The problem here is that I don't see us having the data structures
needed for getting proper beaming. Where I don't see means I don't
understand automatic beaming rules and exceptions enough in order to say
for sure.
Eighth notes in 3/4 measures are usually beamed in groups of 6.
However, if you don't get a complete group of 6 together (where a
subdivided beam is ok), the pattern falls apart into 2+2+2.
So the defaults should look like [8 8 8 8 8 8] and even [8. 16 8 8 8 8],
but 4. [8 8 8] is wrong and needs to be 4. 8 [8 8] instead.
6/8 would have [8 8 8] [8 8 8], [8. 16 8] [8 8 8] and 4. [8 8 8],
respectively.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Misleading autobeaming in 3/4
On Sun, 2011-08-14 at 12:00 -0400, lilypond-user-requ...@gnu.org wrote: So the defaults should look like [8 8 8 8 8 8] and even [8. 16 8 8 8 8], but 4. [8 8 8] is wrong and needs to be 4. 8 [8 8] instead. 6/8 would have [8 8 8] [8 8 8], [8. 16 8] [8 8 8] and 4. [8 8 8], respectively. -- David Kastrup Hi All, I must add that (I am speaking as a living composer, for what that is worth these days), the above question has more to do with phrasing and tempo. I write the 4. [8 8 8] with musical textures that are developing rapidly with a fast tempo, and I write 4. 8 [8 8] when things are developing slowly. Also, it depends upon the other parts of the music, if there are further simultaneous subdivisions. But, it is mainly because of phrasing. Brahms and Chopin expedited their notation. Didn't Chopin and Brahms write 4. [8 8 8]? Craig Bakalian ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Font problem with fink compiled lilypond
Am 2011-08-14 um 14:22 schrieb Jean-Alexis Montignies: I've been compiling lilypond with fink (MacOS X 10.6) for two years. Since a update about one year ago I didn't track down, I have some trouble with some unicode characters (in that case 0x266D which is a flat sign). The binary version works with the same chars. The advantage of the fink compiled version is that it is 2-4 times faster. I guess it's a fink, font cache, font library, font problem. May be you hint which library should I look into for this problem. Does anyone have a dependency list for lilypond? LilyPond's font handling is via pango, freetype2 is probably a dependency. Doesn't have fink a command to list dependencies for packages? Perhaps there are different varieties of pango/freetype? (I use MacPorts, and there are some ports that you can install with different options.) Here are the messages I get in the console: warning: no PostScript font name for font `/usr/X11R6/lib/X11/fonts/ misc/10x20.pcf.gz' It's improbable that you want to use an X11 font with LilyPond. I can't imagine why that comes across. What's your custom font setup? warning: FreeType face has no PostScript font name programming error: Improbable offset for stencil: -inf staff space Greetlings from Lake Constance --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
lyricMelismaAlignment parameter type change?
Hello all, When did lyricMelismaAlignment begin to require an exact integer? My 2.13 scores with #-0.9 as the setting are throwing errors in 2.15.8 — feature or bug? Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lyricMelismaAlignment parameter type change?
On 14 August 2011 22:07, Kieren MacMillan kieren_macmil...@sympatico.ca wrote: When did lyricMelismaAlignment begin to require an exact integer? My 2.13 scores with #-0.9 as the setting are throwing errors in 2.15.8 — feature or bug? Where are you setting it? If it's inside a \layout block, then we've recently introduced strict type checking which only used to apply to music blocks. lyricMelismaAlignment's always had the type `ly:dir?' so it expects -1, 0 or 1. This is a bit silly though, since all it does is override LyricText #'self-alignment-X, which has the type `number?'. Will fix shortly. Cheers, Neil ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Font problem with fink compiled lilypond
Here are the messages I get in the console: warning: no PostScript font name for font `/usr/X11R6/lib/X11/fonts/misc/10x20.pcf.gz' It's improbable that you want to use an X11 font with LilyPond. To be more precise: LilyPond only handles outline fonts. A proper filter to ensure that is still missing. Reason is that the FontConfig interface doesn't provide a means to implement it. IIRC, there is already a bug tracker issue which covers this. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
use default directions for \voiceN?
Hi everyone, I'm new to lilypond, so sorry if this is a simple question, but I wasn't able to find an answer in either the documentation or the archives. I have a piece which is mostly monophonic, but occasionally has another voice. Up until now I have been using \\ to split the voices as needed, but it's awkward for several reasons. One is that lilypond won't tie notes across what it considers separate voices. So when switch from \oneVoice to having two voices, it doesn't know that \voiceOne is actually the same voice as the one in \oneVoice. The other thing is that due to pick up notes and the like, it becomes awkward to factor out repeated patterns. Both of these problems should be solved if I switch to using two voices throughout. However, it's quite ugly to have all the stems forced in a certain direction and rests in odd places for long stretches of music that effectively only has one voice. Ideally I could write everything as two voices, but with a setting that says if I measure has visible notes from one voice only (say all the others have 's' hidden rests), then to treat it as a \oneVoice for the purpose of beam direction and rest placement. Or, simpler, a way to override beam direction for a voice to restore automatic directions within a given expression. I'm guessing both of these are possible, but I don't know quite the right knobs to tweak to modify a voice in this way. And I imagine it must be a fairly common problem, so surely someone else has already done something like this? thanks in advance! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: use default directions for \voiceN?
Hi Evan,
I'm guessing both of these are possible, but I don't know quite the
right knobs to tweak to modify a voice in this way. And I imagine it
must be a fairly common problem, so surely someone else has already
done something like this?
Instantiate the voices explicitly:
\relative g' {
g4 a b c ~ |
{ \voiceOne c4 d e f } \new Voice { \voiceTwo a,2 a } \oneVoice
}
Hope this helps!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: use default directions for \voiceN?
On Sun, Aug 14, 2011 at 7:27 PM, Kieren MacMillan
kieren_macmil...@sympatico.ca wrote:
Hi Evan,
I'm guessing both of these are possible, but I don't know quite the
right knobs to tweak to modify a voice in this way. And I imagine it
must be a fairly common problem, so surely someone else has already
done something like this?
Ha, I should really do more research. Just a bit more archive
trolling turned up \stemNeutral, which appears to be just what I want.
Looking at the code in there makes a lot of things clearer.
Instantiate the voices explicitly:
\relative g' {
g4 a b c ~ |
{ \voiceOne c4 d e f } \new Voice { \voiceTwo a,2 a } \oneVoice
}
Right, my problem was getting a tie from the end of voiceTwo to tie
into the beginning of oneVoice. It didn't want to tie even when the
notes were the same pitch. But keeping them as two voices solves the
problem, and \stemNeutral deals with the ugliness of staying in two
voices when one is silent. So I think I'm good now, thanks :)
While I'm here... assignment in lilypond makes macros, but they
don't take arguments. However, it's very common for music to repeat
except a little bit at the end, or a few notes in the middle or
something. It looks like you can do full on functions by dropping
down into scheme, but then you (apparently?) lose the nice syntax. Is
there a nice way to factor almost the same chunks of music? Also,
the traditional kind of macro expansion requires you to know
beforehand where all the holes are to fill and provide them
explicitly, and that doesn't apply so well to music.
Also it feels like I would like some kind of negative start time for
pick-ups, so I could say e.g.
partTwo =
\new Voice { \voiceOne { ... } }
\new Voice { \voiceTwo { \pickup 1 measure { 2s c4 c | ... } } }
music = { \partOne \partTwo }
This way the pickup from partTwo would overlap with the end of
partOne. Otherwise, you have to split the parts up in a somewhat
unnatural way, just to insert a partOnePointFive that mixes the pickup
of partTwo with the tail of partOne. And that leads to more messiness
if you have a rondo kind of A B C B D B thing. Does that make sense?
Am I doing it wrong?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Setting arbitrary filename for .midi
I'm working with a multi-score lilypond file. I'd like to be able to set arbitrary filenames for each midi, instead of having lilypond derive the midi filenames from the .ly filename. Am I not searching in the right places, or maybe I should log this as a feature request? Thx, Javier Ruiz___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
