Hello Jacques,
Yes, this is possible. It’s just that Lilypond thinks that a slur of that
shape would not look good in that place. You can change the scoring parameters
Lilypond uses for determining how ugly a slur looks.
For example you can increase Slur.details.edge-attraction-factor to increa
ps://lsr.di.unimi.it/LSR/Item?id=134>, second attached image?
>>
>> Thanks for your help!
>>
>> JM
>
> Hi Jacques,
>
> LilyPond does support cross-staff slurs. In your example, it thinks the slur
> is going to look ugly if crossing the staves, and choos
without setting
control points manually, as is shown in
https://lsr.di.unimi.it/LSR/Item?id=134
<https://lsr.di.unimi.it/LSR/Item?id=134>, second attached image?
Thanks for your help!
JM
Hi Jacques,
LilyPond does support cross-staff slurs. In your example, it thinks the
slur is go
Hello folks,
MusicXML has the concept of a slur to a note in another staff, and MusicScore
provides this feature.
The simple attempt, first attached image, doesn’t produce a satisfactory result.
Is there a way to obtain such a slur in LilyPond without setting control points
manually, as is show
On Sat, 2014-04-12 at 04:38 +, efa...@faswebdesign.com wrote:
> I'm trying to score a piano piece that has cross-staff slurs on
> arpeggios. I've searched the documentation andlooket at the snippets,
> but there’s nothing that’s clear enough (simple enough?) for me to
> u
Assuming that you mean arpeggios in the sense of a chord spelt out as a series
of notes, then there is an example of cross-staff slurs here:
http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-keyboards#changing-staff-manually
--
Phil Holmes
- Original Message
I'm trying to score a piano piece that has cross-staff slurs on arpeggios. I've
searched the documentation andlooket at the snippets, but there’s nothing
that’s clear enough (simple enough?) for me to understand.
Can anyone provide a sample (or point me to one) or offer a suggestion
On Mon, Oct 04, 2010 at 09:21:49AM +0300, Dmytro O. Redchuk wrote:
> On Sun 03 Oct 2010, 14:52 Graham Percival wrote:
> > 2b. if you can't spot the problem, point them at
> > http://lilypond.org/tiny-examples.html
> This is rather for bug-lilypond, i'd say. In lilypond-user it is customary to
> sen
On Sun, Oct 3, 2010 at 8:49 PM, Carl Sorensen wrote:
> I greatly prefer having short snippets inline. That way I can read them in
> my mail reader, rather than having to open them to see what's up.
Ditto. If I ever want to compile one, I have a dedicated ~/toto.ly
file that I only use for pastin
On Sun 03 Oct 2010, 14:52 Graham Percival wrote:
> On Sun, Oct 03, 2010 at 02:37:59PM +0100, James Lowe wrote:
>
> > 1. Open Email
> > 2. Read Email. Spot problem. Reply
>
> Yes.
mutt! all-in-one, whether example is attached or inline =O]
((2Graham: i know you know,))
> > If someone sends an ly
On 10/3/10 6:36 AM, "Martin Tarenskeen" wrote:
>
>
>
> On Sun, 3 Oct 2010, Phil Holmes wrote:
>
>> There were a couple of errors in the snippet you posted - the version number
>> should be in inverted commas "", and you
>> have "arpeggi" which I assume should be arpeggio.
>
> I personally
On Sun, Oct 03, 2010 at 02:37:59PM +0100, James Lowe wrote:
> 1. Open Email
> 2. Read Email. Spot problem. Reply
Yes.
> If someone sends an ly file that is umpty-thrumpty lines long
let's add one more point:
2b. if you can't spot the problem, point them at
http://lilypond.org/tiny-examples.html
Hello,
On 03/10/2010 13:36, Martin Tarenskeen wrote:
On Sun, 3 Oct 2010, Phil Holmes wrote:
There were a couple of errors in the snippet you posted - the version
number should be in inverted commas "", and you
have "arpeggi" which I assume should be arpeggio.
I personally would prefer it i
On 3 October 2010 14:36, Martin Tarenskeen wrote:
>
> I personally would prefer it if lilypond snippets and example code in this
> mailinglist were posted as separate attachement(s) to the mail. I then just
> simply can save the snippet to disk. Now I first have to copy and paste the
> lilypond co
On Sun, 3 Oct 2010, Phil Holmes wrote:
There were a couple of errors in the snippet you posted - the version number
should be in inverted commas "", and you
have "arpeggi" which I assume should be arpeggio.
I personally would prefer it if lilypond snippets and example code in this
mailingl
Thanks, and sorry for not having provided a excellent snippet. The errors don't
appear in my full score and complete part, so 2.13.35 will do the harp part
well I think.
Haipeng
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.or
slurs in the output have a lot of space to cross,
and to my eye LilyPond does a fair job of fitting them in.
--
Phil Holmes
- Original Message -
From: 胡海鹏 - Hu Haipeng
To: lilypond-user
Sent: Sunday, October 03, 2010 12:09 PM
Subject: bad cross-staff slurs
Hello,
A
Hello,
A person reported that in the following harp passage of mine, the slurs are
blurred with the notes. He read the score generated by 2.13.24, so: Is it still
wrong in 2.13.35? How to solve the issue?
Regards
Haipeng
\version 2.13.35
headsOn = \sequential {
\override Dots #'transparent =
Kieren MacMillan wrote:
Other than making the code a little easier to read (using variables,
etc.), I don't think so… see my attached solution (truncated).
Thank you very much. Looks a lot better than my first try.
4) The last ottava; is it possible discard the dashed lines and just
letting it
Mark Polesky wrote:
B,
regarding the slurs, modifying the #'positions property of Slur would be the
ideal solution, but, for some reason, I couldn't make that solution work.
Ok - I got an example of the from Kieren which looks pretty good.
Hope this helps,
Mark
It really does Mark. Thank
Mark Polesky wrote:
Nice work, Kieren. I forgot about#'height-limit. I also forgot to
include an image file (something I'm trying to do more). Here it is:
Mark, yours is much better than the original lilypond solution,
but, particularly in the first measure, the original pdf breathed mu
almost like forever, to get the cross staff slurs to
render. I'm quite sure there must be an easier way to mark them up. Any
of you have an idea?
2) I cannot get the coda above the first bar? (couldn't get the
http://lilypond.org/doc/v2.11/input/lsr/lilypond-snippets/Repeats
to
work
Nice work, Kieren. I forgot about#'height-limit. I also forgot to
include an image file (something I'm trying to do more). Here it is:
Mark
<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-us
B,
regarding the slurs, modifying the #'positions property of Slur would be the
ideal solution, but, for some reason, I couldn't make that solution work. I
opted to use the #'avoid-slur property of TextScript to make an acceptable
(but not ideal) appearance.
Other than that, I put a bunch of idea
Hi B,
1) It took me almost like forever, to get the cross staff slurs to
render. I'm quite sure there must be an easier way to mark them up.
Any of you have an idea?
Other than making the code a little easier to read (using variables,
etc.), I don't think so… see my attache
u experts would
help me out.
The original looks like this:
http://lavender.dk/hrmpf.png
I have some questions regarding this bit:
1) It took me almost like forever, to get the cross staff slurs to
render. I'm quite sure there must be an easier way to mark them up. Any
of you have an ide
26 matches
Mail list logo
