Re: just a frustrated yop…
On Mon, Feb 17, 2014 at 2:50 AM, Kieren MacMillan
kieren_macmil...@sympatico.ca wrote:
There are very few out there who are pushing her farther, or promoting her
more enthusiastically, than I.
Hi Kieren,
(at least) two can play this game :-)
All we would need — as I’ve suggested many times in the past — is a setting
which said “this grob can move left/right/up/down to avoid collisions”
That would be neat, indeed. Another thing I've found myself wishing
for (which remotely relates to your specific example), would be the
ability to automatically tilt (within limits) hairpin spanners, so
that the dynamic at the end stays a bit closer to the staff.
And another thing -- totally unrelated this time -- I've been wishing
for, would be that the determination of stem direction would be made
more intelligent and context-aware; for example the following example
would look a tad better if all the stems were printed upwards:
\relative c' {
g' a b a g8 a b a g2
}
(I'll be adding that to the tracker if I'm told there's something that
can reasonably be expected here.)
Cheers,
Valentin.
attachment: toto.preview.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: just a frustrated yop...
2014-02-18 11:20 GMT+01:00 Valentin Villenave valen...@villenave.net:
On Mon, Feb 17, 2014 at 2:50 AM, Kieren MacMillan
kieren_macmil...@sympatico.ca wrote:
There are very few out there who are pushing her farther, or promoting her
more enthusiastically, than I.
Hi Kieren,
(at least) two can play this game :-)
All we would need -- as I've suggested many times in the past -- is a
setting which said this grob can move left/right/up/down to avoid
collisions
IMO this is possible but too computationally expensive unless you
explicitly mark single grobs to let him move. Which is not a big step
forward.
And another thing -- totally unrelated this time -- I've been wishing
for, would be that the determination of stem direction would be made
more intelligent and context-aware; for example the following example
would look a tad better if all the stems were printed upwards:
\relative c' {
g' a b a g8 a b a g2
}
(I'll be adding that to the tracker if I'm told there's something that
can reasonably be expected here.)
I really believed lily already did this. In fact, that's what lilypond
page in Spahish wikipedia says. Where did this come from? I must have
been dreaming.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: just a frustrated yop…
See http://lsr.dsi.unimi.it/LSR/Snippet?id=751
\relative c' {
g' a b a g8 a b a g2
}
\layout {
\context {
\Voice
\consists Melody_engraver
\override Stem #'neutral-direction = #'()
}
}
--
Phil Holmes
- Original Message -
From: Valentin Villenave valen...@villenave.net
To: Kieren MacMillan kieren_macmil...@sympatico.ca
Cc: Lilypond-User Mailing List lilypond-user@gnu.org
Sent: Tuesday, February 18, 2014 10:20 AM
Subject: Re: just a frustrated yop…
On Mon, Feb 17, 2014 at 2:50 AM, Kieren MacMillan
kieren_macmil...@sympatico.ca wrote:
There are very few out there who are pushing her farther, or promoting her
more enthusiastically, than I.
Hi Kieren,
(at least) two can play this game :-)
All we would need — as I’ve suggested many times in the past — is a
setting which said “this grob can move left/right/up/down to avoid
collisions”
That would be neat, indeed. Another thing I've found myself wishing
for (which remotely relates to your specific example), would be the
ability to automatically tilt (within limits) hairpin spanners, so
that the dynamic at the end stays a bit closer to the staff.
And another thing -- totally unrelated this time -- I've been wishing
for, would be that the determination of stem direction would be made
more intelligent and context-aware; for example the following example
would look a tad better if all the stems were printed upwards:
\relative c' {
g' a b a g8 a b a g2
}
(I'll be adding that to the tracker if I'm told there's something that
can reasonably be expected here.)
Cheers,
Valentin.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
attachment: VV.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: just a frustrated yop…
Valentin Villenave valen...@villenave.net writes:
And another thing -- totally unrelated this time -- I've been wishing
for, would be that the determination of stem direction would be made
more intelligent and context-aware; for example the following example
would look a tad better if all the stems were printed upwards:
\relative c' {
g' a b a g8 a b a g2
}
(I'll be adding that to the tracker if I'm told there's something that
can reasonably be expected here.)
URL:http://lilypond.org/doc/v2.18/Documentation/notation/inside-the-staff#Selected-Snippets-40
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: just a frustrated yop...
On Tue, Feb 18, 2014 at 11:31 AM, Francisco Vila paconet@gmail.com wrote: I really believed lily already did this. In fact, that's what lilypond page in Spahish wikipedia says. Where did this come from? I must have been dreaming. Yes, I've had that dream too for quite some time. But my dream is crushed when I see that output :-) Anyway, here goes nothing: http://code.google.com/p/lilypond/issues/detail?id=3870 Cheers, Valentin. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: just a frustrated yop…
Am 18.02.2014 11:20, schrieb Valentin Villenave:
[...]
And another thing -- totally unrelated this time -- I've been wishing
for, would be that the determination of stem direction would be made
more intelligent and context-aware; for example the following example
would look a tad better if all the stems were printed upwards:
\relative c' {
g' a b a g8 a b a g2
}
I think that LilyPond would have to *understand* the intention of the
composer (or at least the structure of the music) in order to do that
automatically.
Hehe, something like this:
\set doWhatIMean = ##t
...music ...
for the enhanced LilyPond features, and
\unset doWhatIMean
for the standard behavior as currently implemented.
;-)
Marc
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: just a frustrated yop…
On Tue, Feb 18, 2014 at 11:37 AM, David Kastrup d...@gnu.org wrote: URL:http://lilypond.org/doc/v2.18/Documentation/notation/inside-the-staff#Selected-Snippets-40 OK, you got me. (Too bad it only applies to the middle note, however. What would be be great is if its scope could be made tweakable.) (Why isn't this engraver consisted by default? Overhead costs?) On Tue, Feb 18, 2014 at 11:57 AM, Marc Hohl m...@hohlart.de wrote: \set doWhatIMean = ##t Yes! That. :-) Valentin. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: just a frustrated yop…
2014-02-17 2:50 GMT+01:00 Kieren MacMillan kieren_macmil...@sympatico.ca: But this screenshot is a perfect example of how she drives me crazy sometimes: All we would need — as I’ve suggested many times in the past — is a setting which said “this grob can move left/right/up/down to avoid collisions” (with, in a perfect world, a maximum amount of offset in either staff spaces or moments), and the situation seen here could be resolved automatically. I would say that the character indication is allowed to move left+right+up+down, the dynamics is allowed to move up+down, and the rehearsal mark is allowed to move up+down; then Lily would know to push “+Jack:” back to the left a bit, which would allow the dynamics and mark to drop into that huge gap below them. Yes, this is irritating me since forever, too. But it's not something i could do right now :( best, Janek inline: Screen Shot 2014-02-16 at 8.42.02 PM.png___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
just a frustrated yop…
Hello all,As you all well know, I love Lilypond… to the depths of her convoluted code.There are very few out there who are pushing her farther, or promoting her more enthusiastically, than I.But this screenshot is a perfect example of how she drives me crazy sometimes:All we would need — as I’ve suggested many times in the past — is a setting which said “this grob can move left/right/up/down to avoid collisions” (with, in a perfect world, a maximum amount of offset in either staff spaces or moments), and the situation seen here could be resolved automatically. I would say that the character indication is allowed to move left+right+up+down, the dynamics is allowed to move up+down, and the rehearsal mark is allowed to move up+down; then Lily would know to push “+Jack:” back to the left a bit, which would allow the dynamics and mark to drop into that huge gap below them.I certainly realise this would add some time to the spacing engine’s work — but the decision-making algorithm should only engage when collisions are detected, so it’s not like every single grob would be involved on every single pass.le sighKieren.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
