Re: number of staff lines
On Mon, 06 Feb 2012 15:42:03 +0100 David Kastrup wrote: > Nils writes: > > > Hello, > > > > I would like to ask for a quick confirmation, since I never worked > > with an even-numbered staff line count. > > > > If you reduce your stafflines with > > \override StaffSymbol #'line-count = #3 > > or #1 or any odd number there is no question. With a treble clef the > > b' is on the middle line and lines are removed/added above and below. > > > > with even numbers like #2 or #4 the b' is not on a line anymore but > > all stafflines move one step down so a' and c'' are now on the lines. > > > > Is this correct and common engraver practice? > > Anything but a line count of 5 is not common engraver practice with > modern clefs. The various clefs have a dedicated _line_ they are > focused on. G for the treble clef, F for the bass clef, C for the viola > (tenor?) clef. For square chant notation, you tend to have four lines > and an older clef pointing out the C. > > Personally, I don't know the vertical position of the standard clefs > when using four lines, but I would be very much surprised if they lost > the fixed relation to their "key" line. > > -- > David Kastrup > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > Hello again, I talked to a few persons in the university today and they all agreed that the line on which a clef is is variable for any number of lines. But a clef should be never be in between lines, which is what Lilypond does. Nils ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: possible bug with tupletSpannerDuration in quoted music
Hello, On 5 February 2012 21:24, Shevek wrote: > > In 2.14, tupletSpannerDuration doesn't get properly applied to quoted music > unless tupletSpannerDuration is set in the quoted music itself. Bug, or am I > doing something wrong? Possibly, See: http://lilypond.org/doc/v2.14/Documentation/notation/writing-parts#formatting-cue-notes Also there is a section that states: --snip-- The music from the corresponding measures of the quote name is added as CueVoice context and occurs simultaneously with the music, which creates a polyphonic situation. --snip-- so you may need to create a new voice also --snip-- It is possible to adjust which aspects of the music are quoted with \cueDuring by setting the quotedCueEventTypes property. Its default value is #'(note-event rest-event tie-event beam-event tuplet-span-event), which means that only notes, rests, ties, beams and tuplets are quoted, but not articulations, dynamic marks, markup etc. --snip-- Look at the 4th and 5th example for more explanation. See if this helps -- -- James ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Footers outside the type area
Hannes Kuhnert-2 wrote: > > Hello, > > by default footers are part of the regular type area, but I’d like to have > them placed below. > > Especially the notes should fill the same area on every page, regardless > if > there is a footer or not. “foot-separation“ and the footer itself would > then > lie within “bottom-margin“. This would correspond to the class option > “footexclude” in LaTeX, which is the default setting there. > > How can something like that be achieved in LilyPond? > hi I don't think this is possible by now - I'll wait a while to see if somebody know a way, and will add a an enhancement request if needed. Eluze -- View this message in context: http://old.nabble.com/Footers-outside-the-type-area-tp33270154p33279178.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tremolos between two whole notes
Neil,
Thanks for your answer. I knew there would be a way of doing it with
centering beams and so forth; trouble is I'm soo NOT a programmer and even
the simplest override often takes me a while to work out. If you have any
concrete examples of using these overrides for me, perhaps I could just
plug them in and tweak the numbers a little to suit my own situation? Do
you perhaps have any code you could send so I could have a fiddle?
Brent.
On 4 February 2012 16:42, Neil Thornock wrote:
> As far as getting the look you want, you need to use a combination of
> Beam #'gap, Beam #'positions, Beam #'extra-offset, and NoteHead
> #'stem-attachment. I've gotten very nice results with those
> overrides. It's a pain, but it's worth avoiding the horrible default.
>
> Hope that helps,
> Neil
>
> On Fri, Feb 3, 2012 at 9:00 AM, Brent Annable
> wrote:
> > Hello everyone,
> >
> > I have a question, and perhaps a suggestion. I just typeset the following
> > tremolo between two whole notes:
> >
> > \score {
> > \relative c'' {
> >
> > \repeat tremolo 16 { gis32 b }
> >
> > }
> > }
> >
> > and was quite disappointed by the fact that Lilypond places the tremolo
> > beams horizontally and above the notes in question. I much prefer the
> look
> > of the first tremolo in this image:
> >
> > http://media.wiley.com/assets/25/94/0-7645-5105-1_1309.jpg
> >
> > with the beams tilted and occupying the space in-between the whole
> notes. I
> > read through the manual and searched for some snippets, but couldn't find
> > any reference to this tremolo style at all. Is there any relatively
> simple
> > way of achieving this look that I'm missing? And if not, could a tremolo
> > style option perhaps be added for those who prefer them this way?
> >
> > Brent.
> >
> >
> >
> > ___
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
> >
>
>
>
> --
> Neil Thornock, D.M.
> No Stopping, Standing, or Parking:
> http://neilthornock.net/mp3s/nostopping.mp3
> Assistant Professor of Music
> Composition/Theory
> Brigham Young University
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Footers outside the type area
On 2012-02-07 16:04, -Eluze wrote: Hannes Kuhnert-2 wrote: [...] Especially the notes should fill the same area on every page, regardless if there is a footer or not. [...] I don't think this is possible by now - I'll wait a while to see if somebody know a way, and will add a an enhancement request if needed. Eluze Hi, it's a bit clumsy, but there's a workaround: (Untested for a while, but it used to work back when the vertical spacing variables had other names. You might have to fiddle a bit there.) In the \paper block, set 'last-bottom-spacing to a ridiculously large negative 'padding (like -100 staff units) and a fixed positive 'minimum-distance. Then, the vertical extent of whatever belongs to the bottom-most staff is essentially ignored for vertical spacing because of the 'padding; 'minimum-distance sets the distance from the top of the footer area to the middle staff line of the last staff. Thus, you effectively get the last staff at the same position on all pages, regardless of the footer. If you want the staff to move, but the note with the lowest vertical extent to be in the same position, you can try to use 'padding and 'basic-distance instead. I hope this makes sense to you. If not, come back to me; I can dig out an example of the whole stuff as soon as I'm in front of my private machine again. Best, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Custom paper size
On 6-2-2012 12:19, Jan-Peter Voigt wrote:
Hello Joe,
I sometimes use this:
--snip--
#(set! paper-alist (cons '("wide" . (cons (* 15 cm) (* 3 cm)))
paper-alist))
\paper {
#(set-paper-size "wide")
}
\score {
\relative c'' {
bes4 a c b
}
}
--snip--
\paper {
paper-width = 15\cm
paper-height = 3\cm
}
Also does the job AFAIK and seems more intuitive for the common user I
would say.
Any idea whether using paper-width/paper-heigt settings instead of
defining a new paper size has (unwanted) implications on other parts of
the lay-out that can be avoided by using the paper-alist?
regards,
Hans Aikema
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Default Mark and Tempo
Is there a way of merging the default rehearsal mark
and tempo mark into one mark so that they are
aligned together?
Not like this.
\version "2.14.2"
\relative c'' {
c'1
\mark \default
\tempo "Fast" 4 = 120
c
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Default Mark and Tempo
Nels Daily wrote:
>
> Is there a way of merging the default rehearsal mark
> and tempo mark into one mark so that they are
> aligned together?
> Not like this.
>
> \version "2.14.2"
>
> \relative c'' {
> c'1
> \mark \default
> \tempo "Fast" 4 = 120
> c
> }
>
I'm not sure what kind of alignment you mean - maybe the snippet
http://lsr.dsi.unimi.it/LSR/Item?id=575
http://lsr.dsi.unimi.it/LSR/Item?id=575 can give you some ideas!?
Eluze
--
View this message in context:
http://old.nabble.com/Default-Mark-and-Tempo-tp33281785p33281989.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tremolos between two whole notes
Hi Brent,
> On 4 February 2012 16:42, Neil Thornock wrote:
>>
>> As far as getting the look you want, you need to use a combination of
>> Beam #'gap, Beam #'positions, Beam #'extra-offset, and NoteHead
>> #'stem-attachment. I've gotten very nice results with those
>> overrides. It's a pain, but it's worth avoiding the horrible default.
based on Neil's suggestion I worked out the function above. You have
to figure out the values manually. :(
Please note: If you use "2.14.2" it will sometimes produce a warning,
which I didn't manage to avoid or to suppress: "weird stem size, check
for narrow beams" (p.e. with the cross-staff-example of the test), and
you have to use other values.
With "2.15.24" it compiles clean.
\version "2.15.24"
\paper { line-width = 120 }
tweakWholeNoteTremolo =
#(define-music-function (parser location y¹off-y²off)(pair?)
#{
\once \override Beam #'gap = #1.3
\once \override Beam #'extra-offset = #(cons 0 (car y¹off-y²off))
\once \override Beam #'stencil =
#(lambda (grob)
(let* ((pos (ly:grob-property grob 'positions)))
(ly:grob-set-property! grob 'positions
(cons (car pos) (+ (cdr pos) (cdr y¹off-y²off
(ly:beam::print grob)))
#})
%--- test
\score {
\relative c'' {
\tweakWholeNoteTremolo #'(-3 . 1.9)
\repeat tremolo 16 { gis32 d' }
%\break
\tweakWholeNoteTremolo #'(-3.6 . 1.7)
\repeat tremolo 32 { 64 d' }
\tweakWholeNoteTremolo #'(4.4 . -3.5)
\repeat tremolo 16 { a'32 a, }
}
}
\new PianoStaff <<
\new Staff = "right" {
\repeat tremolo 16 {
\tweakWholeNoteTremolo #'(11.2 . -19)
e'''32
\change Staff = "left"
a,,
}
}
\new Staff = "left" {
\clef bass
s1
}
>>
HTH,
Harm
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tremolos between two whole notes
I should have written: based on Neil's suggestion I worked out the function _below_ (not above). :) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Default Mark and Tempo
Hi Nels,
2012/2/7 -Eluze :
>
>
> Nels Daily wrote:
>>
>> Is there a way of merging the default rehearsal mark
>> and tempo mark into one mark so that they are
>> aligned together?
>> Not like this.
>>
>> \version "2.14.2"
>>
>> \relative c'' {
>> c'1
>> \mark \default
>> \tempo "Fast" 4 = 120
>> c
>> }
>>
> I'm not sure what kind of alignment you mean - maybe the snippet
> http://lsr.dsi.unimi.it/LSR/Item?id=575
> http://lsr.dsi.unimi.it/LSR/Item?id=575 can give you some ideas!?
>
> Eluze
> --
> View this message in context:
> http://old.nabble.com/Default-Mark-and-Tempo-tp33281785p33281989.html
> Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
check out this thread, I think you will receive what you want.
http://old.nabble.com/Spacing-issue-with-ledger-lines-and-custom-Marks-context-td33265399.html
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: number of staff lines
My understanding is that the scholarly convention for describing clefs is the clef's note (g1, c1, f, G) followed by the line number, counted from the bottom. Thus on a five line staff, French violin clef is g1, treble clef is g2, soprano clef is c1, mezzo-soprano clef is c2, alto clef is c3, tenor clef is c4, baritone clef is c5 or f3, bass clef is f4, sub-bass clef is f5, gamma clef is G3 (where gamma in the bottom of the gamut [ gamma to ut ], a bass singer's low G ). The merit of the scheme is that it specifies pitch unambiguously for the common five-line staff, chant four-line staff, which has a clef signature for c1 on any of the four lines, and Escorial, which has a six line staff, or for a staff with any other number of lines. It does, however, assume that the various specified notes fall on a line, which is not the case with a staff displaced by octaves, such as the common convention of notating a tenor line in tenor clef an octave down. Such cases, however, are normally notated as an octave (or more) up or down. LilyPond in my experience supports the cx (x=1,...) nicely for a five line staff. I haven't tried it out for other number of lines in the staff. I think also the fx (x=1,...). On Tue, Feb 7, 2012 at 6:57 AM, Nils wrote: > On Mon, 06 Feb 2012 15:42:03 +0100 > David Kastrup wrote: > > > Nils writes: > > > > > Hello, > > > > > > I would like to ask for a quick confirmation, since I never worked > > > with an even-numbered staff line count. > > > > > > If you reduce your stafflines with > > > \override StaffSymbol #'line-count = #3 > > > or #1 or any odd number there is no question. With a treble clef the > > > b' is on the middle line and lines are removed/added above and below. > > > > > > with even numbers like #2 or #4 the b' is not on a line anymore but > > > all stafflines move one step down so a' and c'' are now on the lines. > > > > > > Is this correct and common engraver practice? > > > > Anything but a line count of 5 is not common engraver practice with > > modern clefs. The various clefs have a dedicated _line_ they are > > focused on. G for the treble clef, F for the bass clef, C for the viola > > (tenor?) clef. For square chant notation, you tend to have four lines > > and an older clef pointing out the C. > > > > Personally, I don't know the vertical position of the standard clefs > > when using four lines, but I would be very much surprised if they lost > > the fixed relation to their "key" line. > > > > -- > > David Kastrup > > > > > > ___ > > lilypond-user mailing list > > lilypond-user@gnu.org > > https://lists.gnu.org/mailman/listinfo/lilypond-user > > > > > Hello again, > > I talked to a few persons in the university today and they all agreed that > the line on which a clef is is variable for any number of lines. > But a clef should be never be in between lines, which is what Lilypond > does. > > Nils > > ___ > 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
grace note issue/bug
I have a couple of issues with the attached ly file, version 2.14.2: 1. I get the warning "forced break was overridden by some other event, should you be using bar checks?". Hence, I can't add breaks or pagebreaks wherever I want to. 2. A weird pdf when I add a \grace to the first note in the first measure. If I comment out lines 26 and 27 in the file and uncomment lines 29 and 30, everything works fine. Stumped!. Ly file: http://old.nabble.com/file/p33283512/Gracebug.ly Gracebug.ly Snapshot: http://old.nabble.com/file/p33283512/GraceBug.png GraceBug.png Thanks. -- View this message in context: http://old.nabble.com/grace-note-issue-bug-tp33283512p33283512.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Experimental Web-based Lilypond Editor
First round of Dropbox integration launched, but it won't let anybody log in until Dropbox approves the app for production mode. trevordixon wrote: > > I've been working on something I think the LilyPond community may find very useful: a web-based editor. Before you check it out, keep in mind that it's at a pre-alpha stage. It's likely that certain things won't work as expected, and it will probably crash and be down at times. I've only tested it in Chrome 15 and Firefox 9. It should work in Internet Explorer 9 or 10, but will almost certainly not work in IE8 or earlier. > > Saving will create a new URL that you can share with others. If they save, it will be saved as a new revision, preserving your original. > > This could be useful for: > > Posting example code that you'd like others to look at and mess with. > Quick projects when you don't have access to your regular development environment. > Perhaps as your main editor someday. > > > Future features might include: > > Ability to open and save to your hard drive. > Ability to open and save to Dropbox. > Open to suggestions. > > > See it at: http://lily.sytes.net http://lily.sytes.net > > Let me know how it works for you! > -- View this message in context: http://old.nabble.com/Experimental-Web-based-Lilypond-Editor-tp33242123p33284055.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
