Re: Finetuning TextSpanner beginning and end positions?

2019-05-06 Thread Werner LEMBERG
> [...] I generally understand "padding" as the amount of whitespace > that should be reserved between objects. I never even noticed that > property since in my mind I was looking for something that could in > no way have something to do with it. Anyways, it's not the first > time I find some

Re: Finetuning TextSpanner beginning and end positions?

2019-05-06 Thread Andrew Bernard
Hi Stefano, There are many threads in the archives about this inconsistency with text spanners. It's very confusing for users, nad ends up wasting lots of time. It would be great if this could be unified with the 'shorten' commands of other objects, but I realise the developers are hugely

Re: Finetuning TextSpanner beginning and end positions?

2019-05-06 Thread Stefano Troncaro
Hi Harm, honestly because I generally understand "padding" as the amount of whitespace that should be reserved between objects. I never even noticed that property since in my mind I was looking for something that could in no way have something to do with it. Anyways, it's not the first time I find

Re: Finetuning TextSpanner beginning and end positions?

2019-05-06 Thread Thomas Morley
Am Di., 7. Mai 2019 um 00:23 Uhr schrieb Stefano Troncaro : > > Hi Rick, > > Thank you for your answer. I didn't know that 'bound-details had an X > property. It does what I need but it can get tedious to use because I need to > specify a number from the start of the spanner (or the system if

Re: Finetuning TextSpanner beginning and end positions?

2019-05-06 Thread Stefano Troncaro
Hi Rick, Thank you for your answer. I didn't know that 'bound-details had an X property. It does what I need but it can get tedious to use because I need to specify a number from the start of the spanner (or the system if the spanner is broken into many systems). It takes some trial and error to

Re: Finetuning TextSpanner beginning and end positions?

2019-05-06 Thread Rick Kimpel
Stefano, Have you tried bound-details? I use this for glissandi, and it works well. http://lilypond.org/doc/v2.19/Documentation/internals/textspanner Rick From: lilypond-user on behalf of Stefano Troncaro Sent: Monday, May 6, 2019 11:50 AM To: lilypond-user

Finetuning TextSpanner beginning and end positions?

2019-05-06 Thread Stefano Troncaro
Hello again everyone, I was expecting to be able to use shorten-pair for this in the same way that is used with Hairpins, but it doesn't seem to work and I can't seem to find what property I need to tweak. Any pointers? Thanks for your help, Stéfano

Re: fingering

2019-05-06 Thread Robin Bannister
Gianmaria Lari wrote: If I'm not wrong to generate the two variables (myMusic and myFing) from the previous code should not be that difficult. 1 I duplicate the music expression 2 In the variable where I want to put the music I remove the fingering 3 In the variable where I want to put the

Re: fingering

2019-05-06 Thread Gianmaria Lari
Dear Robin you wrote: > [...] You should limit lilypond to one staff by saying > \new Staff << \myMusic \myFing >> > > > That looks better, but it is still not equivalent. > Try changing the s-2 to s_2: > the notehead and the fingering collide. > To avoid that you should also limit lilypond

Re: fingering

2019-05-06 Thread Gianmaria Lari
I found some solution that I post here to get some feedback and/or other suggestions. Here they are 4 different ways to add fingering to a musical expression: *1 Standard:* \version "2.21.0" \fixed c' {a-1 c' f'-\finger\markup\circle 3 a'-4} *2 Different context *(thanks Pierre

Re: fingering

2019-05-06 Thread Robin Bannister
Gianmaria Lari wrote: But when I finished to enter the fingering, I would definitely prefer having the fingering instruction separated by the music. Something like this (NB: it does not work correctly but I hope the idea is clear): \version "2.21.0" myMusic = {a4 b c' d'} myFing = {s4-1 s-2

Re: landscape orientation differences between versions

2019-05-06 Thread Stephan Schöll
Let me first read through http://lilypond.org/doc/v2.19/Documentation/contributor/documentation-work just for me to imagine what this might mean for me. I'll come back to you afterwards. Regards Stephan Am 04.05.2019 um 23:58 schrieb Carl Sorensen: > > > On 5/4/19, 2:51 PM, "mu...@gmx.ch"

Re: fingering

2019-05-06 Thread Gianmaria Lari
Ciao Stephane! On Mon, 6 May 2019 at 11:23, Stephan Schöll wrote: > Despite of my newbie status on the list, let me ask back: > > What's your intention with separating dynamics, the notes and the > fingerings? > > If the separation is only for displaying purposes in a specific staff, I > would

Re: fingering

2019-05-06 Thread Gianmaria Lari
On Mon, 6 May 2019 at 11:16, Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com> wrote: > Hi Gianmaria, > I suppose you'll have to create/modify your own contect, say > 'Fingerings, such as : > > \version "2.21.0" > myMusic = {a4 b c' d'} > myFing = {s4-1 s-2 s-3 s-4} > << >

Re: fingering

2019-05-06 Thread Stephan Schöll
Despite of my newbie status on the list, let me ask back: What's your intention with separating dynamics, the notes and the fingerings? If the separation is only for displaying purposes in a specific staff, I would simply remove the corresponding engravers from the voice \remove

Re: fingering

2019-05-06 Thread Pierre Perol-Schneider
Hi Gianmaria, I suppose you'll have to create/modify your own contect, say 'Fingerings, such as : \version "2.21.0" myMusic = {a4 b c' d'} myFing = {s4-1 s-2 s-3 s-4} << \new Staff \myMusic \new Dynamics \with { \consists Fingering_engraver } \myFing >> See:

Re: Multimeasure rests not compressed

2019-05-06 Thread Thomas Morley
Am Mo., 6. Mai 2019 um 03:56 Uhr schrieb Davide Liessi : > > Dear all, > > in the following example I expected to see two identical scores, but > in the first one the full bar rests after the rehearsal mark are not > compressed. > > \version "2.19.82" > > \score { > \compressMMRests > \new

fingering

2019-05-06 Thread Gianmaria Lari
I normally enter fingering instruction using the "note-digit" convention ( http://lilypond.org/doc/v2.18/Documentation/notation/inside-the-staff#fingering-instructions) like this: \version "2.21.0" {a4-1 b-2 c'-3 d'-4} This way of proceeding it's in my opinion the easiest and less error prone