Re: doc work

2008-08-16 Thread Trevor Daniels
Graham Percival wrote Friday, August 15, 2008 11:36 PM On Fri, 15 Aug 2008 22:16:13 +0100 "Neil Puttock" <[EMAIL PROTECTED]> wrote: 2008/8/15 Graham Percival <[EMAIL PROTECTED]>: > \midi { \tempo 4 = 60 } > Unfortunately, you can't put \tempo inside a \midi block any more. Oh yeah, I remem

Re: Still confused about context vs. new

2008-08-16 Thread Francisco Vila
2008/8/13 Carl Sorensen <[EMAIL PROTECTED]>: > I have found a place where \new is needed. ... > everything works as it should. Apparently, in the first usage, the unnamed > Staff context had been implicitly created and was unsuccessfully reused. > > Given this result, it appears to me that \new is

Re: doc work

2008-08-16 Thread Robin Bannister
Graham Percival wrote I would prefer that early users placed a \tempo 4 = 60 in their score block, which is easier to understand, works in MIDI, and permits dotted notes to be used Early users would think in terms of dotted notes and write \tempo 4. = 60 But no, no. You had to write

Re: doc work

2008-08-16 Thread Trevor Daniels
Robin Bannister wrote Saturday, August 16, 2008 10:11 AM Subject: Re: doc work Graham Percival wrote (Actually it was me) I would prefer that early users placed a \tempo 4 = 60 in their score block, which is easier to understand, works in MIDI, and permits dotted notes to be used Early

Re: doc work

2008-08-16 Thread Robin Bannister
Trevor Daniels wrote ? I don't understand. \tempo 4.=60 works fine in the \score block. Sorry. For "early" read "prehistoric", I suppose. Because [1] worked, I never needed to do anything differently. And convert-ly.py (2.10.33) now removes \tempo from my files. [1] http://lists.gnu.org/arch

Re: Still confused about context vs. new

2008-08-16 Thread Carl D. Sorensen
On 8/16/08 2:41 AM, "Francisco Vila" <[EMAIL PROTECTED]> wrote: > > But, instead of doing reverse engineering all the time, shouldn't the > core developers simply explain how did they coded \context and \new, > when are they needed, what do they differ in, etc? I believe that the docs started

combine chords, lyrics and melody - resending now that I've subscribed...

