Dear all,
I am presently re-engraving a number of almost forgotten piano pieces.
One of them has under the first bar of the LH staff the text: "sempre 2 Ped",
Ped being the usual standard notation as generated by \sustainOn.
Although the LilyPond documentation tells me somewhere that "Pedal indi
On 22.01.2017 01:10, David Wright wrote:
I would use PDFs if you
can,
Or SVGs, if the respective software supports them.
as they can be rescaled as much as you like without becoming
blurred.
Best, Simon
___
lilypond-user mailing list
lilypond-use
On 22.01.2017 10:36, Robert Blackstone wrote:
I am presently re-engraving a number of almost forgotten piano pieces.
One of them has under the first bar of the LH staff the text: "/sempre
2 Ped/", Ped being the usual standard notation as generated by \sustainOn.
Although the LilyPond documenta
Consider:
\version "2.19.43"
\new Staff
<<
\set Staff.instrumentName = \markup "Treble Recorder"
{
\grace f'8
g'4 g'
}
>>
with the grace note the instrument name is not printe
Le dimanche 22 janvier 2017 à 10:40 +, Richard Shann a écrit :
> Consider:
>
> \version "2.19.43"
> \new Staff
> <<
> \set Staff.instrumentName = \markup "Treble Recorder"
> {
> \grace f'8
> g'4 g'
>
On Sun, 2017-01-22 at 11:56 +0100, Jean Bréfort wrote:
> Le dimanche 22 janvier 2017 à 10:40 +, Richard Shann a écrit :
> > Consider:
> >
> > \version "2.19.43"
> > \new Staff
> > <<
> > \set Staff.instrumentName = \markup "Treble Recorder"
> >
On Sat, 2017-01-21 at 23:47 +0100, Simon Albrecht wrote:
> On 21.01.2017 21:46, David Sumbler wrote:
> >
> > could somebody explain to me what the warning
> > actually means, and what I would need to do to stop it appearing?
> It signifies problem in the calculation of beam slope. I get it all
> t
2017-01-22 11:40 GMT+01:00 Richard Shann :
> Consider:
>
> \version "2.19.43"
> \new Staff
> <<
> \set Staff.instrumentName = \markup "Treble Recorder"
> {
>\grace f'8
>g'4 g'
> }
>
Richard Shann writes:
> Consider:
>
> \version "2.19.43"
> \new Staff
> <<
> \set Staff.instrumentName = \markup "Treble Recorder"
> {
>\grace f'8
>g'4 g'
> }
> >>
>
> with
Hello Simon,
Thanks for your advice. In its simple form, i.e. by adding: _\markup { \italic
{sempre 2} \musicglyph #"pedal.Ped" } , it works perfectly.
The other method, as in the ME you gave, it did not work.
But I got exactly what I needed. Thanks again.
Best regards,
Robert
On 22 Jan 2017,
On 22.01.2017 12:09, David Sumbler wrote:
Your suggestion is clearly a tweak to Beam.positions, but I can't find
the documentation for the use of \offset. Assuming that there is such
documentation, could you point me to it, please?
Alas, \offset is a 2.19 addition, but undocumented. Is there a
On Sun, 2017-01-22 at 12:23 +0100, Thomas Morley wrote:
> 2017-01-22 11:40 GMT+01:00 Richard Shann :
> > Consider:
> >
> > \version "2.19.43"
> > \new Staff
> > <<
> > \set Staff.instrumentName = \markup "Treble Recorder"
> > {
> >
Now to everyone...
On Jan 22, 2017 6:14 AM, "David Nalesnik" wrote:
On Jan 22, 2017 5:54 AM, "Simon Albrecht" wrote:
On 22.01.2017 12:09, David Sumbler wrote:
> Your suggestion is clearly a tweak to Beam.positions, but I can't find
> the documentation for the use of \offset. Assuming that
Hi Andrew,
2017-01-22 8:37 GMT+01:00 Andrew Bernard :
> In my large score, at one point there is a very large gap between a span
> bar/barline and the chords in the bar, which have lots of accidentals
> (dodecaphonic style). I would prefer to be able to move the chords left
> closer to the barline
Simon Albrecht wrote Sunday, January 22, 2017 11:54 AM
> Alas, \offset is a 2.19 addition, but undocumented. Is there an entry in
> Changes?
> Anyway, that’s clearly something we need to fix for 2.20.
See https://sourceforge.net/p/testlilyissues/issues/3830/
Trevor
Decimo tertio Kalendas Februarias MMXVII scripsit Malte Meyn :
>
>
> Am 20.01.2017 um 18:39 schrieb Jérôme Plût:
> > Problem 1: why, on the third beat, is the alto voice (playing a g')
> > displayed on the "down" Staff?
>
> It doesn’t in LilyPond 2.19.53, which version are you using?
I am using
On 21/01/17 02:18, Andrew Bernard wrote:
> Hi Andrew,
>
> The manual is not well written concerning this matter. A \tempo is a
> metronome mark (I don't think that is entirely obvious).
>
> {
> \mark \default
>
> \once \override Score.MetronomeMark.extra-offset = #'(8 . 0)
> \tempo "A temp
I want to make a Scheme macro \BlankStaff that outputs a single white
staff. (Optionnally, \BlankStaff #3 would output three of them, etc.
In particular, using “\include "blank-staff.ly"” is a non-solution).
A snippet does the white staff:
http://lilypond.org/doc/v2.19/Documentation/snippets/staf
Hi Andrew (et al.),
I would suggest X-offset is perhaps a good choice:
{
\mark \default
\once \override Score.MetronomeMark.X-offset = #11
\tempo "A tempo" 8 = 104
s2^\markup { \musicglyph #"scripts.segno" } | s2*15 \bar "||”
}
Or perhaps even extra-spacing-width/height, etc. In any case
2017-01-22 19:30 GMT+01:00 Jérôme Plût :
>
> I want to make a Scheme macro \BlankStaff that outputs a single white
> staff. (Optionnally, \BlankStaff #3 would output three of them, etc.
> In particular, using “\include "blank-staff.ly"” is a non-solution).
>
> A snippet does the white staff:
> http
On 22/01/17 20:12, Thomas Morley wrote:
P.S.
The actual topic of this thread, \layout in scheme, is not answered.
Though, I doubt you still need it. If I'm wrong, please shout and I'll
have a second thought
If you do feel the need to process layouts in Scheme, this may point you
in the right dir
On Sun, Jan 22, 2017 at 8:12 AM, Trevor Daniels wrote:
>
> Simon Albrecht wrote Sunday, January 22, 2017 11:54 AM
>
>> Alas, \offset is a 2.19 addition, but undocumented. Is there an entry in
>> Changes?
>> Anyway, that’s clearly something we need to fix for 2.20.
>
> See https://sourceforge.net/p
Hello Harm,
A good and excellent solution. Works fine in my context.
It's hard to find one's way among all the spacing alist variables, as the
documentation for each is fairly thin. This is really helpful.
Andrew
___
lilypond-user mailing list
lilypond
23 matches
Mail list logo
