Re: Collision between bar number and rehearsal mark
For a manual solution (or moving all rehearsal marks or bar numbers up), see
sections Moving objects and Fixing overlapping notation in the manual.
If you want LilyPond to automatically detect the situation and only move
things when necessary, you can upgrade to the latest development version
2.11.x or wait for the coming 2.12, where exactly these kind of collisions
are avoided by default.
/Mats
Henning Plumeyer wrote:
Hi there,
two weeks ago I found LilyPond and already came across some hurdles.
But now I don't find an answer in the docs for my problem:
How can I avoid the collision between the bar number and the rehearsal
mark
in the following example:
snippet %
\version 2.10.10
\paper{ ragged-right=##t }
\relative c'{
% next two lines after this comment found in
bar-number-every-five-reset.ly
% on the page http://lilypond.org/doc/v2.10/input/test/collated-files
% I want bar numbers every 5 bars, for demo, I chose every 2 bars
here
\override Score.BarNumber #'break-visibility = #end-of-line-invisible
\context Score \applyContext #(set-bar-number-visibility 2)
c1 c \mark #1 c
}
end snippet %
Hope it's possible to move the rehearsal mark only in case of
collision, not all
rehearsal marks.
Greetings
Henning
___
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: GDP: fourth rearrangement
Looks great! A few minor details: - In Rhythms, I would like to rearrange the order a bit, to put the most common aspects at the top. For example: 1.2 Rhythms 1.2.1 Writing rhythms + Durations + Augmentation dots + Tuplets + Scaling durations 1.2.2 Writing rests + Rests + Skips + Multi measure rests 1.2.3 Bars + Bar check + Bar lines + Bar numbers + Barnumber check + Rehearsal marks 1.2.4 Displaying rhythms + Time signature + Partial measures + Unmetered music + Polymetric notation + Automatic note splitting + Automatic beams + Manual beams + Feathered beams 1.2.5 Special rhythmic concerns + Aligning to cadenzas + Time administration + Proportional notation (introduction) - You have a much better feeling for the English language than I do, but do you think that we should keep the current mixture of staff and stave to denote the same thing, for example in the subsection titles within Staff notation? - I'm sure some people don't agree that Fingering instructions belong to Educational use, but it's OK with me. Same goes for Ambitus - Coloring objects and Parentheses do not only apply to Note heads and stems, in general. - How about adding some section like Other typesetting features, which could contain things that don't really fit in anywhere else, like the four I mentioned above. - Again, I might not have the right intuition for English language, but how about replacing Text in a score with something along the lines of Textual annotations I would also move New dynamic marks from 1.17.2 to 1.17.1. - Why doesn't Text markup commands belong under 1.17.2 Text markup? /Mats Graham Percival wrote: Based on the feedback, it seems that most users would vastly prefer something like this? http://lilypondwiki.tuxfamily.org/index.php?title=Doc Numbered titles are new HTML pages; un-numbered titles are on the same HTML page. Sections 1.9 through 1.16 weren't put into the same arrangement, but you can imagine how it would continue. - Graham ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sans Font for Lilypond texts?
If all you want to do is to get a Sans font for lyrics, it's just to
redefine the
corresponding font property. To do this for all Lyrics contexts in your
file,
you can add
\layout{
\context{
\Lyrics
\override LyricText #'font-family = #'sans
}
}
anywhere at the top level of the .ly file.
On the other hand, if you want this specific file, you have to use the
(make-pango-font-tree ...) command, which unfortunately needs to know
the current staff size. One practical way to do it is to remove the line
myStaffSize = #20
from your .ly file and in your .lytex do
\begin[staffsize=11]{lilypond}
\paper{ myStaffSize = #11 }
\include test.ly
\end{lilypond}
If you also want to be able to run the same .ly file standalone, then
you could
make a separate wrapper .ly file that just contains
\paper{ myStaffSize = #20 }
\include test.ly
/Mats
Dominic Neumann wrote:
Hi,
I want to try to have all my lyrics typeset in a Sans font. Therefor
I´ve used a snippet from LSR
(http://lsr.dsi.unimi.it/LSR/Snippet?id=221):
%%% BEGIN OF SNIPPET %%%
\paper {
myStaffSize = #20
#(define fonts
(make-pango-font-tree Bitstream Vera Sans
Nimbus Sans
Luxi Mono
(/ myStaffSize 20)))
}
%%% END OF SNIPPET %%%
I substituted Times New Roman with Bitstream Vera Sans what isn´t a
very good way, I think.
When producing lilypond-output directly with lilypond this works quite
good, but together with lilypond-book the layout is very bad: the
barlines and stems are smaller than they should be to suit the size of
the noteheads.
I produced two simple examples to show what I did:
BEGIN OF PURE LILYPOND-FILE
\version 2.10.29
\paper {
myStaffSize = #20
#(define fonts
(make-pango-font-tree Bitstream Vera Sans
Nimbus Sans
Luxi Mono
(/ myStaffSize 20)))
}
verseOne = \lyricmode {
\set stanza = 1.
test bla blub -- ber
test bla blub -- ber
}
\score {
{
\relative c'' {
\key d \major
\time 2/4
cis4 d | e fis
cis4 d | e fis
\bar |.
}
\addlyrics { \verseOne }
}
}
ENDOF PURE LILYPOND-FILE
BEGIN OF LYTEX-FILE
\documentclass{article}
\begin{document}
\lilypondfile[staffsize=11]{test.ly}
\end{document}
END OF LYTEX-FILE
As you see, I cannot change the Staffsize and everything belonging to
it from within the LyTeX-file. How can I achieve this in another way?
I hope there is a more straight-forward way ...
Thanks, Dominic
PS: It seems that the \sans command only works within \markup
commands. So I cannot say \sans at the beginning of the document to
make everything appear in a Sans font.
___
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
Sans Font for Lilypond texts?
Hi,
I want to try to have all my lyrics typeset in a Sans font. Therefor
I´ve used a snippet from LSR
(http://lsr.dsi.unimi.it/LSR/Snippet?id=221):
%%% BEGIN OF SNIPPET %%%
\paper {
myStaffSize = #20
#(define fonts
(make-pango-font-tree Bitstream Vera Sans
Nimbus Sans
Luxi Mono
(/ myStaffSize 20)))
}
%%% END OF SNIPPET %%%
I substituted Times New Roman with Bitstream Vera Sans what isn´t a
very good way, I think.
When producing lilypond-output directly with lilypond this works quite
good, but together with lilypond-book the layout is very bad: the
barlines and stems are smaller than they should be to suit the size of
the noteheads.
I produced two simple examples to show what I did:
BEGIN OF PURE LILYPOND-FILE
\version 2.10.29
\paper {
myStaffSize = #20
#(define fonts
(make-pango-font-tree Bitstream Vera Sans
Nimbus Sans
Luxi Mono
(/ myStaffSize 20)))
}
verseOne = \lyricmode {
\set stanza = 1.
test bla blub -- ber
test bla blub -- ber
}
\score {
{
\relative c'' {
\key d \major
\time 2/4
cis4 d | e fis
cis4 d | e fis
\bar |.
}
\addlyrics { \verseOne }
}
}
ENDOF PURE LILYPOND-FILE
BEGIN OF LYTEX-FILE
\documentclass{article}
\begin{document}
\lilypondfile[staffsize=11]{test.ly}
\end{document}
END OF LYTEX-FILE
As you see, I cannot change the Staffsize and everything belonging to
it from within the LyTeX-file. How can I achieve this in another way?
I hope there is a more straight-forward way ...
Thanks, Dominic
PS: It seems that the \sans command only works within \markup
commands. So I cannot say \sans at the beginning of the document to
make everything appear in a Sans font.
attachment: purelilyfile.pngattachment: lybookfile.png___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding an end-of-line cautionary key signature
Just add
\once \set Staff.explicitKeySignatureVisibility = #end-of-line-invisible
at the beginning of your \new Staff{...}.
/Mats
Steven Weber wrote:
Lilypond 2.11.32, Windows XP
I’m working on a piece that has several measures of divisi. Because
the piece has a lot of time changes, I don’t want to create a full
second voice and use \RemoveEmptyStaffContext. The LSR has a great
snippet that shows how to temporarily add an additional staff
(http://lsr.dsi.unimi.it/LSR/Item?id=110), but when I add a break
before the parts divide, I get extra space at the end of the line
before the break (where a cautionary key signature would be printed).
I assume this is because in the new staff context, I set the key
signature. Is there a way to suppress this extra space while still
printing the key signature at the beginning of the line?
I’ve tried hiding the stencil (which does remove the space at the end
of the line, but unfortunately, also removes it from the beginning of
the line). It seems like the break-visibility option should really
cover this situation, but none of the options I’ve tried have worked.
Can someone spot what I’m doing wrong, or suggest a better way to do this?
Here’s a brief example that demonstrates what I’m trying to do:
\version 2.11.32
\include english.ly
\score
{
\new StaffGroup
{
\clef bass
\key ef \major
% Just to fill up some space
\unfoldRepeats
{
\repeat volta 2
{
g, af, bf, c |
d ef f g |
}
}
\break
% Start the div. section here
{
\unfoldRepeats
{
\repeat volta 2
{
g, af, bf, c |
d ef f g | % The end of this line has the extra space
}
}
}
\new Staff
{
\once \override Staff.TimeSignature #'stencil = ##f
\once \override Staff.KeySignature #'break-visibility =
#end-of-line-invisible
\clef bass
\key ef \major
\unfoldRepeats
{
\repeat volta 2
{
g, af, bf, c |
d ef f g |
}
}
}
}
\layout
{
\context
{
\Score
}
}
}
___
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: Hiding an end-of-line cautionary key signature
I've added a new example in the LSR, showing this solution (for version 2.10
it turns out that also the time signature is playing a trick here), see
http://lsr.dsi.unimi.it/LSR/Item?u=1id=325
I also send the corresponding example as a bug report (or feature request).
The setting of Staff.explicitKeySignatureVisibility shouldn't be necessary
in the following example:
\version 2.11.32
\score {
\new StaffGroup \relative c''{
\new Staff
\key f \major
c1 c^Unwanted extra space \break
{ c1 c }
\new Staff {
\key f \major
c1 c
}
c1 c^Fixed here \break
{ c1 c }
\new Staff {
\once \set Staff.explicitKeySignatureVisibility =
#end-of-line-invisible
\key f \major
c1 c
}
}
}
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding an end-of-line cautionary key signature
2007/9/14, Mats Bengtsson [EMAIL PROTECTED]: I've added a new example in the LSR, showing this solution (for version 2.10 it turns out that also the time signature is playing a trick here), see http://lsr.dsi.unimi.it/LSR/Item?u=1id=325 Thanks; approved. Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sans Font for Lilypond texts?
Okay, that works good. I also added
\override StanzaNumber #'font-family = #'sans
for the stanza numbers to be in the same style.
But for consictency I´d like to have some other fonts also being Sans,
e.g. the font of the volta brackets. I couldn´t find something about
it in the manual.
I tried to add
\override VoltaText #'font-family = #'sans
to the above, but it didn´t help.
And is there a way to set the default font for markups to Sans?
Thanks,
Dominic
2007/9/14, Mats Bengtsson [EMAIL PROTECTED]:
If all you want to do is to get a Sans font for lyrics, it's just to
redefine the
corresponding font property. To do this for all Lyrics contexts in your
file,
you can add
\layout{
\context{
\Lyrics
\override LyricText #'font-family = #'sans
}
}
anywhere at the top level of the .ly file.
On the other hand, if you want this specific file, you have to use the
(make-pango-font-tree ...) command, which unfortunately needs to know
the current staff size. One practical way to do it is to remove the line
myStaffSize = #20
from your .ly file and in your .lytex do
\begin[staffsize=11]{lilypond}
\paper{ myStaffSize = #11 }
\include test.ly
\end{lilypond}
If you also want to be able to run the same .ly file standalone, then
you could
make a separate wrapper .ly file that just contains
\paper{ myStaffSize = #20 }
\include test.ly
/Mats
Dominic Neumann wrote:
Hi,
I want to try to have all my lyrics typeset in a Sans font. Therefor
I´ve used a snippet from LSR
(http://lsr.dsi.unimi.it/LSR/Snippet?id=221):
%%% BEGIN OF SNIPPET %%%
\paper {
myStaffSize = #20
#(define fonts
(make-pango-font-tree Bitstream Vera Sans
Nimbus Sans
Luxi Mono
(/ myStaffSize 20)))
}
%%% END OF SNIPPET %%%
I substituted Times New Roman with Bitstream Vera Sans what isn´t a
very good way, I think.
When producing lilypond-output directly with lilypond this works quite
good, but together with lilypond-book the layout is very bad: the
barlines and stems are smaller than they should be to suit the size of
the noteheads.
I produced two simple examples to show what I did:
BEGIN OF PURE LILYPOND-FILE
\version 2.10.29
\paper {
myStaffSize = #20
#(define fonts
(make-pango-font-tree Bitstream Vera Sans
Nimbus Sans
Luxi Mono
(/ myStaffSize 20)))
}
verseOne = \lyricmode {
\set stanza = 1.
test bla blub -- ber
test bla blub -- ber
}
\score {
{
\relative c'' {
\key d \major
\time 2/4
cis4 d | e fis
cis4 d | e fis
\bar |.
}
\addlyrics { \verseOne }
}
}
ENDOF PURE LILYPOND-FILE
BEGIN OF LYTEX-FILE
\documentclass{article}
\begin{document}
\lilypondfile[staffsize=11]{test.ly}
\end{document}
END OF LYTEX-FILE
As you see, I cannot change the Staffsize and everything belonging to
it from within the LyTeX-file. How can I achieve this in another way?
I hope there is a more straight-forward way ...
Thanks, Dominic
PS: It seems that the \sans command only works within \markup
commands. So I cannot say \sans at the beginning of the document to
make everything appear in a Sans font.
___
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
=
--
--
Verlag IT-Dienstleistungen
Dominic Neumann
Lessingstraße 8
09130 Chemnitz
Tel.: 03 71 / 2 83 93 74
eMail: [EMAIL PROTECTED]
Web: http://verlag.dominicneumann.de/
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to make different horizontal spacing for each staff?
Valentin Villenave v.villenave at gmail.com writes:
2007/9/13, Mats Bengtsson mats.bengtsson at ee.kth.se:
I don't understand why you set measurePosition (which tells where the next
note is in the measure). Rather, you could set measureLength
corresponding to
the scaling of the durations that you have applied (ideally that should
be done
automatically by compressMusic, but this doesn't seem to happen now).
Oh yes! I missed the point about the second argument of make-moment
being set to the second argument of compressMusic.
I had tried with measureLength indeed, but since my second argument
was wrong the barlines were messed up, whereas the measurePosition
trick made them disappear.
Indeed compressMusic should configure make-moment as well. I think
this explains #453, which I reported a few days ago.
Anyway, it's in LSR now.
Thanks,
Valentin
Hi Valentin and Mats!
Thanks for help.
This is a part of the composition by Morton Feldman that I am writing:
\include deutsch.ly
#(set-global-staff-size 13)
\layout {
\context { \Score
\remove Timing_translator
\remove Default_bar_line_engraver
}
\context {
\Staff
\consists Timing_translator
\consists Default_bar_line_engraver
}
}
\paper {
#(set-paper-size a3 'landscape)
}
\new Staff {
\clef bass \time 2/4 des2
\time 7/8 r8 des2.
\time 2/2 r4 des2.
\time 5/8 r8 des2
\time 2/4 r8 des4.~
\time 5/8 des4 r8 des4~
\time 2/4 \times 2/3 { des4 r des~ }
\time 7/8 des2. r8
\time 9/8 r8 des1
\time 7/8 r2. c,8~\
\time 5/4 c2 r4\! c2~\
\time 5/8 c8\! r2
\time 2/4 \times 2/3 { r2 c4~\ }
\time 5/8 c4.\! r8 c8~\
\time 3/4 c2.\! \bar |
}
\new Staff {
\time 3/4
\clef treble R2.
R2.
R2.
R2.
R2.^timp.
\clef bass h16 h h h h h h r h h h h
h h h r16 r16 h h h h h h h
r8 r16 h h h h h h h r8
r8 h16 h h h h h h r r8
r16 h h h h h r h h h h h
h h r h h h h h h h r h
h h h h r h h h h r h h
h h h h r h h h h h r h
h h h h r h h h h h h h
r h h h h h h h r8 h16 h
}
There is no need for compressing music as the number of eighth notes in both
staves is the same. The problem is that I would need regular intervals between
the sixteenth notes.
Vít
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: fourth rearrangement
Hi Graham Based on the feedback, it seems that most users would vastly prefer something like this? http://lilypondwiki.tuxfamily.org/index.php?title=Doc I like this layout; the criterion being whether I would look in the right section for the answers to questions. I especially like the new arrangement for vocal music. Two comments of detail: Should 1.4 Staff notation include a subsection on Staff groupings, maybe? Metronome marks currently in 1.4.2 perhaps would be better in the Displaying Rhythms section 1.2.2. This would then permit a rearrangement of subsections 1.4.2 and 1.4.3 to something like 1.4.2 Writing parts + Instrument names + Cue notes + Quoting other voices Do you plan to have links pointing to the substantive section from other sections in which people might look? For example, I might look under 1.2.1 Writing rhythms for grace notes and it would be useful to find there a link saying grace notes are to be found under 1.3.3 Other Expressive marks - For grace notes see Trevor (D) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to make different horizontal spacing for each staff?
2007/9/14, Vít Reichel [EMAIL PROTECTED]: There is no need for compressing music as the number of eighth notes in both staves is the same. The problem is that I would need regular intervals between the sixteenth notes. Oh, I understand now! This is indeed tricky; the Spacing_engraver, and every properties of the SpacingSpanner object, apply to the whole score, no matter where you put it. I have no idea how to solve this. Hopefully someone will have one. Regards, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to make different horizontal spacing for each staff?
Valentin Villenave wrote: 2007/9/14, Vít Reichel [EMAIL PROTECTED]: There is no need for compressing music as the number of eighth notes in both staves is the same. The problem is that I would need regular intervals between the sixteenth notes. Oh, I understand now! This is indeed tricky; the Spacing_engraver, and every properties of the SpacingSpanner object, apply to the whole score, no matter where you put it. Actually, I don't understand exactly what you are asking for. If you want the 16th notes regularly spaced, read the two sections on Proportional notation in the manual. At the bottom of the second of these two (Sect. 11.6.5), you will also find settings that makes it possible for LilyPond to insert more line breaks, which seems to be another problem in your current score. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sans Font for Lilypond texts?
Dominic Neumann wrote: Okay, that works good. I also added \override StanzaNumber #'font-family = #'sans for the stanza numbers to be in the same style. But for consictency I´d like to have some other fonts also being Sans, e.g. the font of the volta brackets. I couldn´t find something about it in the manual. I tried to add \override VoltaText #'font-family = #'sans to the above, but it didn´t help. And is there a way to set the default font for markups to Sans? I think it's time for you to read section 9.3 The \override command in the manual, which tells you how to find this information yourself. For the volta brackets, the relevant link to the program reference is found in section VoltaBracket. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to make different horizontal spacing for each staff?
Mats Bengtsson mats.bengtsson at ee.kth.se writes: Actually, I don't understand exactly what you are asking for. If you want the 16th notes regularly spaced, read the two sections on Proportional notation in the manual. At the bottom of the second of these two (Sect. 11.6.5), you will also find settings that makes it possible for LilyPond to insert more line breaks, which seems to be another problem in your current score. /Mats I want the top staff to stay exactly the way it is now and for the bottom staff, make a completly independent spacing so that the sixteenth notes would be spaced more ragularly. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sans Font for Lilypond texts?
Thank you for you hint. I´ve read section 9.3 and also found the program-reference. But in VoltaBracket I couln´t find a property to set to font(-family). I only found the font-encoding property, but this doesn´t help me by now. In the manual (8.1.7. Font selection) is written: font-encoding is a symbol that sets layout of the glyphs. This should only be set to select di?erent types of non-text fonts, e.g. So I cannot/shouldn´t use it for what I want!? Can you please give me another hint? Or is it not possible to change the default font for VoltaBracket and I have to play around with \markups? Dominic 2007/9/14, Mats Bengtsson [EMAIL PROTECTED]: Dominic Neumann wrote: Okay, that works good. I also added \override StanzaNumber #'font-family = #'sans for the stanza numbers to be in the same style. But for consictency I´d like to have some other fonts also being Sans, e.g. the font of the volta brackets. I couldn´t find something about it in the manual. I tried to add \override VoltaText #'font-family = #'sans to the above, but it didn´t help. And is there a way to set the default font for markups to Sans? I think it's time for you to read section 9.3 The \override command in the manual, which tells you how to find this information yourself. For the volta brackets, the relevant link to the program reference is found in section VoltaBracket. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sans Font for Lilypond texts?
Dominic Neumann wrote: Thank you for you hint. I´ve read section 9.3 and also found the program-reference. But in VoltaBracket I couln´t find a property to set to font(-family). I only found the font-encoding property, but this doesn´t help me by now. The list of properties only shows the properties that are set by default, so it's not an exhaustive list. To see all available properties, you have to browse through all the links to different interfaces at the bottom. In your case, it's the font-interface that's relevant. There, you can see that the font-family property is available. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sans Font for Lilypond texts?
Hi Mats: The list of properties only shows the properties that are set by default, so it's not an exhaustive list. To see all available properties, you have to browse through all the links to different interfaces at the bottom. More proof of the need for a full list, as we've been discussing... ;-) We really shouldn't have to keep saying this kind of thing on the list: such questions should be answered by the docs, if possible. Best regards, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: can't generate pdf file
The most likely problem is that you have managed to enter something in your file that does not follow the syntax, so that LilyPond gets confused. Do you get any xxx.log file (assuming that your input file was called xxx.ly)? In that case, you will hopefully get some hints in it on what's wrong. Another common problem if you use Notepad in Windows is that it has saved the file with a double suffix, like myfile.ly.txt. This is one of the reasons that it's better to use the text editor that's started when you just double click on the LilyPond icon. For future usage questions, please use the lilypond-user mailing list and reserve bug-lilypond for pure bug reports. I have already redirected this mailing thread to lilypond-user (make sure to click Reply All if you followup this email). If you can't solve the problem yourself, please include a copy of your .ly file when you send the question to the mailing list. /Mats Nicholas Dominguez wrote: I had no trouble the first day generating a file according to the instructions. I'm using Windows XP. Now I am unable to generate a file when I drag/drop or double click on the .ly file I've created in Notepad. help! Nick ___ bug-lilypond mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-lilypond -- = 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
GDP: fifth arrangement
http://lilypondwiki.tuxfamily.org/index.php?title=Doc General notes: - we're only dealing with the Notation Reference now. I want to get this finalized so we can start the real work, so things like Titles / page formatting / changing defaults / etc will be dealt with later. - stuff from the old instrument-notation will be dealt with as we come to them in GDP - The most important... the only important... stuff right now is to have material in the right sections, and ideally have stuff in the right subsections for the non-instrument notations. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: fifth arrangement
On 9/14/07, Graham Percival [EMAIL PROTECTED] wrote: http://lilypondwiki.tuxfamily.org/index.php?title=Doc General notes: - we're only dealing with the Notation Reference now. I want to get this finalized so we can start the real work, so things like Titles / page formatting / changing defaults / etc will be dealt with later. - stuff from the old instrument-notation will be dealt with as we come to them in GDP - The most important... the only important... stuff right now is to have material in the right sections, and ideally have stuff in the right subsections for the non-instrument notations. How about 1.11 Rhythmic music -- 1.11 Percussion? Rhythmic music makes me want to go salsa dancing ... -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: fifth arrangement
On 9/14/07, Trevor Bača [EMAIL PROTECTED] wrote: On 9/14/07, Graham Percival [EMAIL PROTECTED] wrote: http://lilypondwiki.tuxfamily.org/index.php?title=Doc General notes: - we're only dealing with the Notation Reference now. I want to get this finalized so we can start the real work, so things like Titles / page formatting / changing defaults / etc will be dealt with later. - stuff from the old instrument-notation will be dealt with as we come to them in GDP - The most important... the only important... stuff right now is to have material in the right sections, and ideally have stuff in the right subsections for the non-instrument notations. How about 1.11 Rhythmic music -- 1.11 Percussion? Rhythmic music makes me want to go salsa dancing ... 1.1 through 1.7 is looking very solid. How about this slight reshuffling for the second box? o 1.8 Chord names o 1.9 Piano music o 1.10 Percussion o 1.11 Guitar o 1.12 Other instrument-specific notation o 1.14 Ancient notation o 1.15 Vocal music (Primary motivation is to pull Chord names out of the sequence [Piano music - Percussion - Guitar - Other instr], which makes a strong cognitive block IMO.) -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Half a \prall
Is is possible to produce a \prall and a \mordent, but with only one wave (one peak and one valley). The idea is to notate a special ornament similar to these, but where the speed does not admit the terminating note of a Pralltriller or mordent (used in Bulgarian music). Hans Aberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Half a \prall
These symbols correspond to one symbol each in the LilyPond font, so I'm afraid you would have to use some trick with \markup to draw a white area on top of half the symbol. Similar tricks have been described several times on the mailing list (and I think there are examples in LSR). /Mats Hans Aberg wrote: Is is possible to produce a \prall and a \mordent, but with only one wave (one peak and one valley). The idea is to notate a special ornament similar to these, but where the speed does not admit the terminating note of a Pralltriller or mordent (used in Bulgarian music). Hans Aberg ___ 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
individually-coloured staff line possible?
Hello-
I would really appreciate any ideas anyone has on this problem.
Is there a way of making a 5-line, treble-clef staff, with the middle line
(i.e. the B line) individually coloured in red? Here's what I have sofar but
I'm a bit stuck: (I'm only newly converted to lilypond!)
% single-line red staff:
Boo = \relative c'' {
\override Staff.StaffSymbol #'color = #red \override Staff.StaffSymbol
#'line-count = 1
c4
}
% normal 5-line staff:
Hoo = \relative c''
{s2 e4}
{
% tried to superimpose red 1-line staff onto normal black, but they're not
see-through
\override VerticalAlignment #'forced-distance = #0
\Boo \Hoo
}
--
View this message in context:
http://www.nabble.com/individually-coloured-staff-line-possible--tf4441889.html#a12673355
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
GDP: six
http://lilypondwiki.tuxfamily.org/index.php?title=Doc ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: fourth rearrangement
Trevor Daniels wrote: Do you plan to have links pointing to the substantive section from other sections in which people might look? For example, I might look under 1.2.1 Writing rhythms for grace notes and it would be useful to find there a link saying grace notes are to be found under 1.3.3 Other Expressive marks - For grace notes see Yes, of course; many links like that are planned. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: six
Just for the record: Ancient notation _could_ be split genre-wise into two separate chunks Gregorian Chant and Mensural Notation. However, for a _reference_ manual, I think it is ok as it currently is (e.g. having a single section on ligatures rather than separate ones per genre). For a _tutorial_, however, IMO you definitely would like to split it genre-wise. Greetings, Juergen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: fourth rearrangement
Mats Bengtsson wrote:
- You have a much better feeling for the English language than I do, but
do you think that we should keep the current mixture of staff and
stave
to denote the same thing, for example in the subsection titles within
Staff notation?
No; we should use staff and staves. One of the instructions for the
Trivial/Easy will be to fix any such mistakes.
I think I wrote when dealing with multiple @internalsref{Staff}s, you
can..., but such phrases should be rephrased to multiple @{Staff}
contexts.
- How about adding some section like Other typesetting features, which
could
contain things that don't really fit in anywhere else, like the four I
mentioned above.
I've expanded the Education section to include all of these things. I'm
not wild about the name Education, but I think all these items work
well inside that section (whatever we name the section).
- Again, I might not have the right intuition for English language, but
how about
replacing Text in a score with something along the lines of Textual
annotations
I would also move New dynamic marks from 1.17.2 to 1.17.1.
To match other subsection titles, I called it Writing text.
- Why doesn't Text markup commands belong under 1.17.2 Text markup?
As Valentin said; the markup commands are even more of a reference.
Hmm... actually, what about moving these into an Appendix?
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: six
Le 14.09.2007 17:23, Graham Percival disait : http://lilypondwiki.tuxfamily.org/index.php?title=Doc Sounds very promising. I like this progressive discovery. Just one question: due to the alignement and their timing effect, wouldn't it be judicious to move the grace notes to the 1.2.6 Special rhythmic concerns, at least through a link? Cheers, Jean-Charles ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: fourth rearrangement
2007/9/14, Graham Percival [EMAIL PROTECTED]: As Valentin said; the markup commands are even more of a reference. Hmm... actually, what about moving these into an Appendix? Agreed, but if we do, we'll have to improve the actual markup manual section, so that users only exceptionally have to digg into these lists (as it is now, I almost have to browse them twice a day). When it's time, I can write this part of the GDP if none else wants to. Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: fourth rearrangement
Valentin Villenave wrote: 2007/9/14, Graham Percival [EMAIL PROTECTED]: As Valentin said; the markup commands are even more of a reference. Hmm... actually, what about moving these into an Appendix? Agreed, but if we do, we'll have to improve the actual markup manual section, so that users only exceptionally have to digg into these lists (as it is now, I almost have to browse them twice a day). When it's time, I can write this part of the GDP if none else wants to. Err... why? What's the difference between looking at a list of markup commands in section 8.1.8 or 1.8.3 or Appendix M ? I mean, yes, we plan on improving all sections of the manual, but why single out the list of markup commands? Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: six
Jean-Charles Malahieude wrote: Just one question: due to the alignement and their timing effect, wouldn't it be judicious to move the grace notes to the 1.2.6 Special rhythmic concerns, at least through a link? Of course we'll have @seealso links everywhere in the manual. That's not a concern. That said, the timing effect argument has convinced me, so I moved grace notes into 1.2.6. Besides, I like having grace notes inside a subsection called special rhythmic concerns. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Half a \prall
I discovered they can be produced using Unicode U+1D19D for the half Pralltriller, and adding U+1D1A0 for the half mordent. So the question becomes: Can ornaments like \prall be created using Unicode characters? Hans Aberg On 14 Sep 2007, at 17:08, Mats Bengtsson wrote: These symbols correspond to one symbol each in the LilyPond font, so I'm afraid you would have to use some trick with \markup to draw a white area on top of half the symbol. Similar tricks have been described several times on the mailing list (and I think there are examples in LSR). /Mats Hans Aberg wrote: Is is possible to produce a \prall and a \mordent, but with only one wave (one peak and one valley). The idea is to notate a special ornament similar to these, but where the speed does not admit the terminating note of a Pralltriller or mordent (used in Bulgarian music). Hans Aberg ___ 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: GDP: fourth rearrangement
On 9/14/07, Graham Percival [EMAIL PROTECTED] wrote: Mats Bengtsson wrote: - You have a much better feeling for the English language than I do, but do you think that we should keep the current mixture of staff and stave to denote the same thing, for example in the subsection titles within Staff notation? No; we should use staff and staves. One of the instructions for the Trivial/Easy will be to fix any such mistakes. Hmm... I'm detecting a distinctly American bias here. I wonder whether there's space for a Queen's English translation. ;) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: six
2007/9/14, Juergen Reuter [EMAIL PROTECTED]: Ancient notation _could_ be split genre-wise into two separate chunks Gregorian Chant and Mensural Notation. However, for a _reference_ manual, I think it is ok as it currently is (e.g. having a single section on ligatures rather than separate ones per genre). For a _tutorial_, however, IMO you definitely would like to split it genre-wise. I would be OK to split the Ancient notation. Thanks for suggesting, btw; feel free to suggest any other improvement you might think of, since this whole part would otherwise remain more or less untouched -- as most of us, when it comes to such subjects, are complete ignoramuses ;) Regards, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: fourth rearrangement
Neil Puttock wrote: On 9/14/07, *Graham Percival* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: No; we should use staff and staves. One of the instructions for the Trivial/Easy will be to fix any such mistakes. Hmm... I'm detecting a distinctly American bias here. As a Canadian, I always try to write good English, not that other language. Other than -ise. -ize looks much cooler, since it has a z in it. :) I wonder whether there's space for a Queen's English translation. ;) Really? Do people across the pond say staffs ? It sounds like the kind of thing an American would come up with. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: fourth rearrangement
2007/9/14, Graham Percival [EMAIL PROTECTED]: Err... why? What's the difference between looking at a list of markup commands in section 8.1.8 or 1.8.3 or Appendix M ? There's none. Appendix aren't meant to contain daily vital stuff, that's all :) I mean, yes, we plan on improving all sections of the manual, but why single out the list of markup commands? I was mostly thinking out loud: Oh; I musn't forget to write at last decent documentation for all these commands that have been making me tear my hair out for months... Btw: every notation software I've ever outthere used uses staff/staves. As for the US/UK debates, Ian raised something about bars/measures on http://lilypondwiki.tuxfamily.org/index.php?title=Talk:Doc maybe you guys could go arguing there as well ;) Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: fourth rearrangement
On 9/14/07, Graham Percival [EMAIL PROTECTED] wrote: Neil Puttock wrote: On 9/14/07, *Graham Percival* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: No; we should use staff and staves. One of the instructions for the Trivial/Easy will be to fix any such mistakes. Hmm... I'm detecting a distinctly American bias here. As a Canadian, I always try to write good English, not that other language. Other than -ise. -ize looks much cooler, since it has a z in it. :) I do apologize; I shouldn't make assumptions. I don't have any beef with -ize; if it's good enough for the OED, it's fine by me. I wonder whether there's space for a Queen's English translation. ;) Really? Do people across the pond say staffs ? It sounds like the kind of thing an American would come up with. In the UK, we say stave/staves. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: six
Valentin Villenave wrote: 2007/9/14, Juergen Reuter [EMAIL PROTECTED]: Ancient notation _could_ be split genre-wise into two separate chunks Gregorian Chant and Mensural Notation. However, for a _reference_ manual, I think it is ok as it currently is (e.g. having a single section on ligatures rather than separate ones per genre). For a _tutorial_, however, IMO you definitely would like to split it genre-wise. I would be OK to split the Ancient notation. Thanks for suggesting, btw; feel free to suggest any other improvement you might think of, since this whole part would otherwise remain more or less untouched -- as most of us, when it comes to such subjects, are complete ignoramuses ;) Actually, I'd rather leave Ancient notation completely untouched until somebody knowledgeable about it has the time to deal with it. (that doesn't just mean Juergen; there's other people around that use this) In any case, I think it's safe to leave it alone until GDP would naturally get to that section -- that will probably be in Dec or Jan. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: fourth rearrangement
Valentin Villenave wrote: 2007/9/14, Graham Percival [EMAIL PROTECTED]: Err... why? What's the difference between looking at a list of markup commands in section 8.1.8 or 1.8.3 or Appendix M ? There's none. Appendix aren't meant to contain daily vital stuff, that's all :) What, like a list of all Feta font characters, or notehead styles, or colours? This is totally something for appendix C. As for the US/UK debates, Ian raised something about bars/measures on http://lilypondwiki.tuxfamily.org/index.php?title=Talk:Doc maybe you guys could go arguing there as well ;) I've left a message on that page, but I'll repeat it here: please keep discussion about the docs on the mailist. I think it's important that there's a single place to discuss this stuff. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hiding an end-of-line cautionary key signature
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=471
Cheers,
- Graham
Mats Bengtsson wrote:
I've added a new example in the LSR, showing this solution (for version
2.10
it turns out that also the time signature is playing a trick here), see
http://lsr.dsi.unimi.it/LSR/Item?u=1id=325
I also send the corresponding example as a bug report (or feature request).
The setting of Staff.explicitKeySignatureVisibility shouldn't be necessary
in the following example:
\version 2.11.32
\score {
\new StaffGroup \relative c''{
\new Staff
\key f \major
c1 c^Unwanted extra space \break
{ c1 c }
\new Staff {
\key f \major
c1 c
}
c1 c^Fixed here \break
{ c1 c }
\new Staff {
\once \set Staff.explicitKeySignatureVisibility =
#end-of-line-invisible
\key f \major
c1 c
}
}
}
/Mats
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: six
On 14.09.2007 (08:23), Graham Percival wrote: http://lilypondwiki.tuxfamily.org/index.php?title=Doc * 1 Notation Reference o 1.1 Pitches I don't like the sectioning of this one. Why is Transpose and Instrument transpositions split up? It doesn't make sense to me. Ottava brackets should also belong here somewhere. Also, Changing multiple pitches -- it sounds precise, but it isn't necessarily so. At least it sounds unnecessarily complex Join Note names in other languages with Writing pitches - that's where it belongs. That leaves Clef and Key signature, which might come first -- since it's fairly fundamental -- or last, since it falls a little on the side of the other items. Thus: o 1.1 Pitches + Clef + Key signature + Normal pitches + Note names in other languages + Accidentals + Cautionary accidentals + Micro tones + Relative octaves/Octave check + Transpositions + Ottava brackets o 1.4 Repeats + Repeats and MIDI I wonder: isn't it more natural to gather the midi stuff in one place and just have a cross reference here? After all, the page looks the same regardless of what the midi output sounds like; the person who is likely to need this information, will have trouble with his midi file and will be looking for it in the midi section, not primarily under repeats. At least I would. I did. o 1.7 Educational use (or increasing readibility ?) I don't like this one, I must say. Neither font size, improvisation, or shape notes or fingering have much to do with educational use in my book. I think font size should go in a page layout section or something (at least that's how I use it, but I can also see how it would fit here). The sections are ok, I guess, but please don't call it all educational use... How about Appearance Tweaks or something? o 1.15 Ancient notation I have no problem with this section -- and it is my area. Eyolf -- Brandy-and-water spoils two good things. -- Charles Lamb ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: six
Eyolf Østrem wrote:
On 14.09.2007 (08:23), Graham Percival wrote:
http://lilypondwiki.tuxfamily.org/index.php?title=Doc
* 1 Notation Reference
o 1.1 Pitches
I don't like the sectioning of this one. Why is Transpose and
Instrument transpositions split up? It doesn't make sense to me.
Ottava brackets should also belong here somewhere.
Instrument transpositions affects how pitches are displayed in cues and
on midi. Ottava displays how pitches are displayed.
Transpose affects the actual _pitches_. Remember our distinction
between content and presentation.
{ fis''' }
is that note, regardless of instrument transpositions or ottava. If we
stick \transpose, then fis''' will produce a different pitch.
Also, Changing multiple pitches -- it sounds precise, but it isn't
necessarily so. At least it sounds unnecessarily complex
I'm not wild about that name; please suggest an alternative.
Join Note names in other languages with Writing pitches - that's
where it belongs.
Note names in other languages _is_ in writing pitches.
That leaves Clef and Key signature, which might come first -- since
it's fairly fundamental -- or last, since it falls a little on the
side of the other items. Thus:
Again, these clearly affect the way we _display_ pitches, not the actual
_pitches_ themselves.
+ Repeats and MIDI
I wonder: isn't it more natural to gather the midi stuff in one place
and just have a cross reference here?
Repeats is slated for a huge rewrite anyway. I have no objection
whatsoever to removing this subsection and putting in a link. But
please raise this issue again when we come to Repeats (probably in 5 or
6 weeks), since I have many other issues to keep track of.
o 1.7 Educational use (or increasing readibility ?)
I don't like this one, I must say. Neither font size, improvisation,
or shape notes or fingering have much to do with educational use in my
book.
They make the music easier to read. Again, I'm not wild about the
section name, as you can tell from the (?) in the name.
I think font size should go in a page layout section or something (at
least that's how I use it, but I can also see how it would fit here).
The sections are ok, I guess, but please don't call it all educational
use... How about Appearance Tweaks or something?
hmm... I'd rather avoid the term tweaks, since we use that elsewhere
to mean \override stuff. Modifying appearance for legibility is too long.
(whoops, notation font size should go in inside the staff. fixed.)
I'm quite happy with having a section that includes those subsections,
but I'm seriously stumped as to what to call it.
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: six
2007/9/14, Graham Percival [EMAIL PROTECTED]: o 1.7 Educational use (or increasing readibility ?) They make the music easier to read. Again, I'm not wild about the section name, as you can tell from the (?) in the name. I'm quite happy with having a section that includes those subsections, but I'm seriously stumped as to what to call it. Some time ago, I had proposed Special effects, which was both fun and attractive -- John seemed to like it. However, Educational use is absolutely fine. I've seen many reactions here, these past few days, which I honestly couldn't understand at all (when people ranted against such terms as decorating, educational, or Rune's idea of a funny, childish logo). I mean: come on! Wasn't any of you guys a kid once? Why should music be *serious*stuff, and nothing else? Let me rephrase: LilyPond *is* perfect for educational purposes. Face it, once and for all. Playing with noteheads, staves appearance etc is *great* for having fun when reading music, learning solfege, etc. I'm speaking as a teacher (I work with both kids and grown-ups, sometimes in the same room at the same time), but also as a former kid myself. Sure, these notation effects are not reserved to education, as you said Eyolf. You use some of them in your book, so do I in my opera, and so on. But I think this would be a mistake to somehow hide the wonderful educational resources of LilyPond, and I surely hope that nobody here is trying to. Just some thoughts that I wanted to share with you. Regards, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sans Font for Lilypond texts?
2007/9/14, Mats Bengtsson [EMAIL PROTECTED]:
Dominic Neumann wrote:
Thank you for you hint. I´ve read section 9.3 and also found the
program-reference.
But in VoltaBracket I couln´t find a property to set to font(-family).
I only found the font-encoding property, but this doesn´t help me by
now.
The list of properties only shows the properties that are set by
default, so
it's not an exhaustive list. To see all available properties, you have
to browse
through all the links to different interfaces at the bottom. In your
case, it's
the font-interface that's relevant. There, you can see that the
font-family property
is available.
/Mats
I didn´t know that. But I´ve tried the font-family thing without any
success. Here you can see a sample ly-file:
%%% START %%%
\version 2.10.29
harmonies = {
\chordmode {
c1 d c d
}
}
\score {
{
\new ChordNames \with {
voltaOnThisStaff = ##t
\consists Bar_engraver
\override VoltaBracket #'minimum-space = #2.2
\override VoltaBracket #'font-family = #'sans
} { \harmonies }
\new Staff \with {
voltaOnThisStaff = ##f
}
\relative c' {
\key c \major
\time 4/4
\repeat volta 2 {
c4 e g e | d fis a fis |
}
\alternative {
{ c4 e g e }
{ d4 fis a fis }
}
\bar |.
}
}
\layout {
indent = #0
\context {
\Score
\remove Bar_number_engraver
}
\context {
\Lyrics
\override LyricText #'font-family = #'sans
\override StanzaNumber #'font-family = #'sans
}
}
}
%%% END %%%
The font of the volta bracket numbers is still the old one. What am I
doing wrong?
Dominic
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: six
On 14.09.2007 (13:10), Graham Percival wrote:
Eyolf Østrem wrote:
I don't like the sectioning of this one. Why is Transpose and
Instrument transpositions split up? It doesn't make sense to me.
Ottava brackets should also belong here somewhere.
Instrument transpositions affects how pitches are displayed in cues and on
midi. Ottava displays how pitches are displayed.
Transpose affects the actual _pitches_. Remember our distinction between
content and presentation.
{ fis''' }
is that note, regardless of instrument transpositions or ottava. If we
stick \transpose, then fis''' will produce a different pitch.
Yes, but where are people going to be looking for it? Better to have
it under the same heading and explain that distinction there, instead
of having them scurrying from place to place between technically
distinct but conceptually related items.
Also, Changing multiple pitches -- it sounds precise, but it isn't
necessarily so. At least it sounds unnecessarily complex
I'm not wild about that name; please suggest an alternative.
My suggestion is (a) to let go of that level of sectioning, or (b) if
that isn't viable, call that section octaves and transposition or
something.
Join Note names in other languages with Writing pitches - that's
where it belongs.
Note names in other languages _is_ in writing pitches.
Sorry, I meant Normal pitches -- to a spaniard, si IS the normal
pitch, that's what I was getting at.
That leaves Clef and Key signature, which might come first -- since
it's fairly fundamental -- or last, since it falls a little on the
side of the other items. Thus:
Again, these clearly affect the way we _display_ pitches, not the actual
_pitches_ themselves.
To me, this borders on the level of technicalities. Much as I
appreciate the absolute pitch approach of Lilypond, I'm not so sure if
it enhances the usability of the manual to enforce that distinction in
how the material is presented. After all, cis IS not the actual
pitch itself either, it's some letters that are used to *represent*
(sounding) pitches in a different (written) notation.
But these theoretical issues apart, my main concern is with what to
me appears as unnecessary fragmentation. Then again, it's no hanging
matter.
+ Repeats and MIDI
I wonder: isn't it more natural to gather the midi stuff in one place
and just have a cross reference here?
Repeats is slated for a huge rewrite anyway. I have no objection
whatsoever to removing this subsection and putting in a link. But please
raise this issue again when we come to Repeats (probably in 5 or 6
weeks), since I have many other issues to keep track of.
OK.
o 1.7 Educational use (or increasing readibility ?)
I don't like this one, I must say. Neither font size, improvisation,
or shape notes or fingering have much to do with educational use in my
book.
They make the music easier to read.
Shape notes is not only about making it easier to read, is it? It's
closer to a notational system of its own. The affinities with
solmization are strong, and even though that too had an educational
function, it went way beyond that.
Fingering: sure, it's educational too, but again, I wouldn't have
thought of looking for it there. How about in the instrument section
somewhere?
Again, I'm not wild about the section
name, as you can tell from the (?) in the name.
I think font size should go in a page layout section or something (at
least that's how I use it, but I can also see how it would fit here).
The sections are ok, I guess, but please don't call it all educational
use... How about Appearance Tweaks or something?
hmm... I'd rather avoid the term tweaks, since we use that elsewhere to
mean \override stuff. Modifying appearance for legibility is too long.
What if one drops for legibility (since there can be many other
reasons to modify the appearance) and call it modifying appearance?
Eyolf
--
Debian is the Jedi operating system: Always two there are, a master and
an apprentice.
-- Simon Richter on debian-devel
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volta with text snippet needs font correcting
Date: Tue, 11 Sep 2007 15:56:32 +0200 From: Reinhold Kainhofer [EMAIL PROTECTED] Subject: Re: Volta with text snippet needs font correcting To: lilypond-user@gnu.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 Am Dienstag, 11. September 2007 schrieb Valentin Villenave: Hello everybody, I don't know who has sent the following snippet, but there seems to be a bug with fonts in it: http://lsr.dsi.unimi.it/LSR/Item?u=1id=317 If the author of the original snippet can correct it, it would be great; otherwise, anyone can feel free to post the correct input in this mailinglist thread. Isn't this one of the purposes of the snippet: By default the volta brackets seem to use the dynamics font, which has letters for p, r, f, s, z, m etc., while all other letters look different. Thus one needs to set the font of the volta bracket text manually, which is shown in the second score in the snippet (which is unfortunately not shown in LSR...). The PDF from the whole snippet is attached to see the difference. Maybe the description of the snippet should be extended to explain this (and the snippet itself could use some comments as to the purpose of the settings). Cheers, Reinhold This was my first effort to post a snippet after searching for solutions to the various formatting issues. I've gone over it again and would appreciate any further comments. Cheers, Perry ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: six
Shape notes is not only about making it easier to read, is it? It's closer to a notational system of its own. The affinities with solmization are strong, and even though that too had an educational function, it went way beyond that. Fingering: sure, it's educational too, but again, I wouldn't have thought of looking for it there. How about in the instrument section somewhere? What about Editorial Notation Additions? Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Volta with text snippet needs font correcting
2007/9/15, Perry Gilfillan [EMAIL PROTECTED]:
This was my first effort to post a snippet after searching for
solutions to the various formatting issues. I've gone over it again
and would appreciate any further comments.
Great to hear from you Perry :)
It's perfect. Your snippet was already fine, by the way. (You posted
it twice but I removed one of those.)
I just couldn't understand what it was precisely about, since the font
change didn't work on my computer, and wasn't displayed by the LSR.
LSR's LilyPond is running in jail mode (in a small dedicated
partition, for security reasons). This makes impossible to use some
features, and you have to put only one \score block (the others will
be ignored). When writing a two-lines snippet, it is recommended to
use \break instead, like you've done.
Some local control freaks (just to see if he'll recognize himself ;)
tend to prefer continuative forms titles, e.g. adding text to volta
brackets instead of volta with text. Since your title made sense,
this is no big deal (not to me, at least).
Since i'm kind of a control freak myself, I would recommend not to use
OS-specific proprietary fonts such as Arial. But this is pure hair
splitting.
Generally, it's not recommended to add a \version number in LSR
snippets. They're supposed to be always corresponding to the last
stable version (currently, 2.10).
Your snippet demonstrates a feature for which the syntax has changed
in 2.11; therefore it will get broken when the LSR will be running the
next stable 2.12 version, which is to be released soon. Theorically,
convert-ly should handle it, and I plan to check all the snippets for
broken code, but in such a case you can already help when writing your
snippet, by:
-adding a few words in your Subject:
Subject of your snippet [needs syntax update]
-adding the new syntax (if you know it) in the snippet, commenting it
with some explanation:
\score {
a2. b4 c8 d e'
%% please uncomment the following line when running 2.12
% \override Staff.FooBar #'baz = ##t
\override Staff.Foobar #'some-deprecated-property = #'( bar . foo)
c d e
}
This helps users as well, since you give them explanations about how
to make it work with new versions.
Of course, this isn't mandatory at all. Your snippet was already great
(btw, thank you for using HTML in the desciption, it's much easier to
read than plain text). I hope you'll get used to add anything
interesting you can think of; this is how LSR becomes each day more
and more useful!
Regards,
Valentin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