2008-08-16 Thread ayryq
Is there any way to simply combine chords, lyrics, and melody sections into a single LP "variable?" I am trying to create pop leadsheets and my score sections look like this one: %-- \score { << \new ChordNames { \transpose g g { \set chordChanges = ##t

Re: combine chords, lyrics and melody - resending now that I've subscribed...

2008-08-16 Thread David Bobroff
Unless I'm misunderstanding your question I think you probably can do what you're talking about. You may need to experiment a bit to get it to behave the way you want. -David ayryq wrote: Is there any way to simply combine chords, lyrics, and melody sections into a single LP "variable?" I am

Re: Still confused about context vs. new

2008-08-16 Thread Han-Wen Nienhuys
On Tue, Aug 12, 2008 at 8:45 PM, Carl Sorensen <[EMAIL PROTECTED]> wrote: >> \context implicitly instantiates a new context if the >> one named doesn't yet exist, so \new is redundant, *except* where you >> want multiple distinct contexts with the same name, or you're using >> unnamed contexts (whi

Using one identifier or another

2008-08-16 Thread Johan Vromans
Hi, In a template file I want to check if a particular identifier has been defined, and act accordingly. For example: \score { \allMusic \layout { } } \score { \unfoldRepeats \allMusic \midi { } } In the MIDI block, I would like to use identifier allMusicForMID

Re: doc work

2008-08-16 Thread Kieren MacMillan
Hi Graham, If I'm not mistaken, putting them in \book results in foo.pdf(main score) foo-0.pdf (1st violin) foo-1.pdf (2nd violin) foo-2.pdf (viola) foo-3.pdf (cello) Yes... although there is (or should be) a request in the system for the ability to change the output name of a \b

Re: doc work

2008-08-16 Thread Kieren MacMillan
Hi Walter, I just looked at that template and noticed that the first example on the page A.3.1 gives a template for a score where everything is in one file. But it outputs a score only, no parts — I'm talking about having a single-file input with multiple-file output. just about any Li

Re: doc work

2008-08-16 Thread Kieren MacMillan
Hi Patrick, I agree. Well, we appear to be in the minority... ;-) Thanks for your input! Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Please forget LM MG NR IR SL AU

2008-08-16 Thread John Mandereau
2008/8/11 Bertalan Fodor (LilyPondTool) <[EMAIL PROTECTED]>: > My point is that lilypond-user reading users won't get used to it. Many of > them are newcomers and beginners. They don't usually follow the > conversations on the list. > > Perhaps it's because of my software developer experience, but

Re: it's all up to you users (was: Please forget LM MG NR IR SL AU)

2008-08-16 Thread John Mandereau
2008/8/13 Graham Percival <[EMAIL PROTECTED]>: >It's a waste because, 7 days from now, there will be precisely > half a dozen people who are updating the documentation. There's > at least 50 people who can answer simple questions here. To be > efficient, those six people should spend their time u

Re: combine chords, lyrics and melody - resending now that I've subscribed...

2008-08-16 Thread Patrick Horgan
ayryq wrote: I believe you can, I was going to clip your stuff, build it on my machine, and build an example for you, but this example won't actually build on my machine. Just as a hint, in the work I did for O Magnum Mysterium, I combined several thing like this: sopranoTotal = \simultaneo

Re: Ties & Tuplet Full Length

2008-08-16 Thread Ole Schmidt
Peter, thanks for your help, but where do I have to put the \override NoteColumn #'X-offset command in an Piano(Staff) score to be active in the hole score (for all line breaks...)? ole Am 13.08.2008 um 17:11 schrieb Peter Johnson: These are two different questions. Ole Schmidt wrote:

Re: combine chords, lyrics and melody - resending now that I've subscribed...

2008-08-16 Thread Carl Sorensen
Patrick Horgan gmail.com> writes: > > ayryq wrote: > > I believe you can, I was going to clip your stuff, build it on my > machine, and build an example for you, but this example won't actually > build on my machine. Just as a hint, in the work I did for O Magnum > Mysterium, I combined sev

Re: Memory Requirements

2008-08-16 Thread Bertalan Fodor
I think 256MB is enough for LilyPond and 256MB is enough for Tomcat (if you use that for the webapp part). However I don't really know LilyPond's memory needs but that can be fine-tuned with Guile GC settings (you can find the environment variable for this in the manual). Bert > --- Origin

Re: Memory Requirements

2008-08-16 Thread Han-Wen Nienhuys
I just finished a major cleanup of the GUILE GC module. Hopefully this will tame lily's requirements a bit. On Sat, Aug 16, 2008 at 3:56 PM, Bertalan Fodor <[EMAIL PROTECTED]> wrote: > I think 256MB is enough for LilyPond and 256MB is enough for Tomcat (if you > use that for the webapp part). How

Re: doc work

2008-08-16 Thread Patrick Horgan
Kieren MacMillan wrote: The last time I checked Mutopia, I was shocked by the (low) quality of the coding. =( I personally would never suggest that anyone use any Mutopia file I've seen as an example/template. How about the O Magnum Mysterium that I just re-did and contributed back to Mutopi

Re: Second review of NR 2.7 Chords

2008-08-16 Thread Neil Puttock
Hi Carl, You've done a great job with this. There are a few details which I'd like to mention: - chords-headword.ly: Further to Andrew's comments about the G flat (it should be an F sharp), the chord names seem to be a bit off. For example, in the second bar, the first chord has a 'C' above it;

Re: Second review of NR 2.7 Chords

2008-08-16 Thread Carl D. Sorensen
Neil, Thanks for your very careful review. I will fix each of these issues. But I do have a bit of discussion on the headword below. I especially appreciate your careful review of style. I find that after a certain number of iterations on my work, I become blind to style issues and spelling er

Re: Second review of NR 2.7 Chords

2008-08-16 Thread Neil Puttock
2008/8/16 Carl D. Sorensen <[EMAIL PROTECTED]>: > I really hesitate to say anything here, because I'm a real novice at music. > However, I think that the chord is a first inversion Gm chord, rather than a > first inversion G chord, due to the key signature (feel free to correct me > if I'm wrong).

Re: Proposed syntax change: renaming of \center-align markup command

2008-08-16 Thread Neil Puttock
Thanks for the feedback, everybody. To recap, the favoured option is as follows: horizontal alignment (single): \left-align, \center-align, \right-align vertical alignment (stacked): \left-column, \center-column, \right-column As for \hcenter and \column, should I leave these as duplicates of \c

Re: Proposed syntax change: renaming of \center-align markup command

2008-08-16 Thread James E. Bailey
Am 17.08.2008 um 00:39 schrieb Neil Puttock: Thanks for the feedback, everybody. To recap, the favoured option is as follows: horizontal alignment (single): \left-align, \center-align, \right- align vertical alignment (stacked): \left-column, \center-column, \right- column As for \hcenter

Re: Proposed syntax change: renaming of \center-align markup command

2008-08-16 Thread Neil Puttock
2008/8/16 James E. Bailey <[EMAIL PROTECTED]>: > I think the names for the commands are great, but I'm still confused. > > \hcenter and \column and duplicates of \center-align and \left-column > (currently \center-align and \left-align)? Umm, really? Hmm, perhaps that was badly worded. :) To cla

Re: doc work

2008-08-16 Thread Stan Sanderson
On Aug 16, 2008, at 3:22 PM, Patrick Horgan wrote: Kieren MacMillan wrote: The last time I checked Mutopia, I was shocked by the (low) quality of the coding. =( I personally would never suggest that anyone use any Mutopia file I've seen as an example/template. How about the O Magnum Myst

Re: Proposed syntax change: renaming of \center-align markup command

2008-08-16 Thread James E. Bailey
Am 17.08.2008 um 01:27 schrieb Neil Puttock: - change the current behaviour of \center-align to match \hcenter; keep \hcenter for backwards compatibility, or remove it What if I want a vertically centered column of arguments? Then, rather than just using \center-align, I have to use \column