Re: lilypond-user Digest, Vol 57, Issue 76
Michael Sperone wrote:
Thanks Neil,
I was able set the 4/4 time signature in the /layout section, but as
for setting other global settings, I can't seem to figure them out.
I'd like to be able to set modern style accidentals, and.. .well I
can't think of anything else right now off the top of my head, but I'd
like to be able to fix anything I want for the whole score at once.
Setting the accidental styles works differently than most other settings.
As you have already noticed, you can unfortunately not use
#(set-accidental-style 'modern)
in a \layout block, only together with the music. Actually, this call to the
function set-accidental-style corresponds to a number of property settings.
By checking the implementation of this function, I found out that the
"modern"
style corresponds to the following setting:
\layout{
\context{
\Staff
%%% Equivalent to #(set-accidental-style 'modern) :
autoAccidentals = #'(Staff (same-octave . 0) (any-octave . 0)
(same-octave . 1))
}
}
PS... how come my posts are coming up only as attachments in the digest?
Probably since your email program is configured to send emails in HTML
format
(sometimes refered to as "Rich text").
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: MIDI output trick
What LilyPond version are you using? In recent versions, there's no need to
use \applymusic, rather you can use the function \unfoldRepeats as
described
in the section on "Repeats and MIDI".
Also, this function should not have any influence on the MIDI instruments.
I think you original problem was due to something else. Since you didn't
include any complete example, I cannot provide any more specific help,
but don't hesitate to send a new question to the mailing list with more
details,
if you want to sort it out. Anyway, there should be no reason to unfold your
repeats by hand as you proposed below.
/Mats
Charles E. Kinney wrote:
Lilyponders,
While trying to get the music from all staves in a piece to combine
for MIDI output, I found a tip in the archives to create a staff group
to combine the music parts, then a score section for print output,
then a separate score section for the MIDI, more or less as follows:
%%%
%% Create staff grouping for music:
fullScore = \new StaffGroup <<
\melody % flute
\righthand % electric grand
\lefthand% drawbar organ
\bass% electric bass (finger)
>>
%% Stock print output section . . .
\score { . . . }
%% And now output MIDI with unwrapped repeats:
\score{
\applymusic #unfold-repeats \fullScore
\midi{\tempo 4 = 100 }
}
%%%
Which works just great! However, the only part that has the desired
MIDI instrument setting is the last part (bass). The first parts are
all the default piano. Bummer.
After a bit of fumbling around, I hit on this change . . .
%%%
%% Create staff grouping for music:
fullScore = \new StaffGroup <<
\new Staff << \melody \melody >>% flute
\new Staff << \righthand \righthand >> % electric grand
\new Staff << \lefthand \lefthand >>% drawbar organ
\new Staff << \bass \bass >>% electric bass (finger)
>>
etc . . .
. . . which worked beautifully! Every part is created, combined and
plays back with the desired instruments.
I've only started using Lilypond about 10 days ago, and I don't
read or write music that well (I'm a play-by-ear bass & guitarist).
I have a number of songs I want to transcribe properly (as well as
demo), and Lily is making the process remarkably painless. So in the
spirit of FOSS, I thought I should give back to the community.
Thanks all!
Chuck Kinney
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book macros/variables
In any text editor, it's trivial to automatically replace all occurences of
something like
\lilystart
by
\begin[staffsize=12]{lilypond}
\include "bookstyle.ly "
or whatever, so I have personally not seen any need for this feature.
Of course it's very clever to do what you did, namely to include a
separate .ly file that contains all the necessary settings.
If you have a large number of short snippets, I see that your solution
might be
convenient. Did you consider using a standard preprocessor like CPP or M4
(search the mailing list archives for "preprocessor" for some related
discussions
on the use of preprocessors in pure .ly files)?
/Mats
v!ictor [EMAIL PROTECTED] wrote:
hello lilyponders,
I've been using lilypond-book for the first time. love it!
There's one thing that I'd like to have though. I'd love to be able to
define macros in a similar way as in latex. Is this possible?
From what I've read in the documentation, lilypond-book only knows to
look for \begin{lilypond} and \lilypond{ }, so no macros can be
defined *for lilypond-book* inside the latex file. If you try to do
this, lilypond-book ignores them and then latex tries to interpret
them and fails.
So i wrote a little parser that looks for a lilypond delimiter,
specifically \lily{ [music] } and replaces that for whatever i define
in my parser, for example
\begin[staffsize=12]{lilypond}
\include "bookstyle.ly "
[music]
\end{lilypond}
Now compiling a lilypond-book becomes a three step process:
1. parse book.tex to find \lily{ } and replace with arbitrary lilypond
stuff
2. run lilypond-book on book.tex
3. run latex on book.tex
So if there is no way of doing this in lilypond-book, would anyone
else be interested in integrating something like this in the core
lilypond-book code? would it be useful for others?
best,
victor
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Odd Jobs (mostly documentation)
Hi Graham, Are you interested in helping LilyPond? Yes! =) GENERAL EDITING / JANITORIAL: - check manual for current correctness (does it make sense, is the info up-to-date, etc) - verify anything in the "bugs" sections - standardize # signs http://lists.gnu.org/archive/html/lilypond-devel/2006-10/msg00180.html - avoid future tense http://lists.gnu.org/archive/html/lilypond-devel/2006-01/msg00076.html Is this job still open? Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
lyrics
Hello, Is there a way to put lyrics in the sheet music? Thanks, Rhodie Rhodie Jacobson Pastor, Community United Methodist Church 9225 Jason Ave. NE PO Box 5 Monticello, MN 55362 (763) 295-2652 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lyrics
Yes, you can include lyrics. You read this: http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Printing-lyrics#Printing-lyrics, didn't you? /Helge - Original Message - From: Rhodel Jacobson To: lilypond-user@gnu.org Sent: Tuesday, August 28, 2007 12:08 AM Subject: lyrics Hello, Is there a way to put lyrics in the sheet music? Thanks, Rhodie Rhodie Jacobson Pastor, Community United Methodist Church 9225 Jason Ave. NE PO Box 5 Monticello, MN 55362 (763) 295-2652 ___ 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: "programming error: Going back in MIDI time"
Haven't heard any response- can anyone ID the cause of this message?
It does not seem to be causing any other problems, yet...
On Mon, Aug 27, 2007 at 12:20:59PM -0400, Ed Ravin wrote:
>
> I get these messages at the end of every compilation. Platform is
> Mac OS 10.3.9. Any idea what this means?
>
> GNU LilyPond 2.10.29
> Processing `southern.ly'
> Parsing...
> Interpreting music... [8][16][22]
> Preprocessing graphical objects...
> Interpreting music...
> MIDI output to `southern.midi'...
> programming error: Going back in MIDI time.
> continuing, cross fingers
> programming error: Going back in MIDI time.
> continuing, cross fingers
> programming error: Going back in MIDI time.
> continuing, cross fingers
> programming error: Going back in MIDI time.
> continuing, cross fingers
> programming error: Going back in MIDI time.
> continuing, cross fingers
> programming error: Going back in MIDI time.
> continuing, cross fingers
> Layout output to `southern.ps'...
> Converting to `southern.pdf'...
>
> The score block that generates the MIDI output is below.
>
> \score { % no layout, just MIDI, unfold repeats
> {
> <<
> \new Staff = "singer"
> <<
> \new Voice = "vocal" {
> \autoBeamOff
> \melody
> }
> >>
> \new Lyrics \lyricsto vocal \new Lyrics { \text }
> \new PianoStaff = "piano" <<
> #(set-accidental-style 'piano)
> \new Staff = "upper" { \unfoldRepeats \upper }
> \new Staff = "lower" { \unfoldRepeats \lower }
> >>
> >>
> }
>
> \midi {
> \context {
> \Score
> tempoWholesPerMinute = #(ly:make-moment 72 4)
> }
> }
>
>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user
>
--
Ed Ravin | "The law, in its majestic equality, forbids the rich as
| well as the poor to sleep under bridges, to beg in the
eravin@ | streets, and to steal bread."
panix.com| --Anatole France, Le Lys Rouge [1894]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Tip: lyrics with polyphony / stem directions (without specifically instantiated voices)
I've discovered a number of threads on this topic (how lyrics don't work when you use such
as <<{a' b'} \\ { c' d'}>>. I didn't seem to have trouble with lyrics in my
early days of trying this . . . (but, maybe then I was just focusing on the music, before
putting the lyrics in; whatever the case, I ended up not using them for another reason).
Anyway, I've come across a situation where I needed to have this (i.e. stem directions
pointing different ways on the same note, only a few times). So . . . I looked through the
LilyPond discussion and found various things, none of which in and of themselves provided a
satisfactory solution (although they helped me come up with what follows).
Anyway, I found a way that works better for me (although it requires adjusting
if you need to change the system width). I did, however, discover a solution.
Basically, I just used underscores to make one word look like two, and I
re-aligned the lyrics to make them shift over in the right direction. This
makes it look fine (although it would be nice if they made some way to have
differing stem directions in the same chord without having multiple voices, on
a chord by chord basis, rather than all of them that follow).
So, here's the code:
In the lyrics area:
\once \override Score . LyricText #'self-alignment-X = #-1
Iam \skip 1
(the skip is for the note without lyrics; 'am' overlaps onto it so it looks
like it belongs there; the number of underscores may vary significantly, and
also the integer assigned with the override up there, depending on the
direction it needs to shift: i.e. -1, 1, 0, etc.)
Here's the note code I used for the spot to put the lyrics over:
<<{f'4.} \\ {f'4.}>>
It takes a little tweaking, but it works better and faster than anything else
I've tried (it's not always practical to have multiple voices, especially when
your number of staffs changes in the middle of the song, at least in certain
ways, and you only want one midi for the song). Anyway, this is just a tip for
those needing a solution to this, since there are many I've seen asking the
question.
I don't suppose they're planning to make a more standard solution, yet, are
they? I would personally suggest just adding a tweak to chords (rather than
messings with voices) to add the ability to make the stems go in opposing
directions (it's not the durations that matter so much). Something simple like
this:
<\stemUp f' \stemDown f'>4
or
<\stemUp c'' a' \stemDown f'> (This would signify that both c'' and a' were up,
on the same stem, and only f' was down. Making it so multiple up stems appeared
would be bad, I think, in a chord context like this. I don't think the middle notes
should be able to go against both the top and the bottom, in this context.)
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
programming error: (de)crescendo on items with specified volume.
I started getting this message:
programming error: (de)crescendo on items with specified volume.
When I added this line to the melody portion (of a singer with piano piece)
\times 2/3 { e8 e e } e,4. \> e8 \! \p ^"rit." ds e |
The warning goes away if I remove the "\p". I have plenty of similar
syntax elsewhere in the file, like:
b8 a4. \> ^"rit." r8 f8 \! \mp e f |
This is the same piece that has the other warning I just posted
about "going back in MIDI time". In spite of the two warnings both
the PDF and MIDI output seem OK.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tip: lyrics with polyphony / stem directions (without specifically instantiated voices)
Hi Mark:
I've discovered a number of threads on this topic (how lyrics don't
work when you use such as <<{a' b'} \\ { c' d'}>>
I'm not sure what you mean by "lyrics don't work" -- have you tried
<< { a' b' } \new Voice { c' d' } >>
instead of
<< { a' b' } \\ { c' d' } >>
That works perfectly for me in every situation I've run into.
In other words, in what circumstance would you *not* want to
specifically instantiate the extra Voice context(s)?
If this doesn't solve the problem you're talking about, please post a
minimal code example, so we (I) can see what you're talking about.
Hope this helps,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "programming error: Going back in MIDI time"
Hi Ed, On 8/29/07, Ed Ravin <[EMAIL PROTECTED]> wrote: > > Haven't heard any response- can anyone ID the cause of this message? > It does not seem to be causing any other problems, yet... > Would you mind posting the \melody section? Without that, it's impossible to diagnose. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "programming error: Going back in MIDI time"
On 8/29/07, Neil Puttock <[EMAIL PROTECTED]> wrote: > > Hi Ed, > > On 8/29/07, Ed Ravin <[EMAIL PROTECTED]> wrote: > > > > Haven't heard any response- can anyone ID the cause of this message? > > It does not seem to be causing any other problems, yet... > > > > Would you mind posting the \melody section? Without that, it's impossible > to diagnose. > > Regards, > Neil Sorry, I've just realized it could also be in \upper or \lower. If you can post a minimal example which has this error, it would be easier to work out what's happening. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: programming error: (de)crescendo on items with specified volume.
Hi Ed,
I started getting this message:
programming error: (de)crescendo on items with specified volume.
When I added this line to the melody portion (of a singer with
piano piece)
\times 2/3 { e8 e e } e,4. \> e8 \! \p ^"rit." ds e |
The warning goes away if I remove the "\p".
Since \! and \p both visually (and, thus, technically) terminate a
decrescendo, there might be some sort of (internal Lilypond) conflict
going on when you put both on the same note.
Try getting rid of the \! instead of the \p -- it will have the same
(visual) effect, but will leave the explicit volume/dynamic in place.
This is the same piece that has the other warning I just posted
about "going back in MIDI time". In spite of the two warnings both
the PDF and MIDI output seem OK.
I predict that eliminating the \! will result in eliminating the
error messages without affecting the "OK-ness" of the PDF and MIDI
output. =)
Hope this helps!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Changing staffs in the middle of the song
I've come across many songs where the number of staffs changes in the middle of the song. How is this ideally done? I've found a number of ways to do it . . . but they're not easy, ideal, or what I would call standard (not very reusable; pretty much, I have to spend hours finding a new way every time, unless I want to use multiple scores in the same sheet music). So, let's say I start out with two staffs: one with a treble clef and one with a bass clef. Then, I need to change to three staffs where the top is treble, with piano accompaniment on a treble and a bass clef staff below. Then, I want to change to a full choir staff where each voice gets its own staff . . . And . . . I want to do this all on one score. Anyway, how do I do this, normally? Or . . . is this not a 'normal' thing to do? Here's a solution I found for changing from a solo staff with a two staff piano accompaniment to a regular hymn-style two staff setup on the chorus: I just didn't continue with the treble clef of the piano accompaniment, and then it sort of happened naturally. However, this would definitely not stand up for a need for more complex staff changes (and adding multiple voices would be a definite problem here, and that's why I had to come up with the solution for my previous post). Anyway, thanks for all the help you can offer! ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Odd Jobs (mostly documentation)
The FretBoards context that I sponsored some time back, still needs to be added to the instrument specific section of the manual. Graham Percival-2 wrote: > > Are you interested in helping LilyPond? There are many tasks that are > available which do not have time to do ourselves. Some of these require > a fair amount of technical knowledge, but many of them only require a > moderate amount of lilypond skill. > > > Lilypond Odd Jobs > - > > Cameron Horsburgh has agreed to monitor the lilypond-user maillist > documentation issues. > > > ONE-SHOT JOBS (estimated time: 30min - 2 hrs each) > - create example for automatic accidental examples that demonstrates > everything > - add avoid-slur settings to everything in scm/script.scm > - preprocessor docs > - convert-ly bugs and tips > - musicxml: current features, limitations > - pdf chapter headings (in sidebar) > - special markup command examples (note head styles, rotation, etc: > complicated stuff to show off some possibilities). Maybe as LSR or > input/test/ instead of manual. > - add one-line examples to 8.1.6 Overview of text markup > commands. See > http://lists.gnu.org/archive/html/lilypond-user/2007-01/msg00143.html > > > TECHNICAL ABILITY REQUIRED > - integrate LSR: > http://lists.gnu.org/archive/html/lilypond-devel/2006-08/msg00146.html > (once LSR is done) > - clean up input/test/ > - copy any useful examples from input/regression into input/test/ > > > GENERAL EDITING / JANITORIAL: > - check manual for current correctness (does it make sense, is the info > up-to-date, etc) > - verify anything in the "bugs" sections > - standardize # signs > http://lists.gnu.org/archive/html/lilypond-devel/2006-10/msg00180.html > - avoid future tense > http://lists.gnu.org/archive/html/lilypond-devel/2006-01/msg00076.html > > > ADVANCED > - So, another thing for the todo list > is to do through ly/music-functions-init.ly and add a doc string to every > function listed. > - ideally, add examples as well; see 12.1.7 Overview of available music > functions. See > http://lists.gnu.org/archive/html/lilypond-user/2007-01/msg00143.html > - Some type of doc. that oulined the lexical construction of Lilypond > would be helpful. > > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user > > -- View this message in context: http://www.nabble.com/Lilypond-Odd-Jobs--%28mostly-documentation%29-tf2941878.html#a12395128 Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: programming error: (de)crescendo on items with specified volume.
Hi Kieren, On 8/29/07, Kieren MacMillan <[EMAIL PROTECTED]> wrote: > > > Since \! and \p both visually (and, thus, technically) terminate a > decrescendo, there might be some sort of (internal Lilypond) conflict > going on when you put both on the same note. > > This is the same piece that has the other warning I just posted > > about "going back in MIDI time". In spite of the two warnings both > > the PDF and MIDI output seem OK. > > I predict that eliminating the \! will result in eliminating the > error messages without affecting the "OK-ness" of the PDF and MIDI > output. =) > I can't verify this error, but the documentation advises you to explicitly terminate (de)crescendos to prevent problems with the MIDI output. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: programming error: (de)crescendo on items with specified volume.
Hi Kieren, On 8/29/07, Kieren MacMillan <[EMAIL PROTECTED]> wrote: > > > Since \! and \p both visually (and, thus, technically) terminate a > decrescendo, there might be some sort of (internal Lilypond) conflict > going on when you put both on the same note. > > This is the same piece that has the other warning I just posted > > about "going back in MIDI time". In spite of the two warnings both > > the PDF and MIDI output seem OK. > > I predict that eliminating the \! will result in eliminating the > error messages without affecting the "OK-ness" of the PDF and MIDI > output. =) > I can't verify this error, but the documentation advises you to explicitly terminate (de)crescendos to prevent problems with the MIDI output. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Changing staffs in the middle of the song
Hi Mark, How is this ideally done? This is an on-going issue; check the archives for a recent thread regarding choral scores. As it turns out, I just had an interesting brainstorm on how to handle this -- inspired by the \RemoveEmptyStaffContext thread with Valentin in the last little while -- but I will need some time to make a working example. In the meantime, I think we're stuck with I have to spend hours finding a new way every time =\ Regards, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: programming error: (de)crescendo on items with specified volume.
Hi Neil, the documentation advises you to explicitly terminate (de) crescendos to prevent problems with the MIDI output. Ah... I don't do much work with MIDI, so I've never run into that part of the docs... Here's hoping you solve the problem! Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tip: lyrics with polyphony / stem directions (without specifically instantiated voices)
Kieren MacMillan wrote:
Hi Mark:
I've discovered a number of threads on this topic (how lyrics don't
work when you use such as <<{a' b'} \\ { c' d'}>>
I'm not sure what you mean by "lyrics don't work" -- have you tried
<< { a' b' } \new Voice { c' d' } >>
instead of
<< { a' b' } \\ { c' d' } >>
That works perfectly for me in every situation I've run into.
In other words, in what circumstance would you *not* want to
specifically instantiate the extra Voice context(s)?
Well, the situation is the one I mentioned in my other thread you just replied
to (when dealing with changes in the numbers of staffs in certain ways).
By saying the lyrics don't work, I mean the lyrics skip the 'polyphonic' notes.
This is a known issue, though. I didn't mean to pose a problem so much as a
work-around for it.
Here are links to some threads about the issue (for a better idea of what I
mean):
http://www.nabble.com/No-lyrics-to-polyphony-tf2834191.html#a7912625
http://www.nabble.com/Polyphony-and-%28disappearing%29-lyrics-tf4112255.html#a11693011
http://www.nabble.com/Cannot-get-the-lyrics-in-polyphony-tf1467125.html#a3965155
etc. (just look up lyrics pholyphony in a search)
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: programming error: (de)crescendo on items with specified volume.
I started getting this message:
programming error: (de)crescendo on items with specified volume.
b8 a4. \> ^"rit." r8 f8 \! \mp e f |
try this
with \f before \> \p
\score {
{ b8 a4.\f \> ^"rit." r8 f8 \! \mp e f }
\midi { }
}
and without dynamics
\score {
{ b8 a4.\> ^"rit." r8 f8 \! e f }
\midi { }
}
return not programming error :-)
You must specified a volume (dynamics) with logique (de)crescendo
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: programming error: (de)crescendo on items with specified volume.
You must specified a volume (dynamics) with logique (de)crescendo
ditto the midiMaximumVolume and midiMinimumVolume do not equal.
this example return
programming error: (de)crescendo on items with specified volume.
\score {
{
\set Staff.midiMaximumVolume = #0.5
\set Staff.midiMinimumVolume = #0.5
b8 a4.\f\> ^"rit." r8 f8 \! \p e f
}
\midi { }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tip: lyrics with polyphony / stem directions (without specifically instantiated voices)
Hi Mark,
By saying the lyrics don't work, I mean the lyrics skip the
'polyphonic' notes.
Sorry, I must be dense here... =\
Please tell me what behaviour you find unexpected in the attached
snippet (note that the lyrics clearly DO NOT skip the 'polyphonic
notes') -- that way, I'll know exactly what you're talking about, and
might be able to be of more help.
Thanks,
Kieren.
_
\version "2.11.30"
theMusic = \relative c'
{
e4 d c2 |
e4 d c2 |
<<
{
\voiceOne
g'4 f8. f16 e2 |
g4 f8. f16 e2
}
\new Voice
{
\voiceTwo
e4 d c2 |
e4 d c2
}
>> \oneVoice
}
theWords = \lyricmode
{
Three blind mice, three blind mice,
See how they run, see how they run.
}
\score
{
<<
\new Voice = "singer" \theMusic
\new Lyrics \lyricsto "singer" \theWords
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to deal with Time Signatures horizontal alignment?
2007/8/26, Valentin Villenave <[EMAIL PROTECTED]>: > This is the point; the time signatures should be aligned with the > barlines, *unless* they're at the beginning of the line (then they > have to be put after the clef). > > This is because in such orchestral scores, the time signature is > printed above the 1st flute staff, above the 1st Horn staff and above > the 1st Violins staff (in other words, above each main instrument > groups). Since there is no barline between those staves, the > TimeSignature can be aligned with the barlines, *but* since the first > barline of each system is always printed, then the TimeSignature has > to be moved after the Clef. OK, so just to sum up the situation: I now have TimeSignatures aligned with barlines, which is fine for the topmost TimeSig, but not for the "internals" ones between each StaffGroup (since, when occuring at the beginning of a system, they collide with the left barline). Not being able to move *only* those TimeSignatures, here's what I'll do to prevent such collisions: I'll simply kill them :) for the topmost TimeSig, I just specify \override TimeSignature #'break-visibility = #end-of-line-invisible and for the smallest ones inside the systems; \override TimeSignature #'break-visibility = ##(#f #t #f) It sort of works, so I guess this thread is now closed. Many thanks to you guys, particularly Kieren, Neil, Joe, and last but not least, Han-Wen "God" Nienhuys :) Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tip: lyrics with polyphony / stem directions (without specifically instantiated voices)
Kieren MacMillan wrote:
. . .
Please tell me what behaviour you find unexpected in the attached
snippet (note that the lyrics clearly DO NOT skip the 'polyphonic
notes') -- that way, I'll know exactly what you're talking about, and
might be able to be of more help.
. . .
Your example looks perfectly fine, and I see no unexpected results.
At first I thought this would cause problems when used inside of another
context, but, you do something new to me I haven't seen suggested with this
before (\oneVoice, and no \new Voice before the first voice). I tried it out
in my situation, and it works.
It looks like there is a solution to the problem, and perhaps people in the
past just didn't understand the questions of the people asking properly . . .
Anyway, here is the code that works, in the fashion I want it to work (this
example isn't one of a situation that would require it, as that would be too
complex, but it is one that shows it can work how I want it to):
\version "2.10.29"
sopWords = \lyricmode
{
\set stanza = "1. "
TestOne testTwo
}
\score
{
<<
\new Staff
<<
\new Voice = "sopranos"
{
\voiceOne
\time 4/4
\key c \major
a'4
<<
{\voiceOne a'}
\new Voice
{\voiceTwo a'}
>> \oneVoice
\bar "|."
}
\new Lyrics = sopranos { s1 }
>>
\context Lyrics = sopranos \lyricsto sopranos \sopWords
>>
}
Thank you for your help! This will help out with quite a lot of other issues, actually, it
seems. I suspect the key was using \oneVoice to set it back, since the reason it didn't
show up using <<{} \\ {}>> was that they produced extra voices or something
like that which couldn't be referenced properly. What I tried before, at your first
suggestion, was doing what I did on the outer framework in this code (i.e. without
\oneVoice).
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Lyric encoding for LilyPond midis
I've been having trouble with my karaoke midis made from LilyPond, seeing as my midi player doesn't do UTF-8. Generally speaking, the only UTF-8 characters I need are also included in the extended ASCII character set (which my karaoke player—or pretty much any karaoke player—should be fine with). Is there a way to make it so the applicable characters are translated to that character set for the midi so I don't see garbled stuff every time I type characters such as the following? —, “, ”, í, ß, ð, Þ, and so forth. Anyway, that would be nice to know. I'd rather leave the text/source/ly file as UTF-8 if I could, though (but I'd still want to know, if not). If not . . . Do you have any suggestions for a good UTF-8 compatible karaoke midi player (preferably one specifically meant for that, rather than something huge like Winamp)? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tip: lyrics with polyphony / stem directions (without specifically instantiated voices)
Hi Mark,
It looks like there is a solution to the problem
Glad it worked!
perhaps people in the past just didn't understand the questions of
the people asking properly . . .
Perhaps... that's why I kept trying to clarify what question you were
really asking, so that I could answer the question you were really
asking! =)
Graham: may I suggest one thing that might help the docs? In 6.3
(especially .4, Explicitly instantiating voices), maybe if the notes
in each Voice context were independently (i.e., differently)
coloured, the examples (and thus the constructs and internal Lilypond
mechanisms) would be even more clear immediately?
For an example, see the attached snippet.
Best regards,
Kieren.
___
\version "2.11.30"
\markup \wordwrap { At first it may be difficult to understand why
the three C notes are not tied in the following example: }
\score
{
\new Staff \relative c''
{
c ~ << { c ~ } \\ { a } >> c
}
}
\markup \wordwrap { By colouring the main Voice red, the problem
becomes clear: }
\score
{
\new Staff \relative c''
{
\override Voice.NoteHead #'color = #red
c ~ << { c ~ } \\ { a } >> c
}
}
\markup \wordwrap
{
Within the \typewriter {"<< \\\ >>"} polyphony section, two
completely new Voice contexts, independent from the main Voice, have
been constructed automatically by Lilypond. There are several ways to
compensate for this instantiation, but the easiest is simply to avoid
the \typewriter { "\\\ " } construct entirely — within the "<< >>"
construct, any notes before an explicit \typewriter { "\\new Voice" }
command will belong to the main Voice context (i.e., the one
“outside” the polyphony):
}
\score
{
\new Staff \relative c''
{
\override Voice.NoteHead #'color = #red
c ~ << { c ~ } \new Voice { a } >> c
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Tweaking placement of rehearsal marks
Hello I am using \mark in my first measure to give instructions on the feel of the piece. The mark's text overlaps some beams and some notes on the various parts when they are printed individually. How can I tweak to avoid overlapping? The commands I am using are: \once \override Score.RehearsalMark #'self-alignment-X = #left \mark "Smooth, light, precise" Thanks Nick Didkovsky ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tweaking placement of rehearsal marks
If you upgrade to the latest development version, 2.11.x, there is no need for any tweaking, since these kind of collisions are avoided automatically. If you want to stick to the stable version, read about how to modify the padding of different objects in section "Common Tweaks". Note that RehearsalMark is handled at the score level, just as the MetronomeMark object mentioned in that text. /Mats Nick Didkovsky wrote: Hello I am using \mark in my first measure to give instructions on the feel of the piece. The mark's text overlaps some beams and some notes on the various parts when they are printed individually. How can I tweak to avoid overlapping? The commands I am using are: \once \override Score.RehearsalMark #'self-alignment-X = #left \mark "Smooth, light, precise" Thanks Nick Didkovsky ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tweaking placement of rehearsal marks
You should also read chapter 5, particularly 5.2. The section is called "fixing overlapping notation", which sounds like a good place to start. Cheers, - Graham Mats Bengtsson wrote: If you upgrade to the latest development version, 2.11.x, there is no need for any tweaking, since these kind of collisions are avoided automatically. If you want to stick to the stable version, read about how to modify the padding of different objects in section "Common Tweaks". Note that RehearsalMark is handled at the score level, just as the MetronomeMark object mentioned in that text. /Mats Nick Didkovsky wrote: Hello I am using \mark in my first measure to give instructions on the feel of the piece. The mark's text overlaps some beams and some notes on the various parts when they are printed individually. How can I tweak to avoid overlapping? The commands I am using are: \once \override Score.RehearsalMark #'self-alignment-X = #left \mark "Smooth, light, precise" Thanks Nick Didkovsky ___ 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: Tip: lyrics with polyphony / stem directions (without specifically instantiated voices)
Excellent idea! I will add something like this to the manual, extended with
yet another example that shows how to manually specify \voiceOne and so on.
/Mats
Kieren MacMillan wrote:
Hi Mark,
It looks like there is a solution to the problem
Glad it worked!
perhaps people in the past just didn't understand the questions of
the people asking properly . . .
Perhaps... that's why I kept trying to clarify what question you were
really asking, so that I could answer the question you were really
asking! =)
Graham: may I suggest one thing that might help the docs? In 6.3
(especially .4, Explicitly instantiating voices), maybe if the notes
in each Voice context were independently (i.e., differently) coloured,
the examples (and thus the constructs and internal Lilypond
mechanisms) would be even more clear immediately?
For an example, see the attached snippet.
Best regards,
Kieren.
___
\version "2.11.30"
\markup \wordwrap { At first it may be difficult to understand why the
three C notes are not tied in the following example: }
\score
{
\new Staff \relative c''
{
c ~ << { c ~ } \\ { a } >> c
}
}
\markup \wordwrap { By colouring the main Voice red, the problem
becomes clear: }
\score
{
\new Staff \relative c''
{
\override Voice.NoteHead #'color = #red
c ~ << { c ~ } \\ { a } >> c
}
}
\markup \wordwrap
{
Within the \typewriter {"<< \\\ >>"} polyphony section, two
completely new Voice contexts, independent from the main Voice, have
been constructed automatically by Lilypond. There are several ways to
compensate for this instantiation, but the easiest is simply to avoid
the \typewriter { "\\\ " } construct entirely — within the "<< >>"
construct, any notes before an explicit \typewriter { "\\new Voice" }
command will belong to the main Voice context (i.e., the one “outside”
the polyphony):
}
\score
{
\new Staff \relative c''
{
\override Voice.NoteHead #'color = #red
c ~ << { c ~ } \new Voice { a } >> c
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Odd Jobs (mostly documentation)
Kieren MacMillan wrote: GENERAL EDITING / JANITORIAL: - check manual for current correctness (does it make sense, is the info up-to-date, etc) - verify anything in the "bugs" sections - standardize # signs http://lists.gnu.org/archive/html/lilypond-devel/2006-10/msg00180.html - avoid future tense http://lists.gnu.org/archive/html/lilypond-devel/2006-01/msg00076.html Is this job still open? Yes, definitely. The one-shot jobs might have a better result/payoff ratio, but if you're interested in this, it's certainly open! There are three different levels you could pursue: - (low) read the docs, experiment with "bugs", find mistakes. Then write emails to me detailing all these changes, and I'll happily make the corrections. - (medium) download the source, then edit the .texinfo files (they're easy to understand, even if you've never used texinfo) to make corrections. If you do this, then you could also read/resolve any comments in the docs. :) - (high) download the source, build docs on your home computer (see Program Usage, 1.2.4 Building documentation without compiling LilyPond), edit texinfo, build docs again to make sure you have a good patch, then send patches to me. Speaking from experience, the last option is much more satisfying (since you can actually see the changes), but requires a bit more technical ability. Since you're using OSX, it shouldn't be too hard. (I did everything like this until two weeks ago) oh, you should have fink installed; you might want to look into that if you don't have it already. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
lilypond odd jobs (updated Aug 2007)
Here's the latest version of my "odd jobs" list. These are things that would be nice, but the documentation team does not have the resources to do themselves. In other words, if one of you doesn't do it, it won't get done. Lilypond Odd Jobs - ONE-SHOT JOBS (estimated time: between 0.5 and 2 hours) - special markup command examples (note head styles, rotation, etc: complicated stuff to show off some possibilities). Maybe as LSR instead of manual. - document (manual or LSR) adding command-line arguments to lilypond scores: http://www.mail-archive.com/lilypond-user@gnu.org/msg16042.html http://lists.gnu.org/archive/html/lilypond-user/2006-10/msg00271.html - document (manual or LSR) adding arguments to \include: http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00642.html - document (manual or LSR) first/last page header commands: http://www.mail-archive.com/lilypond-user@gnu.org/msg24949.html - document (manual or LSR) multiple tags: http://lists.gnu.org/archive/html/lilypond-user/2007-01/msg00635.html - prettify the main "snippets" page of the docs. input/lsr/LSR.ly http://lilypond.org/doc/v2.11/input/lsr/collated-files - doc FretBoards in chapter 7. Added sometime... since 2.6? check the NEWS files. TECHNICALLY ADVANCED - convert-ly bugs and tips - preprocessor docs - musicxml: document current features, limitations - musicxml: programming. (it's currently not supported) GENERAL EDITING / JANITORIAL: - check manual for current correctness (does it make sense, is the info up-to-date, etc) - verify anything in the "bugs" sections - standardize # signs http://lists.gnu.org/archive/html/lilypond-devel/2006-10/msg00180.html - avoid future tense http://lists.gnu.org/archive/html/lilypond-devel/2006-01/msg00076.html ADVANCED - go through ly/music-functions-init.ly and add a doc string to every function listed. - Some type of doc that outlined the lexical construction of Lilypond ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tip: lyrics with polyphony / stem directions (without specifically instantiated voices)
Looking back at the section on Explicitly instantiating voices, I now
notice that
more or less the same idea is already used, but with different shapes of
the note
heads instead of using different colors. The example also shows the use of
explicit \voiceOne, \voiceTwo and \oneVoice commands.
Mark, what do you say? Is the current example in the manual too complex so
that the main points are not clear enough? Should we replace that example
by Kieren's?
(For the record, there are plenty of answers to similar questions in the
mailing list
archives, that show exactly the same construct. I'm surprised that you
didn't find
them.)
/Mats
Mats Bengtsson wrote:
Excellent idea! I will add something like this to the manual, extended
with
yet another example that shows how to manually specify \voiceOne and
so on.
/Mats
Kieren MacMillan wrote:
Hi Mark,
It looks like there is a solution to the problem
Glad it worked!
perhaps people in the past just didn't understand the questions of
the people asking properly . . .
Perhaps... that's why I kept trying to clarify what question you were
really asking, so that I could answer the question you were really
asking! =)
Graham: may I suggest one thing that might help the docs? In 6.3
(especially .4, Explicitly instantiating voices), maybe if the notes
in each Voice context were independently (i.e., differently)
coloured, the examples (and thus the constructs and internal Lilypond
mechanisms) would be even more clear immediately?
For an example, see the attached snippet.
Best regards,
Kieren.
___
\version "2.11.30"
\markup \wordwrap { At first it may be difficult to understand why
the three C notes are not tied in the following example: }
\score
{
\new Staff \relative c''
{
c ~ << { c ~ } \\ { a } >> c }
}
\markup \wordwrap { By colouring the main Voice red, the problem
becomes clear: }
\score
{
\new Staff \relative c''
{
\override Voice.NoteHead #'color = #red
c ~ << { c ~ } \\ { a } >> c
}
}
\markup \wordwrap
{
Within the \typewriter {"<< \\\ >>"} polyphony section, two
completely new Voice contexts, independent from the main Voice, have
been constructed automatically by Lilypond. There are several ways to
compensate for this instantiation, but the easiest is simply to avoid
the \typewriter { "\\\ " } construct entirely — within the "<< >>"
construct, any notes before an explicit \typewriter { "\\new Voice" }
command will belong to the main Voice context (i.e., the one
“outside” the polyphony):
}
\score
{
\new Staff \relative c''
{
\override Voice.NoteHead #'color = #red
c ~ << { c ~ } \new Voice { a } >> c
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Lyric encoding for midis
I've been having trouble with my karaoke midis made from LilyPond, seeing as my midi player doesn't do UTF-8. Generally speaking, the only UTF-8 characters I need are also included in the extended ASCII character set (which my karaoke player—or pretty much any karaoke player—should be fine with). Is there a way to make it so the applicable characters are translated to that character set for the midi so I don't see garbled stuff every time I type characters such as the following? —, “, ”, í, ß, ð, Þ, and so forth. Anyway, that would be nice to know. I'd rather leave the text/source/ly file as UTF-8 if I could, though (but I'd still want to know, if not). If not . . . Do you have any suggestions for a good UTF-8 compatible karaoke midi player (preferably one specifically meant for that, rather than something huge like Winamp)? -- View this message in context: http://www.nabble.com/Lyric-encoding-for-midis-tf4350688.html#a12396560 Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Lyric encoding for LilyPond midis
I've been having trouble with my karaoke midis made from LilyPond, seeing as my midi player doesn't do UTF-8. Generally speaking, the only UTF-8 characters I need are also included in the extended ASCII character set (which my karaoke player—or pretty much any karaoke player—should be fine with). Is there a way to make it so the applicable characters are translated to that character set for the midi so I don't see garbled stuff every time I type characters such as the following? —, “, ”, í, ß, ð, Þ, and so forth. Anyway, that would be nice to know. I'd rather leave the text/source/ly file as UTF-8 if I could, though (but I'd still want to know, if not). If not . . . Do you have any suggestions for a good UTF-8 compatible karaoke midi player (preferably one specifically meant for that, rather than something huge like Winamp)? -- View this message in context: http://www.nabble.com/Lyric-encoding-for-LilyPond-midis-tf4350985.html#a12397580 Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
