\thinspace in Lyrics
Is there anyway to use Latex commands like \thinspace in Lyrics? ``' looks ugly without \thinspace. Thanks! tssfulk ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
cautionary accidental: double barline?
Hello list, when changing the key lilypond (2.2.2, cygwin) prints a single barline before the cautionary accidentals at the end of the line. Isn't a double barline standard? I looked at several examples in printed scores and always found a double barline. Thank you, Thomas ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
User-defined messages in .ly compilation output?
Is it possible to write messages to the terminal during the compilation of a
.ly file? (not the compilation of lilypond itself!)
For example, perhaps I would like to be able to indicate that the warnings
generated by a certain piece of code are to be expected, as in:
\version "2.2.2"
guitarPart = \notes {
\key d \major
d1
\key a \major
a1
}
\score {
\notes {
<<
\new Staff {
%% COMPILES OK
\clef bass
\guitarPart
}
\new TabStaff {
%% EXPECT WARNINGS: Junking event: `KeyChangeEvent'
\guitarPart
}
>>
}
\paper{}
}
Is there a way to insert into the compilation output something like:
lilypond (GNU LilyPond) 2.2.2
Running lilypond-bin...
Now processing `file.ly'
Parsing...
Interpreting music...
message: expect errors in TabStaff <--- CAN I DO THIS?
file.ly:2:14: warning: Junking event: `KeyChangeEvent':
\key d \majo
r
file.ly:4:14: warning: Junking event: `KeyChangeEvent':
\key a \majo
r
[3]
Preprocessing graphical objects...
Thanks for your help.
Magnus Lewis-Smith
___ALL-NEW Yahoo! Messenger -
so many all-new ways to express yourself http://uk.messenger.yahoo.com
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cautionary accidental: double barline?
On Friday 18 June 2004 09.16, Thomas Scharkowski wrote: > Hello list, > > when changing the key lilypond (2.2.2, cygwin) prints a single > barline before the cautionary accidentals at the end of the line. > Isn't a double barline standard? > I looked at several examples in printed scores and always found a > double barline. If you want to add a double barline, you can use \bar "||". It would IMHO be a bit confusing if a double barline would be added by default; and the extra \bar "||" is not much extra work. (And no - I don't think it's standard. But I think you usually change key signatures only around the kind of barlines where it's appropriate to use \bar "||" for musical reasons) Erik ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Time
On Thursday 17 June 2004 04.09, Joshua Koo wrote:
> Wow, Amazing! Well I didnt expect you would really type up and time
> yourself. I was just waiting to get some approimate estimates.
Well, I just did it for fun.. I never actually benchmarked my typesetting, I
also wanted to see how much time it actually takes.
> I definally
> took much much much longer than you did, and means I would have to improve
> myself much more. Thanks for pointing out the possible mistakes. Bar 17:
> According to my score, it it correct.
Then it probably is correct; i just suspected it wasn't since it looked
inconsistent with the way it was done in some other places.
(but I'm not a cello player)
> So the dirty way was to use *2/3 when you didnt want triplets, and \times
> 2/3 when you needed the tripplets? Think I ask the question a while back
> here, but cant remember if it was answered. But anyway this is my method.
>
> \override TupletBracket #'number-visibility = ##f
Thanks.. I remembered it was something like this, so I grepped for "tuplet"
everywhere.. but apparently I didn't grep -i.
> \header {
>title = "Brandenberg Concerto No.5 (Keyboard Concencerto) Mvt 3"
>composer = "J.S. Bach"
>tagline = "[EMAIL PROTECTED] WIP for mutopia-project"
>meter = "Allegro"
btw, I think this should be piece.. meter is for metronome markings, I think.
I'm not sure though.
Erik
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cautionary accidental: double barline?
> On Friday 18 June 2004 09.16, Thomas Scharkowski wrote: > > Hello list, > > > > when changing the key lilypond (2.2.2, cygwin) prints a single > > barline before the cautionary accidentals at the end of the line. > > Isn't a double barline standard? I looked at several examples in > > printed scores and always found a double barline. > > If you want to add a double barline, you can use \bar "||". It would > IMHO be a bit confusing if a double barline would be added by default; > and the extra \bar "||" is not much extra work. > > (And no - I don't think it's standard. But I think you usually change > key signatures only around the kind of barlines where it's appropriate > to use \bar "||" for musical reasons) > > Erik Thank you! I have tried \bar "||", but it does not work with repeats as you will see in the example below. The first score is without repeats and is o.k.. With repeats \bar "||" has the effect that lilypond does not print the first repeat bar, see score 3. Am I missing something or is it a bug? Thomas ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: User-defined messages in .ly compilation output?
Magnus Lewis-Smith writes:
> Is it possible to write messages to the terminal during the compilation of a
> .ly file? (not the compilation of lilypond itself!)
How about this ;-)
\version "2.2.2"
guitarPart = \notes {
\key d \major
d1
\key a \major
a1
}
\score {
\notes {
<<
\new Staff {
%% COMPILES OK
\clef bass
\guitarPart
}
\new TabStaff {
#(display "message: expect errors in TabStaff <--- CAN I DO
THIS?
\n" (current-error-port))
%% EXPECT WARNINGS: Junking event: `KeyChangeEvent'
\guitarPart
}
>>
}
\paper{}
}
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cautionary accidental: double barline?
On Friday 18 June 2004 13.05, Thomas Scharkowski wrote: > > On Friday 18 June 2004 09.16, Thomas Scharkowski wrote: > > Thank you! > I have tried \bar "||", but it does not work with repeats as you will > see in the example below. > The first score is without repeats and is o.k.. > With repeats \bar "||" has the effect that lilypond does not print > the first repeat bar, see score 3. > Am I missing something or is it a bug? I suppose you forgot to attach something, but it sounds like \bar "||:" is what you're looking for. (there seems to be a bug though, the bar line is not printed when in the middle of a line) Erik ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
(Fwd) Re: cautionary accidental: double barline?
Sorry, I missed to paste my example.
Here it comes:
\version "2.2.2"
% Ex 1
\score {
\notes { \relative c'{
\key fis \major
eis^\markup fis gis ais \bar "||" \break
\key f \major
bes c d e
}}
\paper {}
}
% Ex 2
\score {
\notes { \relative c'{
\key fis \major
eis fis gis ais \break
\key f \major
\repeat volta 2 { bes c d e }
}}
\paper {}
}
% Ex 3
\score {
\notes { \relative c'{
\key fis \major
eis fis gis ais \bar "||" \break
\key f \major
\repeat volta 2 { bes c d e }
}}
\paper {}
}
--- Forwarded message follows ---
From: Thomas Scharkowski <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject:Re: cautionary accidental: double barline?
Date sent: Fri, 18 Jun 2004 13:05:41 +0200
> On Friday 18 June 2004 09.16, Thomas Scharkowski wrote:
> > Hello list,
> >
> > when changing the key lilypond (2.2.2, cygwin) prints a single
> > barline before the cautionary accidentals at the end of the line.
> > Isn't a double barline standard? I looked at several examples in
> > printed scores and always found a double barline.
>
> If you want to add a double barline, you can use \bar "||". It would
> IMHO be a bit confusing if a double barline would be added by
> default; and the extra \bar "||" is not much extra work.
>
> (And no - I don't think it's standard. But I think you usually
> change key signatures only around the kind of barlines where it's
> appropriate to use \bar "||" for musical reasons)
>
> Erik
Thank you!
I have tried \bar "||", but it does not work with repeats as you will
see in the example below. The first score is without repeats and is
o.k.. With repeats \bar "||" has the effect that lilypond does not
print the first repeat bar, see score 3. Am I missing something or is
it a bug?
Thomas
--- End of forwarded message ---
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cautionary accidental: double barline?
You are right, "||:" does it! Thomas > I suppose you forgot to attach something, but it sounds like \bar > "||:" is what you're looking for. (there seems to be a bug though, the > bar line is not printed when in the middle of a line) > > Erik ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: User-defined messages in .ly compilation output?
--- Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote: > Magnus Lewis-Smith writes: > > > Is it possible to write messages to the terminal during the compilation of > a > > .ly file? (not the compilation of lilypond itself!) > > How about this ;-) > > #(display "message: expect errors\n" (current-error-port)) > Nearly there. If I use the 'display' command I get Now processing `file.ly' Parsing... message: expect errors file.ly:232:66: error: syntax error, unexpected SCM_T: #(display "message: expect errors\n" (current-error-port) ) Interpreting music... Incidentally, are there facilities similar to __FILE__ and __LINE__ in C? Thanks Magnus Lewis-Smith ___ALL-NEW Yahoo! Messenger - so many all-new ways to express yourself http://uk.messenger.yahoo.com ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: User-defined messages in .ly compilation output?
Magnus Lewis-Smith writes: > Nearly there. If I use the 'display' command I get > > Now processing `file.ly' > Parsing... > message: expect errors > > file.ly:232:66: error: syntax error, unexpected SCM_T: > #(display "message: expect errors\n" (current-error-port) > ) Sorry, it seems you need 2.3.x for this. In 2.2.x you can use embedded scheme only at certain places, probably you can do something like: a-#(begin (display "foe") "") > Incidentally, are there facilities similar to __FILE__ and __LINE__ in C? No, but that's an interesting idea. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
What properties should I set?
Hello, advanced LilyPond users could help me. I'm writing a "tweaking wizard" for the LilyPond plugin for jEdit. That means that the user can choose a context and the plugin will tell him the context properties that make sense. My question is: for example in the ChordNames context. In the doc I find the properties of the engravers and I find the translator properties that are given a default value. Is that all that should be set? Another example: it is well-known that in a Staff context I can set the midiInstrument property, but I can not find it out from the internals-documentation. I look at dynamic_performer, I found it, and found it also in Tunable-context-properties. But how can I figure out that setting midiInstrument makes sense in (and only in?) a Staff context? Please let me understand the structure. Thanks, Bert ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
What properties should I set?
[EMAIL PROTECTED] writes: > Another example: it is well-known that in a Staff context I can set the > midiInstrument property, but I can not find it out from the > internals-documentation. I look at dynamic_performer, I found it, and found > it also in Tunable-context-properties. But how can I figure out that setting > midiInstrument makes sense in (and only in?) a Staff context? > > Please let me understand the structure. MIDI contexts are undocumented, currently. (sorry.) -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
User-defined messages in .ly compilation output?
[EMAIL PROTECTED] writes:
> generated by a certain piece of code are to be expected, as in:
>
> \version "2.2.2"
> guitarPart = \notes {
> \key d \major
> d1
> \key a \major
> a1
> }
> \score {
> \notes {
> <<
> \new Staff {
> %% COMPILES OK
> \clef bass
> \guitarPart
> }
> \new TabStaff {
> %% EXPECT WARNINGS: Junking event: `KeyChangeEvent'
> \guitarPart
> }
> >>
> }
> \paper{}
> }
>
> Is there a way to insert into the compilation output something like:
>
> lilypond (GNU LilyPond) 2.2.2
> Running lilypond-bin...
> Now processing `file.ly'
> Parsing...
> Interpreting music...
>
> message: expect errors in TabStaff <--- CAN I DO THIS?
>
> file.ly:2:14: warning: Junking event: `KeyChangeEvent':
> \key d \majo
> r
Jan's try is a 1st start, but outputs the message during the parse. I
think you're looking for
\applycontext #(lambda (x) (display "HI THERE"))
See also "Context evaluation" in the manual.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
\thinspace in Lyrics
Is there anyway to use Latex commands like \thinspace in Lyrics? ``' looks ugly without \thinspace. Thanks! tssfulk ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Pages and line breaks
One thing I realised is thats the score doesnt end at the end of the pages. It would be great if I do something like this \fit-pages 4 Almost all scores I see starts from the start of the page to the bottom of the pages where it ends. Will defining where the page break work better? Or do I have to change the size of the staffs manually so that all the music fits nicely just to the pieces of paper? Anyway about page breaking, I been to both Finale's and Seblius webpages. Both of them have some features to determine the page breaks automatically. Finale smart page turns options to calculate where page breaks. http://www.finalemusic.com/finale/features/ftr-smartpageturns.asp Sibelius shows off that they put the multimeasure rest at the end of page so flipping is easiler. http://www.sibelius.com/products/sibelius/3/powertools.html ay, is there a features-request email that i should email instead of here? Thanks, Joshua ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pages and line breaks
Joshua Koo writes: > One thing I realised is thats the score doesnt end at the end of the pages. Page layout has been in development since March. Check-out the development branch, there are packages for several platforms. It's not been heavily used, so expect to find bugs. > It would be great if I do something like this \fit-pages 4 I have thought about this, but I'm not sure that it is very useful. Either the score fits, or it doesn't, given the spacing you prefer. > Anyway about page breaking, I been to both Finale's and Seblius > webpages. Both of them have some features to determine the page > breaks automatically. > Finale smart page turns options to calculate where page breaks. Colour me unimpressed. Having seen the quality and correctness of the output they produce (esp. finale) I would be very surprised if they got this right. > Sibelius shows off that they put the multimeasure rest at the end of > page so flipping is easiler. Interesting. I wonder what happens when you stress that feature. This is another thing that we have been thinking about. With the current page breaking algorithm, you should be able to do that by hand, adding positive or negative stimulations for page breaks. Before we choose to automate such a feature, we would like to have some good feel for when and where to put how big penalties. If you are interested, you can help shed some light on this. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Narrow Word Lyric
Hi, is it possilbe for a 2-syllable word in the lyrics to be shown as a single word if the notes are closed enought. That is a word seperated with -- eg. Hel -- lo, be shown below the notes as "Hello" instead of Hel-lo if notes are determinded closed enought. Thanks, Joshua ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problems with lilypond-book after upgrade
On 6/16/04 4:10 PM, "Han-Wen Nienhuys" <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] writes: >> >> PS. I love Lilypond, but the manual is really awful. You really need to >> write it with a user/reader who has no programming experience in mind. > While this might be true for some parts of the manual, I personally think the manual has improved significantly over the last versions after 1.9. I think that there are places in the manual that could use examples when there aren't any, and I think the whole business of tweaking could be improved as others have confessed on this list that inputting the notes and getting them to print really doesn't take any longer that any other notation program. But there is a LOT of time spent on the tweaking stage. I have noticed that over the last year there have been repeated requests for how to do certain things (height of alternative ending and getting chords to appear at the correct height). Perhaps much of this could be solved by having an organized document that is included with the Lilypond documentation or can be downloaded from the site that includes a catalogue of tweaks. If you want to do something common, you look to this document and simply copy the text from it and paste it into your .ly file, change the numbers to suit you and away you go! I would be willing to help with such a document. Walter Hofmeister ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Narrow Word Lyric
On Friday 18 June 2004 20.41, Joshua Koo wrote:
> Hi,
>
> is it possilbe for a 2-syllable word in the lyrics to be shown as a single
> word if the notes are closed enought. That is a word seperated with -- eg.
> Hel -- lo, be shown below the notes as "Hello" instead of Hel-lo if notes
> are determinded closed enought.
You can do this manually, by using melismata or similar:
<<
\context Voice=A \notes { c8\melisma c\melismaEnd }
\new Lyrics \lyricsto A \lyrics { Hello }
>>
would replace
<<
\context Voice=A \notes { c8 c }
\new Lyrics \lyricsto A \lyrics { Hel -- lo }
>>
I beleive that the following has the same effect & might be more handy:
<<
\context Voice=A \notes { c8 c }
\new Lyrics \lyricsto A \lyrics { Hello \skip 4 }
>>
Erik
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
