Ack: Still: fingering in chords
On Wed, 5 Mar 2003, Han-Wen Nienhuys wrote:
A form of fingering is supported in lily 1.7 -- see
http://lilypond.org/development/input/regression/out-www/regression.html
,
finger-chords.ly
Thank you! Meanwhile I'm aware of the fact that LilyPond can
show the numbers as Up- and Down-text. My question was because some
users requested fingering in NoteEdit and this is suggestive
iff the destination systems support fingering.
But I want to use this occasion to point to a more serious
problem (I know I already did it, but I don't get tired to
remember):
It is not possible to tie only a subset of a chord:
e2 ~ g c ~e g c (extended syntax)
I know you default answer is: Split it into voices!
But this is a great effort for such a small request.
Furthermore: Think about how far away the g is
from c and e although it belongs to the same chord.
And it is not connected to the same stem. Ok, this last
statement could be wrong. In *my* solution it is not
connected to the same stem:
\include paper20.ly
violinA = \notes\relative c' { \voiceOne
\clef violin
e2 c' ~ e c'
\bar |.
}
violinB = \notes\relative c' { \voiceTwo g'2 g }
Violin =
\context Voice=ViolinA \violinA
\context Voice=ViolinB \violinB
\score {
\context Staff=violin \Violin
}
--
J.Anders, Chemnitz, GERMANY ([EMAIL PROTECTED])
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Ack: Still: fingering in chords
On Wed, 5 Mar 2003, Han-Wen Nienhuys wrote: I think it is the proper solution. For example, the difference between (pseudo-syntax) Hmm! I know from my own programming: It is a problem to change such fundmental things. But how would you transcribe this ? (Note this can happen frequently in obligato (strings) parts in light music): c1 ~ e ~ g | c ~ e ~ a |c d ~ f ~ a | d f g ~ b | c ~ e g | c d fis! a | c~ e g~ c e g and c~ e~ g~ c e g is very small, and likely to be unnoticed. Separate voices are much clearer. -- J.Anders, Chemnitz, GERMANY ([EMAIL PROTECTED]) ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Ok forget this mail ...
On Wed, 5 Mar 2003, Joerg Anders wrote: But how would you transcribe this ? obligato (strings) parts in light music): c1 ~ e ~ g | c ~ e ~ a |c d ~ f ~ a | d f g ~ b | c ~ e g | c d fis! a | Ok forget this mail, I konw the answer: c1 e g ~ | c e a ~ |c d f a ~ | d f g b ~ | c e g ~ | c d fis! a -- J.Anders, Chemnitz, GERMANY ([EMAIL PROTECTED]) ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Ack: Still: fingering in chords
[EMAIL PROTECTED] writes:
On Wed, 5 Mar 2003, Han-Wen Nienhuys wrote:
I think it is the proper solution. For example, the difference between
(pseudo-syntax)
Hmm! I know from my own programming: It is a problem to change such fundmental
things.
It can already be done, see below. I don't think it is a good idea to
export this kind of trickery by default, though.
\header {
texidoc = Tieing only parts of chords is possible. It requires
putting the Tie engraver at Thread level, and redirecting untied notes
to a different thread.
}
\version 1.7.13
\score {
\notes \context Thread \relative c' {
c-~ e \context Thread = untied c'
c e c'
}
%% comment out New_tie_engraver for lily 1.6
\paper {
\translator {
\ThreadContext
\consists Tie_engraver
\consists New_tie_engraver
}
\translator { \VoiceContext
\remove Tie_engraver
\remove New_tie_engraver
}
}}
%% new-chords-done %%
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Mixing notehead sizes in a 'chord'?
I'm not really up to date with the latest features in the 1.7.x
releases, but at least for earlier versions, the solution used to
be to make separate Thread contexts for the different note heads.
The example file input/regression/note-head-style.ly ends with
an example of how this can be done. However, when looking at the
output of this example in the document
http://lilypond.org/development/input/regression/out-www/regression.html
this particular output line of the example seems to be missing, I don't
understand why.
/Mats
Hans Forbrich wrote:
In the piece I'm working - SATB + Piano - the Tenors have 'alternate'
notes which are designated by a reduced notehead size. Since IMHO these
are 'one voice', ideally these alternates could be represented (Lily
1.7.13) as
c \tiny a \normfontsize 4.-( e \tiny c \normfontsize 8-)
However, trying this I find that all noteheads in a chord become the
same size.
A second variant would be to create 2 voices ... (which should also
allow separate slurs/ties for each pair - also needed, but probably a
separate question)
{c4.-( e8-) } \\ { \stemUp \slurUp \tiny a4.-( c8-) }
This seem to work some of the time, but occasionally the stems get out
of alignment. More accurately, the alignment of the tiny normal
noteheads is on the 'front' of the grob which, when stems are up, causes
the tiny and the normal stems to both be visible. (Making stems
transparent results in a gap between the tiny notehead the 'master'
stem, therefore not acceptable.)
Related questions:
1) Any hope of getting mixed notehead sizes in a chord sometime?
1a) If it's there now, how do I do this? (What did I overlook?)
--- or ---
2) How can I use 'stem-based' notehead alignment or nudge the tiny notes
to line up with the stems of the normal font?
Advice, corrections, pointers to appropriate doc, etc. appreciated.
/Hans
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.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
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Q on Lilybook - mixing notes and text
lilypond-book is pretty good at mixing lilypond music with tex (or Latex) text. However, it forces one to learn how to use (in my case) Latex, and it operates within the constraints of Latex. Latex requires some getting used to, though. It certainly is not your ordinary WYSIWYG word processor: it's a completely different, but very powerful animal. The not so Short Introduction to LaTeX at http://www.ctan.org/tex-archive/info/lshort/english/ is a decent primer to Latex. Hope this helps. Oscar ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Fontsize change when setting cue notes
[EMAIL PROTECTED] writes:
In the middle of a voice I have the following:
{)gs2 s2 | s1}
\context Voice = cue {
\property Staff.fontSize = #-1
\property Voice.Stem \override #'length = #5.5
\property Voice.Beam \override #'thickness = #0.384
\property Voice.Beam \override #'space-function =
#(lambda (beam mult) (* 0.8 (Beam::space_function beam mult)))
s4 e'2 e4 | e f e d
\property Staff.fontSize\unset
} |
The G-sharp gets set in the small font. Is there a way to avoid this?
yes, explicitly set font-relative-size on the Accidentals grob.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Chords under voltas ?
[EMAIL PROTECTED] writes: BTW while searching the archives I saw that several people were interested in reducing the font size for chords. This is what I managed to come with: \context ChordNames ... \property ChordNames.ChordName \set #'font-magnification = #'0.8 ... because the font-relative-size doesn't work. bugreport please? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
\raise in markup (lilypond 1.7.13)
[EMAIL PROTECTED] writes:
Hello,
I'm trying to raise text markup with lilypond 1.7.13.
I believe I've followed the manual instructions... but can't achieve
what I'd would like to.
texts like these are alignedt such that the bottom of the text
coincides with the top of the staff. Any \raise is annulled in this
way. Try (for example)
\markup { \raise #2.0 { .. } }
(you may want to set #'word-space to #0 to suppress the space between
and \raise. )
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
1.7.12: minimumVerticalExtent and HariKariStaffContext
[EMAIL PROTECTED] writes: Am I missing something or using the wrong overrides? Please supply a small .ly example. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Can't convince Lylipond to merge different voices with same notes.
[EMAIL PROTECTED] writes: Hello, Despite having followed (I think) the manuel advices (by setting \property Staff.NoteCollision \override #'merge-differently-headed = ##t), I can't convince Lylipond (1.7.12) to merge different voices with same notes... I join an example source (test.ly) and the png output. Has anybody an idea ? Am I wrong ? Or is there an issue I've not figured out ? This is a bug -- thanks for reporting it. I'll look into it, but in the meantime, you should use force-hshift for manual control. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
chord names
[EMAIL PROTECTED] writes: Hi, I've just started using Lilypond (1.6.6) and I can't get chord names to work. I found some messages in the archives about this, so it seems it is really a problem with Lilypond rather than me. I wonder if there is a solution for this already. I've tried to upgrade to more recent version of Lilypond, but there are lots of other packages I would have to upgrade too (I'm using Red Hat 7.3). Recent Lilypond 1.7 releases have much improved chord name support. Unfortunately, they do require an upgrade to GUILE 1.6 or newer. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
figured bass nitpick
[EMAIL PROTECTED] writes: Since the figured bass context by definition discards note requests, it would be nice if lily would stop printing out the: See 1.7 CVS. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
SpacingSpanner properties: spacing-increment andshortest-duration-space
[EMAIL PROTECTED] writes:
How or where are the SpacingSpanner properties spacing-increment and
shortest-duration-space set or modified?
I added the following to the manual
The @internalsref{SpacingSpanner}, is score wide, so its properties
must be overriden from the @code{\paper} block, e.g.
@example
\paper @{ \translator @{
\ScoreContext
SpacingSpanner \override #'spacing-increment = #3.0
@} @}
@end example
(remove @ for usable input.)
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Segno, Coda
[EMAIL PROTECTED] writes: Hi. Is there any facility to produce From Segno to Coda, or similar? I'm using s1^#'(text From(music scripts-segno) (text to ) (music script-coda)) You've found the facility :-) Futhermore, how to produce From Segno to Coda Coda --|| | --|| | --|| (blank space)| --|| | --|| | (I hope it is clear enough). This is not supported, unfortunately. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Transpose - output to a new .ly
[EMAIL PROTECTED] writes: Is it possible to have the transposed music output to a new lilypond .ly file? No, in general this is not possible, but you can try to hack something together using \apply, to dump the transposed note names, though. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: turning off spurious warnings
That works! Thanks. The documentation makes it sound like is the right way to skip lyrics. On another note (no pun intended!): the latest version of python (2.3a2) generates these warnings for ly2dvi: /usr/local/share/lilypond/1.7.13/python/gettext.py:141: FutureWarning: hex/oct constants sys.maxint will return positive values in Python 2.4 and up if strToInt(buffer[:4]) != 0x950412de: /usr/local/share/lilypond/1.7.13/python/gettext.py:144: FutureWarning: hex/oct constants sys.maxint will return positive values in Python 2.4 and up if strToInt(buffer[:4]) != 0x950412de: /usr/local/share/lilypond/1.7.13/python/gettext.py:189: FutureWarning: hex/oct constants sys.maxint will return positive values in Python 2.4 and up Mike From: Han-Wen Nienhuys [EMAIL PROTECTED] Date: Wed, 5 Mar 2003 20:14:02 +0100 [EMAIL PROTECTED] writes: I've just started working with Lilypond 1.7.13, after a long absence from lilypond use. I notice that I get warnings if I have empty lyrics that don't match a notehead (say, they match a rest). For empty lyrics I just put in an empty string (), which works, but then Lilypond treats that as a real lyric and raises the unnecessary warning when the empty string matches a rest. Is there a way to get around this? have you tried using \skip ? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
