In 2.14 we should be able to do this (because we already can in the
development version) :
% tieDynamic to the next dynamic mark, so that they are placed as a
% group
tieDynamic = #(make-music 'CrescendoEvent 'span-direction START
'span-type 'text 'span-text )
{
d'16 \ d'' d''\!
On Tue, Oct 26, 2010 at 3:51 AM, Keith E OHara k-ohara5...@oco.net wrote:
Please don't ask the poor users to learn another new concept, if we can
extend what they have learned already.
Sure, let's ask them to use dirty hacks instead. That should work well :-)
More seriously, if this
On Tue, 26 Oct 2010 02:13:49 -0700, Valentin Villenave wrote:
the goal would be to improve LilyPond's *default*
behaviour, not to require users to change the syntax they use. Now, if
power-users happen to want to modify the new behavior (and even
possibly disable it), they should *also* have be
On Tue, 26 Oct 2010 13:14:42 -0700, Werner LEMBERG wrote:
it looks like `dynamic-gap.png' (attached), and the huge gap between
the crescendo and decrescendo hairpin is not what I expect.
Additionally, I get a nasty warning
programming error: Improbable offset for stencil: -nan staff space
% tieDynamic to the next dynamic mark, so that they are placed as
% a group
tieDynamic = #(make-music 'CrescendoEvent 'span-direction START
'span-type 'text 'span-text )
Hmm, using 2.13.37, this has nasty side effects and doesn't yield
the expected result...
Hmm, wondering
On Tue, Oct 26, 2010 at 9:34 PM, Keith E OHara k-ohara5...@oco.net wrote:
I might have been over-reacting after my recent difficulties trying to use
CueVoice for purposes formerly recommended in the manual. Or, it may just
be that old people always caution against new things; it's part of our
On Tue, 26 Oct 2010 14:20:27 -0700, Valentin Villenave valen...@villenave.net
wrote:
You're right. I think I'm gonna suggest a patch for our 2.14
Documentation. (attached)
No, Wait! Trevor and I already worked out a revision . . .
Ah. Very funny.
Where were you when I was defending the need
On Fri, 22 Oct 2010 00:17:05 -0700, Valentin Villenave wrote:
I could imagine a way of making LilyPond aware of nearly-adjacent
dynamics. Something like a 'neighborhood property, that would take a
ly:moment as argument... If anyone else wants to help write a feature
request, I'll add it to the
Hi,
2010/10/19 Valentin Villenave valen...@villenave.net
On Tue, Oct 19, 2010 at 11:43 AM, Jan Warchoł
lemniskata.bernoulli...@gmail.com wrote:
(...) Lily places all related dynamics at the same vertical position
level
Er, it seems that we're already doing that
Not exactly that. This
On Oct 21, 2010, at 5:43 PM, Jan Warchoł wrote:
Hi,
2010/10/19 Valentin Villenave valen...@villenave.net
On Tue, Oct 19, 2010 at 11:43 AM, Jan Warchoł
lemniskata.bernoulli...@gmail.com wrote:
(...) Lily places all related dynamics at the same vertical position level
Er, it seems that
On Thu, Oct 21, 2010 at 6:08 PM, James Bailey
derhindem...@googlemail.com wrote:
Unfortunately, lilypond doesn't care about your opinion. You end a hairpin,
and then at some later point in time start a new one. Lilypond is just a
dumb program, it doesn't care if it's only a 16th note later or
In most music I see out there, I've noticed that related dynamics (and often
markup) are usually parallel (such that if you drew a horizontal line, it
would meet both at the same vertical position). In fact, I'm hard pressed to
think of a situation where they're not in the sheet music I've seen
a'\p?var1 c' d' b'\mf?var1 f'\markup{asdf}?var1 d''2\?var2 e''4\!
c''\?var2 b'\!
I mean, all the var1 dynamics are parallel with each other. All the var2
dynamics are parallel with each other. However, the var1 dynamics are not
parallel with the var2 ones (unless by coincidence).
--
View this
2010/10/19 Cordilow arv...@gmail.com
In most music I see out there, I've noticed that related dynamics (and
often
markup) are usually parallel (such that if you drew a horizontal line, it
would meet both at the same vertical position). In fact, I'm hard pressed
to
think of a situation where
On Tue, Oct 19, 2010 at 11:43 AM, Jan Warchoł
lemniskata.bernoulli...@gmail.com wrote:
Lily places all dynamics from this group at the same vertical position level
if the difference is greater, Lily divides this group of related
dynamics in more groups in such a way that the differencies
If I understand correctly, is this similar to the (rather hackish, imo) lsr
snippet? http://lsr.dsi.unimi.it/LSR/Item?id=450
On Oct 19, 2010, at 8:46 AM, Cordilow wrote:
In most music I see out there, I've noticed that related dynamics (and often
markup) are usually parallel (such that if
If I understand correctly, is this similar to the (rather hackish, imo) lsr
snippet? http://lsr.dsi.unimi.it/LSR/Item?id=450
I don't think so. What I mean is with multiple notes so that the dynamics
above each note (not the same note) are the same height above the staff.
--
View this message
It's a nice idea, however i'd prefer that LilyPond would do this more
automatically (the less input user needs to type the better).
Lily forgets about dynamics that are not related to any other dynamics,
i.e.
too far apart (like 2 full measures apart or 30 staff spaces apart) …
It's a good
On Tue, Oct 19, 2010 at 11:43 AM, Jan Warchoł
lemniskata.bernoulli...@gmail.com wrote:
Lily forgets about dynamics that are not related to any other dynamics, i.e.
too far apart (like 2 full measures apart or 30 staff spaces apart)
for each group of related dynamics:
for each dynamic in
On Oct 19, 2010, at 7:59 PM, Cordilow wrote:
If I understand correctly, is this similar to the (rather hackish, imo) lsr
snippet? http://lsr.dsi.unimi.it/LSR/Item?id=450
I don't think so. What I mean is with multiple notes so that the dynamics
above each note (not the same note) are the
LilyPond where one could add a tag to certain dynamics to make them
parallel: e.g.
a'\p?var1 c' d' b'\mf?var1 f'\markup{asdf}?var1 d''2\?var2 e''4\!
c''\?var2 b'\!
James wrote:
If I understand correctly, is this similar to the (rather hackish, imo) lsr
snippet?
On Tue, Oct 19, 2010 at 9:03 PM, Keith E OHara k-ohara5...@oco.net wrote:
Some people like to put all dynamics at exactly the same height:
http://lsr.dsi.unimi.it/LSR/Item?id=357
Speaking of which, this snippet is slightly out-of-date since the
Dynamics context is now built-in and ready-to-use.
22 matches
Mail list logo
