Re: Fwd: 2.13.3 docs emacs mode documentation AU 2.2.1 out of date?
On Sat, Jul 25, 2009 at 02:21:46PM -0500, Tim McNamara wrote: > Here is the entire text from 2.2.1 for lilypond-mode for Emacs: -snip- > It *is* a bit terse and seems incomplete, and indeed differs from the > discussion we just had in which Paul was given different instructions. Thanks for looking into this. The entire AU is slated for huge restructuring. Could you keep these instructions handy, and when I get to this point and/or ask for public comments on the new AU, could you send me updated text then? Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: volta repeats with alternatives
In message <4a68a0ff.7040...@ultrasw.com>, Paul Scott writes Is there a setting or something to do this automatically? Why isn't it done by default anyway? (btw: the override command is just used to demonstrate the problem, I only need the measure numbers at the beginning of each line.) This has been discussed here before. This is the way LilyPond works. Lily's way is consistent with many printed scores even though your way is sometimes done. There's a third way too ... I sometimes come across pieces where - let's say - an eight bar repeated phrase is counted as sixteen bars. Usually because some other part has the repeat written out in full. But yes - the lilypond way is the way I normally see music - I almost never see it where two bars have the same number. Why would you do that? The main reason for bar numbers is, surely, for the conductor to be able to accurately identify a bar during a rehearsal. How is an ambiguous bar number going to help? What use are bar numbers if they are ambiguous? Cheers, Wol -- Anthony W. Youngman - anth...@thewolery.demon.co.uk ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new spacing test/example
Kieren MacMillan wrote: > OK... and, as I said, I'll be happy to help with the doc update. > It'll just be too late for my frustrating/frustrated attempt to > compile Joe's branch here on my own machine (in order to test > the spacing engine in his most recent patch). Kieren, I sympathize with your situation. I'm also in a sort of limbo with my inability to compile. But we're true beta-testers. We take the hit of getting frustrated, having everything fail, falling down and getting back up and telling others what the heck happened. The fact that things are so confusing right now is because people like you and me (ie. we don't have the programming experience to figure everything out from the source code alone) have never gotten this far without documentation. We're vanguards. And the burden is on us to keep reporting on specific misunderstandings, and to keep track of our own steps (and missteps), so that the next group of Kierens and Marks that come along will have it alot easier. Of all people, I know, things can get *very* frustrating. But somewhere along the line, someone has to deal with what we're dealing with, and when we emerge, we'll be more helpful, and we'll have better documentation to show for it. I once read that a program is only as good as its documentation. And if we're serious about really getting LilyPond to the top (and I think we are) then that's our responsibility. Nobody's going to do it for us. Don't forget -- LilyPond comes with no warranty! Hope this helps. - Mark ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond 2.12.1 - strange result - missing line breaks
On Sun, Jul 26, 2009 at 20:30, Marc Hohl wrote: > Michał Dwużnik schrieb: >> >> Hi, >> >> after quite a long time of not using lilypond I got back to "engraving". >> Attached example (modified SATB example, proven to work with other >> pieces) produces somewhat surprising result >> - printout with second line extending to the right well past the edge >> of the page... >> How should I hint lilypond to break the lines and get good result? >> > > Such weird output is mostly due to the fact of assigning the wrong or no > length to a note. > In the tenor voice, you coded des4.( c4 bes2) which is surely too much for a > 4/4 bar. Thank you for pinpointing the root cause. > Second, you forced a line break in the soprano voice in the middle of a bar. > This is purely my error, noted only after sending, sorry. > To avoid such errors, it is better and more readable to write every bar in a > separate line, > and you can end every bar with a "|" to force bar checks. > That's indeed a great hint for future. Regards Michal PS: The good thing I realized is that the mistake I made shown me clearly I'm typesetting sth more complicated than the last time. Which somehow makes me feeling good ;) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Manipulating grob properties doesn't work
Robin Bannister schrieb: Marc Hohl wrote: This worked fine with ties, but when I try the same with slurs, it simply shows no difference. (display right-bound) says - Tie: # - Slur: # Thank you - this explains why it does not work, so I have to find another way ... Marc Cheers, Robin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond 2.12.1 - strange result - missing line breaks
Michał Dwużnik schrieb: Hi, after quite a long time of not using lilypond I got back to "engraving". Attached example (modified SATB example, proven to work with other pieces) produces somewhat surprising result - printout with second line extending to the right well past the edge of the page... How should I hint lilypond to break the lines and get good result? Such weird output is mostly due to the fact of assigning the wrong or no length to a note. In the tenor voice, you coded des4.( c4 bes2) which is surely too much for a 4/4 bar. Second, you forced a line break in the soprano voice in the middle of a bar. To avoid such errors, it is better and more readable to write every bar in a separate line, and you can end every bar with a "|" to force bar checks. Marc Thanks in advance Michal ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
lilypond 2.12.1 - strange result - missing line breaks
Hi,
after quite a long time of not using lilypond I got back to "engraving".
Attached example (modified SATB example, proven to work with other
pieces) produces somewhat surprising result
- printout with second line extending to the right well past the edge
of the page...
How should I hint lilypond to break the lines and get good result?
Thanks in advance
Michal
global = {
\version "2.12.1"
\key c \minor
\time 4/4
}
sopranonotes = \relative c''
{
r2 c2~ c c~ c des2 c1 r4 c2 c4 c2 c4 c b1
a2 \break r2 r1 r r r r4 c2 c4 f1 e1
r1 r2 f2~ f es des c4 c4~ (c4 bes8 as bes4 ) bes4 c2 r4 c~ c c c c des2( c) c1
}
sopranowords = \lyricmode
{
O vos om- nes, qui trans- i- tis per vi- am
et vi- de- te, si_ est do- lor si- mi- lis, si- cut do- lor me- us
}
altonotes = \relative c''
{
c,1 as'2.~ g8 f g4~ a bes2 g1 as2. as4 as2 g4 as g8( f f2 e4) f2
r2 r c'2~ c es2~ es4 d4 d2 c2. bes4 c4.( d8 es4 c4~ c4 bes8 as bes2) c1
r2 c~ c bes c g bes as4 g f2. f4 g1 a4. a8 a4 g4 bes2( g) a1
}
altowords = \lyricmode
{
O vos om- nes, qui trans- i- tis per vi- am
at- ten- di- te
et vi- de- te, si est do- lor si- - - - mi- lis, si- cut do- lor me- us
}
tenornotes = \relative c'
{
\clef "G"
r2 c~ c es~ es f( f4)(e) e2 r4 f2 f4 f2 es4 c4 des4.( c4 bes2)
c r f1 as2. g4 g2 f2( f4) es f( g as2 g4 as~ as8 g f es f2) g1
as1 g2 f g r4 g( g8 f f2) e4 f2 r4 f~ f e r4 f~ f e e2 f4. f8 f4 c' b2( c) f1
}
tenorwords = \lyricmode
{
O vos om- nes, qui trans- i- tis per vi- am
at- ten- di- te
et vi- de- te, si est do- lor si- mi- lis, si- mi- lis, si- cut do- lor me- us
}
bassnotes = {
\clef bass c2 d2}
basswords = \lyricmode { mi mi }
\score{
\context ChoirStaff
<<
\context Staff = soprano <<
\context Voice = sop { << \global \sopranonotes >> }
\lyricsto "sop" \new Lyrics \sopranowords
>>
\context Staff = alto <<
\context Voice = alt { << \global \altonotes >> }
\lyricsto "alt" \new Lyrics \altowords
>>
\context Staff = tenor <<
\context Voice = ten { << \global \tenornotes >> }
\lyricsto "ten" \new Lyrics \tenorwords
>>
\context Staff = bass <<
\context Voice = bas { << \global \bassnotes >> }
\lyricsto "bas" \new Lyrics \basswords
>>
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Manipulating grob properties doesn't work
Marc Hohl wrote: This worked fine with ties, but when I try the same with slurs, it simply shows no difference. (display right-bound) says - Tie: # - Slur: # Cheers, Robin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new spacing test/example
Graham, The reason that those instructions aren't in the maoing docs are that nobody's reviewed the maoing compiling instructions. The reason that nobody's reviewed the maoing compiling instructions are that I'm waiting for it to be added to the maoing CG. They're not in the maoing CG because that's waiting for the maoing big doc rearrangment. The maoing big doc rearrangement is currently in process, after waiting for a maoing long discussion about what should be done in said rearrangement. Well I'm maoing glad that's been maoing cleared up! Yes. That said, we *know* that the CG isn't finished yet. And that's my main priority for 2.14 -- even more than the website. Once the CG is ready... at least for non-programming tasks, which should only take a week or two (once we finally /start/ that process), we can start GOP. Have patience. It's happening as quickly as it can be done in an efficient manner. OK... and, as I said, I'll be happy to help with the doc update. It'll just be too late for my frustrating/frustrated attempt to compile Joe's branch here on my own machine (in order to test the spacing engine in his most recent patch). Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: new spacing test/example
On Sat, Jul 25, 2009 at 09:50:59PM -0400, Kieren MacMillan wrote: > Hi Carl, > >>> p.s. Clearly, these instructions should be in the Lilypond docs >>> instead of spread all over mao's green web < once I've got things up >>> and running, I'll put together a doc patch so that future Mac users >>> won't have to go through all this frustration... The reason that those instructions aren't in the maoing docs are that nobody's reviewed the maoing compiling instructions. The reason that nobody's reviewed the maoing compiling instructions are that I'm waiting for it to be added to the maoing CG. They're not in the maoing CG because that's waiting for the maoing big doc rearrangment. The maoing big doc rearrangement is currently in process, after waiting for a maoing long discussion about what should be done in said rearrangement. >> Ivo Boumann's web site (which is linked from the download page) shows >> multiple ways of installing LilyPond, including the link to Nicolas's >> how-to guide. > > I personally don't think that's sufficient: the docs should be self- > contained, yes? Yes. That said, we *know* that the CG isn't finished yet. And that's my main priority for 2.14 -- even more than the website. Once the CG is ready... at least for non-programming tasks, which should only take a week or two (once we finally /start/ that process), we can start GOP. Have patience. It's happening as quickly as it can be done in an efficient manner. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Manipulating grob properties doesn't work
Marc Hohl schrieb:
I am starting to implement bends in lilypond.
As a first step, I want to make the right tab note head
covered by a slur transparent.
This worked fine with ties, but when I try the same with slurs,
it simply shows no difference.
What am I doing wrong here?
Marc
-
\version "2.13.3"
test = \relative c {
c4 ( d ) e ( f )
c4( cis) d ( es )
c4( es) e( gis )
c4 ( cih ) c4 ( cisih )
}
#(define-public (slur::tab-bend grob)
(let* ((original (ly:grob-original grob))
(left-bound (ly:spanner-bound grob LEFT))
(right-bound (ly:spanner-bound grob RIGHT)))
;; original is not used at the moment, but there will be
,, different situations where an broken slur has to be handled
differently
To prevent some misunderstandings: the comment here was included in the
mail client,
and the , instead of a ; is just a typo...
(ly:grob-set-property! right-bound 'transparent #t)))
% this last line above doesn't seem to have any effect; why?
\layout {
\context {
\TabVoice
\revert Slur #'stencil % I have tablature features installed and
want the slurs to be visible for now
\override Slur #'after-line-breaking = #slur::tab-bend
}
}
\score {
<<
\new Staff { \clef "G_8" \test }
\new TabStaff { \clef "tab" \test }
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Manipulating grob properties doesn't work
I am starting to implement bends in lilypond.
As a first step, I want to make the right tab note head
covered by a slur transparent.
This worked fine with ties, but when I try the same with slurs,
it simply shows no difference.
What am I doing wrong here?
Marc
-
\version "2.13.3"
test = \relative c {
c4 ( d ) e ( f )
c4( cis) d ( es )
c4( es) e( gis )
c4 ( cih ) c4 ( cisih )
}
#(define-public (slur::tab-bend grob)
(let* ((original (ly:grob-original grob))
(left-bound (ly:spanner-bound grob LEFT))
(right-bound (ly:spanner-bound grob RIGHT)))
;; original is not used at the moment, but there will be
,, different situations where an broken slur has to be handled
differently
(ly:grob-set-property! right-bound 'transparent #t)))
% this last line above doesn't seem to have any effect; why?
\layout {
\context {
\TabVoice
\revert Slur #'stencil % I have tablature features installed and
want the slurs to be visible for now
\override Slur #'after-line-breaking = #slur::tab-bend
}
}
\score {
<<
\new Staff { \clef "G_8" \test }
\new TabStaff { \clef "tab" \test }
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
