Graham Percival wrote Wednesday, August 06, 2008 7:58 AM
On Tue, 5 Aug 2008 17:03:58 -0700
"Patrick McCarty" <[EMAIL PROTECTED]> wrote:
You do raise a lot of interesting points though. I'm not the best
person to address these concerns though.
No he doesn't. At least, he hasn't raised any n
Hi,
Unfortunately, I haven't had the time to be very active in the review of
the GDP drafts, but I happened
to look into "New dynamic marks" of 1.3.1 and have some comments:
- The markup command for \roundf is unnecessarily complicated and the
result looks bad. The \center-align markup comman
The best solution for you is probably to use #(make-dynamic-script ... )
to define all your dynamic commands, see subsection "New dynamics".
Then, they will behave exactly as all the other dynamics.
I haven't investigated how much tweaks would be involved to make
ordinary \markup commands work b
Francisco
The LM's role (at least in my view) is to introduce concepts and
explanations in a logical order. It makes no attempt to be either rigorous
or comprehensive, neither should it. The NR's role, in contrast, is to
present complete and accurate facts, sweetened with a smattering of
ex
kenny,
how about
#(define (color-notehead grob)
(pitch-to-color (ly:event-property (ly:grob-property grob 'cause)
'pitch)))
#(define (pitch-to-color pitch)
(cond
((and (eqv? (ly:pitch-octave pitch) 0) (eqv? (ly:pitch-alteration
pitch) 0) (eqv? (ly:pitch-notename pitch) 6)) (x11-
I personally have *never* needed to use \new.
\context implicitly instantiates a new context if the
one named doesn't yet exist, so \new is redundant, *except* where you
want multiple distinct contexts with the same name, or you're using
unnamed contexts (which, internally, is the same thin
On Wed, Aug 6, 2008 at 3:58 AM, Graham Percival <[EMAIL PROTECTED]> wrote:
> On Tue, 5 Aug 2008 17:03:58 -0700
> "Patrick McCarty" <[EMAIL PROTECTED]> wrote:
>
>> You do raise a lot of interesting points though. I'm not the best
>> person to address these concerns though.
>
> No he doesn't. At le
Since I have only used LilyPond for 11 years, I have some remaining
questions on how it works.
Can anybody tell me exactly what happens with the context names in the
following example.
\relative c' <<
\new Staff \new Voice = myvoice { c d e f }
\new Staff \context Voice = myvoice { g f e d }
>>
Karl Hammar wrote:
That is strange, why do you need to do the \new DrumVoice-lines in
drummode? Example of 2.5.1.3:
\new DrumStaff <<
\new DrumVoice = "1" { s1 *2 }
\new DrumVoice = "2" { s1 *2 }
\drummode {
bd4 sn4 bd4 sn4
Trevor Daniels wrote:
So, for the example in question, the NR should certainly state
categorically what the voice names are in the various constructs, and
examples showing the differences would be fine. But I don't think
there is any need to put lengthy explanations in the NR - it's a
refer
Dear lilypond-users,
I have a problem with ties in connection with automatic note splitting. I
don't understand why the ties in the below quoted example look so strange:
Is it a bug?
\score {
\new Staff {
\new Voice \with {
\remove "Note_heads_engraver"
\consists "Completion_heads_e
I need to create a tempo marking that would look like this:
\tempo 4 ~ 4. = 53
...if \tempo worked like that. I was trying to cobble something
together by creating a markup containing music. My plan was to print a
quarter tied to a dotted quarter, move a text script using offset and
remove
Mats, you wrote, Wednesday, August 06, 2008 1:26 PM
Trevor Daniels wrote:
So, for the example in question, the NR should certainly state
categorically what the voice names are in the various constructs, and
examples showing the differences would be fine. But I don't think
there is any need
Then don't remove the engraver, just set the stencil to #f or the grob
transparent.
David Bobroff wrote:
I need to create a tempo marking that would look like this:
\tempo 4 ~ 4. = 53
...if \tempo worked like that. I was trying to cobble something
together by creating a markup containing m
Thanks! That seems to work.
-David
Bertalan Fodor (LilyPondTool) wrote:
Then don't remove the engraver, just set the stencil to #f or the grob
transparent.
David Bobroff wrote:
I need to create a tempo marking that would look like this:
\tempo 4 ~ 4. = 53
...if \tempo worked like that.
Why not follow the approach used in
http://lsr.dsi.unimi.it/LSR/Item?id=204 ?
/Mats
David Bobroff wrote:
I need to create a tempo marking that would look like this:
\tempo 4 ~ 4. = 53
...if \tempo worked like that. I was trying to cobble something
together by creating a markup containin
Which LilyPond version are you using?
Exactly what is it that you think looks strange? Is it the tie
introduced by the note splitting or the
one you specified manually? When I tried to remove the automatic note
splitting from your example,
the remaining tie looked exactly the same.
/Mats
S
In addition to my previous answer: The size of the markup text is larger
since the template contains
the line:
\override TextScript #'font-size = #2
If you just remove that line, you should get the same size as the normal
dynamics.
The question is why the setting was done in the first pla
I am using a Mac computer OS 10 version 8. Can I download lilypond?
Thanks for answering
Dolores Dickey
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Hi,
Trying to make my first lilypond song and put let it be on score but I
can't make the timing of the lyrics fit with the melody... :
\version "2.11.53"
melody = \relative c' {
\clef treble
\key c \major
\time 4/4
\partial 4
g8 a c4 c d a c c d e f f f e e d d2
On Wed, Aug 6, 2008 at 1:44 AM, Mats Bengtsson <[EMAIL PROTECTED]> wrote:
>
> - The markup command for \roundf is unnecessarily complicated and the result
> looks bad. The \center-align markup command is intended to produce a column
> of (internally) center aligned markups. If you only have a singl
2008/7/27 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> I don't understand the original code. 'me' should already be the
> staff-symbol
That's only true for Staff_symbol_referencer::on_line () before the patch.
The revised version, Staff_symbol::on_line (), deals with two separate
cases, i.e., standar
On Mon, Aug 4, 2008 at 7:51 AM, Francisco Vila <[EMAIL PROTECTED]> wrote:
> 2008/8/3 Trevor Daniels <[EMAIL PROTECTED]>:
>> Hi Francisco
>>
>> Not a bad suggestion. I've tried to fix the
>> issues you mentioned - still not perfect, but
>> better. Revised code attached.
>
> Trevor: great.
>
> Meas
23 matches
Mail list logo
