Re: Problem with Fonts too big
Hi Bernard, > Hard to say what is the cause. You could try clearing your font cache with > > fc-cache -r -v > > as root. thank you for your suggestion. Unfortunately no visible change though. What seems strange is that all stuff except "regular" characters is rendered as supposed to. Only dynamics like \f and \p etc. and of course lyrics, title, footer etc. are rendered scaled way to large (w/o measuring it looks at least a factor of 10 too big). Does LP treat these differently renderingwise (as in: could that provide a hint where I could look?) Kind regards, Michael -- Michael Gerdau email: m...@qata.de GPG-keys available on request or at public keyserver signature.asc Description: This is a digitally signed message part. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: wierd beamlet behaviour
Hi Andrew, > Have you overridden Flag.stencil anywhere in your stylesheets to use some > modification of #old-straight-flag etc? No… but that’s definitely what it looks like! Thanks, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: wierd beamlet behaviour
Kieren,
Compiled in 2.18.2 the beams are parallel.
Mark
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of Kieren MacMillan
Sent: Friday, November 11, 2016 7:34 PM
To: Lilypond-User Mailing List
Subject: wierd beamlet behaviour
Hello all,
In the following screenshot, you will notice some odd beamlet behaviour:
The following minimal snippet does NOT show this problem:
SNIPPET ENDS
\version "2.19.49"
\language "english"
beamtest = {
16([ bf''8)] 16([ af''8)] 16([ g''8]) 16([ f''8)] 16([ ef''8)]
}
\score { \beamtest }
SNIPPET ENDS
Any thoughts what this might be? I’m pretty sure it’s not the PDF viewer
(because the minimal example looks fine in the same viewer).
The number of stylesheet layers involved in the score I’m engraving is pretty
high, so it would be nice to have at least an idea of which haystack to look in
to find this particular needle...
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: wierd beamlet behaviour
Hi Kieran, As you say, compiles fine. Have you overridden Flag.stencil anywhere in your stylesheets to use some modification of #old-straight-flag etc? Andrew ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
wierd beamlet behaviour
Hello all,
In the following screenshot, you will notice some odd beamlet behaviour:
The following minimal snippet does NOT show this problem:
SNIPPET ENDS
\version "2.19.49"
\language "english"
beamtest = {
16([ bf''8)] 16([ af''8)] 16([ g''8]) 16([ f''8)] 16([ ef''8)]
}
\score { \beamtest }
SNIPPET ENDS
Any thoughts what this might be? I’m pretty sure it’s not the PDF viewer
(because the minimal example looks fine in the same viewer).
The number of stylesheet layers involved in the score I’m engraving is pretty
high, so it would be nice to have at least an idea of which haystack to look in
to find this particular needle...
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Pedal cautionary continuations and other bracket decorations
Well. Despite what I said about after line breaking, that must have been the
case with an earlier version of the code. Changing my code to use after line
breaking, thus:
pedalWithArrowsAndText =
\override Score.PianoPedalBracket.after-line-breaking =
#(lambda (grob)
works fine.
But a second issue arises. After a sustainOff followed by a sustainOn on a
note, the pedal bracket left hand side text decoration is repeated at that
point. So thats probably a more interesting issue that still needs figuring
out.
Im pasting the updated code here to make it easy to just compile.
Andrew
== snip
\version "2.19.50"
\include "scheme.ily"
#(use-modules (srfi srfi-1))
#(define (make-arrow-path arrow-length arrowhead-height arrowhead-width)
"Arrow with triangular arrowhead."
(list
'moveto 0 0
'lineto arrow-length 0
'lineto arrow-length (/ arrowhead-width 2)
'lineto (+ arrow-length arrowhead-height) 0
'lineto arrow-length (- (/ arrowhead-width 2))
'lineto arrow-length 0
'closepath
))
pedalWithArrowsAndText =
\override Score.PianoPedalBracket.after-line-breaking =
#(lambda (grob)
;; function to modify the individual grob part
(define add-decorations
(lambda (g list-length)
(let* (
;; unpack the argument
(index (car g))
(grobber (cadr g))
(last (= index list-length))
;; Get the default-stencil and its x-dimension and x-length.
(stil (ly:piano-pedal-bracket::print grobber))
(stil-x-extent (ly:stencil-extent stil X))
(stil-x-length (interval-length stil-x-extent))
;; make arrow for the rhs end
(thickness 0.1)
(arrowhead-height 1.0)
(arrowhead-width 1.0)
(arrow-length 1.0)
(arrow (make-path-stencil (make-arrow-path arrow-length
arrowhead-height arrowhead-width) thickness 1 1 #t))
(new-stil (if (not last)
(ly:stencil-combine-at-edge stil X RIGHT arrow
-2)
stil))
;; make text for the lhs end
(text-stil
(grob-interpret-markup grobber
(markup
#:line
(#:abs-fontsize
6
(#:sans
(#:upright
(#:whiteout (#:box (#:pad-markup 0.3 "½ ped")
(new-stil (ly:stencil-stack new-stil X LEFT text-stil -6)))
(dbg index)
(dbg (ly:grob-basic-properties grobber))
(sep)
(dbg (ly:grob-properties grobber))
(sep) (sep)
(ly:grob-set-property! grobber 'stencil new-stil
(let* (
(stil (ly:piano-pedal-bracket::print grob))
(orig (ly:grob-original grob))
(pieces (if (ly:grob? orig)
(ly:spanner-broken-into orig)
'()))
(pieces-indexed-list (zip (iota (length pieces) 1) pieces))
(pieces-length (length pieces)))
;; We want arrows on all segments but the last, and text on all
segments, so
;; we have to pass some notion of list index to the function doing the
;; decorating. Hence the ziplist combining grob segment and index in
pairs.
(let loop ((x 1)
(count 0))
(if (< count pieces-length)
(begin
(add-decorations (list-ref pieces-indexed-list count)
pieces-length)
(loop x (+ count 1))
)))
stil))
%===
treble = {
\clef treble
\time 4/4
c'4 c' c' c'
c' c' c' c'
}
bass = {
\clef bass
\time 4/4
c4
\pedalWithArrowsAndText
c\sustainOn c c
c c c c
\break
c c c c
\break
c c c^\sustainOff\sustainOn c
\break
c c c c
\break
c c c c
\break
c c c c\sustainOff
}
\score {
\new PianoStaff
<<
\new Staff = "treble" { \treble }
\new Staff = "bass" { \bass }
>>
\layout {
\context {
\Score
pedalSustainStyle = #'bracket
}
}
}
== snip
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Pedal cautionary continuations and other bracket decorations
For the Scheme gurus. For a long time I have needed to decorate or embellish pedal brackets to customise them. Two things I need are arrows on the right hand side, and text markers similar to cautionary pedal indications on the left hand side, so each new broken bracket shows 1/2 ped at the start, for example. I am aware that there have been discussions of similar things on the list, but it seems the only solutions were workarounds using text spanners. I have found this to be unsatisfactory, for my purposes. So I have developed Scheme code to achieve this effect. I am pleased to say I nearly have it working, but I am bedevilled by the fact that in this example the second line does not get decorated. I confess I am stumped. I wonder if anyone here can see what must be some silly error in the logic? I am not saying this is a bug. I am sure it is my dullness at work. I apologise for this being a fairly complex bit of code to digest, but I have a feeling many people want this type of pedal customisation judging from the archived discussions, and I feel it may end up being a useful contribution, hence worth debugging. One aspect that has me puzzled is that if you add more treble notes so that two staves are alive for longer the problem shifts around. I would have thought that pedal on the bottom staff would not be affected by a staff above, and this behaviour may be a clue to the issue, but I am unable to hear what it is telling me. My thinking on this to date is that I remain very ignorant of when things are laid out and what order, if any, various internal constructions are done, so I am think this may be to do with the possibility that treating the broken spanner as an ordered list that is there ready to be modified may be a fundamental error. For what its worth, therefore, I tried implementing this as an after line breaking callback, but the same problem shows. Any help most appreciated. Andrew == snip \version "2.19.50" #(use-modules (srfi srfi-1)) #(define (make-arrow-path arrow-length arrowhead-height arrowhead-width) "Arrow with triangular arrowhead." (list 'moveto 0 0 'lineto arrow-length 0 'lineto arrow-length (/ arrowhead-width 2) 'lineto (+ arrow-length arrowhead-height) 0 'lineto arrow-length (- (/ arrowhead-width 2)) 'lineto arrow-length 0 'closepath )) pedalWithArrowsAndText = \once \override Score.PianoPedalBracket.stencil = #(lambda (grob) ;; function to modify the individual grob part (define add-decorations (lambda (g list-length) (let* ( ;; unpack the argument (index (car g)) (grobber (cadr g)) (last (= index list-length)) ;; Get the default-stencil and its x-dimension and x-length. (stil (ly:piano-pedal-bracket::print grobber)) (stil-x-extent (ly:stencil-extent stil X)) (stil-x-length (interval-length stil-x-extent)) ;; make arrow for the rhs end (thickness 0.1) (arrowhead-height 1.0) (arrowhead-width 1.0) (arrow-length 1.0) (arrow (make-path-stencil (make-arrow-path arrow-length arrowhead-height arrowhead-width) thickness 1 1 #t)) (new-stil (if (not last) (ly:stencil-combine-at-edge stil X RIGHT arrow -0.105) stil)) ;; make text for the lhs end (text-stil (grob-interpret-markup grobber (markup #:line (#:abs-fontsize 6 (#:sans (#:upright (#:whiteout (#:box (#:pad-markup 0.3 "½ ped") (new-stil (ly:stencil-stack new-stil X LEFT text-stil -6))) (ly:grob-set-property! grobber 'stencil new-stil (let* ( (stil (ly:piano-pedal-bracket::print grob)) (orig (ly:grob-original grob)) (pieces (if (ly:grob? orig) (ly:spanner-broken-into orig) '())) (pieces-indexed-list (zip (iota (length pieces) 1) pieces)) (pieces-length (length pieces))) ;; We want arrows on all segments but the last, and text on all segments, so ;; we have to pass some notion of list index to the function doing the ;; decorating. Hence the ziplist combining grob segment and index in pairs. (let loop ((x 1) (count 0)) (if (< count 5) (begin (add-decorations (list-ref pieces-indexed-list count) pieces-length) (loop x (+ count 1)) ))) stil)) %=== treble =
Re: Potential bug: Slur begins or ends with tenuto
On 11.11.2016 23:54, Daniel Rosen wrote: It appears that LilyPond is refusing to allow Slur.positions to be specified in increments smaller than 0.5 staff spaces. Indeed the positions property does not set staff positions directly at all. To understand, one has to know how LilyPond draws slurs in the first place: It tries out a number of candidates and the one with the best score (or rather the least demerit) is chosen – a heuristic algorithm[1][2]. Now, setting the positions property can only influence which of the candidates will be chosen. If there is no candidate matching your choice of positions, the closest one will be chosen. For finer control, you need \shape. HTH, Simon [1] This is explained in more depth in the LilyPond essay, I think. [2] I think there is a way to have more candidates be created, but I don’t recall how, sorry. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Problem with Fonts too big
HI Michael, Hard to say what is the cause. You could try clearing your font cache with fc-cache -r -v as root. Andrew -Original Message- From: lilypond-user [mailto:lilypond-user-bounces+andrew.bernard=gmail@gnu.org] On Behalf Of Michael Gerdau Sent: Saturday, 12 November 2016 10:01 AM To: lilypond-user@gnu.org Subject: Problem with Fonts too big on my Arch Linux system lilypond has all at a sudden started to print all regular fonts way too big. E.g. the following code produces the attached pdf: ... Does anybody know what might be the cause and where I might look to fix this? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re:Advice about layout / page formatting
> -- Forwarded message --
> From: Jim Duke
> To: "Lilypond User (lilypond-user@gnu.org)"
> Cc:
> Date: Tue, 11 Oct 2016 14:39:13 +
> Subject: Advice about layout / page formatting
> I'm seeking advice on how to approach typesetting some hymns for use in
> worship. The music in our worship is A Capella congregational singing, and
> we use both sheet music, which we put in folders in the pews, and slides,
> which we project on a large screen at the front of the auditorium. For
> each hymn I want to produce a PDF of the sheet music, a set of PNG files
> for each of the slides, and a MIDI file to aid in teaching the hymns to the
> congregation.
>
> ...
>
> First, on the first slide of every verse I put a title at the top with the
> name of the song and the song number in our hymal. On following slides
> from the same verse, there is no title. But, I'd like the first system on
> every slide to start at the same place on the page. As we present the
> slides the movement of the systems around on the page is distracting. I'd
> like to fix them on the page if I could. Because of how large I want the
> fonts to be, I typically can fit two systems on each page. I have no idea
> how to accomplish that. Is there a parameter that directly controls the
> distance from the top of the page to the first system?
>
I was going through old digests and didn't see this part of your question
answered.
There are a pair of variables that influence where the music starts on the
page: one for the first page, and one for all the others. I say
"influence" since I think these are offsets from the header, not an
absolute position on the page.
I typically set these in a paper block overrides within a book, since I
often have to (or want to) tweak these on per-book basis.
Included are some other page layout variables I tend to use.
\book {
\paper {
top-margin = #10
right-margin = #17
% First page spacing after header
markup-system-spacing #'padding = #6
% Subsequent page spacing after header
top-system-spacing #'minimum-distance = #14
% Spacing in between systems
system-system-spacing #'minimum-distance = #13
}
\score {
...
}
}
HTH,
David Elaine Alt
415 . 341 .4954 "*Confusion is
highly underrated*"
ela...@flaminghakama.com
self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Getting the direction when defining a new markup command
Kevin Barry writes:
> Dear All,
>
> I am trying to set the direction of an arrow in a markup function
> based on whether the markup is placed above or below the staff, but I
> am ready to give up. Here is a condensed version of my most recent
> attempt. Does anyone know how to do this?
>
> \version "2.19.45"
>
> #(define-markup-command (test layout props arg)
>(integer?)
>(let ((dir (lambda (grob)
> (if (= UP (ly:grob-property grob 'direction))
> -1
> 1
> (interpret-markup layout props
>#{
> \markup { \arrow-head #Y #dir ##f }
>#})))
>
> \markup \test #1
"based on whether the markup is placed above or below the staff"? What
staff? Your example is a bit too minimal.
How about
\version "2.19.45"
#(define-markup-command (test layout props arg)
(integer?) #:properties ((direction))
(interpret-markup layout props
#{
\markup { \arrow-head #Y #direction ##f }
#}))
\new Staff {
c^\markup \test #1 _\markup \test #2
}
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Problem with Fonts too big
Hi list,
on my Arch Linux system lilypond has all at a sudden started to print
all regular fonts way too big. E.g. the following code produces the
attached pdf:
%%
\version "2.19.50"
\paper {
top-margin = 40
right-margin = 40
print-first-page-number = ##t
}
{ c'' }
%%
This happens with 2.18.2 as well as 2.19.48+ onwards. I think the cause
had been some "fontstuff" update on my system but I have not been able
to find out what (what I consider the usual suspects I have already
tried to reinstall - no success).
Does anybody know what might be the cause and where I might look to
fix this?
Thank you,
Michael
--
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver
fonts-big.pdf
Description: Adobe PDF document
signature.asc
Description: This is a digitally signed message part.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Potential bug: Slur begins or ends with tenuto
> -Original Message-
> From: Daniel Rosen
> Sent: Friday, November 11, 2016 5:54 PM
> To: lilypond-user Mailing List (lilypond-user@gnu.org) u...@gnu.org>
> Subject: Potential bug: Slur begins or ends with tenuto
>
> It appears that LilyPond is refusing to allow Slur.positions to be specified
> in
> increments smaller than 0.5 staff spaces. I can't find any mention of a
> constraint like this in any of the manuals.
It just occurred to me that the following example does a much better job of
illustrating this point than the one I previously submitted:
\version "2.19.50"
\relative c'' {
\stemUp
\override Slur.positions = #'(-1 . -1)
b( b)
\override Slur.positions = #'(-1.25 . -1)
b( b)
\override Slur.positions = #'(-1.5 . -1)
b( b)
}
DR
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Potential bug: Slur begins or ends with tenuto
I'm sending this to the user list first because I'm having trouble with the
search functionality in the new issue tracker, so I can't tell if this has
already been reported:
\version "2.19.50"
\relative c' {
\override Slur.positions = #'(-4 . -4)
c( c)
\override Slur.positions = #'(-4.25 . -4)
c( c)
\override Slur.positions = #'(-4.5 . -4)
c( c)
}
It appears that LilyPond is refusing to allow Slur.positions to be specified in
increments smaller than 0.5 staff spaces. I can't find any mention of a
constraint like this in any of the manuals.
DR
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Getting the direction when defining a new markup command
Dear All,
I am trying to set the direction of an arrow in a markup function
based on whether the markup is placed above or below the staff, but I
am ready to give up. Here is a condensed version of my most recent
attempt. Does anyone know how to do this?
\version "2.19.45"
#(define-markup-command (test layout props arg)
(integer?)
(let ((dir (lambda (grob)
(if (= UP (ly:grob-property grob 'direction))
-1
1
(interpret-markup layout props
#{
\markup { \arrow-head #Y #dir ##f }
#})))
\markup \test #1
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
Am 11.11.2016 um 21:21 schrieb Noeck: > parserDefine = > #(define-void-function (name val) (symbol? scheme?) > (ly:parser-define! name val)) Thank you, that worked. Regards Bernhard -- spitzhalde9 D-79853 lenzkirch bernhard.kle...@gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09 signature.asc Description: OpenPGP digital signature ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
Am 11.11.2016 um 21:18 schrieb Bernhard Kleine: > Could you please make a concrete proposition? parserDefine = #(define-void-function (name val) (symbol? scheme?) (ly:parser-define! name val)) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
Am 11.11.2016 um 21:11 schrieb Urs Liska: > > Am 11. November 2016 21:02:34 MEZ, schrieb Noeck : >> >> Am 11.11.2016 um 20:42 schrieb Bernhard Kleine: >>> #(define-void-function (name val)(symbol? not-null?) >> It looks to me as if "not-null?" does not exist in guile. There is >> not-pair? and there is null? But not not-null? It works with not-pair? >> but that's probably not the right answer. >> >> Unfortunately, I can't tell you what the correct replacement would be. > I think scheme? should be fine as you can bind any scheme value to a > variable. > > Urs > Could you please make a concrete proposition? thanks Bernhard signature.asc Description: OpenPGP digital signature ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
Am 11. November 2016 21:02:34 MEZ, schrieb Noeck : > > >Am 11.11.2016 um 20:42 schrieb Bernhard Kleine: >> #(define-void-function (name val)(symbol? not-null?) > >It looks to me as if "not-null?" does not exist in guile. There is >not-pair? and there is null? But not not-null? It works with not-pair? >but that's probably not the right answer. > >Unfortunately, I can't tell you what the correct replacement would be. I think scheme? should be fine as you can bind any scheme value to a variable. Urs > >Cheers, >Joram > >___ >lilypond-user mailing list >lilypond-user@gnu.org >https://lists.gnu.org/mailman/listinfo/lilypond-user -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
Am 11.11.2016 um 20:42 schrieb Bernhard Kleine: > #(define-void-function (name val)(symbol? not-null?) It looks to me as if "not-null?" does not exist in guile. There is not-pair? and there is null? But not not-null? It works with not-pair? but that's probably not the right answer. Unfortunately, I can't tell you what the correct replacement would be. Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
Am 11.11.2016 um 19:58 schrieb Simon Albrecht:
> On 11.11.2016 19:41, Bernhard Kleine wrote:
>> I added this to testmain.ly before the \book
>> parserDefine =
>> #(define-void-function (name val)(symbol? not-null?)
>> (ly:parser-define! name val))
>> and got this error:
>>
>> F:/Meine Noten/EigeneNoten/WeihnachtsLieder/testmain.ly:17:2 <0>:
>> error: GUILE signaled an error for the expression beginning here
>>
>> #
>>
>> (define-void-function (name val)(symbol? not-null?)
>>
>>
>> Maybe some other requirement is missing.
>
> Likely that requirement is a (more) recent version of LilyPond. One of
> your earlier attachments said \version "2.19.5", and that version
> required the function definition to begin with
> #(define-void-function (parser location name val)(…)…)
> The parser and location arguments can be omitted since somewhere in
> the 2.19 series.
>
> Best, Simon
>
>>
Starte lilypond.exe 2.19.49 [testmain.ly]...
Processing `F:/Meine Noten/EigeneNoten/WeihnachtsLieder/testmain.ly'
Parsing...
F:/Meine Noten/EigeneNoten/WeihnachtsLieder/testmain.ly:17:2 <0>: error:
GUILE signaled an error for the expression beginning here
#
(define-void-function (name val)(symbol? not-null?)
Obviously the actual version!
the file:
\version "2.19.49"
\language "deutsch"
#(set-global-staff-size 17)
\paper {
#(set-paper-size "a4")
}
\header {
title = "main"
tagline = \markup {
Gesetzt durch Bernhard Kleine mit
\line { LilyPond \simple #(lilypond-version) (http://lilypond.org/) }
}
}
parserDefine =
#(define-void-function (name val)(symbol? not-null?)
(ly:parser-define! name val))
\book {
\bookpart {
\include "2test.ly"
}
}
signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Stepping down and moving on
Hi David, Just echoing everyone else's sentiments: your contribution to our lives and work through your work on LilyPond is incalculable. As a lurker of course I don't really understand much of what you do, but it's clear that LilyPond would be far behind where it is now without your development and leadership. I am sorry that I was never in a position to help out financially, so I am happy to hear about your new job. I wish you all the best! Kevin ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
Am 11. November 2016 19:41:21 MEZ, schrieb Bernhard Kleine
:
>I added this to testmain.ly before the \book
> parserDefine =
>#(define-void-function (name val)(symbol? not-null?)
>(ly:parser-define! name val))
>and got this error:
>
>F:/Meine Noten/EigeneNoten/WeihnachtsLieder/testmain.ly:17:2 <0>:
>error:
>GUILE signaled an error for the expression beginning here
>
>#
>
>(define-void-function (name val)(symbol? not-null?)
>
>
>Maybe some other requirement is missing.
Ah, if you use 2.18 you have to write (parser location name val)
This was changed in the meantime.
HTH
Urs
>
>Bernhard
>
>Am 11.11.2016 um 18:43 schrieb Jan-Peter Voigt:
>> Hello
>>
>> there's one solution, I use in this cases:
>>
>> parserDefine =
>> #(define-void-function (name val)(symbol? not-null?)
>> (ly:parser-define! name val))
>>
>> as parserDefine is a void function, you can all it anywhere - even
>> inside a music expression:
>>
>> \parserDefine global { ... }
>>
>> instead of
>>
>> global = { ... }
>>
>> Of course, you might use a shorter name like just 'def' instead of
>> parserDefine. But take care not to use a reserved name like 'define'.
>>
>> HTH
>> Jan-Peter
>>
>> Am 11.11.2016 um 17:15 schrieb Federico Bruni:
>>> Il giorno ven 11 nov 2016 alle 16:45, Bernhard Kleine
>>> ha scritto:
However when the global variable to the top of 2test.ly, the file
could be compiled. I tried then the same on my full piece and I
failed while parsing with
F:/Meine Noten/EigeneNoten/WeihnachtsLieder/2test.ly:2:1: error:
syntax error, unexpected STRING
global = {
To make this evident I include the files once more. I do not
understand this.
>>>
>>> I hit the same wall some time ago :)
>>>
>>> If you read the first error message:
>>>
>>> /tmp/2test.ly:2:1: error: syntax error, unexpected STRING
>>>
>>> it points to the definition of global in the included file.
>>>
>>> The problem here is that the variable is included (and evaluated)
>>> within a \bookpart block, but variables can be defined only at top
>>> level.
>>> That's why you need an extra file only for variables (the use of
>.ily
>>> extension is only a useful convention, as Urs already wrote).
>>>
>>> I don't think that there's another way to achieve what you want.
>>>
>>>
>>>
>>>
>>> ___
>>> 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
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
On 11.11.2016 19:41, Bernhard Kleine wrote:
I added this to testmain.ly before the \book
parserDefine =
#(define-void-function (name val)(symbol? not-null?)
(ly:parser-define! name val))
and got this error:
F:/Meine Noten/EigeneNoten/WeihnachtsLieder/testmain.ly:17:2 <0>:
error: GUILE signaled an error for the expression beginning here
#
(define-void-function (name val)(symbol? not-null?)
Maybe some other requirement is missing.
Likely that requirement is a (more) recent version of LilyPond. One of
your earlier attachments said \version "2.19.5", and that version
required the function definition to begin with
#(define-void-function (parser location name val)(…)…)
The parser and location arguments can be omitted since somewhere in the
2.19 series.
Best, Simon
Bernhard
Am 11.11.2016 um 18:43 schrieb Jan-Peter Voigt:
Hello
there's one solution, I use in this cases:
parserDefine =
#(define-void-function (name val)(symbol? not-null?)
(ly:parser-define! name val))
as parserDefine is a void function, you can all it anywhere - even
inside a music expression:
\parserDefine global { ... }
instead of
global = { ... }
Of course, you might use a shorter name like just 'def' instead of
parserDefine. But take care not to use a reserved name like 'define'.
HTH
Jan-Peter
Am 11.11.2016 um 17:15 schrieb Federico Bruni:
Il giorno ven 11 nov 2016 alle 16:45, Bernhard Kleine
ha scritto:
However when the global variable to the top of 2test.ly, the file
could be compiled. I tried then the same on my full piece and I
failed while parsing with
F:/Meine Noten/EigeneNoten/WeihnachtsLieder/2test.ly:2:1: error:
syntax error, unexpected STRING
global = {
To make this evident I include the files once more. I do not
understand this.
I hit the same wall some time ago :)
If you read the first error message:
/tmp/2test.ly:2:1: error: syntax error, unexpected STRING
it points to the definition of global in the included file.
The problem here is that the variable is included (and evaluated)
within a \bookpart block, but variables can be defined only at top
level.
That's why you need an extra file only for variables (the use of
.ily extension is only a useful convention, as Urs already wrote).
I don't think that there's another way to achieve what you want.
___
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
--
spitzhalde9
D-79853 lenzkirch
bernhard.kle...@gmx.net
www.b-kleine.com,www.urseetal.net
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
___
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: Book and variables -- lost how to remedy
I added this to testmain.ly before the \book
parserDefine =
#(define-void-function (name val)(symbol? not-null?)
(ly:parser-define! name val))
and got this error:
F:/Meine Noten/EigeneNoten/WeihnachtsLieder/testmain.ly:17:2 <0>: error:
GUILE signaled an error for the expression beginning here
#
(define-void-function (name val)(symbol? not-null?)
Maybe some other requirement is missing.
Bernhard
Am 11.11.2016 um 18:43 schrieb Jan-Peter Voigt:
> Hello
>
> there's one solution, I use in this cases:
>
> parserDefine =
> #(define-void-function (name val)(symbol? not-null?)
> (ly:parser-define! name val))
>
> as parserDefine is a void function, you can all it anywhere - even
> inside a music expression:
>
> \parserDefine global { ... }
>
> instead of
>
> global = { ... }
>
> Of course, you might use a shorter name like just 'def' instead of
> parserDefine. But take care not to use a reserved name like 'define'.
>
> HTH
> Jan-Peter
>
> Am 11.11.2016 um 17:15 schrieb Federico Bruni:
>> Il giorno ven 11 nov 2016 alle 16:45, Bernhard Kleine
>> ha scritto:
>>> However when the global variable to the top of 2test.ly, the file
>>> could be compiled. I tried then the same on my full piece and I
>>> failed while parsing with
>>> F:/Meine Noten/EigeneNoten/WeihnachtsLieder/2test.ly:2:1: error:
>>> syntax error, unexpected STRING
>>> global = {
>>>
>>> To make this evident I include the files once more. I do not
>>> understand this.
>>
>> I hit the same wall some time ago :)
>>
>> If you read the first error message:
>>
>> /tmp/2test.ly:2:1: error: syntax error, unexpected STRING
>>
>> it points to the definition of global in the included file.
>>
>> The problem here is that the variable is included (and evaluated)
>> within a \bookpart block, but variables can be defined only at top
>> level.
>> That's why you need an extra file only for variables (the use of .ily
>> extension is only a useful convention, as Urs already wrote).
>>
>> I don't think that there's another way to achieve what you want.
>>
>>
>>
>>
>> ___
>> 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
--
spitzhalde9
D-79853 lenzkirch
bernhard.kle...@gmx.net
www.b-kleine.com, www.urseetal.net
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
Hello
there's one solution, I use in this cases:
parserDefine =
#(define-void-function (name val)(symbol? not-null?)
(ly:parser-define! name val))
as parserDefine is a void function, you can all it anywhere - even
inside a music expression:
\parserDefine global { ... }
instead of
global = { ... }
Of course, you might use a shorter name like just 'def' instead of
parserDefine. But take care not to use a reserved name like 'define'.
HTH
Jan-Peter
Am 11.11.2016 um 17:15 schrieb Federico Bruni:
Il giorno ven 11 nov 2016 alle 16:45, Bernhard Kleine
ha scritto:
However when the global variable to the top of 2test.ly, the file
could be compiled. I tried then the same on my full piece and I
failed while parsing with
F:/Meine Noten/EigeneNoten/WeihnachtsLieder/2test.ly:2:1: error:
syntax error, unexpected STRING
global = {
To make this evident I include the files once more. I do not
understand this.
I hit the same wall some time ago :)
If you read the first error message:
/tmp/2test.ly:2:1: error: syntax error, unexpected STRING
it points to the definition of global in the included file.
The problem here is that the variable is included (and evaluated)
within a \bookpart block, but variables can be defined only at top level.
That's why you need an extra file only for variables (the use of .ily
extension is only a useful convention, as Urs already wrote).
I don't think that there's another way to achieve what you want.
___
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: Book and variables -- lost how to remedy
Il giorno ven 11 nov 2016 alle 16:45, Bernhard Kleine
ha scritto:
However when the global variable to the top of 2test.ly, the file
could be compiled. I tried then the same on my full piece and I
failed while parsing with
F:/Meine Noten/EigeneNoten/WeihnachtsLieder/2test.ly:2:1: error:
syntax error, unexpected STRING
global = {
To make this evident I include the files once more. I do not
understand this.
I hit the same wall some time ago :)
If you read the first error message:
/tmp/2test.ly:2:1: error: syntax error, unexpected STRING
it points to the definition of global in the included file.
The problem here is that the variable is included (and evaluated)
within a \bookpart block, but variables can be defined only at top
level.
That's why you need an extra file only for variables (the use of .ily
extension is only a useful convention, as Urs already wrote).
I don't think that there's another way to achieve what you want.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
Thank you for the explanation. Bernhard Am 11.11.2016 um 16:48 schrieb Urs Liska: > Am 11.11.2016 um 16:45 schrieb Bernhard Kleine: >> First of all: I look through the Lilypond Notation Reference and there >> was not a single occurence of .ily. Maybe you will explain more. > The file extension actually doesn't matter to LilyPond at all. > It is a (useful) convention to name files *.ily that are not intended to > be compiled directly (as ."include"ly) > > HTH > Urs > > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user -- spitzhalde9 D-79853 lenzkirch bernhard.kle...@gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09 signature.asc Description: OpenPGP digital signature ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
Am 11.11.2016 um 16:45 schrieb Bernhard Kleine: > First of all: I look through the Lilypond Notation Reference and there > was not a single occurence of .ily. Maybe you will explain more. The file extension actually doesn't matter to LilyPond at all. It is a (useful) convention to name files *.ily that are not intended to be compiled directly (as ."include"ly) HTH Urs -- Urs Liska www.openlilylib.org signature.asc Description: OpenPGP digital signature ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
Am 11.11.2016 um 15:28 schrieb Federico Bruni:
> Il giorno ven 11 nov 2016 alle 14:40, Federico Bruni
> ha scritto:
>> Il giorno ven 11 nov 2016 alle 13:50, Bernhard Kleine
>> ha scritto:
>>> I have for the sake a MWE a main file and a included file. When this
>>> file was compiled alone with a header and language it compiled well.
>>> Now, given I want to get a book with several songs, I encounter errors
>>> since the variables disturb the compilation.
>>>
>>> The files are attached. Please let me know how to change the input
>>> that
>>> correct compilation occurs.
>>
>> Hi Bernard
>>
>> 2test.ly file contains a variable which is defined after it's called.
>> This cannot work, because lilypond parses the file from top to
>> bottom, IIUC.
>>
>> If you want to compile a single piece independently from a book
>> (collection of pieces), the best approach is probably using a .ily
>> file for music definitions and variables. Basic example:
>>
>> % File score1.ily
>> % The point here is: just define variables, do not print anything.
>> global = {
>> ...
>> }
>> ScoreOneMusic = \score {
>> \global
>> ...
>> \layout {}
>> }
>
> The other point that I should have highlighted is: you must use
> different variable names in each score, otherwise the latest
> definition will override the previous ones. So instead of "global" you
> should rather use e.g. "ScoreOneGlobal".
>
>>
>>
>> % File score1.ly
>> \include "score1.ily"
>> \ScoreOneMusic
>>
>>
>> % File book.ly
>> \include "score1.ily"
>> \include "score2.ily"
>>
>> \book {
>> \bookpart {
>>\ScoreOneMusic
>> }
>> \bookpart {
>>\ScoreTwoMusic
>> }
>> }
First of all: I look through the Lilypond Notation Reference and there
was not a single occurence of .ily. Maybe you will explain more.
However when the global variable to the top of 2test.ly, the file could
be compiled. I tried then the same on my full piece and I failed while
parsing with
F:/Meine Noten/EigeneNoten/WeihnachtsLieder/2test.ly:2:1 <0>: error:
syntax error, unexpected STRING
global = {
To make this evident I include the files once more. I do not understand
this.
Regards Bernhard
global = {
\set fontSize = #0.8
\key d \major
% \numericTimeSignature
\time 4/4
\mergeDifferentlyHeadedOn
\partial 4
}
stimme = \relative c'' {
\global
%Melodie
\repeat volta 2 {
a4 | d a8[ a] g4 fis8[ e] |
}
}
verseOne = \lyricmode {
Auf! Chris -- ten singt fest -- li -- che
}
repeatFirst = \lyricmode {
Es schal -- le auf Er -- den laut
}
\score {
\new StaffGroup
<<
\new Staff
<<
\new Voice = "stimme" \stimme
>>
\new Lyrics \lyricsto "stimme" \verseOne
\new Lyrics \lyricsto "stimme" \repeatFirst
>>
\layout {
indent = 0
\context {
\Voice
\consists "Melody_engraver"
\override Stem #'neutral-direction = #'()
}
}
\header {
title = "Auf! Christen singt festliche Lieder"
composer = "Text und Melodie: Fulda, 1778"
}
}
\version "2.19.5"
\language "deutsch"
#(set-global-staff-size 17)
\paper {
#(set-paper-size "a4")
}
\header {
title = "main"
tagline = \markup {
Gesetzt durch Bernhard Kleine mit
\line { LilyPond \simple #(lilypond-version) (http://lilypond.org/) }
}
}
\book {
\bookpart {
\include "2test.ly"
}
}
signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ties over multiple chords
On 11.11.2016 09:52, Mojca Miklavec wrote: \set tieWaitForNote = ##t does the trick. Wonderful, thank you. Is there some way to limit the scope of this command or is it best to simply use \set tieWaitForNote = ##f once I no longer need it? \unset tieWaitForNote _might_ work (untested), but especially with a boolean like this \set tieWaitForNote = ##f is the way to go. Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Book and variables -- lost how to remedy
Il giorno ven 11 nov 2016 alle 14:40, Federico Bruni
ha scritto:
Il giorno ven 11 nov 2016 alle 13:50, Bernhard Kleine
ha scritto:
I have for the sake a MWE a main file and a included file. When this
file was compiled alone with a header and language it compiled well.
Now, given I want to get a book with several songs, I encounter
errors
since the variables disturb the compilation.
The files are attached. Please let me know how to change the input
that
correct compilation occurs.
Hi Bernard
2test.ly file contains a variable which is defined after it's called.
This cannot work, because lilypond parses the file from top to
bottom, IIUC.
If you want to compile a single piece independently from a book
(collection of pieces), the best approach is probably using a .ily
file for music definitions and variables. Basic example:
% File score1.ily
% The point here is: just define variables, do not print anything.
global = {
...
}
ScoreOneMusic = \score {
\global
...
\layout {}
}
The other point that I should have highlighted is: you must use
different variable names in each score, otherwise the latest definition
will override the previous ones. So instead of "global" you should
rather use e.g. "ScoreOneGlobal".
% File score1.ly
\include "score1.ily"
\ScoreOneMusic
% File book.ly
\include "score1.ily"
\include "score2.ily"
\book {
\bookpart {
\ScoreOneMusic
}
\bookpart {
\ScoreTwoMusic
}
}
___
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: Book and variables -- lost how to remedy
Il giorno ven 11 nov 2016 alle 13:50, Bernhard Kleine
ha scritto:
I have for the sake a MWE a main file and a included file. When this
file was compiled alone with a header and language it compiled well.
Now, given I want to get a book with several songs, I encounter errors
since the variables disturb the compilation.
The files are attached. Please let me know how to change the input
that
correct compilation occurs.
Hi Bernard
2test.ly file contains a variable which is defined after it's called.
This cannot work, because lilypond parses the file from top to bottom,
IIUC.
If you want to compile a single piece independently from a book
(collection of pieces), the best approach is probably using a .ily file
for music definitions and variables. Basic example:
% File score1.ily
% The point here is: just define variables, do not print anything.
global = {
...
}
ScoreOneMusic = \score {
\global
...
\layout {}
}
% File score1.ly
\include "score1.ily"
\ScoreOneMusic
% File book.ly
\include "score1.ily"
\include "score2.ily"
\book {
\bookpart {
\ScoreOneMusic
}
\bookpart {
\ScoreTwoMusic
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Book and variables -- lost how to remedy
Hi,
I have for the sake a MWE a main file and a included file. When this
file was compiled alone with a header and language it compiled well.
Now, given I want to get a book with several songs, I encounter errors
since the variables disturb the compilation.
The files are attached. Please let me know how to change the input that
correct compilation occurs.
Thanks for any help!
Bernhard
--
spitzhalde9
D-79853 lenzkirch
bernhard.kle...@gmx.net
www.b-kleine.com, www.urseetal.net
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
stimme = \relative c'' {
\global
%Melodie
\repeat volta 2 {
a4 | d a8[ a] g4 fis8[ e] |
}}
verseOne = \lyricmode {
Auf! Chris -- ten singt fest -- li -- che
}
repeatFirst = \lyricmode {
Es schal -- le auf Er -- den laut
}
\score {
\new StaffGroup
<<
\new Staff
<<
\new Voice = "stimme" \stimme
>>
\new Lyrics \lyricsto "stimme" \verseOne
\new Lyrics \lyricsto "stimme" \repeatFirst
>>
\layout {
indent = 0
\context {
\Voice
\consists "Melody_engraver"
\override Stem #'neutral-direction = #'()
}
}
global = {
\set fontSize = #0.8
\key d \major
% \numericTimeSignature
\time 4/4
\mergeDifferentlyHeadedOn
\partial 4
}
\header {
title = "Auf! Christen singt festliche Lieder"
composer = "Text und Melodie: Fulda, 1778"
}
}
\version "2.19.5"
\language "deutsch"
#(set-global-staff-size 17)
\paper {
#(set-paper-size "a4")
}
\header {
title = "main"
tagline = \markup {
Gesetzt durch Bernhard Kleine mit
\line { LilyPond \simple #(lilypond-version) (http://lilypond.org/) }
}
}
\book {
\bookpart {
\include "2test.ly"
}
}
signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Stepping down and moving on
On Wed, Nov 9, 2016 at 12:09 PM, David Kastrup wrote: > > Hi folks and team, > > Partly in connection with a drop of my productivity particularly this > year, the amount of financial support for my work from members of the > LilyPond community went down from overall survivable to disastrous. Of > course this is bitter for those of you that did contribute in > significant amounts to my subsistence but I have to be moving on. David - Words fail me. LilyPond owes you so much. I wish you the best in your new job. Don't be a stranger, Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: assign "extra" repeat to last alternative
Hi Pierre
Ok, thanks for the link (good to remember that I need to use \tag to
get the right MIDI music).
Il giorno gio 10 nov 2016 alle 10:36, Pierre Perol-Schneider
ha scritto:
Hi Federico,
I'm afraid you have to do it manually.
See LSR: http://lsr.di.unimi.it/LSR/Item?id=915
Cheers,
Pierre
2016-11-10 8:53 GMT+01:00 Federico Bruni :
Hi
As it's written in the documentation, "If there are more repeats
than there are alternate endings, the earliest repeats are given the
first alternative".
If I want to change this behaviour I should use manual repeats? Or
there's a smarter way?
This is what I'd like to achieve:
\repeat volta 4 {
c1
}
\alternative {
{ d1 } % 1st alternative
{ e1 } % 2nd alternative
{ f1 } % 3rd and 4th alternatives
}
Thanks
Federico
___
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: Ties over multiple chords
Richard Shann writes: > On Fri, 2016-11-11 at 10:09 +0100, David Kastrup wrote: >> Richard Shann writes: >> >> > On Fri, 2016-11-11 at 09:15 +0100, Urs Liska wrote: >> >> Try \set tieWaitForNotes = ##t >> > >> > Is there any circumstance in which it is useful to have this set >> > false? >> >> When you want to catch a mistake instead of silently getting ties across >> half the score? Particularly for stuff like >> >> c~ << e \\ c >> d e c >> >> you have the effect that the tie will reach across the whole phrase >> since the second c is not in the tied voice. If LilyPond silently does >> "something" > Well, there would be no need for the quotes if ~ was documented to tie > from the current note to the next occurrence of that note in the current > voice. >> this may cause a visual surprise > > the "visual surprise" would be much more useful to highlight the > mistake than the current behavior, where the absence of the tie may > not be noticed. Uh, the visual surprise comes _without_ a warning. If you don't study all of your visual output closely (and there is some expectation that LilyPond's output will at least be playable even if tweaking might improve it) you'll miss it. The tie that is absent comes _with_ a warning. >> when the score is getting used. "Used" is not "proofread". >> However, a useful default may also be to draw the tie anyway but >> _warn_ unless tieWaitForNotes is set. Sure, people ignore warnings >> all the time but at their own peril. > > that sounds excellent. Mojca pointed out that tieWaitForNote = ##t _also_ causes different behavior for cases where tieWaitForNote = ##f would produce a proper result without warning. So there are use cases for tieWaitForNote where there is a difference but we would not want a warning. That makes designing a coherent strategy quite muddier. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ties over multiple chords
On Fri, 2016-11-11 at 10:09 +0100, David Kastrup wrote: > Richard Shann writes: > > > On Fri, 2016-11-11 at 09:15 +0100, Urs Liska wrote: > >> Try \set tieWaitForNotes = ##t > > > > Is there any circumstance in which it is useful to have this set > > false? > > When you want to catch a mistake instead of silently getting ties across > half the score? Particularly for stuff like > > c~ << e \\ c >> d e c > > you have the effect that the tie will reach across the whole phrase > since the second c is not in the tied voice. If LilyPond silently does > "something" Well, there would be no need for the quotes if ~ was documented to tie from the current note to the next occurrence of that note in the current voice. > this may cause a visual surprise the "visual surprise" would be much more useful to highlight the mistake than the current behavior, where the absence of the tie may not be noticed. > when the score is getting > used. > > However, a useful default may also be to draw the tie anyway but _warn_ > unless tieWaitForNotes is set. Sure, people ignore warnings all the > time but at their own peril. that sounds excellent. Richard ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ties over multiple chords
Mojca Miklavec writes: > On 11 November 2016 at 09:49, Richard Shann wrote: >> On Fri, 2016-11-11 at 09:15 +0100, Urs Liska wrote: >>> Try \set tieWaitForNotes = ##t >> >> Is there any circumstance in which it is useful to have this set false? >> That is, why is it not the default? (I never found this and when >> typesetting some music that made extensive use of written arpeggiation, >> instead I laboriously constructed workarounds ...) > > The second alternative in my example is one use case when one might > want to have this set to false. > > If it is set to false, one can simply do: > 8~ 4. > > If it is true, one has to put a tie on each separate pitch: > 8 4. > else g will wait forever and tie to some random pitch somewhere else. Actually, I think that even tieWaitForNotes will stop a chord tie as soon as one note is completed. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ties over multiple chords
Richard Shann writes: > On Fri, 2016-11-11 at 09:15 +0100, Urs Liska wrote: >> Try \set tieWaitForNotes = ##t > > Is there any circumstance in which it is useful to have this set > false? When you want to catch a mistake instead of silently getting ties across half the score? Particularly for stuff like c~ << e \\ c >> d e c you have the effect that the tie will reach across the whole phrase since the second c is not in the tied voice. If LilyPond silently does "something" this may cause a visual surprise when the score is getting used. However, a useful default may also be to draw the tie anyway but _warn_ unless tieWaitForNotes is set. Sure, people ignore warnings all the time but at their own peril. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ties over multiple chords
On 11 November 2016 at 09:49, Richard Shann wrote: > On Fri, 2016-11-11 at 09:15 +0100, Urs Liska wrote: >> Try \set tieWaitForNotes = ##t > > Is there any circumstance in which it is useful to have this set false? > That is, why is it not the default? (I never found this and when > typesetting some music that made extensive use of written arpeggiation, > instead I laboriously constructed workarounds ...) The second alternative in my example is one use case when one might want to have this set to false. If it is set to false, one can simply do: 8~ 4. If it is true, one has to put a tie on each separate pitch: 8 4. else g will wait forever and tie to some random pitch somewhere else. (Not to mention that newbies probably frequently mistakenly use this instead of slurs and might wonder why the connection to a pitch three lines lower.) A bigger problem might be that this command is a bit nontrivial to find. Mojca ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ties over multiple chords
On Fri, 2016-11-11 at 09:15 +0100, Urs Liska wrote:
> Try \set tieWaitForNotes = ##t
Is there any circumstance in which it is useful to have this set false?
That is, why is it not the default? (I never found this and when
typesetting some music that made extensive use of written arpeggiation,
instead I laboriously constructed workarounds ...)
Richard
>
> Am 11. November 2016 08:59:23 MEZ, schrieb Mojca Miklavec
> :
> Hello,
>
> I don't know how to explain in proper terms what I want to achieve,
> but I hope that it will be clear from the example below (I would be
> grateful for a proper English term for this as well :).
>
> I wrote the same thing twice. The second alternative works, but looks
> ugly to me. I would like to use the first alternative (which is a bit
> of cheating), but ties don't work properly there, most likely lilypond
> has problems interpreting where the tie should point to.
>
> Is there any better workaround?
>
> \version "2.19.30"
> \language "deutsch"
>
> melody = \fixed c' {
> \time 2/4
> \key b \major
>
> % first alternative: this doesn't work
> << {f'2~} {s8 d'4.~} {s4 b4~} {s4. g8} >> |
> 4. r8 |
>
> << {f'2~} {s8 es'4.~} {s4 a4~} {s4. g8} >> |
> 4. r8 |
>
> % second alternative: this
> works
> f'8~ 8~ 8~ 8~ |
> 4. r8 |
>
> f'8~ 8~ ~ 8~ |
> 4. r8 |
> }
>
> \new PianoStaff <<
> \new Voice = "melody" {
> \melody
> }
>
>
> (I could cheat with slurs, but I have no clue how to use them in this
> example.)
>
> Thank you,
> Mojca
>
> (please CC me)
>
>
> __
>
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ties over multiple chords
Dear Simon, On 11 November 2016 at 09:16, Simon Albrecht wrote: > On 11.11.2016 08:59, Mojca Miklavec wrote: >> >> Hello, >> >> I don't know how to explain in proper terms what I want to achieve, >> but I hope that it will be clear from the example below (I would be >> grateful for a proper English term for this as well :). >> >> I wrote the same thing twice. The second alternative works, but looks >> ugly to me. I would like to use the first alternative (which is a bit >> of cheating), but ties don't work properly there, most likely lilypond >> has problems interpreting where the tie should point to. >> >> Is there any better workaround? > > > Hi Mojca, > > \set tieWaitForNote = ##t > does the trick. Wonderful, thank you. Is there some way to limit the scope of this command or is it best to simply use \set tieWaitForNote = ##f once I no longer need it? Not that I expect that I'll have to disable it as I usually don't write ties unless I actually need them (except very rarely between chords with less-than-perfect match), I would only like to know the general principle (in TeX there is \begin ... \end :). Thank you, Mojca ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ties over multiple chords
On 11.11.2016 08:59, Mojca Miklavec wrote: Hello, I don't know how to explain in proper terms what I want to achieve, but I hope that it will be clear from the example below (I would be grateful for a proper English term for this as well :). I wrote the same thing twice. The second alternative works, but looks ugly to me. I would like to use the first alternative (which is a bit of cheating), but ties don't work properly there, most likely lilypond has problems interpreting where the tie should point to. Is there any better workaround? Hi Mojca, \set tieWaitForNote = ##t does the trick. Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ties over multiple chords
Try \set tieWaitForNotes = ##t
Am 11. November 2016 08:59:23 MEZ, schrieb Mojca Miklavec
:
>Hello,
>
>I don't know how to explain in proper terms what I want to achieve,
>but I hope that it will be clear from the example below (I would be
>grateful for a proper English term for this as well :).
>
>I wrote the same thing twice. The second alternative works, but looks
>ugly to me. I would like to use the first alternative (which is a bit
>of cheating), but ties don't work properly there, most likely lilypond
>has problems interpreting where the tie should point to.
>
>Is there any better workaround?
>
>\version "2.19.30"
>\language "deutsch"
>
>melody = \fixed c' {
> \time 2/4
> \key b \major
>
> % first alternative: this doesn't work
> << {f'2~} {s8 d'4.~} {s4 b4~} {s4. g8} >> |
> 4. r8 |
>
> << {f'2~} {s8 es'4.~} {s4 a4~} {s4. g8} >> |
> 4. r8 |
>
> % second alternative: this works
> f'8~ 8~ 8~ 8~ |
> 4. r8 |
>
> f'8~ 8~ ~ 8~ |
> 4. r8 |
>}
>
>\new PianoStaff <<
> \new Voice = "melody" {
>\melody
> }
>>>
>
>(I could cheat with slurs, but I have no clue how to use them in this
>example.)
>
>Thank you,
>Mojca
>
>(please CC me)
>
>
>
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
