Re: GDP: renaming Program {usage, reference}
Eyolf Østrem wrote: Sorry - my fault, I was thinking of the Program Usage, which to a large extent has to do with how to write code to produce a certain output (the LP-book part) leaving bits and pieces which not necessarily belongs together with the notation reference thematically, but which on the other hand is so few pages, dealing with the fundamentals of how to run the program, that it seems logical to have it in one place. I don't follow -- especially the to a large extent. In the newly-renamed Application Usage, is there anything other than chapter 4 which you believe should be in NR? I really can't see anything of the sort. Now, chapter 4 is debatable. But with the exception of 4.6.3, this chapter is dealing with including lilypond input inside lilypond-book -- the NR remains the source of information about lilypond input. As such, I decided it made more sense in AU than in NR. I'll grant that it might be nice to include info like 4.6.3 in a later chapter of the NR; sorting out this kind of thing *is* on my list. My mind could be changed on this issue, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: text first draft
Trevor Daniels wrote:
Graham Percival asked on 03 November 2007 06:57
Text
REWRITE
- overview of text entry: rename? Also, fill in.
- or possibly delete it?
A real-life example would be good to encourage the
reader to go further, and convince him the solution
to his particular problem will be found here.
It is a difficult section, and encouragement is
needed.
Well, there will be an inspirational headword eventually in 1.8 Text.
As for the Overview specifically, I take it this a vote in favor of
keeping it?
\fatText goes into @commonprop
There should be a distinction between simple
commands like this and the more arcane overrides
which expose scheme and LP internals. The former
are fine in the main text; the latter should be
in @commonprop.
Actually, \fatText _is_ simply an arcane override -- but one which the
developers thought was so common that they included a predefined
variable. Look in ly/propert-init.ly :
fatText = { \override TextScript #'extra-spacing-width = #'(0 . 0)
\override TextScript #'infinite-spacing-height = ##t }
There was a proposal to explain this in every single @commonprop
section, but I think it's better to include one GOOD explanation of this
kind of thing in the LM.
(let's put this specific question to rest for a few days; I promise we
will return to it)
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Numbered musical notation (Jianpu)
On 3 Nov 2007, at 10:16, Silas S. Brown wrote: Would it be feasible to make Lilypond produce the numbered musical notation described at http://en.wikipedia.org/wiki/Numbered_musical_notation ? I don't know about LilyPond, but one can try using the Unicode combining marks. (Like perhaps U+0320 COMBINING MINUS SIGN BELOW.) The problem is to get it to display properly. Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: text first draft
From: Graham Percival 04 November 2007 08:31
Trevor Daniels wrote:
Graham Percival asked on 03 November 2007 06:57
Text
REWRITE
- overview of text entry: rename? Also, fill in.
- or possibly delete it?
A real-life example would be good to encourage the
reader to go further, and convince him the solution
to his particular problem will be found here.
It is a difficult section, and encouragement is
needed.
Well, there will be an inspirational headword
eventually in 1.8 Text.
As for the Overview specifically, I take it this
a vote in favor of
keeping it?
Yes
\fatText goes into @commonprop
There should be a distinction between simple
commands like this and the more arcane overrides
which expose scheme and LP internals. The former
are fine in the main text; the latter should be
in @commonprop.
Actually, \fatText _is_ simply an arcane override
-- but one which the
developers thought was so common that they
included a predefined
variable.
The difference exactly. That's why I think this
predefined variable should be in the main text.
Look in ly/propert-init.ly :
fatText = { \override TextScript
#'extra-spacing-width = #'(0 . 0)
\override TextScript
#'infinite-spacing-height = ##t }
There was a proposal to explain this in every
single @commonprop
section, but I think it's better to include one
GOOD explanation of this
kind of thing in the LM.
I agree entirely. A ref to the explanation is
all that is required.
(let's put this specific question to rest for a
few days; I promise we
will return to it)
Sorry, couldn't resist replying :)
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: OO and MIDI support
On Friday 05 October 2007, Hans Aberg wrote: On 5 Oct 2007, at 01:20, Graham Percival wrote: Midi support in lilypond is quite limited, and this is not likely to change in the near future. Might it possible to handle this by OO (object orientation)? The idea is that if objects can be defined (in pseudocode) turn := default: ... midi: ... short: ... quintuplet: ... ; And one then is able to write code like d8^\turn[staff-short,midi-quintuplet] if one in this position wants the turn to not be the defaults, but then the staff to be written in the short form, and MIDI be written as a quintuplets. The principle is quite general. So it might be useful for handing a number of problems. The enhanced MIDI support would emerge as a byproduct of this OO support. I don't understand all of this, but wouldn't it be possible to achieve most of this functionality with tags? You could just use \keepWithTag #'midi when creating midi, and then tag stuff with midi in the definition of \turn. Erik ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Scheme code for extracting LilyPond header properties?
On Tuesday 09 October 2007, John Zaitseff wrote:
Dear Nicolas / LilyPonders,
I store a field in the header, lastupdated, in the form 09-Oct-2007;
the \parsed-date function converts that to something like 9 October,
2007:
% \parsed-date DATE - convert a DD-MMM- property to a fully printed
date #(define-markup-command (parsed-date layout props date) (symbol?)
Convert the property @var{date} containing a date in the
form DD-MMM- into a nicely formatted stencil output D ,
.
(let* ((datestr (chain-assoc-get date props)))
(interpret-markup layout props
(if (string? datestr)
(markup #:simple
(strftime %e %B, %Y (car (strptime %d-%b-%Y
datestr datestr
(Of course, I should rewrite that to make it somewhat more robust.
It works for me, however).
You may want to use SRFI-19 for this,
http://www.gnu.org/software/guile/manual/html_node/SRFI_002d19.html#SRFI_002d19
Erik
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Mediawiki extension
Hello, I have some problems on a setup with Debian + Mediawiki + Lilypond. I installed it according to http://www.mediawiki.org/wiki/Extension:LilyPond I have Debian stable (Etch), Lilypond 2.8.7. Then I had to upgrade Lilypond to 2.10.29 (Debian testing) and guile to 1.8.2 (Debian unstable). I copied some Lilypond files from some other sites, including lilypond.org, but they do not work out of the box. Simple examples work, but complex ones do not. There are many syntax errors. See http://www.wikilivres.info/wiki/index.php/Musique_de_Table http://www.wikilivres.info/wiki/index.php/Down_to_the_Sea http://www.wikilivres.info/wiki/index.php/Belle_qui_tiens_ma_vie Help very much appreciated. However the result is quite nice when it works: http://www.wikilivres.info/wiki/index.php/Wikilivres:Lilypond Seeing the difficulties I have to set up Lilypond with Mediawiki, I understand why the developers of the Wikimedia Foundation refuse to enable it on Wikipedia and related projects. That's quite a pity, because it would be very useful there. Regards, Yann -- http://www.non-violence.org/ | Site collaboratif sur la non-violence http://www.forget-me.net/ | Alternatives sur le Net http://fr.wikipedia.org/ | Encyclopédie libre http://fr.wikisource.org/ | Bibliothèque libre http://wikilivres.info | Documents libres ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
still space between lyric syllabes when hyphens are removed
Hi, When lyric syllabes with a hyphen in between come very close together, the hyphen is removed. Which is OK. But: sometimes there is still a little bit of space between the syllabes. What I would like is that IF the hyphen is removed (e.g. when shorter than 1 staffspace), the syllabes are placed fully together (including kerning), and not with a (small) space in between. Would that be possible with some setting? I know how I can force the hyphens to be there, but actually I like the possibility of removing the hyphens. But if they are removed, the syllabes must really look like one word, and not still have a small distance. Tia, Met vriendelijke groet, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ You must be the change you wish to see in the world. -- Mahatma Gandi ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Newbie question about variable durations
Op zaterdag 3 november 2007, schreef Ben:
I thought I had this figured out, but now I'm stuck. My program generates
midi notes and converts them to lily variables (ie noteone = {ees'} ). What
I need to do next is add my durations onto them. It seems so simple but I
get error after error.
Yes, you can't simply write
\noteone4
to get ees'4 when \noteone is set to {ees'}
this has bitten me as well, and it is caused by the fact that \noteone is not
just some string, but a fully-fledged music expression.
I have no simple solution. I think it would involve writing a small scheme
function to take a music expr and replaces it's duration.
You could maybe look at
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Music-functions
Met vriendelijke groet,
Wilbert Berendsen
--
http://www.wilbertberendsen.nl/
You must be the change you wish to see in the world.
-- Mahatma Gandi
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: OO and MIDI support
On 4 Nov 2007, at 17:43, Erik Sandberg wrote: Midi support in lilypond is quite limited, and this is not likely to change in the near future. Might it possible to handle this by OO (object orientation)? The idea is that if objects can be defined (in pseudocode) turn := default: ... midi: ... short: ... quintuplet: ... ; And one then is able to write code like d8^\turn[staff-short,midi-quintuplet] if one in this position wants the turn to not be the defaults, but then the staff to be written in the short form, and MIDI be written as a quintuplets. The principle is quite general. So it might be useful for handing a number of problems. The enhanced MIDI support would emerge as a byproduct of this OO support. I don't understand all of this, but wouldn't it be possible to achieve most of this functionality with tags? You could just use \keepWithTag #'midi when creating midi, and then tag stuff with midi in the definition of \turn. I am not sure how this stuff you are mentioning is working, but essentially what OO does is creating an easy to use user interface. It is perfectly possible to do OO programming by hand in C, and C++ gets some of its OO from such C by hand programming techniques, only developed as language features. And Guile has some OO package, I think. What I wrote above is a form of tagging, whose definition later can be changed by the - above, and in the compilation, selected by some context variables. Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mediawiki extension
Hi Yann, I copied some Lilypond files from some other sites, including lilypond.org, but they do not work out of the box. Simple examples work, but complex ones do not. There are many syntax errors. You are using examples from old lilypond versions that do not compile anymore. See http://lilypond.org/doc/v2.11/Documentation/user/lilypond-program/Updating-files-with-convert_002dly This http://www.wikilivres.info/wiki/index.php/Musique_de_Table compiles now, so you setup is fine. You want to check your .ly files using lilypond on the command line before adding them to the wiki. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
song with multi-voice ending
I've a song with one voice, but the ending has three.
I need those in different staves, because they've slightly different
texts, but I didn't manage it yet.
What's wrong with my code below?
The first (one voice) part works.
---
\score {
{
\context ChordNames {
\germanChords
\set chordChanges = ##t
\akkorde
}
\context Staff = Oben
\global
\context Voice = eins { \hauptstimme }
\lyricsto eins \new Lyrics { \text }
\context ChordNames {
\germanChords
\set chordChanges = ##t
\akkordeSchluss
}
\context Staff = Oben \context Voice = eins {
\schlussEins }
\lyricsto eins \new Lyrics { \textSchlussEins }
\context Staff = Mitte \context Voice = zwei {
\schlussZwei }
\lyricsto zwei \new Lyrics { \textSchlussZwei }
\context Staff = Unten \context Voice = drei {
\schlussDrei }
\lyricsto drei \new Lyrics { \textSchlussDrei }
}
\layout {
indent = 0\cm
}
}
---
LilyPond says:
Analysieren...
Interpretation der Musik...[8][16]
Vorverarbeitung der grafischen Elemente...
Interpretation der Musik...
Programmierfehler: Moment is not increasing. Aborting interpretation.
Fortsetzung, die Finger kreuzen
[7]
(I don't think the translation of the error messages was such a good
idea...)
Greetlings from Lake Constance
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net
http://angerweit.tikon.ch/lieder/
https://www.cacert.org (I'm an assurer)
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: song with multi-voice ending
What LilyPond version do you use?
I don't have the time now to make dummy definitions of all your
variables, so I have not done any trial and error. However, I would
first try something along the lines of
\score {
\new ChordNames {
\germanChords
\set chordChanges = ##t
\akkorde \akkordeSchluss
}
\new Staff = Oben
\global
\new Voice = eins {\hauptstimme \shlussEins
\new Staff = mitte \new Voice = zwei {
\schlussZwei }
\new Staff = unten \new Voice = drei {
\schlussDrei }
}
\new Lyrics \lyricsto eins { \text \textSchlussEins }
\new Lyrics \with {alignBelowContext=mitte } \lyricsto zwei {
\text \textSchlussZwei }
\new Lyrics \with {alignBelowContext=unten } \lyricsto drei {
\text \textSchlussDrei }
}
/Mats
Quoting fiëé visuëlle [EMAIL PROTECTED]:
I've a song with one voice, but the ending has three.
I need those in different staves, because they've slightly different
texts, but I didn't manage it yet.
What's wrong with my code below?
The first (one voice) part works.
---
\score {
{
\context ChordNames {
\germanChords
\set chordChanges = ##t
\akkorde
}
\context Staff = Oben
\global
\context Voice = eins { \hauptstimme }
\lyricsto eins \new Lyrics { \text }
\context ChordNames {
\germanChords
\set chordChanges = ##t
\akkordeSchluss
}
\context Staff = Oben \context Voice = eins {
\schlussEins }
\lyricsto eins \new Lyrics { \textSchlussEins }
\context Staff = Mitte \context Voice = zwei {
\schlussZwei }
\lyricsto zwei \new Lyrics { \textSchlussZwei }
\context Staff = Unten \context Voice = drei {
\schlussDrei }
\lyricsto drei \new Lyrics { \textSchlussDrei }
}
\layout {
indent = 0\cm
}
}
---
LilyPond says:
Analysieren...
Interpretation der Musik...[8][16]
Vorverarbeitung der grafischen Elemente...
Interpretation der Musik...
Programmierfehler: Moment is not increasing. Aborting interpretation.
Fortsetzung, die Finger kreuzen
[7]
(I don't think the translation of the error messages was such a good
idea...)
Greetlings from Lake Constance
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net
http://angerweit.tikon.ch/lieder/
https://www.cacert.org (I'm an assurer)
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
erratic key change marking
I am having some trouble with an erratic key change mark. The d major change
seems to leave an open staff line with the d mark before that actual begining of
the music. Any help would be great!
Regards,
Michael
Here is the code:
\version 2.10.33
\header{
title = Breaking Something
subtitle = Copy Right Michael Listrom
}
\score {
\relative c'' {
\tempo 8 = 180
\new PianoStaff
\new Staff {
\time 5/8
%intro
c8 [b c] r g
c [d c] r g
f' [e] r g [b,]
d [e f] r b,
%bar 2
f'[e f] r b,
f'[g f] r d
g [a g] r g,
d' [e f] r g
%bar 3
f [e f] r b,
c [d e f g]
f [e f] r b,
c [d e f g]
%bar 4
c, [d ees d c]
b [d c g aes]
g [aes b c d]
c [d ees d c]
%bar 5
f [g aes g f]
c [d ees d c]
g' [g, g' f ees]
d [ees f ees d]
%bar 6
c [b c d c]
d [ees] r d [es]
g [d ees d ees]
c [b c g aes]
%bar 7
c4. f8 [e]
c [d c] r4
f8 [e] r4.
c8 [b c] r d
%verse 1
c r f [e d]
b r e [d c]
a r b [d e]
g r a [b a]
%chorus
\key a \major
a [e a] r fis
gis [fis] r gis [fis]
gis [a e] r fis
gis [fis] r gis [e]
%chorus pt 2
e [f e a, b]
e [f e a, g]
b [c d f e]
%verse 2
\key c \major
a [b a f e]
d [e f g a]
b [d, c d e]
d [c b a g]
%bridge
f' [ees] r ees [d]
f [e] r f [g]
f [ees] r ees [d]
f [e] r f [g]
%bar 8
a [b a g f]
f [e b d g,]
a [b d e f]
g [a g f e]
%bar 9
f [f f g, c]
c [g e' d c]
g' [a g f e]
e [f e d c]
%bar 10
\key d \major
d [a] r b [cis]
d [a] r g [fis]
g [a b a g]
fis [e fis d a'']
\key c \major
%part 11
b [a g e d]
c [g a b d]
e [f g g, f']
e [d b a g]
%part 12
c [d ees g, d']
ees [f g aes g]
f [ees d ees f]
d [c b c d]
%part 13
g, [g g a b]
c [g a b a]
c [b aes g aes]
f' [ees d ees d]
%part 14
c [g] r a [b]
c [g] r a [b]
c [g] r a [b]
c [g] r a [b]
%part 15
d [e f] r g,
d' [c b] r a
b [d e f g]
a [b a g, a]
%part 16
b [d c g] r
b [d c g] r
d' [e f g] r
b, [d c g] r
}
\new Staff {
\clef bass
%intro
e, [d e c] r
e [d e c] r
r4 r4 r8
r4 r4 r8
%bar 2
r4. b4
b8 [c a] r g
r4 r4 r8
r4 r4 r8
%bar 3
c [b c g'] r
c, [b c d e]
c [b c
Re: Chords do not appear at the right position
Hi Niklas Uhrberg,
I forward your questions to the user mailinglist.
op zondag 4 november 2007, schreef je:
Ok, thanks a lot for answering.
I got it working also by using chordmode copying one of the templates.
Is there a way to have triangle denoting a major seven chord appear
aligned with the chord symbol (e.g. 'C') instead of in the upper
position (the same height as the normal alteration symbols such as
'+5' '7' ?
I'm have not seen the 'major triangle' at this upper position before.
I have just discovered Lilypond and it looks promising for my needs.
I'm going to try the import tool to convert from MusicXML to ly and if
that works fine things are just wonderful.
The MusicXML import tool has recently seen much development, so the most
recent Lilypond version will probably work well!
Thanks for great sowtware!
Best regards,
Niklas
On Nov 4, 2007 9:02 PM, Wilbert Berendsen [EMAIL PROTECTED] wrote:
this is not a bug, you should write:
\version 2.10.29
\chords { c1 |
c1 |
g2:7sus4 c2 |
c1
}
\relative c'' {
g4. c8 ~ c4 e4 ~ |
e2. r4 |
d4. e8 ~ e4 c4 ~ |
c1 |
}
note the added and . Otherwise, the chords and the notes create just
two unrelated music scores.
Met vriendelijke groet,
Wilbert Berendsen
--
http://www.wilbertberendsen.nl/
You must be the change you wish to see in the world.
-- Mahatma Gandi
Met vriendelijke groet,
Wilbert Berendsen
--
http://www.wilbertberendsen.nl/
You must be the change you wish to see in the world.
-- Mahatma Gandi
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
