Alberto Simões-2 wrote
> Just finished a transcription of a simple piece (four pages, for piano).
> I took all my care to correctly transcribe it, but I would love if
> someone could help proofreading it.
> ...
> If you are willing to help, you do not need to mess with the lilypond
> code. You ca
> If you are willing to help, you do not need to mess with the lilypond
> code. You can just annotate somehow the PDF, and I'll fix the code.
I'm not that used to editing in PDF, therefor I will give measures as
of the PDF:
I have found one missing note:
in Bar 169 in the left hand there is missi
On 02/11/2015 07:19, Johan Vromans wrote:
On Sun, 1 Nov 2015 21:27:52 +
Alberto Simões wrote:
If you are willing to help, you do not need to mess with the lilypond
code. You can just annotate somehow the PDF, and I'll fix the code.
Small nitpick: *you* did the transcribing, LilyPond did
Thank you, and thank you Michael Gerdau too.
Will make fixes later tonight.
Alberto
On 02/11/2015 08:31, tisimst wrote:
Alberto Simões-2 wrote
Just finished a transcription of a simple piece (four pages, for piano).
I took all my care to correctly transcribe it, but I would love if
someone cou
> > Is there something like a "best practice" w/r to the use of \relative?
> > Or why does this difference exist ?
[long and extensive explanation skipped]
> So there's not really a "best practice" but rather one that requires
> least choice-making for those not interested in making more choices
Hello
After your precious help, I consider my task of transcribing this music
complete. Of course, I am happy to fix any issue:
https://github.com/ambs/music/tree/master/Gounod/ValseDesSylphes
Best regards,
Alberto
___
lilypond-user mailing list
Hello,
I am trying to compile a score and its parts using lilypond version
2.19.30. If I activate french-beaming (using \override Stem.french-beaming
= ##t in the \context \Staff), the program returns a segfault. When
french-beaming is not active, the compilation runs nicely. I have attached
to th
Hi, I don’t have the time to look at the whole score. But the f sharp in
m. 1 is wrong. Maybe you or someone else should check again the whole
piece for correct pitches.
Am 02.11.2015 um 22:44 schrieb Alberto Simões:
Hello
After your precious help, I consider my task of transcribing this musi
Sorry for replying to my own message so hastily, but making further tests I
may have found something
interesting:
I have many beams going over rests. If I remove every manual beaming over
rests, the problem disappears
and everything works fine (except for the fact that beaming over rests is
importa
> Hi, I don’t have the time to look at the whole score. But the f sharp in
> m. 1 is wrong. Maybe you or someone else should check again the whole
> piece for correct pitches.
Correct and I did not spot that while I did my proofreading...
[I did check the whole piece for correct pitches]
Kind reg
Am 02.11.2015 um 23:07 schrieb Jean Menezes da Rocha:
Hello,
I am trying to compile a score and its parts using lilypond version
2.19.30. If I activate french-beaming (using \override Stem.french-beaming
= ##t in the \context \Staff), the program returns a segfault. When
french-beaming is not
No problem Urs. Thanks for all you do.
Craig
On Mon, 2 Nov 2015 at 17:54 Urs Liska wrote:
> Oops, sent instead of saved ...
> I'll have to return to this later.
>
>
> Am 2. November 2015 08:50:39 MEZ, schrieb Urs Liska :
>>
>> Hi Craig,
>>
>> actually I see there's nothing *I* have to look int
Thanks for the tip, Malte! When trying to produce a minimal example I was
able to find the exact condition that causes this issue: when a beamed
group of 16ths *ends with* a rest, the segfault is produced.
For instance, the code
\relative c' {
\override Stem.french-beaming=##t
c16[ d e r]
}
p
I'm generating parts from an orchestral score, and am running an issue
where long tempo markings over collapsed multi-measure rests would force
the text to stack up in an ugly way on top of each other. Is there some
way of telling lilypond to prefer stretching the horizontal width of the
bars inste
Hi,
How about:
\version "2.18.2"
\score {
\new Staff {
\set Score.skipBars = ##t
\override Score.MetronomeMark.extra-spacing-width = #'(-0.0 . 0.4)
\override Score.MetronomeMark.extra-spacing-height = #'(-inf.0 . +inf.0)
\tempo "Allegro con moto" 4 = 120
R1*8
\tempo "Ada
On Mon, 2 Nov 2015 23:18:08 +0100
Malte Meyn wrote:
> Hi, I don’t have the time to look at the whole score. But the f sharp in
> m. 1 is wrong. Maybe you or someone else should check again the whole
> piece for correct pitches.
Listening to the midi often quickly reveals false pitches.
-- Joh
Am 03.11.2015 um 00:38 schrieb H. S. Teoh:
I'm generating parts from an orchestral score, and am running an issue
where long tempo markings over collapsed multi-measure rests would force
the text to stack up in an ugly way on top of each other. Is there some
way of telling lilypond to prefer st
Hello,
Or also:
\score {
\new Staff {
\set Score.skipBars = ##t
\markLengthOn
\tempo "Allegro con moto" 4 = 120
R1*8
\tempo "Adagio sostenuto" 4 = 50
R1*8
}
}
JM
> Le 3 nov. 2015 à 07:26, Pierre Perol-Schneider
> a écrit :
>
> Hi,
> How about:
>
> \version "2.18
Oops, totally forgot this one!
2015-11-03 8:38 GMT+01:00 Jacques Menu :
> Hello,
>
> Or also:
>
> \score {
> \new Staff {
> \set Score.skipBars = ##t
> \markLengthOn
> \tempo "Allegro con moto" 4 = 120
> R1*8
> \tempo "Adagio sostenuto" 4 = 50
> R1*8
> }
> }
>
> JM
>
>
19 matches
Mail list logo
