Re: Thank you!
2008/1/8, Graham Percival [EMAIL PROTECTED]:
On Tue, 8 Jan 2008 02:19:26 +0100
Valentin Villenave [EMAIL PROTECTED] wrote:
However, you may have noticed that my way is different than yours: I
use to always do a few different LilyPond-related tasks at a same
time, so that I never get bored
So do I.
- oversee normal bug reports
- manage volunteers
- explain things to new volunteers
- read all mailists for anything relevant
- discuss various long-ranging plans, or in some cases postpone
such discussions
- apply Trevor's patches to the LM, after fixing build issues
- manually merge .itely files where two people were working on
them at the same time and moved text around
- carefully review and commit patches from newer helpers
- explain what the docs meant to newer helpers, so that they can
phrase it better
- discuss specifics of doc sections with helpers who are working
on those sections
- manage TODO lists
- manage doc sources for people who aren't using git
Since I'm hitting 4 hours a day, I'm clearly doing too much --
especially for somebody who's retiring. Therefore I feel entirely
justified in shelving discussion about whatever we were talking
about.
I might be spending even more time these days. Clearly too much for me
too, but it's just so exciting :)
Since you have so much energy, you can go and fix some mistakes:
- Unanswered bug report from Raphael Manfredi from Jan 6. Two reports
were made; Mats answered one of them. You can't be bored of bugs
already.
Oh yes. I was hesitating whether to accept it or to ask for a minimal
example -- in the end I just marked it with a star (on my Gmail web
interface) and postponed it.
I should have a bug-day like you did on wednesdays, for all things
that are more than just copy/pasting reports.
- obvious mistakes in the Pitches snippet list. Since I've
announced the almost-final version of Pitches, it would have
been nice if these were already fixed.
OK, I have reviewed all Pitches-tagged snippets. removed a few.
- WTF are glissano-contemporary and jazz-combo-template listed here?
glissando-contemporary: seemed obvious to me. It is a notation that
affects Pitches, in a very specific way. However, after having
re-checked it, I'm not convinced anymore (this is not a real
glissando as it isn't meant to lead from one pitch to another). Tag
removed.
jazz-combo-template: ok, it's kind of a riddle. I tagged it as Pitches
(it was the #4 or #5 tag, because it's obviously not this snippet's
primary purpose) just because it was a very nice example of
transposing instruments. OK, I removed the Pitches tag.
- there's some obvious indentation problems. I'm particularly
concerned about preventing-extra... since that's included verbatim in
the manual. Some advanced user is going to point out this problem in a
day or two.
Oh yes. I have to say I didn't really pay attention to this detail. I
now have reviewed and corrected all docs-tagged snippets, and you
should not get this problem anymore.
- a few snippets have odd extra {} around the entire thing.
I have found and corrected a couple of these, but it's hard to find
all of them since I can hradly search for { :(
- ambiti-multiple-voices has some problems with the snippetverbatim.
You could leave this for John to fix, but it would be nice if you could
figure out why it's happening and fix it yourself.
I can't. Maybe it's because I've used some code/code formatting
tags in the HTML description, other than that, I don't understand
what's happening.
These tasks aren't as urgent as the bug reports, so I didn't
bother mentioning them a week ago when I first noticed them.
You should have; I (still) handle LSR snippets much better than bug reports.
2008/1/8, Graham Percival [EMAIL PROTECTED]:
Oops, I just remembered what else I was going to say:
- you can't use blockquote in the .css, since that's used in the
@warning. Try doing something with the class= commands
instead.
Yes, I already have worked this out (but I thought this was to be postponed :)
Cheers,
Valentin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Orchestral score
Hi Jeremiah!
I'm still running v2.8.X and I don't know what has changed since.
Nevertheless I'm going to show you how I handle score layout. Perhaps my
logical approach can give you the right clou...
Reilly schrieb:
I have a score with 22 staves, one system to a page.
I want Lilypond to layout the score so that the the score fills the
page. It would be very nice if the first staff and last staff on each
page lined up when laid side by side. In other words, I want Lilypond
to stretch the interstaff spacing appropriately for each page...
When it comes to score layout I spread staves within a system manually
like follows:
% -
% begin of code
% -
\score {
\context StaffGroup = orchestra {
\context Staff = instr1 {
% here the vertical-extent is set
\override Staff.VerticalAxisGroup #'Y-extent = '(-6 . 6)
% description see below
\firstPageCorr
\music1
}
\context Staff = instr2 {
% here the vertical-extent is set - '(-6 . 6) doesn't have to be
% the same as before
\override Staff.VerticalAxisGroup #'Y-extent = '(-6 . 6)
\music2
}
... (and so on)
}
}
% -
% end of code
% -
I increase/decrease the vertical-extent for every staff by varying '(-6
. 6) until the system fits the whole page. Now I've got pages with
equally spaced staves that look nice.
Problem: The first page only holds the title, the first system on the
following page.
To solve this I reduce the overall extent of the first system. It looks
like this:
% -
% begin of code
% -
\dummyvoice = {
\overrideProperty
#Score.NonMusicalPaperColumn
#'line-break-system-details
#'((fixed-alignment-extra-space . -15))
}
% -
% end of code
% -
Hoope it will help and kind regards
Thies
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Thank you!
On Tue, 8 Jan 2008 11:48:55 +0100 Valentin Villenave [EMAIL PROTECTED] wrote: 2008/1/8, Graham Percival [EMAIL PROTECTED]: - WTF are glissano-contemporary and jazz-combo-template listed here? glissando-contemporary: seemed obvious to me. It is a notation that affects Pitches, in a very specific way. However, after having Since we introduce glissandi in Expressive, it should be tagged with that. - ambiti-multiple-voices has some problems with the snippetverbatim. You could leave this for John to fix, but it would be nice if you could figure out why it's happening and fix it yourself. I can't. Maybe it's because I've used some code/code formatting tags in the HTML description, other than that, I don't understand what's happening. buildscripts/makelsr.py To be honest, *I* don't understand what's happening either... but only because I haven't looked. This is your (and John's) problem now. Since you have git write abilit, it would be nice if you handled the mundane updating. Read the script, and ask John some questions in French if necessary. - REMEMBER TO ALWAYS CHECK THE UNSAFE SNIPPETS MANUALLY!!! somebody could dump scheme 'rm -rf /' into LSR and have it not break everything (because LSR runs in a chroot environment). But then when I do git update and build the docs, my system gets hosed. These tasks aren't as urgent as the bug reports, so I didn't bother mentioning them a week ago when I first noticed them. You should have; I (still) handle LSR snippets much better than bug reports. I was hoping that you'd notice them. I don't want to have to check all your work myself. Yes, I already have worked this out (but I thought this was to be postponed :) Go ahead and send me an updated file. I make no guarantees about when I'll look at it, though. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Thank you!
2008/1/8, Graham Percival [EMAIL PROTECTED]: Since we introduce glissandi in Expressive, it should be tagged with that. It was too. That's the cool thing with tags, you know :) buildscripts/makelsr.py To be honest, *I* don't understand what's happening either... but only because I haven't looked. I have, and still don't understand. What's the matter with you? You're almost blaming me for not having learned Python yet. - REMEMBER TO ALWAYS CHECK THE UNSAFE SNIPPETS MANUALLY!!! What do you mean by unsafe? I read and compile every new snippet before approving it, and I have been reviewing the full LSR to read every snippet that were entered before I was in charge. Basically, there's hardly one snippet with whom I'm not familiar know. somebody could dump scheme 'rm -rf /' into LSR and have it not break everything (because LSR runs in a chroot environment). But then when I do git update and build the docs, my system gets hosed. I haven't thought about that. I don't know how harmful can Scheme code be, but there's clearly a potential issue here. However, it would require that a dangerous snippet was approved, and this is not gonna happen. I was hoping that you'd notice them. I don't want to have to check all your work myself. I would have in the end. But at the time where I started my full LSR reviewing-tagging, I had no idea some snippets could get included verbatim -- otherwise I sure would have corrected the indentation (besides, most of the non-indented snippets were originally added by myself, sometimes based on some former regtests). Go ahead and send me an updated file. I make no guarantees about when I'll look at it, though. Maybe I'll talk web-design with John first; I remember he had some ideas too. V. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Thank you!
On Tue, 8 Jan 2008 21:01:17 +0100 Valentin Villenave [EMAIL PROTECTED] wrote: 2008/1/8, Graham Percival [EMAIL PROTECTED]: buildscripts/makelsr.py To be honest, *I* don't understand what's happening either... but only because I haven't looked. I have, and still don't understand. What's the matter with you? You're almost blaming me for not having learned Python yet. I thought you said you knew python... or maybe that was your brother? ... and maybe it was perl, not python? Still, download the lsr-docs, and try running the file... oh wait, you're on windows: the only OS that doesn't include python by default. Python is a good thing to have installed, but that might be too much bother for this. - REMEMBER TO ALWAYS CHECK THE UNSAFE SNIPPETS MANUALLY!!! What do you mean by unsafe? lilypond -dsafe foo.ly the file will be safe or unsafe. It comes down to what kinds of scheme is used. break everything (because LSR runs in a chroot environment). But then when I do git update and build the docs, my system gets hosed. I haven't thought about that. I don't know how harmful can Scheme code be, but there's clearly a potential issue here. However, it would require that a dangerous snippet was approved, and this is not gonna happen. It's possible to hide a lot of nasty stuff in scheme. Having a short list of things you need to look at carefully will make it much easier. But since John's doing this, never mind. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
different tempos
hi, my name is kostia, i am a student of composition and this is my first post. first of all: thank you for lilypond! amazing software and ideology behind it!! now, i have a question concidering music where each instrument plays its own, individual tempo that, in addition, may change during the piece. i've tried to write down a piece with different tempos by using the \compressMusic - command and making one huge bar for the whole piece with different lengths for each staff. but this led to extremely uncomfortable time signatures and i couldn't find out how to make appropriate line breaks: i seem to get one line for the whole piece, which of course doesn't fit on the paper. did anyone try to solve similar problems and has some useful suggestions for me? (i'm very new to lilypond...) or is there even the possibility to somehow set an individual tempo (in bpm maybe) for each staff and get a notation that would be proportionally correct, somewhat like space-notation? i hope, that i express myself clearly. if not, i will try to post an example (must still find out how to do that on that list? just attaching a pdf to the email?) thanks! and my best wishes for the new year! kostia. ___ Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=00 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
You can support software freedom in 2008!
Dear free software supporter, Today we're stepping up our year-end fundraiser to support our 2008 campaign goals for software freedom. Our target is 500 new FSF members or $100,000 -- whichever comes first by January 31. Please help us reach our target by joining as a member at http://fsf.org/associate/support_freedom/join_fsf, or making a donation at http://www.fsf.org/associate/donate/. Our anti-DRM campaign DefectiveByDesign.org and the coming launch of the End Software Patents Coalition campaign need your support! You can help even more by: * Putting our fundraising widget on your website http://www.fsf.org/associate/widget/ * Encouraging your employer to give back by subscribing them to the FSF newsletter ($240 annually) http://www.fsf.org/appeal/2007/subscription * Asking friends to join (you'll get referral gifts and recognition!) http://www.fsf.org/associate/referral/ * Purchasing a gift membership for a friend or family member http://www.fsf.org/associate/gift/ * Signing your organization up in the FSF patron program (from $2,000) http://www.fsf.org/donate/patron/ Please spread the word by forwarding this e-mail or the link to the video message. Thanks for your continued support! Peter and the Free Software Foundation team! ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: You can support software freedom in 2008!
On Tue, Jan 08, 2008 at 09:23:43PM +, Free Software Foundation wrote: From: Free Software Foundation [EMAIL PROTECTED] To: [EMAIL PROTECTED] [...] Dear free software supporter, Today we're stepping up our year-end fundraiser to support our 2008 campaign goals for software freedom. [...] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user Does this kind of FSF spam really belong to the lilypond-user mailing list (and to the lilypond-devel list, where it appeared too)? I don't think so. Indeed, I consider sending campaigns to mailing lists without the mailinglist address at least in the to: or cc: headers as offensive spam. Ciao, Kili ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
font and staff size
Hello.
I want to use a less heavy font (smaller notes or wider staff) - less
black on paper. So maybe I should combine the font feta18 with staff-sice
20 or 21. But how to set the font size?
I found in the lilypond documentation only how to change the staff-size
(see below). But I cannot change the font. Who can help?
Thank you.
Werner
---
11.2 Music layout
11.2.1 Setting the staff size
To set the staff size globally for all scores in a file (or in a book
block, to be precise), use set-global-staff-size.
#(set-global-staff-size 14)
This sets the global default size to 14pt staff height and scales all
fonts accordingly.
To set the staff size individually for each score, use
\score{
...
\layout{
#(layout-set-staff-size 15)
}
}
The Feta font provides musical symbols at eight different sizes. Each
font is tuned for a different staff size: at a smaller size the font
becomes heavier, to match the relatively heavier staff lines. The
recommended font sizes are listed in the following table:
font name staff height (pt)staff height (mm) use
feta11 11.22 3.9 pocket scores
feta13 12.60 4.4
feta14 14.14 5.0
feta16 15.87 5.6
feta18 17.82 6.3 song books
feta20 20 7.0 standard parts
feta23 22.45 7.9
feta26 25.28.9
These fonts are available in any sizes. The context property fontSize and
the layout property staff-space (in StaffSymbol) can be used to tune the
size for individual staves. The sizes of individual staves are relative
to the global size.
See also
This manual: Section 8.4.8 [Selecting notation font size], page 207.
---
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
what is an .ily file?
I asked this question the other day but I buried it in with three other of my questions, so it was easy to miss, so I'll ask again. What is an .ily file used for? Thanks, Tim Reeves ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: what is an .ily file?
For example, this file: http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=input/mutopia/W.A.Mozart/mozart-hrn3-allegro.ily;hb=999f5d5eba3835abd274a751ec9dc9741ee77292 is an included lilypond file from this other: http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=input/mutopia/W.A.Mozart/mozart-hrn-3.ly;hb=999f5d5eba3835abd274a751ec9dc9741ee77292 'ily' (i is for include) is an extension you give to files that are to be included inside others with the \include statement, so you can distinguish them from the main files. php files can include ihtml files, texinfo files can include itely (include+texinfo+lilypond) files, and so on. 2008/1/9, Tim Reeves [EMAIL PROTECTED]: What is an .ily file used for? -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: volunteering and other questions
2008/1/7, Tim Reeves [EMAIL PROTECTED]:
2. The advanced layout and titling stylesheet example in the LSR
(http://lsr.dsi.unimi.it/LSR/Item?id=368) makes no sense to
me at all.
Well, it's just the first try in what could become a quite exciting
whole new way of using the LSR: it is a collection of keywords and
shortcuts that are easy to use and to type, while they actually
involve very advanced formatting tricks under the hood.
Basically, you could write a whole book (music, but text as well)
using these commands (plus the few other commands that Nicolas will
post soon).
It says, Below is just a temporary dummy example to ensure LSR
compatibility. Remember to remove it when using the actual code.
You said you were running the development lilypond version, well, the
problem is, the LSR is not.
The LSR has always been running only *stable* lilypond versions.
However, as I told you, this particular snippet involves lots of
advanced things that have recently been implemented (this summer,
IIRC). So, I had basically two choices: either I wouldn't bother
adding this snippet and just would say: let's do this in a year,
either I had to cheat and comment the whole code so the LSR can accept
it...
Where do I get the actual code?
...But you can't post a fully commented snippet, you have to put some
notes, or some text in it. So did I, with my dummy line. If you
click on this image, you'll see the *actual* code.
(The description makes it sound like it will do something like what Nicolas'
framwork in his Couperin book will do, but I can't figure out how to use
Nicolas' code. It seems I need Linux, but I'm running WinXP. I surmise that
the makefile is key to his framework, and to use it I need Linux, right?)
Not at all! First of all, you can perfectly use a makefile on Windows,
you just have to install a program named MSYS. But that's not the
point.
You don't need the makefile at all. Nicolas uses it for his very
advanced framework, to allow some complicated options to be passed to
lilypond. But you can actually, and that's what's great with this
snippet, use the same shortcuts than Nicolas, without having to even
*understand* how it works!
3. Suggestions for change to LM:
Chapter 2.1.1:
Under Windows, replace To get an empty file to start from, run the editor
as described above and use New in the File menu.
with
To get an empty file to start from, run the editor as described above and
use New in the File menu, or right-click on the desktop and select
New...Text Document, and change the extension to .ly.
Chapter 2.1.3
a comment is a remark for the human reader of the music input; it is
ignored while parsing, so it has no effect on the printed output. There are
two types of comments. The percent symbol % introduces a line comment;
anything after % on that line is ignored. A block comment marks a whole
section of music input as a comment. Anything that is enclosed in %{ and %}
is ignored. (Comments do not nest.)
What does Comments do not nest mean? Does it mean I can't put a comment
within a comment? I tried it and it seemed to be no problem.
Yes you will have problems: if you write
%{
this is a first comment block
%{
This is a second comment block
%}
this line should be commented as well, but it's not.
%}
4. What is a .ily file?
It is basically, as far as I can understand, a programmer's use: you
can't give the same extension to a file that is meant to be compiled
as is, than to another file that is only meant to be included in
another.
(actually, you perfectly can, but it's just inelegant I guess)
So Nicolas has this very elegant solution, that is to name all his
files something.ily, then include them all in a master file, and only
give the .ly extension to the master file that has to be compiled.
I assume the i in ily stands fot inclusion or whatever. This is
a personal choice AFAICT, however consider it as a good habit
(Actually, this goes for every line in Nicolas code :)
Hope this is more clear this way; you can also refer to the other
discussion about this snippet on
http://lists.gnu.org/archive/html/lilypond-user/2008-01/msg00191.html
By the way, if you can think of a more self-explanatory way to present
it in the LSR, I'm your man ;)
Cheers,
Valentin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: what is an .ily file?
2008/1/9, Tim Reeves [EMAIL PROTECTED]: I asked this question the other day but I buried it in with three other of my questions, so it was easy to miss, so I'll ask again. What is an .ily file used for? I'm answering on the other thread. Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shift rests
Sorry, the attachemnt failed to upoad
I posted this question 2 days ago but I got no response - maybe the
attachement will illustrate what I mean!
I would appreciate any hint about shifting rests horizontally.
Thnx!
Luc
Isn't a pitched rest supposed to shift to the right or - vice versa - a
chord relative to the rest?
\version 2.11.37
\paper { ragged-right =##t }
{ d' g' }
\\
{ \override NoteColumn #'force-hshift = #2. b \rest }
--
Gruss
Luc
shiftOn.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shift rests
I posted this question 2 days ago but I got no response - maybe the
attachement will illustrate what I mean!
I would appreciate any hint about shifting rests horizontally.
Thnx!
Luc
Isn't a pitched rest supposed to shift to the right or - vice versa - a
chord relative to the rest?
\version 2.11.37
\paper { ragged-right =##t }
{ d' g' }
\\
{ \override NoteColumn #'force-hshift = #2. b \rest }
{ \override NoteColumn #'force-hshift = #2. d' g' }
\\
{ r }
--
Gruss
Luc
___
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/Shift---rests-tp14645928p14702152.html
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: volunteering and other questions
Valentin, You da man! Thanks for your thorough explanations! Tim Reeves ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shift rests
2008/1/9, Luc [EMAIL PROTECTED]: I posted this question 2 days ago but I got no response These things happen :) Isn't a pitched rest supposed to shift to the right or - vice versa - a chord relative to the rest? Why would it be shifted to the *right*? the rest and the chord are simultaneous events, so LilyPond tries to put them vertically aligned. (Plus, when you do'nt use a pitched rest, as you noticed, there is no collision). If you really want to shift your rest to the right, use \once \override Voice.Rest #'X-offset = #2 beware: you'd better use \once before \override, or else your override will stay active in the whole score until you type \revert. Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
position whole measure rest
Hello, I know that I can position a rest vertically using e.g. d'1\rest .
But how can I alter the vertical position of a whole-measure rest (R1)? I want
it to move outside the staff, so it should also get a ledger line.
\relative c'
{ e2 e4 a } \\
{ R1 }
The R1 is drawn too close to the notes.
TIA,
with best regards,
Wilbert Berendsen
--
http://www.wilbertberendsen.nl/
You must be the change you wish to see in the world.
-- Mahatma Gandi
attachment: whole-rest.png___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: font and staff size
Op maandag 7 januari 2008, schreef Werner: I want to use a less heavy font (smaller notes or wider staff) - less black on paper. So maybe I should combine the font feta18 with staff-sice 20 or 21. But how to set the font size? Try \set Staff.fontSize = #-1 http://lilypond.org/doc/v2.11/Documentation/user/lilypond-learning/Size-of-objects Met vriendelijke groet, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ You must be the change you wish to see in the world. -- Mahatma Gandi ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shift rests
2008/1/9, Luc [EMAIL PROTECTED]: I posted this question 2 days ago but I got no response These things happen :) No problem, I just wanted to be sure somebody reads it... Isn't a pitched rest supposed to shift to the right or - vice versa - a chord relative to the rest? Why would it be shifted to the *right*? the rest and the chord are simultaneous events, so LilyPond tries to put them vertically aligned. Because I use \override NoteColumn #'force-hshift = #2. in one voice! This works with a normal note, but not with a \rest-ed note. (Plus, when you do'nt use a pitched rest, as you noticed, there is no collision). I have reduced the score to the essential (lilypond-wise), originally it is a 4 voice arrangement of a piece of John Dowland for lute or guitar where another note appears in the bass (e,) and then the collision occurs! If you really want to shift your rest to the right, use \once \override Voice.Rest #'X-offset = #2 This helps, thanks! -- Gruss Luc ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: position whole measure rest
Wilbert Berendsen wrote:
Hello, I know that I can position a rest vertically using e.g. d'1\rest .
But how can I alter the vertical position of a whole-measure rest (R1)? I want
it to move outside the staff, so it should also get a ledger line.
\relative c'
{ e2 e4 a } \\
{ R1 }
The R1 is drawn too close to the notes.
TIA,
with best regards,
Wilbert Berendsen
Something like this?
{ e'2 e4 a } \\
{ \override MultiMeasureRest #'staff-position =#-7 R1 }
HTH,
Brett
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Tweaking confusion
Borrowing heavily from the LSR and the archive, I created a Tempo Mark
I could use in my scores. The trick was to make an initial tempo mark
(Allegro con moto with a metronome mark) print left justified with the
time signature. I succeeded with the following code:
tempoOne = {
\override Score.RehearsalMark #'break-align-symbol =
#'time-signature
\once \override Score.RehearsalMark #'self-alignment-X = #-1
\mark \markup{ \bold Allegro con moto { \smaller { \note #4 #1 =
112 } } }
\override Score.MetronomeMark #'transparent = ##t
\tempo 4 = 112
}
There was one problem, however. Although I specified self-alignment
left justified, the tempo mark was NOT left justified. I was able to
tweak it into a left justified position by adding:
\once \override Score.RehearsalMark #'X-offset = #7
So far, so good.
However, the tempo mark was too high above the staff. So I tried to
move it lower with the following code:
\once \override Score.RehearsalMark #'Y-offset = #-3
Unfortunately, the tempo mark did not move lower.
So, I did some more research and discovered the following code:
(a) \once \override Score.RehearsalMark #'break-align-symbols = #' (
time-signature )
which is ever so slightly different from my code line
(b) \override Score.RehearsalMark #'break-align-symbol =
#'time-signature
(Note especially the 's' on the end of symbols.) Why two slightly
different code? Is one more correct than the other? Or are they
different code?
Code (a) actually worked great and left justified the tempo mark
without using the X-offset =#7.
But, I still cannot lower the tempo mark.
Although I was able to left justify the tempo mark with code (a), in
the manual I read that I should use the following code:
\once \override Staff.TimeSignature #'break-align-anchor-alignment =
#LEFT
I thought this simple (ahem, ahem) tweak, would be a good
illustration of precisely how baffled I am by Lilypond code. I really
don't know what I am doing and batter my music into the right form by
dint of research and lots of trial and error. I don't want to do it
this way.
In one of the model snippets for a tempo mark, the author included the
following line of code:
\once \override Score . RehearsalMark #'no-spacing-rods = ##t
Questions:
1. What is no-spacing-rods for?
2. Why two codes for break-align-symbol, both of which work, but not
quite the same way?
3. Why can I left justify with Score.RehearsalMark #'break-align-symbol
while the manual suggests that I use Staff.TimeSignature
#'break-align-anchor-alignment?
4. Is there a difference in question #3? Should I have a preference?
5. Why is this so hard anyway? ;-)
Much obliged.
Cheers,
Jeremiah
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re:font and staff size
I'm working on the editorial section of the GDP and the answer is in there however I've not had time to work on that so it makes more sense. Selecting notation font size: However if you look there you should see the answer. If you do the search for font size even through the index you should get to the correct place. If this isn't what you are looking for please explain more. Yours- Jay Jay Hamilton www.soundand.com 206-328-7694 - Message: 1 Date: Mon, 7 Jan 2008 19:25:59 + (UTC) From: Werner [EMAIL PROTECTED] Subject: font and staff size To: lilypond-user@gnu.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=utf-8 Hello. I want to use a less heavy font (smaller notes or wider staff) - less black on paper. So maybe I should combine the font feta18 with staff-sice 20 or 21. But how to set the font size? I found in the lilypond documentation only how to change the staff-size (see below). But I cannot change the font. Who can help? Thank you. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: You can support software freedom in 2008!
= I haven't seen it on -devel; has it been removed somehow? I don't think so. Indeed, I consider sending campaigns to mailing lists without the mailinglist address at least in the to: or cc: headers as offensive spam. Hmm... OTOH, LilyPond *is* a GNU software. They have helped us in some ways (ok, maybe they could have been even more helpful sometimes, but we're still using their savannah resources, and so on), and by being members of the LilyPond community, we are some kind of an extension of the (very large) GNU community. You are right about our being members of this community, however, It would have been common courtesy to ask for permission before posting or perhaps they did. Maybe we should ask someone before jumping to conclusions. I have noticed that various GNU software communities have very different standards concerning this kind of funding requests. Neo Office, for instance, brings you back to the website on first launch after installing the program or a patch to ask for cash donations. Other projects simply would not tolerate such behaviour. This is likely the case with Lilypond, since many members already have supported the Lilypond Developers with paid for feature requests. However, the milk has been spilled and as in our case, we cannot make time move backward (yet). Cheers, David -- David Fedoruk B.Mus. UBC,1986 Certificate in Internet Systems Administration, UBC, 2003 http://recordjackethistorian.wordpress.com Music is enough for one's life time, but one life time is not enough for music Sergei Rachmaninov ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
