Hi Till
Might the tempo indication and metronome marks be better placed in the Rhythm
section? If you think so let me know, as I'm working on Rhythms right now.
Trevor D
-Original Message-
From: [EMAIL PROTECTED]
[mailto:lilypond-user-bounces+t.daniels=treda.co.u
[EMAIL
OK, I think that's partially what I am asking about. I would just
never have found that myself. I would have asked the wrong question.
I think that Zbynek and I might be asking the same question. Language
is the barrier for both of us.
Let me re-phrase my question to see if I understand this:
Hi David
I've made a note to add something about this in the section of the NR that
deals with rests. I should get to that in the next few days.
Trevor D
-Original Message-
From: [EMAIL PROTECTED]
[mailto:lilypond-user-bounces+t.daniels=treda.co.u
[EMAIL PROTECTED] Behalf Of
On 24 Feb 2008, at 21:46, Nicolas Sceaux wrote:
I use a home made emacs mode, named lyqi, which makes it possible
to enter notes and change their duration, alteration, octave, etc,
with few key strokes, and with audio feedback.
The page, with some source code, can be found here:
Mats Bengtsson [EMAIL PROTECTED] writes:
So far, there's no automatic support in LilyPond to avoid collisions
between multi-measure rests and other objects. Their vertical
position is determined by the staff-position property, which by
default is set to zero. The \voiceOne macro sets
So far, there's no automatic support in LilyPond to avoid collisions
between
multi-measure rests and other objects. Their vertical position is
determined by
the staff-position property, which by default is set to zero. The
\voiceOne macro
sets staff-position to +4 and \voiceTwo sets it to -4.
2008/2/25, Hans Aberg [EMAIL PROTECTED]:
On 24 Feb 2008, at 21:46, Nicolas Sceaux wrote:
I'm using a key map described here:
http://nicolas.sceaux.free.fr/index.php/2006/07/01/8
On Mac OS X, keyboard layouts can be created using Ukelele http://
scripts.sil.org/ukelele, though I don't
On 25 Feb 2008, at 13:23, Henning Hraban Ramm wrote:
On Mac OS X, keyboard layouts can be created using Ukelele http://
scripts.sil.org/ukelele, though I don't know if the sound generation
is possible. :-)
As far as I can see, what Nicolas describes is definitely *not*
possible with a OS
Le samedi 23 février 2008 à 21:39 -0300, Han-Wen Nienhuys a écrit :
2008/2/23, Andrew Hawryluk [EMAIL PROTECTED]:
http://www.musicbyandrew.ca/finale-lilypond-1.html
Excellent analysis!
I like these articles too! Rachmaninoff's prelude benchmarking is done
with the same quality as in the
Le dimanche 24 février 2008 à 20:31 -0300, Han-Wen Nienhuys a écrit :
Ok, here's the rub:
we have this mechanism called concave beams, see
http://lilypond.org/doc/v2.11/input/regression/collated-files#beam-concave.ly:
[hmmm, the #filename links are broken; we get the full path name now.
Is
Han-Wen Nienhuys skrev:
This is pretty obvious for single-voice notes; for chords it gets
hairier: which part of the chord notes do we use to decide this?
I think we should look at both top notes and bottom notes. We should
only make the beam horizontal if they agree that the pattern is
On Mon, 2008-01-14 at 01:59 -0800, Risto Vääräniemi wrote:
Dear All,
Risto Vääräniemi wrote:
Has this issue taken some steps backwards? I compiled both of Paul's
examples in this thread using versions 2.11.32 and 2.11.37. The first
one with headers takes two pages on both versions.
On Sun, 2008-02-24 at 22:12 -0300, Han-Wen Nienhuys wrote:
2008/2/22, Oscar van Eijk [EMAIL PROTECTED]:
Any suggestions? Is this a bug?
Yes;
without delving deeper into this, I'd say it might be related to the
recent changes wrt. page layout.
Joe?
Yes, it was caused by my previous
On Sun, 24 Feb 2008 15:48:15 +0200
Till Rettig [EMAIL PROTECTED] wrote:
I just noticed that the staff contexts of the examples in 1.1.3.5 are
PianoStaff. In 1.6 there is only mentioned GrandStaff. Which one is
the preferred one to be used?
Delete them all. That info shouldn't be in 1.6; it
i don't know where i must seek to find the local documentation...
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Le 25 févr. 08 à 14:11, Hans Aberg a écrit :
On 25 Feb 2008, at 13:23, Henning Hraban Ramm wrote:
On Mac OS X, keyboard layouts can be created using Ukelele http://
scripts.sil.org/ukelele, though I don't know if the sound generation
is possible. :-)
As far as I can see, what Nicolas
Here's the .ly files I used.
Waouh thanks !
Thanks for your newspaper !
Good good advertisement !
To prove that LilyPond is formidable, beam can be adapted easily with :
\once \override Beam #'positions = #'(-y1 . -y2)
%%---
RightHandTwo = \relative c'' {
bes, ees4 r
On 25 Feb 2008, at 21:34, Nicolas Sceaux wrote:
It's not just about producing strings. It's also about parsing the
previous
content (to find out, say, the current duration, or octave), and
remembering
previous typings (accidentals for instance). It's also about
modifying the
previous
AH! ok the light is begining to shine on this for me!
This makes perfect sense.
So far, there's no automatic support in LilyPond to avoid collisions
between
multi-measure rests and other objects. Their vertical position is
determined by
the staff-position property, which by default is
These are both valid:
{
c'2-\accent
c'2\accent
}
Should we keep the - version in the docs at all? Does it really add
anything (especially since most people use the plain \ version) ?
It might be good as an introduction to ^ and _, but OTOH we
can do ^ and _ with items that don't have any -,
Does this formula work for the ^_ thing? If we agree on this
sentence, we'll use this throughout the docs:
Dynamics (or whatever) may be manually placed above or below the
staff, for details see @ref{Controlling direction and placement}.
Implicit in this is my tentative decision to go with
On Tue, 26 Feb 2008 00:39:21 -0500
Bryan Stanbridge [EMAIL PROTECTED] wrote:
Graham Percival wrote:
Should we keep the - version in the docs at all? Does it really add
anything (especially since most people use the plain \ version) ?
We might want to keep the -\ version, because it
On Mon, Feb 25, 2008 at 9:50 PM, Graham Percival [EMAIL PROTECTED] wrote:
Interesting! However, as this example indicates, it's not
specific to articulations. We'll add info to LM 3 and
NR 3 about this.
Since there's nothing specific about articulations here, we'll
remove it from NR
On Sun, 24 Feb 2008 15:19:04 +0200
Till Rettig [EMAIL PROTECTED] wrote:
I was first wondering why writing parts is here at all, but I guess
this should not be discussed too broad now, because it had been
discuessed when we decided about the GDP chapter order. I was just
thinking that
On Mon, 25 Feb 2008 22:08:09 -0800
Patrick McCarty [EMAIL PROTECTED] wrote:
On Mon, Feb 25, 2008 at 9:50 PM, Graham Percival [EMAIL PROTECTED]
wrote:
Interesting! However, as this example indicates, it's not
specific to articulations. We'll add info to LM 3 and
NR 3 about this.
BACKGROUND
We now have a number of different terms to refer to several closely related
concepts:
* polymeter
* polymetric time signature
* double time signature
* compound time signature
(
Elsewhere -- just to add them to the mix -- I've seen:
* mixed meter / mixed time signatures
* additive
Great, thanks!
On Mon, 2008-02-25 at 15:49 +0200, Joe Neeman wrote:
On Sun, 2008-02-24 at 22:12 -0300, Han-Wen Nienhuys wrote:
2008/2/22, Oscar van Eijk [EMAIL PROTECTED]:
Any suggestions? Is this a bug?
Yes;
without delving deeper into this, I'd say it might be related to the
27 matches
Mail list logo