Re: title on a separate page (Susan Dittmar)
> But you'll need to make sure the music that's actually used in the sample is > public domain. Please use some other music for the example. I do not know under which license, if at all, Eva pubished the tune. One of the reasons why I just posted an except... Susan pgpmip7EQupKf.pgp Description: PGP signature ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: title on a separate page
Sorry to come a day after the fair... Susan Dittmar a écrit : > Hello folks, > > I am very sorry in case this is a FAQ. I am quite new to lilypond and > maybe did not search the right places. > > I would like to have lilypond generate the title on a page of its own. Isn't that the purpose of the "breakbefore" property inside \header block? (This is a true question, apparently it seems to do nothing with me...) Valentin Villenave a écrit : > By the way, why the mao haven't we included Nicolas' \vspace command > in LilyPond already? I'll send a patch right now. By the way there is also Nicolas' nice ready-to-use "stylesheet" that creates a nice title page. Please see : http://lsr.dsi.unimi.it/LSR/Item?id=368 Sincerely, Xavier ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Vertical spacing
For any vertical spacing problem, please use 2.12 instead; Joe Neeman
has been responsible of a rework of vertical spacing, but he is too
much occupied these days, we all are. See below
2009/10/7 Thomas Scharkowski :
> I hav eadded two pngs to clarify:
> With 2.13.3 "between-system-padding" and "\override
> Staff.VerticalAxisGroup" work as expected, in 2.13.4 there is no effect.
2009/8/4 Joe Neeman :
> The interaction between the different xxx-spacing variables is a little
> complex and I need to document it properly. In this case, the problem is
> that Lyrics are unaffected by between-staff-spacing (because they are
> non-spaceable) and so your override only forces there to be one staff
> unit of padding between adjacent _staves_, which is satisfied by your
> example. Unfortunately, there is not yet any way to control the spacing
> between Lyrics and the staff below it, which is where you really want
> the extra padding AFAICT.
Joe: is this already documented? Hot to control spacing from a lyrics
line and the staff below it? Simple lyrics seem to almost collide.
<< \new Staff { a } \addlyrics { pain }
\new Staff { f' }
>>
Joe: I hate to bug you again, but several users are asking vertical
spacing to have usable defaults and a documentation. Just give us a
hint about when do you think this feature will be finished. Thank you!
In the meantime I recommend users to stay on 2.12
--
Francisco Vila. Badajoz (Spain)
www.paconet.org
www.csmbadajoz.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Error not indicated
On 10/6/09 3:30 PM, "Nick Payne" wrote: > If I accidentally omit the spaces in the scheme pair for the tweak > offset, no error is indicated in the console output but the tweak > doesn't take effect. If either (or both) of the spaces surrounding the . in the pair are missing, then the data structure you are creating is no longer a cons cell of two numbers. '(0 . 1) is a cons cell with 0 as the car and 1 as the cdr '(0. 1) is a list; a cons cell with 0 as the car , and a cons cell with 1 as the car and '() as the cdr as the cdr. i.e. car is 0, caar is 1 cadr is '() '(0 .1) is a list; car is 0, caar is 0.1, cadr is '() '(0.1) is a list, car is 0.1, cdr is '() Perhaps the type checking code in scheme should be a bit stronger. You can avoid this problem by using cons to define your offsets. Instead of '(0 . 1) use (cons 0 1) (note that there is no ' before the opening parenthesis). HTH, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: title on a separate page
Quoting Xavier Scheuer (x.sche...@gmail.com): > > I would like to have lilypond generate the title on a page of its own. > > Isn't that the purpose of the "breakbefore" property inside \header block? > (This is a true question, apparently it seems to do nothing with me...) If so, I misunderstood "breakbefore" -- I thought it forces a new page *before the title* if that's not the beginning of the document. > By the way there is also Nicolas' nice ready-to-use "stylesheet" that > creates a nice title page. > Please see : http://lsr.dsi.unimi.it/LSR/Item?id=368 Thanks! As the title page's contents does not matter to me at all, I don't think this answers my original question, but as I like what I saw up to now of lilypond, there will be other projects soon... Btw, my original problem could be solved using the -dbackend=eps command line switch of lilypond. All I needed was typesetting music on small sheets and removing all unnecessary whitespace around the individual pages. Susan pgpjaonHgmgJR.pgp Description: PGP signature ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: title on a separate page (Susan Dittmar)
Hi all, I'm trying to understand how the Scheme markup command works, and I noticed that it seems to work exactly the same way if one of the lines is commented out, like so: #(define-markup-command (vspace layout props amount) (number?) "This produces a invisible object taking vertical space." ;(ly:make-stencil "" (cons -1 1) (cons 0 amount)) (ly:make-stencil "" (cons -1 1) (cons amount amount))) I'm wondering if there is a reason I'm not seeing to include both lines. Each line creates an invisible box, right? David > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user > On Wed, Oct 7, 2009 at 5:21 AM, Susan Dittmar wrote: > > But you'll need to make sure the music that's actually used in the sample > is > > public domain. > > Please use some other music for the example. I do not know under which > license, if at all, Eva pubished the tune. One of the reasons why I just > posted an except... > >Susan > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user > > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ancient tablatures
> "Marc" == Marc Hohl writes: >> I've made some efforts to transcribe the tablature, but what I want >> ideally is to transcribe what's there, in an input form that doesnt' >> require me to translate the tablature into notes, and then use that >> transcription plus the tuning of the strings to produce both a >> tablature that looks like the one in the facsimile and standard >> notation that a modern keyboard player could deal with. >> Marc> That's an interesting point - I think Dana Emery posted to Marc> the users list that writing tablature as normal notation and Marc> letting lilypond do the translation into tablature is at Marc> least not always the best way. As a transcriber, I would *always* prefer a transcription method that doesn't depend on me doing complicated calculations from my input. In the case of tablature, lots of the real users have never used it in a way that went through note names in their heads, and then there are transcribers like me who've never used tablature to play from at all. Of course, if you're transcribing from standard notation, and just want the tablature as output, you have a different problem. If you've ever known a guitar player who has trouble playing a G when asked, you can imagine that a lute player might well be playing a tablature of a 4-part polyphonic piece without really knowing all the note names. So an input method that says "play the fourth fret on the fourth string" is definitely better than one that says "play A", even if you're also saying "the fourth string is tuned to F". Marc> Hm, then let's try to nail it down: how would you like to input Marc> tablature? I think people should look at abctab2ps, which I mentioned the other day, but when I was actually entering that, I found it a little cumbersome. And of course, it's based on ABC syntax, and we'd want something based on lilypond syntax. The feature that was cumbersome was that you had to treat every "column" in the tablature as an ABC chord. It seems to me that the natural input method for tablature would be something like: here's a new column Here's the length of this column (actually the time between the start of this column and the next one, as strings that aren't refretted by the next column can be left to vibrate). This would be optional, as it wouldn't be necessary to repeat it if the "length" were the same as the previous column. Here are the strings that are fretted in this column. I think the abctab2ps for that is quite compact and straightforward. A string that's skipped is notated with a comma; one that has a letter uses that letter; if there are unfretted strings below the last fretted one, you don't have to specify them. So here's some abctab2ps: [,db,,d2][,d1][,b][,ab,,d2][,db,,d1][a] Note that in ABC, there's a default note length, so the "chords" without a length are the default length (in this case, 4), not the length of the previous note. And in ABC the [] surround a chord. I found writing all those square brackets to indicate new columns a pain, but of course the right editor macro could have fixed that. And of course, if we were doing it as part of lilypond, we'd want to use lilypond-like chord and length indications. And of course instead of just asking someone who's transcribed a few French Tablature pieces in abctab2ps, you should also ask people who've used the other tablature generating programs (Fronimo, Finale...), and people who've used Italian and German tablatures. Marc> or we can use some converters which translate the lute Marc> tablature into lilypond syntax, which again translates this Marc> into a nicely formatted tablature. I'd find that somewhat baroque, which might be suitable. I did think for a while about writing a python program that would produce ABC (and then lilypond) from abctab2ps. I wrote most of this yesterday, before the discussion between Carl and Mark had continued. I agree that it's more important to get the output right than to have an input mode *right now*. Maybe the tab2abc and abc2ly route does make sense, if lilypond gets to where it can produce something like the original. -- Laura (mailto:lcon...@laymusic.org) (617) 661-8097 233 Broadway, Cambridge, MA 02139 http://www.laymusic.org/ http://www.serpentpublications.org I've been singing. I've been taking a part in White sand and grey sand. I don't know anything about it. Never mind. I'll take any part in anything. It's all the same, if you're loud enough. Charles Dickens, _Little Dorrit_ ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: title on a separate page (Susan Dittmar)
On Wed, Oct 7, 2009 at 3:36 PM, David Nalesnik wrote: > #(define-markup-command (vspace layout props amount) (number?) > "This produces a invisible object taking vertical space." > ;(ly:make-stencil "" (cons -1 1) (cons 0 amount)) > (ly:make-stencil "" (cons -1 1) (cons amount amount))) > > I'm wondering if there is a reason I'm not seeing to include both lines. You missed the "if" line just above these two lines :-) The first line makes sure that the amount will never go below zero, even if a negative number is specified. If the number is positive, then the first of these two lines is skipped and the second one is directly executed. Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re:title on a separate page (Susan Dittmar) (David Nalesnik)
Dear All,
When I tried to add the titlepage code to
the LSR, I got a message from Firefox
that lsr.dsi.unimi.it had an out-of-date
certificate and could not be trusted(?)
I have altered the music so it is now
public domain, hopefully.
%start file
\version "2.12.2"
%The next bit is scheme code to define \vspace
#(define-markup-command (vspace layout props amount) (number?)
"This produces a invisible object taking vertical space."
(ly:make-stencil "" (cons -1 1) (cons 0 amount))
(ly:make-stencil "" (cons -1 1) (cons amount amount)))
\paper {
print-page-number=##f
ragged-bottom=##t
ragged-last-bottom=##t
print-all-headers = ##t
}
#(set-global-staff-size 14)
\header {
title = \markup \center-column
{ \vspace #64 \fontsize #10 "The Conqueror Worm" }
subtitle = \markup \center-column { \vspace #64 \fontsize #12 "Evanescence"
}
copyright = "Evanescence (http://www.evanescence.com/)"
tagline = ##f
}
melody = \relative c' {
a'1 ~
a2. a16( gis) a( b)
c2~ c8( e) d( c)
b4. b8 d4 b
a2 c
e4. e,8 e4 e
c'2 b4( a)
g2. g4
a1 ~
a4 b c2
}
textI = \lyricmode {
Lo! __ 'tis __ a __ ga -- la __ night
With -- in the lone -- some lat -- ter years!
An an -- gel __ throng, be -- winged, __ be -- dight
}
guitar = \chordmode {
a1:m f a:m g a:m e
a:m g f r
}
\book {
\pageBreak
\score {
<<
\new ChordNames { \set chordChanges = ##t \guitar }
\new Voice = "one" { \clef treble \melody }
\new Lyrics \lyricsto "one" { \textI }
>>
\layout { indent = 0.0\cm }
\header {
title = "The Conqueror Worm"
subtitle = ""
composer = "Composed by Evanescence"
poet = "Lyrics by Edgar Allan Poe"
}
}
}
%end of file
I like this code because it is short and easy to understand.
It will definitely come in useful.
Fred.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Issue?] hiding Accidental(s) on tied note(s) after a line break
--- On Thu, 10/8/09, David Nalesnik wrote: > From: David Nalesnik > Subject: Re: [Issue?] hiding Accidental(s) on tied note(s) after a line break > To: "Jonathan Wilkes" > Date: Thursday, October 8, 2009, 2:55 AM > Hi Jonathan, > I like this revision of the NR. I have always > opted to put these accidentals in, but I can certainly see > why someone would want to suppress them (read: > awkward-looking ties!) Also, > looking through scores lately with a new eye has shown me > that actual practice is not all that consistent, as you say. > Even in scores that generally repeat accidentals at the > start of the line, there are occasional inconsistencies. > And I have a Henle edition of Chopin mazurkas which > suppresses them, in contrast to other Henle scores (relative > simplicity of the music?). Another Henle edition of Brahms > piano pieces repeats the accidentals fairly consistently, > but not when the affected notes are used immediately after > the tied note (avoiding an awkward-looking repetition, I > suppose.) > > The Chopin edition dates to well before Henle > switched to Finale, but I suspect that some of these omitted > accidentals are due to notation software. Then again, I > have a Boosey&Hawkes collection of new piano music, > which suppresses them everywhere...except in pieces by > Wolfgang Rihm. > > I wrote earlier because I had a moment of terror > thinking that a neat feature of LilyPond would be gone > forever. I realize now that, whichever way the defaults > go, an easy override will be in sight! > > --David I think some of my initial inclinations about notational conventions come from having done things the wrong way 100 times and gotten used to it. As long as the options are clear from the NR, I think Lilypond's default behavior on this issue is probably the correct one. -Jonathan > > On Sat, Oct 3, 2009 at 12:21 AM, > Jonathan Wilkes > wrote: > > --- On Sat, 10/3/09, David Nalesnik > wrote: > > > > > From: David Nalesnik > > > Subject: Re: [Issue?] hiding Accidental(s) on tied > note(s) after a line break > > > To: "Joe Neeman" > > > Cc: "Jonathan Wilkes" , > "lilypond-user" > > > Date: Saturday, October 3, 2009, 5:46 AM > > > Hi, > > > According to Gardner Read: "It is not > > > necessary to repeat the accidental before a tied note > . . . > > > The one exception to this general rule occurs when the > note > > > or notes affected by the accidental and tied over the > > > barline come at the end of a system or at the bottom > of the > > > page. It is helpful to the performer if the > accidental is > > > repeated . . . " (Music Notation, p.131) > > > > > > I know I have spent a lot of time adding these > > > accidentals in Finale (and redoing them whenever the > layout > > > changed), and I very much appreciate that 2.12.2 takes > care > > > of them automatically! > > > > Hi David, > > > > Thanks for that quote; I don't currently have access to > Read's manual. > > > > Well, I still have my Beethoven sonatas out from my last > posting on here, > > and those tied accidentals after line breaks are a lot more > common than > > I thought. In the Schenker edition, they're > inconsistent: sometimes an > > accidental is parenthesized, sometimes its suppressed, but > more often > > than not they're there. In Henle they seem to always > be printed (and > > beautiful). > > > > However, I've got a Peters edition score where > they're always suppressed (it's also a modern score, > and I wonder if that's where the difference > > stems from). > > > > Here's an idea: how about just showing the behavior of > > 'hide-tied-accidental-after-break in NR 1.1.1, under > the heading > > "Accidentals", in the example that follows this > sentence: > > "Accidentals on tied notes are only printed at the > beginning of a new system. [add this] These accidentals > may also be suppressed." > > > > [see attached] > > > > Currently, 'hide-tied-accidental-after-break is only > listed in NR A.14. In > > fact, I remember seeing it there when I was entering a > score, and > > spending 10 very confused minutes trying to figure out why > the heck > > \override Tie #'hide-tied-accidental-after-break = > ##t wouldn't work! > > (Yes, I know it's a property of Accidental now). > > > > -Jonathan > > > > > > > > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Feature Request: Store Measure Numbers in Annotation
Hello, I made a feature request on the Lilypondtool page to be able to jump to any measure in the pdf viewer, and the creator of the software mentioned that this is really a feature request for Lilypond, so I'm posting his response here. Here is Mr. Fodor's response to my request: "If LilyPond stored the measure numbers in the annotation it would be possible, but not otherwise. So it's a feature request for LilyPond. (I think that would be easy to implement in LilyPond.) Actually LilyPond could generate a lot of other information in a separate file, because when rendering a grob, it has access to the Music element that renders the grob." I guess this relates also to another feature request I mentioned- I think it would be really useful to know the list of possible slur 'positions Lilypond chooses from when it compiles a score. Basically, I'd like to compile a score, and if I need to tweak a slur, choose from a list of possible 'positions, rather than entering values and compiling until Lilypond "jumps" to what it thinks is the next satisfactory slur shape. -Jonathan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Vertical spacing
On Wed, 2009-10-07 at 14:28 +0200, Francisco Vila wrote:
> For any vertical spacing problem, please use 2.12 instead; Joe Neeman
> has been responsible of a rework of vertical spacing, but he is too
> much occupied these days, we all are. See below
>
> 2009/10/7 Thomas Scharkowski :
> > I hav eadded two pngs to clarify:
> > With 2.13.3 "between-system-padding" and "\override
> > Staff.VerticalAxisGroup" work as expected, in 2.13.4 there is no effect.
>
> 2009/8/4 Joe Neeman :
> > The interaction between the different xxx-spacing variables is a little
> > complex and I need to document it properly. In this case, the problem is
> > that Lyrics are unaffected by between-staff-spacing (because they are
> > non-spaceable) and so your override only forces there to be one staff
> > unit of padding between adjacent _staves_, which is satisfied by your
> > example. Unfortunately, there is not yet any way to control the spacing
> > between Lyrics and the staff below it, which is where you really want
> > the extra padding AFAICT.
>
> Joe: is this already documented? Hot to control spacing from a lyrics
> line and the staff below it? Simple lyrics seem to almost collide.
No, this isn't done yet. I'll try to do it this weekend.
>
> << \new Staff { a } \addlyrics { pain }
> \new Staff { f' }
> >>
>
>
>
> Joe: I hate to bug you again, but several users are asking vertical
> spacing to have usable defaults and a documentation. Just give us a
> hint about when do you think this feature will be finished.
The documentation should be usable. There are two places to look: the
variables that control spacing within a staff are given as grob
properties and documented in the IR. The variables that control spacing
between staves are given as \paper block properties and documented in
the NR with the other paper block variables. What's missing is a broad
overview of how these fit together. This isn't near the top of my TODO
list right now, so I don't know when I'll write it. However, there are
some emails in the archive (mainly to Reinhold, I think) which give a
reasonably detailed description.
As for usable defaults, it would help tremendously if users (especially
now that devel releases are coming out again) could suggest usable
defaults. I don't work a lot with choral, orchestral or piano music, so
I don't have a strong opinion about what looks good. I'm happy to answer
questions and to help people find defaults, but I'm unlikely to find
good ones by myself.
Regarding lyrics, however, it might be a good idea to hold off on
experimenting with defaults until I fix the padding issue (soon...)
Cheers,
Joe
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
