Indeed I use emacs in Linux. But it is very strange:
1. It worked always fine with Lilypond 2.4.6 and the following versions. Now I
have 2.6.4.3. and the problem started.
2. And: it does not work with jedit!
I love Lilypond but each upgrade serves a new surprise :-)
Thank you,
Wolfgang
PS: M
Pedro Kröger wrote:
Paul Scott <[EMAIL PROTECTED]> writes:
Is the web site behind or is 2.7.14.1 the latest safe version?
the web is behind, I just updated it.
Any reason I shouldn't install 2.7.19 for testing purposes?
none I can think of.
Thanks.
2.7.19 may have a
Paul Scott wrote:
Pedro Kröger wrote:
Paul Scott <[EMAIL PROTECTED]> writes:
Is the web site behind or is 2.7.14.1 the latest safe version?
the web is behind, I just updated it.
The change just made it to the website. The text and link point to
2.7.19.1 but the actual version at
http:
Tomasz Bojczuk wrote:
Concretly i need something like this (in apendix)
Is it possibile ??
but exactliy, i can put only text
Of course it's possible, it's LilyPond, right! ;-)
If you browse through section "8.1.7 Overview of text markup commands",
you will learn how to do the circled n
Nicolas Sceaux <[EMAIL PROTECTED]> wrote:
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
> > I wonder whether this should be changed too. This would mean that
> >
> >\clef alto
> >\clef "alto"
> >
> > becomes
> >
> >\clef #"alto"
> >
> > or
> >
> >\clef #'alto
> >
> > This will
I would recommend you to first typeset your dynamics in a normal
stave attached to normal notes and make sure that you understand
exactly how they are positioned relative to the notes. Then, you can
simply replace the notes by skips and use them in the Dynamics
context instead. A good starting poi
A third alternative is to define an extra "line of music" that only
contains the break commands (and other differences between the
instrumental part and the score):
scorespecifics = { \skip 1*24 \break \skip 1*35 \break }
violinpartspecifics = { \skip 1*18 \break }
and then include these in the r
Just give an explicit name to the Voice of the first guitar:
firstGuitar = \context Voice GuitarOne {
then your commented lines should work directly.
For the separate parts, you could mark the lyrics with tags. A simple
alternative is to write out the full \score block for each separate version
On Thu, 2005-12-15 at 11:07 +0100, Mats Bengtsson wrote:
> However, if you want the lyrics included also in the separate part for
> guitar 2, it's a bit more tricky, at least if the rhythm of the second
> guitar part does not match the lyrics, since then you don't have anything
> in the score that
I see some cases where this would be clearly a win. Few weeks ago, a
singer asked me to change all alto clefs to treble clefs in a
voice+piano reduction score. Just redefining the \clef music function
would have made that really easy and quick.
A query replace alto -> treble is probably
The mystery was indeed in the .emacs file. The following setting
(standard-display-european t)
(set-language-environment 'Latin-1)
contradicted the utf-8 setting:
(custom-set-variables
...
'(current-language-environment "UTF-8")
'(default-input-method "rfc1345")
'(global-font-lock-mode t n
It's certainly no surprise that your "problems" started when you changed
from 2.4 to 2.6, since in version 2.4 you could only use latin1 encoding
(or plain ASCII), which means that LilyPond could only handle western
European text, whereas in verson 2.6 you can "only" use UTF-8 encoding,
which mean
On 12/14/05, Andrzej Kopec <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I want to ask if there is (better) method of utilizing Lilypond to typeset
> aleatoric
> music. For these not familiar with subject:
> http://en.wikipedia.org/wiki/Aleatoric_music
> This notation was broadly used by Witold Luto
Kenneth Teh wrote:
It seems to me that based on these observations, what
Lilypond needs is a context for creating chord names
that
(1) does not try to actually build chords, ie, the
MIDI output produces nothing. This way you avoid all
the problems associated with trying to describe a
voicing w
Andrzej Kopec wrote:
// \\
||--|---|||-
||.-|---|--.|||-
||.-|---|--.|||-
||--o---|---|||-
||--o---|||-
\\ //
This notation
It's true that the jazz chord names printed by
lilypond are weird from a jazz perspective and it is
also true that there is a mechanism via
chordNameExceptions to tweak the output or one could
always use text markup to do it exactly as one wishes.
true
(1) Text markup for chords don't allow yo
Paul Scott <[EMAIL PROTECTED]> writes:
> The change just made it to the website. The text and link point to
> 2.7.19.1 but the actual version at
> http://lilypond.org/download/binaries/autopackage/ is 2.7.19 so the
> link doesn't work.
my mistake, I just corrected it. thanks.
Pedro Kröger
Mats Bengtsson <[EMAIL PROTECTED]> writes:
>>>I see some cases where this would be clearly a win. Few weeks ago, a
>>>singer asked me to change all alto clefs to treble clefs in a
>>>voice+piano reduction score. Just redefining the \clef music function
>>>would have made that really easy and quick
Han-Wen Nienhuys writes:
> >
> > // \\
> > ||--|---|||-
> > ||.-|---|--.|||-
> > ||.-|---|--.|||-
> > ||--o---|---|||-
> > ||--o---|||-
On Wednesday 14 December 2005 09:39 pm, Kenneth Teh wrote:
> I know this is an old topic and various folks have
> discussed this at length on this list. Nonetheless,
> I'd like to throw in a few more remarks on the
> subject.
>
> It's true that the jazz chord names printed by
> lilypond are weird
Andrzej Kopec wrote:
Han-Wen Nienhuys writes:
> >
> > // \\
> > ||--|---|||-
> > ||.-|---|--.|||-
> > ||.-|---|--.|||-
> > ||--o---|---|||-
> > ||--o---
Han-Wen Nienhuys writes:
> I wonder whether this should be changed too. This would mean that
>
>\clef alto
>\clef "alto"
>
> becomes
>
>\clef #"alto"
>
> or
>
>\clef #'alto
>
>
> This will simplify the syntax a bit, at the expense ease of entry.
>
> What do you th
--- Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>
> Kenneth Teh wrote:
> > It seems to me that based on these observations,
> what
> > Lilypond needs is a context for creating chord
> names
> > that
> >
> > (1) does not try to actually build chords, ie, the
> > MIDI output produces nothing. T
23 matches
Mail list logo
