Another option is to use #'extra-offset to reposition
objects after LilyPond has finished its layout. This
is always a last resort, as you have to reposition
objects manually and it is your responsibility to
ensure that other collisions don't ensue. But in this
case it might solve your problem.
Hi Kieren
To be honest, I don't know, but it sounds promising.
When we reach that point in GDP I guess we'll look at this
template rather critically. IMO if we are to keep the
Piano-centred dynamics context which is currently created
manually in the template, it should be built-in so this
Valentin Villenave skrev:
In the LSR? Might be worth giving it a shot. I uncommented the code,
so users can see the full Prelude if they want to (besides, it's cool
to finally use the Large Snippet feature once in a while).
Dear valentin, Please test your code before you publish it to the
Hi Peter,
I had tried this before, by adding these three lines to the
Dynamics context
and leaving the rest as in the original template. [...] It does not
prevent collisions
Interesting... well, it was worth a shot. =\
the Barlines do not become transparent where collisions occur.
Hi Peter,
Well, thanks for replying, but of course it didn't solve the problem.
I know... sorry.
for one who engraves only piano music, it is the harsh reality that
the results
of lilypond are not that pretty when one has the insane idea of
centering dynamics...
[n.b. Perhaps again
Dear Lilypond-users,
as far as I understood this topic, one must have experiences with
writing programs. Do You think it is quite a complicated thing, is it
worth spending a lot of time with it?
Can You give proposals for easy-to-learn books?
Or should I better use a progamm like Finale or
Stefan Thomas skrev:
as far as I understood this topic, one must have experiences with
writing programs.
Not at all.
But one of the great things about lilypond is that /if/ you do have
experience with writing programs then you can take the experience to a
whole new level.
The topic of this
Valentin and Rune are discussing an advanced method for creating
notes automatically. I've used lilypond for five years, and I've
never touched the stuff that they're fiddling with.
To evaluate whether lilypond is good for you, I recommend reading
the tutorial.
Cheers,
- Graham
On Mon, 10 Dec
Rune Zedeler wrote:
Stefan Thomas skrev:
as far as I understood this topic, one must have experiences with
writing programs.
Not at all.
But one of the great things about lilypond is that /if/ you do have
experience with writing programs then you can take the experience to
a whole new
Wilbert Berendsen wrote:
Isn't it a good idea to add the instrument_name_engraver by default to the
ChoirStaff, GrandStaff and StaffGroup contexts?
Sure! Why not go one step further and remove the PianoStaff context
completely.
By now, the only difference compared to a GrandStaff is the
If you refer to the extended syntax
#(set-accidental-style 'STYLE #('CONTEXT))
the current manual is wrong. The correct syntax is
#(set-accidental-style 'STYLE 'CONTEXT)
For example, in the example that's repeated over and over in this section,
you can do the setting once for the full score by
On Mon, 10 Dec 2007 16:48:38 +0100
Mats Bengtsson [EMAIL PROTECTED] wrote:
If you refer to the extended syntax
#(set-accidental-style 'STYLE #('CONTEXT))
the current manual is wrong. The correct syntax is
#(set-accidental-style 'STYLE 'CONTEXT)
...
Do you want me to fix this section, or can
Kieren MacMillan wrote on 10 December 2007 14:28
However, it did give me a brainstorm that might
be helpful: is there
a way to wrap (by default) every dynamic in a
white outline? That
way, the font outline would mask out the barline
immediately around
the f (or whatever the
Stefan Thomas skrev:
thanks for Your fast answer, but I think this stuff is a little bit
to complicated for me, at least at the moment.
Yeah, this is one of those old snippets that has been modified over time
as the lilypond syntax was changed - getting more and more messed up as
different
Hi,
I'm typesetting large choir pieces, and some orchestral instruments should be
combined in the full score into one staff. However, when one of the two
instruments (e.g. first and second hornets) is quiet, I don't want the Solo
I or Solo II written above, but rather real rests printed. An
Hello,
I'm trying not to ask dumb questions, but I'm new here, so undoubtedly I
will from time to time.
Anyhow, two problems with Notepad when invoked via right-click menu for a
.ly file:
(1) - search does not work. At all. Doesn't matter how you invoke it (F3,
from menu, or Ctrl-F), which
How about using a second voice, introduced temporarily while
you want the horns in two parts, like this? It
automatically makes the second horn stems go down, but this
seems no bad thing.
\new Staff
\key e \major
\time 4/4
\relative c'' {
R1 | % Both
{R1 | b2.\f a4 | gis4
Hi Trevor,
Well, there is, although I didn't know it until I went looking!
Yes, you've hit on exactly what I was hoping might be out there... =)
For future reference (e.g., LSR?), I've modified your [lovely]
example to show both outcomes.
Best wishes,
Kieren.
So do you right click and choose edit source? or do you right click and
choose open with and then notepad?
It seems edit source opens lilypad - which does as you say. But if you
open with notepad it works as you expect notepad to work.
I really like the lilypondtool addition to jedit - It
Hello,
is it possible to produce horizontal beams somehow?
\override Beam #'damping = #10 does not work, as already reported
last year:
http://code.google.com/p/lilypond/issues/detail?id=116can=1q=beam
Thank you,
Thomas
Lilypond 2.11.34
___
Thomas
You can override the 'positions property of Beam to place a
beam at any position and angle. This property allows you to
specify the precise heights of the two ends of the beam. If
they are the same the beam is horizontal. Here's an
example:
\version 2.11.34
\relative c'' {
c8 g e c
2007/12/10, Rune Zedeler [EMAIL PROTECTED]:
Dear valentin, Please test your code before you publish it to the LSR.
The new version is even more messed up than the old one.
Gosh... the point is, my computer is broken (again) and I really had
*no* way to check the code.
Thanks to your thorough
Thomas Scharkowski skrev:
is it possible to produce horizontal beams somehow?
\override Beam #'damping = #10 does not work, as already reported
last year:
The value #10 is not big enough
Try
\override Beam #'damping = #+inf.0
:-)
-Rune
Valentin Villenave skrev:
Gosh... the point is, my computer is broken (again) and I really had
*no* way to check the code.
Sorry. I forgot.
Thanks to your thorough work, I'll correct it right now. If I may ask
you one more favor, can you please check what *exactly* was messed up?
Probably
Right! The only real reason to use \partcombine (which is
well-known to be partly broken and inflexible) is if you want
to be able to typeset several versions of the same music,
some with the parts on separate staves and some with the
parts combined into a single stave. If you only want the
Op maandag 10 december 2007, schreef Mats Bengtsson:
Wilbert Berendsen wrote:
Isn't it a good idea to add the instrument_name_engraver by default to
the ChoirStaff, GrandStaff and StaffGroup contexts?
Sure!
There is a little issue with the instrumentName in e.g. the ChoirStaff: when
26 matches
Mail list logo
