Re: Breton bagpipe notation
Eluze wrote
>
> guocuozuoduo wrote
>> Is it possible to setup the basic template for Breton bagpipe notation?
>> (as opposed to Scottish notation, Breton notation has all melody notes
>> stem-up and all grace notes/embellishments stem-down.)
>>
> can you simply reverse the definitions in the \layout section?
> or can you give a tiny example how this should look like? Scottish and
> Breton?
guocuozuoduo wrote
> \score {
> \new Staff {
> \key d \major
> \marchTime
> \bar ".|"
> \stemUp
> \partial 8 e8
> \stemDown \grg
> \stemUp a4
> \stemDown \taor
> \stemUp a8. b16
> \stemDown \dblc
> \stemUp c8
> \stemDown \gre
> \stemUp a
> \stemDown \dblc
> \stemUp c e
> \stemDown \dblA
> \stemUp A4
> \stemDown \grg
> \stemUp A
> \stemDown \grip
> \stemUp A8 e
> \stemDown \dblc
> \stemUp c
> \stemDown \gre
> \stemUp a
> }
> \header {
> piece = "Breton notation"
> }
> \layout {
> \context {
> \Voice
> % All stems go up.
> \override Stem.direction = #UP
> % How would you tell LP that all \pgrace needs to be stem-down while the
> remaining notes to be stem-up?
> % All slurs and ties are below.
> \override Slur.direction = #DOWN
> \override Tie.direction = #DOWN
> }
> }
> }
> [...]
please always respond to the list!
please always send such lists of code as file attachment (if needed at all)!
to your question:
$(add-grace-property 'Voice 'Stem 'direction -1)
in the code or layout section should do the trick.
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Breton-bagpipe-notation-tp159010p159071.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: Horizontalized scores
Thanks Janek! Jay's suggestion worked great. I've been talking with Adam as well and will dig into the ly2video project when I get a chance - could definitely be a lot of overlap with Notezilla! All the best, Erik On Sat, Feb 8, 2014 at 4:36 PM, Janek Warchoł wrote: > Hello, > > 2014-02-07 19:24 GMT+01:00 Erik Linde : > > Hi, > > > > I am the creator of Notezilla, a popular (and fairly new) web application > > that allows users to both listen to classical music, as well as see a > > scrolling representation of the score that has been synced exactly to the > > recording. > > this looks very nice! I haven't heard about it before. > > I hope that Jay's suggestion worked for you. Btw, you may find this > project interesting: https://github.com/aspiers/ly2video > > best, > Janek > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Horizontalized scores
Hello Jay,
Thanks for the tip, I tried it and it works wonders! Truly excellent, will
save me enormous amounts of time :)
Lunch on me if you come to NYC!
Best,
Erik
On Fri, Feb 7, 2014 at 6:36 PM, Jay Anderson wrote:
> On Fri, Feb 7, 2014 at 11:24 AM, Erik Linde wrote:
> > Typically the way we have been generating the images of the sheet music
> that
> > we use on the website, is by setting some of the layout attributes to
> really
> > large values, for example:
> >
> > ragged-last = ##t
> > paper-width = 2400.0\cm
> > paper-height = 50.0\cm
> >
> > or perhaps
> >
> > #(set! paper-alist (cons '("my size" . (cons (* 2000 in) (* 50 in)))
> > paper-alist))
> > #(set-default-paper-size "my size")
> >
> > And then generating a pdf, which we then convert to images.
> >
> > This works very well when generating a simple piece, such as a piano
> piece,
> > but whenever there are multiple instruments, and when the piece is very
> > long, such as is the case for most symphonies (which happen to be the
> most
> > popular pieces on Notezilla), the time required to typeset a file seems
> to
> > increase exponentially with the complexity of the music.
> >
> > For a symphony, it could easily go from a few minutes, when using a
> default
> > layout, such as A4 or letter, to upwards of 10 hours, when using a custom
> > paper format that is extremely wide, for example a 500cm or 1000cm in
> width.
> > Please feel free to use this link to download the example that
> illustrates
> > this - Beethoven's 3rd Symphony Mvt. 1. If I try running "lilypond
> > ScoreMvtI.ly" in this example in a default layout, it takes maybe 10-15
> > minutes or so to typeset. If I uncomment row 27 and 28 (which is where I
> > specify the *huge* paper size), it takes maybe 10 hours...
> >
> > I am wondering if someone on this mailing list knows of any work-arounds
> or
> > tricks that I could employ here to shorten the this time? The only
> > requirements for us is that, in the end, that we get one long horizontal
> > score, where the vertical spacing between the staffs is identical
> throughout
> > the piece. Whatever method we can use to get there would be great to hear
> > about! Maybe one way could be to split up the score into just 3-4 rows
> > instead, and then merge these in Photoshop - my concern with that method
> > would be that the vertical distances between staffs would probably not be
> > identical, which would mean that the horizontal score simply would not
> > work...
>
> Try this:
>
> \paper {
> page-breaking = #ly:one-line-breaking
> }
>
> This should make the compilation much quicker. Also "\override
> Score.NonMusicalPaperColumn #'line-break-permission = ##f" may be
> useful.
>
> -Jay
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Breton bagpipe notation
guocuozuoduo wrote
> Is it possible to setup the basic template for Breton bagpipe notation?
> (as opposed to Scottish notation, Breton notation has all melody notes
> stem-up and all grace notes/embellishments stem-down.)
>
> Here is the code for Scottish notation:
>
> \version "2.19.2"
> \layout {
> ...
can you simply reverse the definitions in the \layout section?
or can you give a tiny example how this should look like? Scottish and
Breton?
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Breton-bagpipe-notation-tp159010p159066.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: Fwd: [SNIPPET] Text with Lettrine
Schneidy wrote > Please find herewith a short text that starts with a lettrine. > Up to now, it was a headache for me to set the first two lines but thanks > to Mike and David it's much easier now. great! sounds like it could be enhanced to simplify the input with a function?! parameter 1 lettrine parameter 2 capitalized text parameter 3 flow text (without deeper thoughts) thanks for your effort so far! Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Fwd-SNIPPET-Text-with-Lettrine-tp159028p159065.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: Define custom/new \accidentalStyles (dodecaphonic minus repeated notes)
Hi Urs,
On Mon, Feb 3, 2014 at 3:16 AM, Urs Liska wrote:
> Hi,
>
> searching the docs and the lilypond-user archive I couldn't find any
> relevant information.
>
> I am looking for a custom \accidentalStyle. Actually I think this is quite
> commonly used, so it would also seem like a useful addition to LilyPond
> proper.
>
> a)
> Every note gets an explicit accidental (including a natural),
> as in the 'dodecaphonic style,
> _except_ when a note is repeated immediately in the same voice.
>
I've seen it too, and I think it would be good to include it.
>
> When looking into music-functions.scm and its set-accidental-style I see
>
> ((equal? style 'dodecaphonic)
> (set-accidentals-properties #f
> `(Staff ,(lambda (c p bn mp) '(#f . #t)))
> '()
> context))
>
>
> So it seems the way to go to make a copy of that definition (e.g. with
> comparing against 'dodecaphonic-no-repeat) and modifying the definition.
>
Yes. That's what I do in the attached file.
>
> Unfortunately I don't have a clue how to proceed. Any trials are simply
> anwered by errors, so I'd prefer not to _try_ but to do at least _informed
> guesses_ ;-)
>
> I assume that the
> `(Staff
> expression returns the
> context pitch barnumber measureposition
> arguments for
> set-accidental-properties
> so this seems the place to define the right arguments.
>
> Unfortunately I haven't _fully_ understood lambda expressions and _barely_
> understood quoting and unquoting.
>
> So I'd be glad about hints/explanations/solutions to
>
> a)
> create a differing but valid argument list at all and
> b)
> determining which '(#f . #t) combinations to use for my purpose.
>
>
I confess that I find what goes on in the source a bit confusing, but I did
come up with something that appears to work. I make no claims about having
done this the right way :)
First of all, I looked at clauses other than that for dodecaphonic for
inspiration, since that one is only good for hit-it-with-a-hammer
situations, and you need some refinement here. You definitely want the
initial #f which prevents old-style cancellations--the extra natural when
flat follows double-flat, but you need some variability in your setting of
the cdr--that is, auto-accidentals.
I used neo-modern as a starting point, and wrote a
'dodecaphonic-no-repeat-rule'.
I had to copy other functions from scm/music-functions.scm since they're
not define-public.
The file includes the demonstration example from the NR.
--David
\version "2.18.0"
%% LOCAL FUNCTIONS FROM scm/music-functions.scm
#(define (key-entry-notename entry)
"Return the pitch of an @var{entry} in @code{localKeySignature}.
The @samp{car} of the entry is either of the form @code{notename} or
of the form @code{(octave . notename)}. The latter form is used for special
key signatures or to indicate an explicit accidental.
The @samp{cdr} of the entry is either a rational @code{alter} indicating
a key signature alteration, or of the form
@code{(alter . (barnum . measurepos))} indicating an alteration caused by
an accidental in music."
(if (pair? (car entry))
(cdar entry)
(car entry)))
#(define (key-entry-octave entry)
"Return the octave of an entry in @code{localKeySignature}
or @code{#f} if the entry does not have an octave.
See @code{key-entry-notename} for details."
(and (pair? (car entry)) (caar entry)))
#(define (key-entry-bar-number entry)
"Return the bar number of an entry in @code{localKeySignature}
or @code {#f} if the entry does not have a bar number.
See @code{key-entry-notename} for details."
(and (pair? (cdr entry)) (caddr entry)))
#(define (key-entry-measure-position entry)
"Return the measure position of an entry in @code{localKeySignature}
or @code {#f} if the entry does not have a measure position.
See @code{key-entry-notename} for details."
(and (pair? (cdr entry)) (cdddr entry)))
%%% END COPIED STUFF
%% BASED on 'neo-modern-accidental-rule' %%
#(define-public (dodecaphonic-no-repeat-rule context pitch barnum measurepos)
(let* ((keysig (ly:context-property context 'localKeySignature))
(entry (find-pitch-entry keysig pitch #t #t)))
(if (not entry)
(cons #f #t)
(let* ((entrymp (key-entry-measure-position entry))
(entrybn (key-entry-bar-number entry)))
(cons #f
(not
(and (equal? entrybn barnum) (equal? entrymp measurepos
%% FROM scm/music-functions.scm with another style added %%
#(define-public (set-accidental-style style . rest)
"Set accidental style to @var{style}. Optionally take a context
argument, e.g. @code{'Staff} or @code{'Voice}. The context defaults
to @code{Staff}, except for piano styles, which use @code{GrandStaff}
as a context."
(let ((context (if (pair? rest)
(car rest) 'Staff))
(pcontext (i
Re: Custom clef
catal...@hotmail.com wrote > I searched how to define a new clef or how to make a \markup block behave > like a clef, unsuccessfully. Here is a snippet that may also be of help: "Using non-standard clef positions and adding customized clef definitions" http://lsr.dsi.unimi.it/LSR/Item?id=401 And an updated version of it I made: http://lsr.dsi.unimi.it/LSR/Item?id=893 (It hasn't been approved yet so it doesn't show up in the LSR search.) HTH, -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/Custom-clef-tp159049p159060.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: [LilyJAZZ] MetronomeMark.style broken in 2.19.0?
> Federico Bruni schrieb: >> 2014-02-09 19:52 GMT+01:00 Thomas Morley : >> >>> I'm not sure which version of the LilyJazz code you use. >>> There are so many around. I even got confused on my own computer. >>> I append the ones I included above. >>> >> >> We should put it here: >> https://github.com/openlilylib/snippets/tree/master/custom-music-fonts/LilyJAZZ > > Yes! Please someone with the necessary skills do it, it will be a nice > complement to the SMuFL adaptor already there. Is it only that? I thought the original author was not reachable to agree on a licence. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Writing LilyPond files conditional on LilyPond version (Wikimedia Score extension)
Am 09.02.2014 23:15, schrieb David Rydh: Hi, I'm experimenting with MediaWiki's Score extension. The current version of the Score extension, 0.2, runs lilypond with -dsafe="#t" (and not --jail) which is quite restrictive. Would it be conceivable to make more Scheme-symbols public in safe mode in future versions of LilyPond? Example: ly:breathing-sign::divisio-maxima etc cannot be used. A better solution would be to convince the Score-developer to use --jail but this would perhaps demand too much from the server owner? I also don't have any control over the version of LilyPond that is installed on the server (typically not so recent) and Score does not attempt to convert the input file so files may break when the version changes. I will ask the Score developer to use convert-ly in the next version. Until then, it could be useful to write ly-files that are sensitive to the version of lilypond. Moreover, even if a conversion is in place, it would be useful to access more recent features if present. Thus, I have two scenarios: 1) I would like to use certain features if they are available (version >=2.16 say) \version "2.14.2" if version >= 2.16 then lily-code fi 2) Manually convert between versions \version "2.14.2" if version >= 2.16 then converted lily-code else old lily-code fi Since the lily-code is running in safe-mode, as mentioned above, there is a very limited repertoire of scheme code that can be used (e.g. ly:parser-include-string cannot be used). Is such conditional lily-code possible to write? In safe mode? I think this should be possible: https://github.com/openlilylib/snippets/blob/master/general-tools/lilypond-version-predicates/definitions.ily https://github.com/openlilylib/snippets/blob/master/general-tools/lilypond-version-predicates/example.ly Thanks in advance, David ___ 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
Writing LilyPond files conditional on LilyPond version (Wikimedia Score extension)
Hi, I'm experimenting with MediaWiki's Score extension. The current version of the Score extension, 0.2, runs lilypond with -dsafe="#t" (and not --jail) which is quite restrictive. Would it be conceivable to make more Scheme-symbols public in safe mode in future versions of LilyPond? Example: ly:breathing-sign::divisio-maxima etc cannot be used. A better solution would be to convince the Score-developer to use --jail but this would perhaps demand too much from the server owner? I also don't have any control over the version of LilyPond that is installed on the server (typically not so recent) and Score does not attempt to convert the input file so files may break when the version changes. I will ask the Score developer to use convert-ly in the next version. Until then, it could be useful to write ly-files that are sensitive to the version of lilypond. Moreover, even if a conversion is in place, it would be useful to access more recent features if present. Thus, I have two scenarios: 1) I would like to use certain features if they are available (version >=2.16 say) \version "2.14.2" if version >= 2.16 then lily-code fi 2) Manually convert between versions \version "2.14.2" if version >= 2.16 then converted lily-code else old lily-code fi Since the lily-code is running in safe-mode, as mentioned above, there is a very limited repertoire of scheme code that can be used (e.g. ly:parser-include-string cannot be used). Is such conditional lily-code possible to write? In safe mode? Thanks in advance, David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Custom clef
Am 09.02.2014 21:54, schrieb catal...@hotmail.com:
Hi list,
I have a cello score using 2 staves, the extra being used to display movements
of the bow (sul tasto / sul ponticello), using glissandi (on a staff with a
single line).
This extra staff has a special "clef" that looks like this:
SP
ST
How can I make this text behave like a clef, i.e. repeating at the beginning of
every line ?
I searched how to define a new clef or how to make a \markup block behave like
a clef, unsuccessfully.
See the attachment. You can play with the values for font-size and
baseline-skip yccording to your needs.
HTH,
Marc
\version "2.18.0"
#(add-new-clef "SPST" "markup.spst" 0 0 0)
#(define-markup-command (spstClef layout props) ()
(interpret-markup layout props
(markup #:vcenter #:bold
#:override (cons 'font-family 'sans)
#:fontsize 1
#:override (cons 'baseline-skip 2)
#:left-align #:center-column ("SP" "ST"
#(define-public (clef::print-spst-if-set grob)
(let ((glyph (ly:grob-property grob 'glyph)))
(if (string=? glyph "markup.spst")
(grob-interpret-markup grob (make-spstClef-markup))
(ly:clef::print grob
\score {
<<
\new Staff {
\clef "bass"
s1
}
\new Staff \with {
\override StaffSymbol.line-count = #1
\override Clef.stencil = #clef::print-spst-if-set
} {
\clef "SPST"
s1
}
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \fill-line while respecting natural widths
2014-02-08 23:22 GMT+01:00 Kieren MacMillan : > Hi David, > >> Hmm--do you think it should be added as an option to \fill-line? > > DEFINITELY! +1000 - this is awesome! As for now, i have added it to the snippets repo(https://github.com/openlilylib/snippets/commit/4bb8a0456c42d5859cd6945b4213901785cfbd23), but please go ahead and add it to official lily! I think it is a feature important enough to warrant a new function. > As just one example: I’m going to use it in the musical theatre scores I’m > engraving right now, > to [evenly] space two columns of dialogue above a system of underscore music. Also, it will be perfect for aligning stanzas for songs. I have already used it in the openlilylib/snippets stanza template (which could be turned into a function, btw - didn't have time to do it myself, yet...): https://github.com/openlilylib/snippets/blob/master/templates/adjustable-centered-stanzas/definitions.ily https://github.com/openlilylib/snippets/commit/eeb8d075dff02d29f02316345774fd18c7a5c732 2014-02-09 12:53 GMT+01:00 Alexander Kobel : > The rationale for \fill-line IMHO is only to be used for one, two or three > arguments, which is the common case in headings. One for center-aligned > (which should be available as \center-line on it's own...), two for > left-right-aligned, three for left-center-right-aligned. That's it. > Everything else gives highly unintuitive results. It's the analogue of one > of the rare features I miss in OpenOffice vs. Word: In the latter, you can > specify the horizontal alignment for groups of words in a single line, > separated by tabs. yes, very good observation! \fill-line is needed exactly for that, and because of this we should keep it like it is (and add David's work as a new function). I won't have time to follow this topic closely, but i support David's efforts! best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ligatures in music font
On Sun, Feb 9, 2014 at 7:31 AM, Noeck wrote: > > [...] > > Hmm, yes for the tuplet5 yes. But not for the tuplet8 that I wanted to > use. So perhaps that’s just a bug in the font? > I can confirm that it doesn't work for tuplet8; in addition, the SMuFL spec mysteriously skips over the gClefLigatedNumberAbove+tuplet8 ligature. Weird. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Custom clef
Hi list, I have a cello score using 2 staves, the extra being used to display movements of the bow (sul tasto / sul ponticello), using glissandi (on a staff with a single line). This extra staff has a special "clef" that looks like this: SP ST How can I make this text behave like a clef, i.e. repeating at the beginning of every line ? I searched how to define a new clef or how to make a \markup block behave like a clef, unsuccessfully. Thanks for your help! Martin ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [LilyJAZZ] MetronomeMark.style broken in 2.19.0?
Am 09.02.2014 20:14, schrieb Marc Hohl: Am 09.02.2014 19:52, schrieb Thomas Morley: 2014-02-09 11:31 GMT+01:00 Marc Hohl : Hi list, I use LilyJAZZ in one of my latest projects. Thanks to Harm's patch, it was possible to use the Jazz font in tempo markings, but this seems to be broken: [...] Hi Marc, Hi Harm, it looks as if I hallucinated – I was sure that I used \tempo in combination with LilyJAZZ in a compilable file *without* any add-ons. Ok, my mind is quite ok – it seems that I had a printout with my \mark\jazzTempoMarkup function and thought that this was coded with \tempo ... my fault. Other that that, your code works perfectly for me – I shortened the stems by 0.666, now it looks quite good. Thanks a lot for your work! You just insured my project deadline. Marc ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [LilyJAZZ] MetronomeMark.style broken in 2.19.0?
Federico Bruni schrieb: >2014-02-09 19:52 GMT+01:00 Thomas Morley : > >> I'm not sure which version of the LilyJazz code you use. >> There are so many around. I even got confused on my own computer. >> I append the ones I included above. >> > >We should put it here: >https://github.com/openlilylib/snippets/tree/master/custom-music-fonts/LilyJAZZ Yes! Please someone with the necessary skills do it, it will be a nice complement to the SMuFL adaptor already there. > >It was in my TODO list but I don't have any time at the moment > > > > >___ >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: [LilyJAZZ] MetronomeMark.style broken in 2.19.0?
Am 09.02.2014 19:52, schrieb Thomas Morley: 2014-02-09 11:31 GMT+01:00 Marc Hohl : Hi list, I use LilyJAZZ in one of my latest projects. Thanks to Harm's patch, it was possible to use the Jazz font in tempo markings, but this seems to be broken: [...] Hi Marc, Hi Harm, it looks as if I hallucinated – I was sure that I used \tempo in combination with LilyJAZZ in a compilable file *without* any add-ons. A quick glance at your detailed response and your solutions showed me that I was wrong, obviously. Strange, very strange ... But nevertheless, thanks a lot for your code, I hope that it will work flawlessly within my project. All the best, Marc ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [LilyJAZZ] MetronomeMark.style broken in 2.19.0?
2014-02-09 19:52 GMT+01:00 Thomas Morley : > I'm not sure which version of the LilyJazz code you use. > There are so many around. I even got confused on my own computer. > I append the ones I included above. > We should put it here: https://github.com/openlilylib/snippets/tree/master/custom-music-fonts/LilyJAZZ It was in my TODO list but I don't have any time at the moment ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \fill-line while respecting natural widths
On 02/08/2014 11:22 PM, Kieren MacMillan wrote: Hi David, Hmm--do you think it should be added as an option to \fill-line? DEFINITELY! As just one example: I’m going to use it in the musical theatre scores I’m engraving right now, to [evenly] space two columns of dialogue above a system of underscore music. But maybe it should be its own separate function, e.g., \spaced-line, or some such thing? Agreed. What about \equispaced-line? The rationale for \fill-line IMHO is only to be used for one, two or three arguments, which is the common case in headings. One for center-aligned (which should be available as \center-line on it's own...), two for left-right-aligned, three for left-center-right-aligned. That's it. Everything else gives highly unintuitive results. It's the analogue of one of the rare features I miss in OpenOffice vs. Word: In the latter, you can specify the horizontal alignment for groups of words in a single line, separated by tabs. \fill-line might not be the best name for that, but it's late to change it. (\equicentered-line? Leftmost and rightmost element don't fit in, though...) And it's description is really bad, now that I read it again... BTW, I'd like to see collision avoidance there (and there should be a comment in the code on what's necessary), but probably it's overkill for what it's used for. On the other hand, especially for two-column-dialogues or verses, I always end up to use manually spaced columns: I want a consistent column separation, I (usually) want columns of consistent width, and I (usually) want the columns to start at the same horizontal position. At least if you have several of those places. Then, it's almost no difference whether you use \spaced-line (\equispaced-line?) or simply a \fill-line (as \center-line) of $stuff to autocalculate left and right margin. Best, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ligatures in music font
Am 09.02.2014 00:19, schrieb Nathan:
> On Sat, Feb 8, 2014 at 2:37 PM, Noeck wrote:
>> Hi again,
>>
\markup {
\fontsize #5
\override #`(font-name . ,smufl-font)
#(markup (string-append
(ly:wide-char->utf-8 (cdr (assoc
"gClefLigatedNumberAbove" smufl-map)))
(ly:wide-char->utf-8 (cdr (assoc "tuplet8" smufl-map)
}
>>
>> But do you know why it does not work with "Above", the clef looks right,
>> but the ligature does not work.
>>
>
> Hmm, it seems to work for me. Are you getting the attached output?
>
Hmm, yes for the tuplet5 yes. But not for the tuplet8 that I wanted to
use. So perhaps that’s just a bug in the font?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE[2]: Harp-Symbols in LilyPond
Many thanks.
> \new Voice = "melody" {
> \set melismaBusyProperties = #'()
> c''4 ( d''4 )
This will affekt all lyrics , all stanzas. But I need this only for the
harp-symbols, not
for stanzas.
With your help I could find a more better solution.
http://lilypond.org/doc/v2.19/Documentation/notation/stanzas#stanzas-with-different-rhythm
s
MuHaOben = \lyricmode {
\set ignoreMelismata = ##t%% ignors slurs and other
\blasenI \blasenII%% harp-symbols
\unset ignoreMelismata%% back to normal
}
MuHaUnten = \lyricmode {
\set ignoreMelismata = ##t
\blasenII \blasenIII
\unset ignoreMelismata
}
StropheI = \lyricmode {
\set stanza = "1."
Lyric Text %% this text is shown in the normal way
}
Now it looks fine.
Regards, Frank
>- Original Message -
>From:
>To:
>Sent: Wednesday, February 05, 2014 10:08 PM
>Subject: RE[2]: Harp-Symbols in LilyPond
>
>
>> \set melismaBusyProperties = #'()
>> this moves the symbol from the middle to the beginning of the slur
>> example c4( d4)
>> I like to have a symbol above both - c and d
>> It should work like c4 d4 (without slurs)
>>
>> I'm looking for something like this:
>>
>> Oben = \lyricmode {
>>\ignor_slures
>>...
>> }
>>
>> BTW
>>>Alternatively, you could experiment with putting your harp symbols in a
>>>dynamics context?
>>
>> I do not understand this statement. Would you please give me an example?
>> May be this can
>> help to solve my problem.
>>
>> Regards, Frank
>
>Firstly, please remember to reply-all, rather than to me indivually.
>
>Secondly, could I recommend a study of the lilypond manuals? For example, I
>suggested using "set melismaBusyProperties". This is documented in the
>Notation Reference and shows how slurs are ignored and a lyric is placed on
>each note. A cut down example is:
>
><<
>\new Voice = "melody" {
>\set melismaBusyProperties = #'()
>c''4 ( d''4 )
>}
>\new Lyrics \lyricsto "melody" {
>a b
>}
>>>
>
>which appears to work exactly as you want: see the attached image.
>Similarly, searching for "dynamics context" will lead to:
>
>http://lilypond.org/doc/v2.19/Documentation/notation/expressive-marks-attached-to-notes#dynamics
>
>which says:
>
>"A Dynamics context is available to engrave dynamics on their own horizontal
>line. Use spacer rests to indicate timing. (Notes in a Dynamics context will
>also take up musical time, but will not be engraved.) The Dynamics context
>can usefully contain some other items such as text scripts, text spanners,
>and piano pedal marks."
>
>--
>Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How do I end an extender line?
- Original Message - From: "Frank Steinmetzger" To: Sent: Sunday, February 09, 2014 2:50 PM Subject: How do I end an extender line? I'm not sure if there's a "right" way, but I do something similar: I use a space in quote marks: " " -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
How do I end an extender line?
Dear list
I'm setting a score in which the women (one staff) and men (another
staff) each sing solo stanzas, then the chorus together, and then alone
again. The order of parts is this:
Men stanza, lyrics attached to men voice, below men staff
Chorus, lyrics attacged to women voice, centered between the staves
Women stanza, lyrics attached to women voice, below women staff
Chorus (same as first chorus)
My problem is: The first stanza (which is for men) ends with an extender
line. During the chorus, the lyrics are covered by the lyrics context
centered between the staves, so the men's lyrics are empty:
{ \repeat unfold 16 _ }
This, however, gives me an extender throughout the entire chorus until
the next proper syllable in the men's lyrics context. To circumvent
that, I inserted a unicode thinspace as lyrics for the men's chorus. It
is invisible but counts as a syllable.
What is the *proper* way here? Searching for this problem I only found
messages about the other way around, where the extender was not spanned
over single underscores (which was reported as a bug).
The only other solution I come up with is to use one single lyrics block
and insert many \set associatedVoice.
Cheers
--
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any Facebook service.
I cried because I had no shoes. Until I saw someone who had no feet.
signature.asc
Description: Digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problems installing Frescobaldi for Mac, issue with py27-pyqt4 install
Dear Carl, 2014-02-09 6:48 GMT+01:00 Carl Peterson : > Please see the log file for port py27-pyqt4 for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pyqt4/py27-pyqt4/main.log Can you please send that file to me? I'll have a look at it and see if I can help. Best wishes. Davide Liessi ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Scheme: default values?
Am 02.02.2014 12:58, schrieb Graham King:
On Sun, 2014-02-02 at 08:51 +0100, Marc Hohl wrote:
Am 29.01.2014 06:41, schrieb Graham King:
To generate MIDI output, I use a piece of boilerplate lilypond code,
containing:
\midi { \context { \Score tempoWholesPerMinute = #currentTempo }}
where it is expected that:
currentTempo = #(ly:make-moment TACTUS RF)
I would like to generalise the boilerplate code so that it works with
suitable defaults even when these variables have not been defined.
Where do you want to define these variables? If you want to use them
via the command line, you can do it as follows (untested!):
Thanks Marc. Normally, TACTUS and RF would be defined at the top level
of a .ly file that \include's the boilerplate. I'm now wondering
whether Guile's catch and throw mechanism is the way to go. There's
some reading and experimenting ahead...
I found another solution somewhere buried in my files:
#(define TACTUS
(if (defined? TACTUS)
TACTUS
50))
Perhaps that's something better suited to your needs?
Marc
___
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
[LilyJAZZ] MetronomeMark.style broken in 2.19.0?
Hi list,
I use LilyJAZZ in one of my latest projects. Thanks to Harm's patch,
it was possible to use the Jazz font in tempo markings, but this
seems to be broken:
\version "2.19.0"
\include "LilyJAZZ.ily"
\score {
\new Staff {
\jazzOn
\override Score.MetronomeMark.font-name = "LilyJAZZText"
\override Score.MetronomeMark.flag-style = #'jazz
\override Score.MetronomeMark.style = #'jazz
\tempo "Slowly" 2 = 60 c'1
}
}
The font is right, but the note appears in the wrong style.
I know that this worked some time before 2.19 but I don't see
any changes in the sources that might have lead to this erroneous
behavior.
Any ideas what's wrong here?
Marc
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
