Re: markup dynamics wrong size
Reinhold Kainhofer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 8. August 2008 schrieb Mats Bengtsson:
Mats Bengtsson wrote:
Yes, it would be very nice to be able to specify the alignment point
of a markup in a more convenient way.
I just realized that it indeed is possible to specify the horizontal
alignment point to be between two parts of a markup:
beforeaftermarkup = \markup {\right-align before \left-align after }
but it's too late at night right now for me to figure out how to set it
to be centered on a symbol (like the f in f molto).
We already had that discussion a while back (the 'Aligning sempre pp
with p...' tread starting on Feb 10) and I summarized all suggestions in
the LSR snippets I quoted in my earlier Mail.
Yes, when I was writing my answer, it suddenly felt very familiar but
since it was late at night,
my brain didn't realize to look for the email thread or possible LSR
entry. Thanks for the link.
Just a comment on the LSR entry: I wouldn't expect many people to be
able to understand
exactly how the different methods work, since there's no mention on how
the default alignment
is done. Also, it doesn't mention the obvious drawbacks of Solutions 1,
2, 3 and 5, that you need
quite some trial and error to get the numbers right.
Does anybody know why this LSR entry isn't included in the Snippet List
of the GDP
documentation. Since it only works under 2.11, it certainly would be
more relevant to
have there than in LSR, for the moment.
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup dynamics wrong size
On Fri, 08 Aug 2008 10:33:34 +0200 Mats Bengtsson [EMAIL PROTECTED] wrote: Does anybody know why this LSR entry isn't included in the Snippet List of the GDP documentation. Because it isn't tagged with docs. I think there's still a lot of snippets that could/should be included in the Snippet Lists, but: 1) somebody needs to identify them 2) somebody needs to make sure those snippets work and have good style 3) the only two volunteers for LSR are doing more useful stuff (Neil as general fixit man, and Valentin slowly doing NR 1.8) *shrug* The technical side is quite simple: a trusted LSR editor only needs to click something like 3-5 times make a snippet automagically appear in the docs. The problem is simply finding volunteers. And no, I'm not going to be involved in training and weeding out people for this task. And I don't suggest that Neil do it; there's too many technical problems that require his know-how and git access to solve. *IF* anybody is willing to this, and *IF* Valentin has the time/inclination to train them, all well and good. If not, this part fo the docs will continue to be not-so-good. Since it only works under 2.11, it certainly would be more relevant to have there than in LSR, for the moment. In this case, it should be removed from LSR and placed in input/new/. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup dynamics wrong size
2008/8/8 Graham Percival [EMAIL PROTECTED]: Because it isn't tagged with docs. I think there's still a lot of snippets that could/should be included in the Snippet Lists, but: Hem, IIRC *I* had initially tagged quite a lot of snippets that *you* made me un-tag :-) I think the documentation has tremendously improved for the past year, and this LSR integration is just brilliant (however improvable). Mats, if you happen to stumble upon snippets you find docs-worthy, *please* give me a ping and I'll be happy to correct them, tag them, and possibly even integrate them in the relevant NR subsections. Of all of us, you are the most likely to know what users look for (or don't) in the docs... 2) somebody needs to make sure those snippets work and have good style Yes, six months ago I ran a full LSR review but this should be done again (not before I'm done with my opera though). 3) the only two volunteers for LSR are doing more useful stuff (Neil as general fixit man, and Valentin slowly doing NR 1.8) Thanks for the credit :) I'm still maintaining the LSR and the bug tracker, though. And even if I might seem distant, I'm never much far away (even when I might be, I'm still working with LilyPond on a 18-hours-a-day basis...) The technical side is quite simple: a trusted LSR editor only needs to click something like 3-5 times make a snippet automagically appear in the docs. The problem is simply finding volunteers. Reinhold's dynamics snippet has been tagged as docs. It should appear in the list within 48 hours or so. I remember having ruled this one out because it was too large, too non-minimalistic for documentation purposes. In this case, it should be removed from LSR and placed in input/new/. Yeah, this is the part I'll have to postpone for now. This snippet (as well as many others) is tagged as version-specific, which means we'll be extra careful with it when the time comes. Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup dynamics wrong size
On Fri, 8 Aug 2008 22:19:41 +0200 Valentin Villenave [EMAIL PROTECTED] wrote: 2008/8/8 Graham Percival [EMAIL PROTECTED]: Because it isn't tagged with docs. I think there's still a lot of snippets that could/should be included in the Snippet Lists, but: Hem, IIRC *I* had initially tagged quite a lot of snippets that *you* made me un-tag :-) That's because you weren't doing step 2) somebody needs to make sure these snippets work and have good style. 2) somebody needs to make sure those snippets work and have good style Yes, six months ago I ran a full LSR review but this should be done again (not before I'm done with my opera though). If you did it properly the first time, and evaluated each snippet properly before approving it, you wouldn't need to do it again now. There's a *reason* that I'm so slow and nitpicky. It saves time in the long run. And IMO it's more honest to only have 4 snippets in Expressive (or whatever) that are actually working and have good style, rather than having 24 snippets with 5 broken and 15 with bad style. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup dynamics wrong size
Mats Bengtsson mats.bengtsson at ee.kth.se writes: The best solution for you is probably to use #(make-dynamic-script ... ) to define all your dynamic commands, see subsection New dynamics. Then, they will behave exactly as all the other dynamics. I haven't investigated how much tweaks would be involved to make ordinary \markup commands work better in the centered dynamics context, but you will certainly always suffer from the same lack of vertical alignment that I just pointed out in an email with subject line Re: GDP: NR 1.3 Expressive marks, second draft on the mailing list. There, you can also find hints on how to use #(make-dynamic-script ) without having to learn Scheme syntax for markup commands. /Mats Thanks - this works very well. However, I have had another issue arise from implementing this technique: Longer dynamic strings (e.g. p delicato, crescendo, etc.) that are engraved as dynamic scripts in this fashion end up getting centered, as a text string, horizontally under the notehead. This necessitates offsetting them somehow; my immediate workaround is to apply \once \override DynamicText #'extra-offset = #'( x . y ) to shift the dynamic string to the appropriate position. With this in mind, however, is there a means of doing the following: a) Defining a dynamic text string that will left-align to the notehead? This is generally what is desired for markings such as cresc. dim., plus other expressive markings (dolce, etc.) that stand alone, i.e. without a dynamic marking such as p, f, etc. b) Defining a dynamic text string that centers the dynamic mark (p, f, etc.) under the notehead as per usual, while allowing any modifiers in the string (e.g. dim., dolce, etc.) to follow to the right? I know that this latter, in particular, is a rather sophisticated request, but it would be worth being able to automate such issues that are likely to occur frequently. Regards, EF ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup dynamics wrong size
Eric Flesher wrote:
Longer dynamic strings (e.g. p delicato, crescendo, etc.) that are engraved
as dynamic scripts in this fashion end up getting centered, as a text string,
horizontally under the notehead. This necessitates offsetting them somehow; my
immediate workaround is to apply
\once \override DynamicText #'extra-offset = #'( x . y )
to shift the dynamic string to the appropriate position.
With this in mind, however, is there a means of doing the following:
a) Defining a dynamic text string that will left-align to the notehead? This is
generally what is desired for markings such as cresc. dim., plus other
expressive markings (dolce, etc.) that stand alone, i.e. without a dynamic
marking such as p, f, etc.
It's tricky (well, see below) to get the alignment into the dynamic
indication itself. However, you can add a
\once \override DynamicText #'self-alignment-X = #LEFT
before the note with the dynamics, to make it left aligned.
To do the alignment within each dynamic indication, you have to
turn off the default alignment mechanism (which just looks at the
left and right edge of the full markup and ignores the internal
alignment point of the markup) by
\override DynamicText #'X-offset = ##f
Then, you can specify the alignment within each markup:
\version 2.10.33
% Left alignment is the default for markups:
pdelicatomarkup = \markup{ p \normal-text \italic delicato }
pdelicato = #(make-dynamic-script pdelicatomarkup)
moltofmarkup = \markup{\right-align \line {\normal-text \italic molto
\dynamic f }}
moltof = #(make-dynamic-script moltofmarkup)
\relative c'{
\override DynamicText #'X-offset = ##f
c \moltof d \pdelicato
}
b) Defining a dynamic text string that centers the dynamic mark (p, f, etc.)
under the notehead as per usual, while allowing any modifiers in the string
(e.g. dim., dolce, etc.) to follow to the right?
One possibility is to use the above described method with
\halign #0.8 ...
as a replacement for
\left-align
for example (you may need some other value than 0.8, use trial and error).
See the documentation of \halign at
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Align
for more information.
However, if the dynamic mark is to be followed by dim, then the
normal solution is
\version 2.10.33
\relative c'{ \setTextDim c \f \ d e f g a b c \! }
The manual describes how to change the text to something else, but
conceptually, this is perhaps not the best solution for p dolce, for
example,
even though it will provide the desired layout.
I know that this latter, in particular, is a rather sophisticated request, but
it would be worth being able to automate such issues that are likely to occur
frequently.
Yes, it would be very nice to be able to specify the alignment point
of a markup in a more convenient way.
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup dynamics wrong size
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Donnerstag, 7. August 2008 schrieb Eric Flesher: Mats Bengtsson mats.bengtsson at ee.kth.se writes: The best solution for you is probably to use #(make-dynamic-script ... ) to define all your dynamic commands, see subsection New dynamics. Then, they will behave exactly as all the other dynamics. I haven't investigated how much tweaks would be involved to make ordinary \markup commands work better in the centered dynamics context, but you will certainly always suffer from the same lack of vertical alignment that I just pointed out in an email with subject line Re: GDP: NR 1.3 Expressive marks, second draft on the mailing list. There, you can also find hints on how to use #(make-dynamic-script ) without having to learn Scheme syntax for markup commands. /Mats Thanks - this works very well. However, I have had another issue arise from implementing this technique: Longer dynamic strings (e.g. p delicato, crescendo, etc.) that are engraved as dynamic scripts in this fashion end up getting centered, as a text string, horizontally under the notehead. This necessitates offsetting them somehow; my immediate workaround is to apply \once \override DynamicText #'extra-offset = #'( x . y ) to shift the dynamic string to the appropriate position. Check the LSR: http://lsr.dsi.unimi.it/LSR/Item?id=393 While all the different methods look similare in lilypond 2.10 (which is the version the LSR is running), in 2.11 there are significant differences in them. b) Defining a dynamic text string that centers the dynamic mark (p, f, etc.) under the notehead as per usual, while allowing any modifiers in the string (e.g. dim., dolce, etc.) to follow to the right? You might try to generalize the ideas from the snippet to achieve this. Cheers, Reinhold - -- - -- Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung Jung-Wien, http://www.jung-wien.at/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIm3Q0TqjEwhXvPN0RAospAKDVB4GB9bqIgtTupVmUwlmi2Q9WSgCeI5vR v5djjZftBTyAnhWcsmpgefE= =e1nV -END PGP SIGNATURE- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup dynamics wrong size
Mats Bengtsson wrote:
Yes, it would be very nice to be able to specify the alignment point
of a markup in a more convenient way.
I just realized that it indeed is possible to specify the horizontal
alignment point to be between two parts of a markup:
beforeaftermarkup = \markup {\right-align before \left-align after }
but it's too late at night right now for me to figure out how to set it
to be centered on a symbol (like the f in f molto).
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup dynamics wrong size
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 8. August 2008 schrieb Mats Bengtsson:
Mats Bengtsson wrote:
Yes, it would be very nice to be able to specify the alignment point
of a markup in a more convenient way.
I just realized that it indeed is possible to specify the horizontal
alignment point to be between two parts of a markup:
beforeaftermarkup = \markup {\right-align before \left-align after }
but it's too late at night right now for me to figure out how to set it
to be centered on a symbol (like the f in f molto).
We already had that discussion a while back (the 'Aligning sempre pp
with p...' tread starting on Feb 10) and I summarized all suggestions in
the LSR snippets I quoted in my earlier Mail.
Cheers,
Reinhold
- --
- --
Reinhold Kainhofer, Vienna University of Technology, Austria
email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/
* Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
* K Desktop Environment, http://www.kde.org, KOrganizer maintainer
* Chorvereinigung Jung-Wien, http://www.jung-wien.at/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIm4PWTqjEwhXvPN0RAtOFAKCLlM9Nl53X4JYrUsOgNy4Jr5DyoQCgh02D
IytD+dPvrHA7gxCBzROoKwI=
=Hy2Z
-END PGP SIGNATURE-
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup dynamics wrong size
The best solution for you is probably to use #(make-dynamic-script ... )
to define all your dynamic commands, see subsection New dynamics.
Then, they will behave exactly as all the other dynamics.
I haven't investigated how much tweaks would be involved to make
ordinary \markup commands work better in the centered dynamics context,
but you will certainly always suffer from the same lack of vertical
alignment that I just pointed out in an email with subject line Re:
GDP: NR 1.3 Expressive marks, second draft on the mailing list. There,
you can also find hints on how to use #(make-dynamic-script ) without
having to learn Scheme syntax for markup commands.
/Mats
Eric Flesher wrote:
Wondering if anyone has experienced the following problem:
When creating new centered dynamics in a piano staff in ver. 2.11.55
(and several earlier versions) using \markup, three things happen:
1. the markup text created is significantly larger than the normal
dynamic size
2. the text does not align with other dynamic markings
3. the presence of the markup text forces additional space between the
staves
The dynamic marking concerned is contained in a variable thus:
pocoF = \markup { \italic poco \dynamic f }
and is deployed locally as follows:
\times 4/5 { s16 s\mp s s-\pocoF s\ } \times 4/5 { s8\! s\mp s16 } s4
(I would include more code, but the file is extremely long.)
Any idea what might be wrong here, and how this could be fixed?
Thanks,
EF
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: markup dynamics wrong size
In addition to my previous answer: The size of the markup text is larger
since the template contains
the line:
\override TextScript #'font-size = #2
If you just remove that line, you should get the same size as the normal
dynamics.
The question is why the setting was done in the first place. Perhaps
it's just a remainder
from some ancient version where this setting made sense, and nobody has
used the
template with text or \markup command lately.
/Mats
Eric Flesher wrote:
Wondering if anyone has experienced the following problem:
When creating new centered dynamics in a piano staff in ver. 2.11.55
(and several earlier versions) using \markup, three things happen:
1. the markup text created is significantly larger than the normal
dynamic size
2. the text does not align with other dynamic markings
3. the presence of the markup text forces additional space between the
staves
The dynamic marking concerned is contained in a variable thus:
pocoF = \markup { \italic poco \dynamic f }
and is deployed locally as follows:
\times 4/5 { s16 s\mp s s-\pocoF s\ } \times 4/5 { s8\! s\mp s16 } s4
(I would include more code, but the file is extremely long.)
Any idea what might be wrong here, and how this could be fixed?
Thanks,
EF
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
markup dynamics wrong size
Wondering if anyone has experienced the following problem:
When creating new centered dynamics in a piano staff in ver. 2.11.55
(and several earlier versions) using \markup, three things happen:
1. the markup text created is significantly larger than the normal
dynamic size
2. the text does not align with other dynamic markings
3. the presence of the markup text forces additional space between
the staves
inline: dynamics.JPEG
The dynamic marking concerned is contained in a variable thus:
pocoF = \markup { \italic poco \dynamic f }
and is deployed locally as follows:
\times 4/5 { s16 s\mp s s-\pocoF s\ } \times 4/5 { s8\! s\mp s16 } s4
(I would include more code, but the file is extremely long.)
Any idea what might be wrong here, and how this could be fixed?
Thanks,
EF___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
