Hello everyone.
Is there anyone on the list who wouldn't mind taking a look at some code
and offering general suggestions on writing input files? I've now
successfully typeset several piano scores and would like some feedback
from experienced users about the structure of my .ly files. I'm stil
Hi all,
I wonder if it's possible to wrap parentheses around an accidental and
a note head. Currently the \parenthesize parenhesizes only the note
head.
One possible use for such a feature is presented in the included image
(parentheses added in another application).
-Risto
%%%
\version "2.
2008/10/10 Risto Vääräniemi <[EMAIL PROTECTED]>:
> One possible use for such a feature is presented in the included image
> (parentheses added in another application).
Hmm. For some reason Gmail preview messes up the image. It probably
doesn't like grayscale images. Here it comes again in full RG
On 10.10.2008, at 09:03, David Stocker wrote:
Hello everyone.
Is there anyone on the list who wouldn't mind taking a look at some
code and offering general suggestions on writing input files? I've
now successfully typeset several piano scores and would like some
feedback from experienced
2008/10/10 Patrick McCarty <[EMAIL PROTECTED]>:
> The blue links are very close to pure blue (#00F), which is a little
> bit intense, but there aren't very many blues that pass the
> guidelines. What does everyone think about this? Are there any
> colors from this design that you like more than
2008/10/10 Risto Vääräniemi <[EMAIL PROTECTED]>:
> Hmm. For some reason Gmail preview messes up the image. It probably
> doesn't like grayscale images. Here it comes again in full RGB.
Looks a lot like
http://code.google.com/p/lilypond/issues/detail?id=155 to me :-)
Cheers,
Valentin
__
On Fri, Oct 10, 2008 at 03:03:53AM -0400, David Stocker wrote:
> \paper {
> #(set-paper-size "concert")
> }
This is entirely a matter of preference, but I'd suggest making the
closing brace be at the same indentation level as the line that opens
the block, like so:
\paper {
#(set-paper-size
2008/10/10 Valentin Villenave <[EMAIL PROTECTED]>:
> Looks a lot like
> http://code.google.com/p/lilypond/issues/detail?id=155 to me :-)
Well, yes and no. :-)
In the case of issue 155 it's quite easy to create a workaround. E.g.
\once \override Score.AccidentalPlacement #'right-padding = #0.4
\p
In the midst of the discussion about different styles of clefs I
mentioned an "English"* style of bass clef. A clear image of such a
clef can be seen here:
http://en.wikipedia.org/wiki/Image:Oldbassclef.png
It's called "old bass clef" there.
-David
*I called it "English" because I've only s
Valentin Villenave wrote:
2008/10/7 Stefan Thomas <[EMAIL PROTECTED]>:
Dear Aaron,
maybee this could help You:
http://lsr.dsi.unimi.it/LSR/Item?id=390
... or (better) this one:
http://lsr.dsi.unimi.it/LSR/Item?id=305
Thanks so much!
Aaron
___
l
I don't know how to get the two vertical lines before and after the
note/chord that defines the pitches on the recitative section. Is there
some command/marking I can attach to a note in the chord so that all
lines would be automatically drawn from the lowest note to the highest.
Or do I need to dr
2008/10/10 Risto Vääräniemi <[EMAIL PROTECTED]>:
> However, what I'm asking for would be a different way to place the
> parentheses:
> ( # note ) versus the current # ( note ). One option might be creating
> a markup "()" and use extra-offset to lower / raise it around the
> note and accident
On 10.10.2008 (16:32), Ari Torhamo wrote:
> I don't know how to get the two vertical lines before and after the
> note/chord that defines the pitches on the recitative section. Is there
> some command/marking I can attach to a note in the chord so that all
> lines would be automatically drawn from
Patrick McCarty wrote:
I've created another design with a color palette that passes the
W3C Web Content Accessibility guidelines for color contrast
Yes, yes, yes! Thank you very much.
At last I feel the web designer was more concerned about
making it easy to read rather than easy to look at
Eyolf Østrem wrote:
On 10.10.2008 (16:32), Ari Torhamo wrote:
I don't know how to get the two vertical lines before and after the
note/chord that defines the pitches on the recitative section. Is there
some command/marking I can attach to a note in the chord so that all
lines would be autom
Thank you, James and Daniel, for your suggestions.
You only need to do that if you use <<{\voiceOne}\new Voice
{\voiceTwo}>>\oneVoice, in which case, all of that is necessary for
the same multi-voice construct.
This has dogged me for several weeks and I finally gave up. Now, seeing
the overall
On 10.10.2008, at 16:21, David Stocker wrote:
Thank you, James and Daniel, for your suggestions.
You only need to do that if you use <<{\voiceOne}\new Voice
{\voiceTwo}>>\oneVoice, in which case, all of that is necessary for
the same multi-voice construct.
This has dogged me for several we
In message
<[EMAIL PROTECTED]>, Danny
Sosa <[EMAIL PROTECTED]> writes
Hello everyone! Thank you all for your help so far.
There is something that I cannot figure out! I need help...
I'm trying to typeset an existing piece of music with lilypond
I thought that using mBreak was a very good idea as
First of all... thanks to James for his help with mBreak, the magic words
were "outside of any music block". I was trying to define mbreak inside the
{}.
Does anyone know how to write rolled chords in Lilypond? it's just like a
little squiggly line left of any chord
this is how I would like to mak
\arpeggio
On 10.10.2008, at 20:11, Danny Sosa wrote:
First of all... thanks to James for his help with mBreak, the magic
words were "outside of any music block". I was trying to define
mbreak inside the {}.
Does anyone know how to write rolled chords in Lilypond? it's just
like a little
On 10.10.2008 (11:11), Danny Sosa wrote:
> First of all... thanks to James for his help with mBreak, the magic words
> were "outside of any music block". I was trying to define mbreak inside the
> {}.
> Does anyone know how to write rolled chords in Lilypond?
The sign in the picture is an arpeggi
... less than 8 minutes and you already solved my problem...
you're amazing! haha
thank you so much!
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
\relative c' {
1 \arpeggio
}
To apply an unbroken arpeggio line to all voices and staves for piano,
use "\set PianoStaff.connectArpeggios = ##t" inside your new \PianoStaff
and use \arpeggio on the same beat within each voice context you want it
to apply to. I don't know if the same command wo
On Thu, 9 Oct 2008 10:08:00 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> Many thanks for this. The abbreviations are fine as they are - these
> headwords are not intended to teach anything, they're just to show
> what is possible. I added midi output (hope that's OK with you -
> what tem
I'm writing a scale pattern using slurs on certain notes with parenthesis "
_ ; ^ ; () " but whenever I try making a slur above the note Lilypond
automatically puts it above the beam. Could you guys help me tweak it so it
does it only above notehead?
Here is what I'm trying to accomplish:
http://
Hi,
sporadically following the discussion about the ongoing work on the new
documentation web site. It is improving every day and looks really
really good. Great job!
I have a couple of things I thought you might (re)consider:
first the width of the text div: I know this has been discussed e
Graham, you wrote Friday, October 10, 2008 7:38 PM
On Thu, 9 Oct 2008 10:08:00 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
Many thanks for this. The abbreviations are fine as they are - these
headwords are not intended to teach anything, they're just to show
what is possible. I adde
On Fri, 10 Oct 2008 22:59:43 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
>
> Graham, you wrote Friday, October 10, 2008 7:38 PM
>
> > On Thu, 9 Oct 2008 10:08:00 +0100
> > "Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> >
> > Err, why midi? It doesn't help anything for the docs, and as
> >
Hi Till,
On Fri, Oct 10, 2008 at 12:43 PM, Till Rettig <[EMAIL PROTECTED]> wrote:
> Hi,
>
> sporadically following the discussion about the ongoing work on the new
> documentation web site. It is improving every day and looks really really
> good. Great job!
Thanks!
> I have a couple of things I
29 matches
Mail list logo
