[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New LilyPond tutorial
From: |
Urs Liska |
Subject: |
Re: New LilyPond tutorial |
Date: |
Thu, 25 Aug 2011 01:15:15 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11 |
Am 24.08.2011 11:49, schrieb Reinhold Kainhofer:
Am Wednesday, 24. August 2011, 02:00:16 schrieb Urs Liska:
Hello list,
I have just put a new tutorial online. You can read it at
http://www.ursliska.de/73.0.html
[..]
Really nice.
Comments that arent' interesting for the public (linguistic details for
example) please privately, LilyPond related comments on the list.
1) You know that you can give dynamics their own directions? So you can simply
write (in rightOne):
<bes bes'>4^\<(
instead of
\dynamicUp
<bes bes'>4\<( ...
\dynamicNeutral
Oops. Of course I know that. But didn't I write something like "forest
for the trees"?
2) Resetting the tie direction to the default in rightOne is much simpler than
you thought. In particular, \voiceOne simply sets (i.e. does the same as
\override) the 'direction property of several grobs, including Tie.
So, to get the oneVoice-behaviour, all you have to do is to revert the Tie's
'direction property to the default:
tweakSix = {
% Simulate \oneVoice style ties
\once \revert Tie #'direction
}
<a a'>4<b b'> \tweakSix<cis cis'>~ q<d d'>
Note that now the \tweakSix has to be placed right before the tie's start,
which is what one would intuitively expect.
No, I wasn't aware of this.
Your solution is definitely better than mine. But I even like Janek's
version more for this.
3) You manually use \oneVoice ... \voiceOne to get proper rest merging.
LilyPond can do that automatically:
http://lsr.dsi.unimi.it/LSR/Item?id=336
I thought that this function has been included into LilyPond, but I can't find
it anywhere...
Ah, it's been started, but never finished:
http://code.google.com/p/lilypond/issues/detail?id=1228
Well, I dont merge the rests but skip them in one voice.
I'll look into this.
4) Thanks for tellung us about the tupletSpannerDuration... I wasn't aware of
that and always copied dozens of "} \times 2/3 {" strings when I wrote some
string ensemble works... This makes life way easier! Amazing, even after years
of using and developing LilyPond, you can learn something new any day!
OK, this makes my embarrassment over 1) smaller ;-)
@all who commented on the coding:
I will collect this sort of feedback and will deal with it when I've
come home from vacation.
Some of the suggestions will replace my coding, some I will comment in
the text and for some I will reference to the respective email comments
(pointing even more to the community aspect).
Cheers,
Reinhold
Re: New LilyPond tutorial, Mike Solomon, 2011/08/24
Re: New LilyPond tutorial, Henning Hraban Ramm, 2011/08/24
Re: New LilyPond tutorial, Reinhold Kainhofer, 2011/08/24