Re: Space on the left end of each line
You didn't tell how you removed the clef and key signatures. If you use \override Staff.KeySignature #'transparent = ##t \override Staff.Clef #'transparent = ##t then they will still take the same space as if they were printed. However, based on your problem description, it seems that you have rather removed the engravers or set ... #'stencil = ##f, which completely removes the clef and time signatures. In the latter case, a direct answer to your question is \override Score.LeftEdge #'space-alist #'first-note = #'(fixed-space . 10.0) /Mats Don Blaheta wrote: This seems like the sort of thing there should be an easy tweak for, but I'm not finding the right properties to change, I guess. I'm setting a bunch of plainchant stuff in more or less modern notation, so it uses modern note heads and spacing rules and five lines, but still doesn't have a time signature or key signature and the clef is only printed on the first line. However, since the notes start in immediately on subsequent lines, the lyrics (which are centred on each note head) sometimes hang off the left end of the staff. When I have a stanza mark or something, then it *really* hangs off the end. So I'd like to allow a fixed-width space at the beginning of the line before the notes start rendering. I say fixed-width because I've tried a bunch of things involving adding an invisible note at the beginning of the line, but since there are a different number of notes on each line, this makes a variable-width space and the result looks very ragged. Ideally this fixed-width space would be configurable, but I'd settle for an invisible clef sign (i.e. a space the same width as the clef sign on the first line). But I couldn't figure out how to do that either. I'm using LP 2.10.0 at the moment, but I'm happy to upgrade again if the answer is to be found in a later version. -- = 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
Redefine r? Horizontal beams? Grace without beam break?
Hi, I'm using Lilypond 2.10.25 and I have a few questions...
Is it possible to redefine the rest note name 'r' and instead use e.g. 'p'
for rests. I'd really like to use 'r' for something else (right hand strokes in
drumming).
Can you have _really_ horizontal beams (possibly always at the same hight)?
The following line does not work, the beams are still leaning ever so
slightly...
\override Beam #'damping = #1000
Another thing, how would I tweak the automatic beaming to have grace notes
that do not break beams? For instance, I'd like the first code snippet to
produce the same output as the second.
\stemDown
a8 \grace {c16[c]} a8
\stemDown
a8[ \grace {c16[c]} a8]
thanks!
hguo
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Same score in 2 books having differents global-staff-size
Here's a simple example:
\score{
\relative c'{c d e f }
\layout{ragged-right = ##t }
}
\score{
\relative c'{c d e f }
\layout{
ragged-right = ##t
#(layout-set-staff-size 26)}
}
/Mats
Gilles THIBAULT wrote:
I have a little score fitting just in one page with this command
#(set-global-staff-size 20)
I want to insert it in a \book of various scores for clarinet
beginners, but this book has a different global size :
#(set-global-staff-size 32)
My goal is to have the same result in both cases.
According to the docs, I know that i have to play with :
#(layout-set-staff-size staffsizetofind)
fontSize = #fontsizetofind
\override StaffSymbol #'staff-space = #(magstep
fontsizetofind)
I have made a lot of trials without success. There is perhaps other
tweakings that i have missed.
I would appreciate some tricks to find the appropriate values or the
way to get that ?
Gilles
%
\version 2.11.34
#(set-global-staff-size 20) % original size
%% #(set-global-staff-size 32)% new size
%% #(define staffsizetofind ?)
%% #(define fontsizetofind ?)
frag = \relative c' {
c d8 e f e d b
}
\score {
\new Staff { \repeat unfold 60 \frag c'1 \bar |. }
\layout {
%% #(layout-set-staff-size staffsizetofind)
\context {
\Staff
%% fontSize = #fontsizetofind
%% \override StaffSymbol #'staff-space = #(magstep
fontsizetofind)
}
}
}
%%%
___
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: Same score in 2 books having differents global-staff-size
I forgot to say that there have been some recent bug fixes
related to layout-set-staff-size, so my example works will with
2.11.34, but not on 2.10.33.
/Mats
Mats Bengtsson wrote:
Here's a simple example:
\score{
\relative c'{c d e f }
\layout{ragged-right = ##t }
}
\score{
\relative c'{c d e f }
\layout{
ragged-right = ##t
#(layout-set-staff-size 26)}
}
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Same score in 2 books having differents global-staff-size
I have a little score fitting just in one page with this command
#(set-global-staff-size 20)
I want to insert it in a \book of various scores for clarinet beginners, but
this book has a different global size :
#(set-global-staff-size 32)
My goal is to have the same result in both cases.
According to the docs, I know that i have to play with :
#(layout-set-staff-size staffsizetofind)
fontSize = #fontsizetofind
\override StaffSymbol #'staff-space = #(magstep fontsizetofind)
I have made a lot of trials without success. There is perhaps other tweakings
that i have missed.
I would appreciate some tricks to find the appropriate values or the way to
get that ?
Gilles
%
\version 2.11.34
#(set-global-staff-size 20) % original size
%% #(set-global-staff-size 32)% new size
%% #(define staffsizetofind ?)
%% #(define fontsizetofind ?)
frag = \relative c' {
c d8 e f e d b
}
\score {
\new Staff { \repeat unfold 60 \frag c'1 \bar |. }
\layout {
%% #(layout-set-staff-size staffsizetofind)
\context {
\Staff
%% fontSize = #fontsizetofind
%% \override StaffSymbol #'staff-space = #(magstep fontsizetofind)
}
}
}
%%%
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Redefine r? Horizontal beams? Grace without beam break?
Hugo Flordal wrote:
Hi, I'm using Lilypond 2.10.25 and I have a few questions...
Is it possible to redefine the rest note name 'r' and instead use e.g. 'p'
for rests. I'd really like to use 'r' for something else (right hand strokes in
drumming).
Unfortunately, the 'r' for rests (and 'R' for multimeasure rests and 's'
for spacer notes)
are hard coded in the program.
Can you have _really_ horizontal beams (possibly always at the same hight)?
The following line does not work, the beams are still leaning ever so
slightly...
\override Beam #'damping = #1000
I hope you have searched the mailing list archives. See for example
http://lists.gnu.org/archive/html/lilypond-user/2006-10/msg00111.html
for one solution.
Another thing, how would I tweak the automatic beaming to have grace notes
that do not break beams? For instance, I'd like the first code snippet to
produce the same output as the second.
\stemDown
a8 \grace {c16[c]} a8
\stemDown
a8[ \grace {c16[c]} a8]
As far as I know, that's not possible. The reason is the explicit beam
within the
grace notes.
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: chattiness in @seealso
Graham Percival wrote:
At the very least, I want it clear which sentence refer to the
Notation Reference, and which sentences refer to the other parts of
the docs.
... I _really_ think this is completely unnecessary, though. And if
you want to add full sentences to every single notation reference
@ref{}, I assume you want to do the same for every @lsr{dir,snippet},
every @internalsref{}, etc ?
Mats, you're the yardstick for efficient NR use. What do you think of
the compact vs. full sentence form of @seealso ? I don't want to
approve any change that makes the NR harder to use for knowledgeable
users, and IMO this is one such change.
In my opinion, the main issue is not how chatty the @seealso is but
rather how
much information you include and where you place it. Regarding your current
version of Durations, I think it's great to mention about and
reference to all these
issues that are related to the main topic of the section. One question
is if this information
should be below @seealso or in the main text. I have previously mainly
thought of
the @seealso as a kind of reference list (bibliography) as it is used
in scientific
papers, i.e. a collection of all cross references mentioned in the main
text.
In Durations, you instead use @seealso to introduce new
concepts/issues that
have not been mentioned in the main text and I kind of like the idea of
putting
these in an item list, where they are easier to spot than in running text.
Still, for cross references that have already been mentioned in the main
text,
it would seem chatty to repeat part of the information again in @seealso.
For the link to Proportional duration, for example, it's probably
necessary
to provide the concept in a full sentence, so the readers realize what the
link is all about. For Writing rests, on the other hand, it's pretty
obvious
from the section name itself.
I'm not sure what the conclusion is, but maybe we can reformulate the
original
question into:
- Should we introduce some new concepts under @seealso or should this
always be done in the main text?
- For issues that are somewhat peripheral and just need a short intro and a
cross reference, should they be described in running text or in an
item list?
- Under @seealso, can we find a nice layout that allows for a mix of
pure links
which already have self-explanatory names, with links that need a
sentence of
explanation?
- Is there a need to repeat all links from the main text also in @seealso?
A side comment: in Durations under @refbugs, the term glyphs
is used several times. Is this is term that is well-known to all readers, or
is it only known to hackers?
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond in MikTeX
Am Donnerstag, den 15.11.2007, 12:15 -0800 schrieb Graham Percival: Helge Kruse wrote: I tried the LaTeX example from the Lilypond manual and ran it with MikTeX on Windows XP. Try reading the manual as well. It discusses the lilypond-book script, which you must run. I have no idea if this is compatible with MikTeX. lilypond-book and MikTeX work fine together, i have it running for a long time already on Win XP - Graham greetings rene ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-user Digest, Vol 60, Issue 42
This still works just fine except that the instrument name oboe
does not print at the beginning of the first line. That part was
working just fine a year ago. Can anybody tell me what happened? I've
tried 2.11.27 and 2.10.33, and it doesn't work with either of them.
Ii can't remember what version I was using a year or two ago when it
all worked just fine. Maybe 2.7.something?
BTW the notes of \alto are defined in LoHow.ly and they print out
just as before.
thanks
\version 2.11.27
\include LoHow.ly
\context Staff { \set Staff.instrument = oboe \clef treble \alto}
--
I'm the Doc, and I approve this message.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-user Digest, Vol 60, Issue 42
Hi James,
the instrument name oboe does not print
\version 2.11.27
\include LoHow.ly
\context Staff { \set Staff.instrument = oboe \clef treble \alto}
If you look at the current docs, you'll see that the relevant
properties are now called instrumentName (for the name on the first
system) and shortInstrumentName (for the name on subsequent systems).
For more info, see:
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/
Instrument-names#Instrument-names
Hope this helps!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Same score in 2 books having differents global-staff-size
Here's a simple example:
\score{
\relative c'{c d e f }
\layout{ragged-right = ##t }
}
\score{
\relative c'{c d e f }
\layout{
ragged-right = ##t
#(layout-set-staff-size 26)}
}
Sorry. I have not been enough clear in my question.
The same score don't belong to the same .ly.
Something like that :
%%
% file1.ly %%%
#(set-global-staff-size 20)
\score{
\relative c'{c d e f }
\layout{ragged-right = ##t }
}
}
... = one page
file2.ly
#(set-global-staff-size 32)
%%% ..severall \score here
%%% = 5 pages
\pageBreak %% begin of page 6
\score{%%% same music than in file1.ly
\relative c'{c d e f }
\layout{
ragged-right = ##t
%% something to add here so that (file1.pdf page 1) =
(file2.pdf page 6)
%% same staff-size, same font size etc
%% #(layout-set-staff-size 20) doen't do the job.
}
%%%
Gilles
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dodgy dotted notes
I am using Version 2.8.6 on Windows 98. Clementi Sonata op.7 no.3 has some bars with dotted quaver followed by demi- semi-quavers and then other notes which can give bar lengths varying from the time sig by 1 to 2 demi-semi-quavers. Manual typesetting can handle this but LP ends up with bar-creep. Any suggestions how to print the notes in the correct places and still end up with no bar-creep. Thanks in advance ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dodgy dotted notes
On 17.11.2007 (01:27), Ossie Wilson wrote: I am using Version 2.8.6 on Windows 98. Clementi Sonata op.7 no.3 has some bars with dotted quaver followed by demi- semi-quavers and then other notes which can give bar lengths varying from the time sig by 1 to 2 demi-semi-quavers. Manual typesetting can handle this but LP ends up with bar-creep. Any suggestions how to print the notes in the correct places and still end up with no bar-creep. I take it that you mean that there are too many notes in the measure. You can either use \times to create a tuplet and then hide it with \once \override TupletNumber 'transparent = ##t or scale the durations with something like a4. b16*2/3 c16*2/3 b16*2/3 where the three 16ths will equal an 8th note. See the manual, chapters on Scaling durations and Tuplets. Eyolf -- Emperor Palpatine: Everything that has transpired has done so according to my design. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: church rests
Hans Aberg wrote: So what should the multi-measure rest symbol k |-| be called? I couldn't really pick out an answer from this discussion, so we'll just keep the current church rests. Since it mentions longa and breve in parentheses, I think it's fine. The glossary makes it clear that this is a lilypond-specific term, anyway. If you object to this, please see the current GDP docs and make a specific suggestion as to how we should change them. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: chattiness in @seealso
Mats Bengtsson wrote:
I'm not sure what the conclusion is, but maybe we can reformulate the
original question into:
- Should we introduce some new concepts under @seealso or should this
always be done in the main text?
Let's go with main text. I'm not completely dead-set on this option,
but I don't think anybody is going to seriously argue against it.
- For issues that are somewhat peripheral and just need a short intro and a
cross reference, should they be described in running text or in an item
list?
The problem with an item list is that it raises questions about anything
which is _not_ on the list. For example, @ref{Ties} doesn't appear in
the item list in Durations. And if we move all the explanations away
from the @seealso, it would seem really weird to include @ref{Ties} in
the main text, then again in an item list in the main text, then _again_
in the complete reference list in @seealso.
So right now my vote is to describe anything which needs describing in
the main text.
- Under @seealso, can we find a nice layout that allows for a mix of
pure links
which already have self-explanatory names, with links that need a
sentence of
explanation?
I can't think of any /nice/ layout. A list that alternates
full-sentences and single-word references is going to look weird. A
typical comma-separated horizontal list would still look slightly
awkward even with the parenthetical remarks.
With all that in mind, I'm proposing that we move all sentences into the
main text, and have a simple
@seealso
Notation Reference: @ref{foo}, @ref{bar}.
- Is there a need to repeat all links from the main text also in @seealso?
Perhaps not a need, but I feel a strong desire to do so. It's a simple
enough job for the Formatters.
A side comment: in Durations under @refbugs, the term glyphs
is used several times. Is this is term that is well-known to all
readers, or
is it only known to hackers?
I deliberately decided not to spend time agonizing over this. I just
dumped Han-Wen's email in that section. As a general rule, the @refbugs
will be more technical, harder to understand, and may possibly be a
simple copypaste from a hacker's email or bug respose.
Making @refbugs easier to read might be something to schedule in the
third round of GDP, but certainly not before that. (first round: making
GDP presentable again. Second round: making GDP significantly better
than 2.11 in all respects. Third round: perfection)
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
