Re: Lilypond midi to stdout?
Why is it important to play the midi file during generation? John O'Hagan wrote: Hi, I'm using Lilypond to print the results of an algorithmic music program written in Python. I'm looking for a way to play the results as they are produced (i.e bar by bar), and it occurred to me that simply playing Lilypond midi files with a midi player would do the trick. However, I can't figure out how to get Lilypond's midi data sent to stdout, where it could then be read from stdin by a player. Whatever I try (including python pipes and even plain shell pipes) it just writes the file to my home directory. Is there any way around this? Regards, John O'Hagan ___ 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
Re: adding rests automatically
Hi Eyolf
No one has looked at Chapter 6 yet, but I agree this could be improved.
I'll do it now.
Trevor
- Original Message -
From: "Eyolf Østrem" <[EMAIL PROTECTED]>
To: "lilypond-user"
Sent: Saturday, October 11, 2008 6:45 PM
Subject: Re: adding rests automatically
On 11.10.2008 (11:01), Carl D. Sorensen wrote:
You can read about music functions in the documentation. See the
notation
reference for 2.11, section 6. Music functions.
The paradigm in the beginning is confusing:
function =
#(define-music-function (parser location var1 var2... )
(var1-type? var2-type?...)
#{
...music...
#})
where
argiith variable
argi-type? type of variable
It is clear what it means, of course, but a mathematician would be
troubled
by a where clause which defines arguments which are not present in the
equation, and a musician may be confused by it, at least intially.
Eyolf
--
___ __Frobtech, Inc.
/__/\ ___/_/\
\ \ \ / /\\
\ \ \_/__ / \ "If you've got the job,
_\ \ \ /\_/___ \ we've got the frob."
// \__\/ / \ /\ \
___//___/\ / _\/__
/ / \ \// //\
__/ / \ \ // // _\__
/ / / \___\// // / /\
/_/__/___/ // /___/ \
\ \ \___\ \\ \ \ /
\_\ \ / /\\ \\ \___\/
\ \/ / \\ \\ /
\_/ /\\ \\/
/__/ \\ /
\ _ \ /_\/
\ //\ \/ \ \ \
// \ \ / \ \ \
\\ /___\/ \ \ \
\\/\__\/
___
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
Re: GDP NR 1.6 Staff notation ready for public review
Am Mon, 13 Oct 2008 11:33:10 +0100 schrieb "Trevor Daniels" <[EMAIL PROTECTED]>: > and post any comments, corrections or criticism to this list. Thanks. Very well done. I only skimmed the text, but understood a lot of things I only imitated before. Certainly an important section. The only thing I could critisize is that the section starts with "... which are marked at the beginning of each line with either a bracket or a brace." But the first examples (single staves) have neither braces nor brackets. How about "which can be marked/grouped together" instead? Then note explicitly in "Grouping Staves" how/that these marks are created. Seb. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Moving guitar fingering orientations
Having spent a bit of time getting my guitar scores the way I like them, I've made up the attached two bar sample that shows most of the guitar-specific notation I use: - left hand fingering with orientation - right-hand fingering with orientation - how to get the fingering notations inside the staff - string number indications - shared noteheads on arpeggios - a music function for showing barres (my adaptation of someone else's adaptation of a funcion I found in a Mutopia score that was not compatible with the current version of Lilypond). Feel free to use it in the documentation or in a repository of samples. Nick -Original Message- From: Valentin Villenave [mailto:[EMAIL PROTECTED] Sent: Monday, 13 October 2008 17:43 To: Jonathan Kulp Cc: Nick Payne; lilypond-user@gnu.org Subject: Re: Moving guitar fingering orientations 2008/10/12 Jonathan Kulp <[EMAIL PROTECTED]>: > Ah. I see it now. Yes, this is easily fixed. How can I alter this > snippet? Valentin, this is your purview, right? Is it o.k. if I just > make these small changes and email it to you? No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.8.0/1722 - Release Date: 13/10/2008 07:50 guitar.ly Description: Binary data <>___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
rolled chords in mulivoice classical guitar score
Greetings!
After digging around considerably in the excellent Lilypond
documentation (am running 2.11.60 on Kubuntu Linux 8.04.1), and running
a number of experiments, I'm defeated on this problem.
A simple test case: I have two voices in a single staff. Periodically, I
want to indicate that the notea co-occuring at a given point are to be
played as a "rolled" arpeggio. There is NO chord notated - just two
voices with single notes. Please don't suggest I merge the voices.
That's not the solution I'm looking for.
P. 90 of Lilypond Notation reference illustrates a rolled arpeggio
across different notes in the same staff, but it involves notes in chord
clusters. Besides, my Lilypond doesn't at all like this stuff (from the
reference):
\new Staff \with {
\consists "Span_arpeggio_engraver"
}
\relative c' {...
I get this error - "warning: cannot find file: `consists' "
So, even if I HAD chord clusters, I'd still have a problem.
This rolled arpeggio business is very common in classical guitar music.
I'm a little surprised there isn't some simple way to indicate it,
but...maybe I'm missing something.
Any help would be much appreciated!
Tom
--
~
Tom Cloyd, MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [EMAIL PROTECTED] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)
~
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: rolled chords in mulivoice classical guitar score
This snippet appears to do what you're asking:
http://lilypond.org/doc/v2.11/input/lsr/lilypond-snippets/Expressive-marks
Go down to where it says "Creating arpeggios across notes in different
voices."
Jon
%
% Start cut-&-pastable-section
%
\paper {
#(define dump-extents #t)
indent = 0\mm
line-width = 160\mm
force-assignment = #""
line-width = #(- line-width (* mm 3.00))
}
\layout {
}
%
% ly snippet:
%
\sourcefilename "creating-arpeggios-across-notes-in-different-voices.ly"
\sourcefileline 0
%% Do not edit this file; it is auto-generated from LSR
http://lsr.dsi.unimi.it
%% This file is in the public domain.
\version "2.11.62"
\header {
lsrtags = "expressive-marks"
texidoces = "
Se puede trazar un símbolo de arpegio entre notas de distintas
voces que están sobre el mismo pentagrama si el grabador
@code{Span_arpeggio_engraver} se traslada al contexto de
@code{Staff} context:
"
doctitlees = "Crear arpegios entre notas de voces distintas"
texidoc = "
An arpeggio can be drawn across notes in different voices on the same
staff if the @code{Span_arpeggio_engraver} is moved to the @code{Staff}
context:
"
doctitle = "Creating arpeggios across notes in different voices"
} % begin verbatim
\new Staff \with {
\consists "Span_arpeggio_engraver"
}
\relative c' {
\set Staff.connectArpeggios = ##t
<<
{ 4\arpeggio 2 } \\
{ 2\arpeggio 2 }
>>
}
%
% end ly snippet
%
Tom Cloyd wrote:
Greetings!
After digging around considerably in the excellent Lilypond
documentation (am running 2.11.60 on Kubuntu Linux 8.04.1), and running
a number of experiments, I'm defeated on this problem.
A simple test case: I have two voices in a single staff. Periodically, I
want to indicate that the notea co-occuring at a given point are to be
played as a "rolled" arpeggio. There is NO chord notated - just two
voices with single notes. Please don't suggest I merge the voices.
That's not the solution I'm looking for.
P. 90 of Lilypond Notation reference illustrates a rolled arpeggio
across different notes in the same staff, but it involves notes in chord
clusters. Besides, my Lilypond doesn't at all like this stuff (from the
reference):
\new Staff \with {
\consists "Span_arpeggio_engraver"
}
\relative c' {...
I get this error - "warning: cannot find file: `consists' "
So, even if I HAD chord clusters, I'd still have a problem.
This rolled arpeggio business is very common in classical guitar music.
I'm a little surprised there isn't some simple way to indicate it,
but...maybe I'm missing something.
Any help would be much appreciated!
Tom
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Moving guitar fingering orientations
That's nice, Nick, thanks! I especially like the barre indication. I already had all the other stuff but this barre is nicer-looking than the default Lilypond barre spanner, I think. Jon Nick Payne wrote: Having spent a bit of time getting my guitar scores the way I like them, I've made up the attached two bar sample that shows most of the guitar-specific notation I use: - left hand fingering with orientation - right-hand fingering with orientation - how to get the fingering notations inside the staff - string number indications - shared noteheads on arpeggios - a music function for showing barres (my adaptation of someone else's adaptation of a funcion I found in a Mutopia score that was not compatible with the current version of Lilypond). Feel free to use it in the documentation or in a repository of samples. Nick -Original Message- From: Valentin Villenave [mailto:[EMAIL PROTECTED] Sent: Monday, 13 October 2008 17:43 To: Jonathan Kulp Cc: Nick Payne; lilypond-user@gnu.org Subject: Re: Moving guitar fingering orientations 2008/10/12 Jonathan Kulp <[EMAIL PROTECTED]>: Ah. I see it now. Yes, this is easily fixed. How can I alter this snippet? Valentin, this is your purview, right? Is it o.k. if I just make these small changes and email it to you? No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.8.0/1722 - Release Date: 13/10/2008 07:50 -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: rolled chords in mulivoice classical guitar score
Tom Cloyd-2 wrote: > > > I get this error - "warning: cannot find file: `consists' " > > This msg means that Lilypond is looking for a file named "consists" - since you only sent this fragment we cannot check if there is a unwanted \include of such a file or something similar! hth -Eluze -- View this message in context: http://www.nabble.com/rolled-chords-in-mulivoice-classical-guitar-score-tp19953962p19954919.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: rolled chords in mulivoice classical guitar score
BTW this works with single notes, too. I changed it as follows and the
arpeggio still works fine:
\new Staff \with {
\consists "Span_arpeggio_engraver"
}
\relative c' {
\set Staff.connectArpeggios = ##t
<<
{ e'4\arpeggio 2 } \\
{ d,2\arpeggio 2 }
>>
}
Jonathan Kulp wrote:
This snippet appears to do what you're asking:
http://lilypond.org/doc/v2.11/input/lsr/lilypond-snippets/Expressive-marks
Go down to where it says "Creating arpeggios across notes in different
voices."
Jon
%
% Start cut-&-pastable-section
%
\paper {
#(define dump-extents #t)
indent = 0\mm
line-width = 160\mm
force-assignment = #""
line-width = #(- line-width (* mm 3.00))
}
\layout {
}
%
% ly snippet:
%
\sourcefilename "creating-arpeggios-across-notes-in-different-voices.ly"
\sourcefileline 0
%% Do not edit this file; it is auto-generated from LSR
http://lsr.dsi.unimi.it
%% This file is in the public domain.
\version "2.11.62"
\header {
lsrtags = "expressive-marks"
texidoces = "
Se puede trazar un símbolo de arpegio entre notas de distintas
voces que están sobre el mismo pentagrama si el grabador
@code{Span_arpeggio_engraver} se traslada al contexto de
@code{Staff} context:
"
doctitlees = "Crear arpegios entre notas de voces distintas"
texidoc = "
An arpeggio can be drawn across notes in different voices on the same
staff if the @code{Span_arpeggio_engraver} is moved to the @code{Staff}
context:
"
doctitle = "Creating arpeggios across notes in different voices"
} % begin verbatim
\new Staff \with {
\consists "Span_arpeggio_engraver"
}
\relative c' {
\set Staff.connectArpeggios = ##t
<<
{ 4\arpeggio 2 } \\
{ 2\arpeggio 2 }
>>
}
%
% end ly snippet
%
Tom Cloyd wrote:
Greetings!
After digging around considerably in the excellent Lilypond
documentation (am running 2.11.60 on Kubuntu Linux 8.04.1), and
running a number of experiments, I'm defeated on this problem.
A simple test case: I have two voices in a single staff. Periodically,
I want to indicate that the notea co-occuring at a given point are to
be played as a "rolled" arpeggio. There is NO chord notated - just two
voices with single notes. Please don't suggest I merge the voices.
That's not the solution I'm looking for.
P. 90 of Lilypond Notation reference illustrates a rolled arpeggio
across different notes in the same staff, but it involves notes in
chord clusters. Besides, my Lilypond doesn't at all like this stuff
(from the reference):
\new Staff \with {
\consists "Span_arpeggio_engraver"
}
\relative c' {...
I get this error - "warning: cannot find file: `consists' "
So, even if I HAD chord clusters, I'd still have a problem.
This rolled arpeggio business is very common in classical guitar
music. I'm a little surprised there isn't some simple way to indicate
it, but...maybe I'm missing something.
Any help would be much appreciated!
Tom
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Moving guitar fingering orientations
Ok I've changed it to include two examples of single notes with
fingering orientation set on them. Snippet copied at the bottom!
Jon
Valentin Villenave wrote:
2008/10/12 Jonathan Kulp <[EMAIL PROTECTED]>:
Ah. I see it now. Yes, this is easily fixed. How can I alter this
snippet? Valentin, this is your purview, right? Is it o.k. if I just make
these small changes and email it to you?
Yes, please do!
Cheers,
Valentin
--
Jonathan Kulp
http://www.jonathankulp.com
%%
\version "2.11.62"
\header {
lsrtags = "editorial-annotations, chords, keyboards, fretted-strings"
texidoces = "
Se puede controlar con precisión la colocación de los números de digitación.
"
doctitlees = "Controlar la colocación de las digitaciones de acordes"
texidoc = "
The placement of fingering numbers can be controlled precisely.
"
doctitle = "Controlling the placement of chord fingerings"
} % begin verbatim
\relative c' {
\set fingeringOrientations = #'(left)
4
\set fingeringOrientations = #'(down)
4
\set fingeringOrientations = #'(down right up)
4
\set fingeringOrientations = #'(up)
4
\set fingeringOrientations = #'(left)
2
\set fingeringOrientations = #'(down)
2
}
%
% end ly snippet
%
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Headword for unfretted-strings
David We can now see this on Reinhold's server. It looks good to me. Are you happy with it? BTW, I see you use \open, which doesn't appear to be documented anywhere, although it is listed as an articulation in App B 10. Presumably this markup means play on an open string, so I'll add it to the Common section of Unfretted strings. Trevor - Original Message - From: "David Séverin" <[EMAIL PROTECTED]> To: "Trevor Daniels" <[EMAIL PROTECTED]> Cc: "Jonathan Kulp" <[EMAIL PROTECTED]>; "Graham Percival" <[EMAIL PROTECTED]>; Sent: Saturday, October 11, 2008 2:21 PM Subject: Re: Headword for unfretted-strings Finally, I did some work to get it done properly in 3 lines, here is what it looks like on my box [with lily doc parameters] What do you think ? Cheers, David ;; - Le Sat, 11 Oct 2008 09:18:51 +0100, "Trevor Daniels" <[EMAIL PROTECTED]> a écrit : David Your extract is now visible on the kainhofer site. Unfortunately it takes up too much space, with the result that the small amount of following text is pushed off the bottom of the first screen. I would prefer to reduce it to the first two lines, after the end of the first two triplets. These two lines already show pretty well all the notational elements contained in the remainder anyway, but I appreciate we lose a lot of the musicality, which is a pity. I'll make this change, again so we can see the result, but please let me know if you are unhappy with this. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
combining parts into a score
Over the last month or so I've been working on 'Lilyponding' a set of parts for a piece I've arranged. The individual parts all look very good now, I think, and are pretty much as I would want them, so I'm very pleased. :) However, I'm getting in a complete tangle trying to combine the parts into a score, and although I've read the documentation and searched on the site, I can't sort myself out. I've only tried to combine two parts so far, as an experimental start, but can't even manage that (*hangs head in shame*). I have done: \include "alto+descant notes.ly" \include "alto2 notes.ly" << \new Staff \alto+descant notes \new Staff \alto2 notes >> which is the layout that it had as a template on the documentation, but had no luck. Also, am I right in thinking that the 'notes' files shouldn't have all the headers and tempo indications which are on the individual parts, but just the notes? If I need to keep some headers, which ones do I keep? And will I need to expand the condensed rests in the parts to single-bar rests, or does it do that automatically? Thanks, Jo -- View this message in context: http://www.nabble.com/combining-parts-into-a-score-tp19952552p19952552.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
GDP NR 1.6 Staff notation ready for public review
Please correct me if I am wrong, but it seems NR 1.6 Staff notation has never been announced as ready for public review, although it seems to be in good shape (thanks to Till) and has been reviewed by members of the GDP team. So I'll do it now. Could all of you will a few minutes to spare please look through this section at http://kainhofer.com/~lilypond/Documentation/user/lilypond/Staff-notation.html#Staff-notation and post any comments, corrections or criticism to this list. Thanks. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: WANTED: Design for documentation
I like the arrangement of the toc on the left side - but I wonder if it is be possible to hide/unhide/resize it when needed!? thanks! -- View this message in context: http://www.nabble.com/WANTED%3A-Design-for-documentation-tp18572050p19956430.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: combining parts into a score
Hello. > \include "alto+descant notes.ly" > \include "alto2 notes.ly" > << > \new Staff \alto+descant notes > \new Staff \alto2 notes > >> This looks quite odd. Although I'm not sure whether lilypond will be confused by it, using spaces in a file name is a bad idea. Morevover "space" characters are used as token separators so that, in the above, "\alto2" refers to a variable named "alto2" and "notes" is a syntax error. Also, LilyPond does not allow non-alphabetic characters in variables so that "alto+descant" is also an error. Best, Gilles ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
overhead projection of lilypond scores
when teaching a congregation a new worship song, it would be rather nice to project the melody line onto the screen as well as the words. But black-on-white is a projection disaster. It really needs to be yellow staff/text on a blue background. And probably a thicker text font than times new roman. Is this achievable, please ? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Moving guitar fingering orientations
Aha! I've already sent a revised snippet to Valentin that shows how a single note needs <> for setting the fingering orientations, but as I was punching holes in my newly printed Learning Manual, I noticed an example that already shows this in section 4.4.2 (or on pp. 104-105 of the .pdf version). It has several instances of single notes with fingerings and in each case the note and fingering is enclosed in a chord construct. There's not an explicit @warning about enclosing single notes in <>, but at least you can see it in the example. Could we add a @warning about this above the example? Jon Valentin Villenave wrote: 2008/10/12 Jonathan Kulp <[EMAIL PROTECTED]>: Ah. I see it now. Yes, this is easily fixed. How can I alter this snippet? Valentin, this is your purview, right? Is it o.k. if I just make these small changes and email it to you? Yes, please do! Cheers, Valentin -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Moving guitar fingering orientations
Sorry, I should have read more carefully. It actually does say explicitly in the text that single notes need chord angle brackets around them, but it might be useful to format this as a @warning anyway? Jon Jonathan Kulp wrote: Aha! I've already sent a revised snippet to Valentin that shows how a single note needs <> for setting the fingering orientations, but as I was punching holes in my newly printed Learning Manual, I noticed an example that already shows this in section 4.4.2 (or on pp. 104-105 of the .pdf version). It has several instances of single notes with fingerings and in each case the note and fingering is enclosed in a chord construct. There's not an explicit @warning about enclosing single notes in <>, but at least you can see it in the example. Could we add a @warning about this above the example? Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP NR 1.6 Staff notation ready for public review
Hi Trevor, On Mon, Oct 13, 2008 at 11:33:10AM +0100, Trevor Daniels wrote: > Please correct me if I am wrong, but it seems NR 1.6 Staff notation has > never been announced as ready for public review, although it seems to be > in good shape (thanks to Till) and has been reviewed by members of the > GDP team. So I'll do it now. > > Could all of you will a few minutes to spare please look through this > section at > > http://kainhofer.com/~lilypond/Documentation/user/lilypond/Staff-notation.html#Staff-notation > > and post any comments, corrections or criticism to this list. Thanks. I was planning on announcing this in a few days after looking it over a few more times, but thanks for doing this. It is definitely ready for review. Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: overhead projection of lilypond scores
Gerry It's possible, but not trivial. This snippet shows how to color the foreground of a score: http://lsr.dsi.unimi.it/LSR/Item?id=443 and this -user mail which I posted shows a very messy way of coloring the background: http://lists.gnu.org/archive/html/lilypond-user/2008-09/msg00083.html No one came up with a better way :( HTH - Original Message - From: "Gerry Prosser" <[EMAIL PROTECTED]> To: Sent: Monday, October 13, 2008 6:01 PM Subject: overhead projection of lilypond scores when teaching a congregation a new worship song, it would be rather nice to project the melody line onto the screen as well as the words. But black-on-white is a projection disaster. It really needs to be yellow staff/text on a blue background. And probably a thicker text font than times new roman. Is this achievable, please ? ___ 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
Re: Moving guitar fingering orientations
Hi Jon Looking at this section again (about a year after I wrote it) I see it doesn't mention using _ and ^ for manually placing single-note fingering. I'll change that too when I fix the warning. Trevor - Original Message - From: "Jonathan Kulp" <[EMAIL PROTECTED]> To: "Valentin Villenave" <[EMAIL PROTECTED]> Cc: Sent: Monday, October 13, 2008 5:21 PM Subject: Re: Moving guitar fingering orientations Sorry, I should have read more carefully. It actually does say explicitly in the text that single notes need chord angle brackets around them, but it might be useful to format this as a @warning anyway? Jon Jonathan Kulp wrote: Aha! I've already sent a revised snippet to Valentin that shows how a single note needs <> for setting the fingering orientations, but as I was punching holes in my newly printed Learning Manual, I noticed an example that already shows this in section 4.4.2 (or on pp. 104-105 of the .pdf version). It has several instances of single notes with fingerings and in each case the note and fingering is enclosed in a chord construct. There's not an explicit @warning about enclosing single notes in <>, but at least you can see it in the example. Could we add a @warning about this above the example? Jon -- Jonathan Kulp http://www.jonathankulp.com ___ 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
Re: GDP NR 1.6 Staff notation ready for public review
On Mon, Oct 13, 2008 at 4:31 AM, Sebastian Menge <[EMAIL PROTECTED]> wrote: > Am Mon, 13 Oct 2008 11:33:10 +0100 > schrieb "Trevor Daniels" <[EMAIL PROTECTED]>: > >> and post any comments, corrections or criticism to this list. Thanks. > > Very well done. I only skimmed the text, but understood a lot of things > I only imitated before. Certainly an important section. > > The only thing I could critisize is that the section starts with > > "... which are marked at the beginning of each line with either a > bracket or a brace." > > But the first examples (single staves) have neither braces nor > brackets. How about "which can be marked/grouped together" instead? Then > note explicitly in "Grouping Staves" how/that these marks are created. Yes, this needs to be reworded/adjusted. I will be able to fix it in a couple days time, unless Trevor manages to fix it before me. ;-) Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP NR 1.6 Staff notation ready for public review
Patrick I'm sorry, I should of course have acknowledged your work as well as Till's, and Andrew for reviewing it. Keeping track of who has done what is not proving easy :( Trevor - Original Message - From: "Patrick McCarty" <[EMAIL PROTECTED]> To: "Trevor Daniels" <[EMAIL PROTECTED]> Cc: "Lilypond-User List" Sent: Monday, October 13, 2008 6:14 PM Subject: Re: GDP NR 1.6 Staff notation ready for public review Hi Trevor, On Mon, Oct 13, 2008 at 11:33:10AM +0100, Trevor Daniels wrote: Please correct me if I am wrong, but it seems NR 1.6 Staff notation has never been announced as ready for public review, although it seems to be in good shape (thanks to Till) and has been reviewed by members of the GDP team. So I'll do it now. Could all of you will a few minutes to spare please look through this section at http://kainhofer.com/~lilypond/Documentation/user/lilypond/Staff-notation.html#Staff-notation and post any comments, corrections or criticism to this list. Thanks. I was planning on announcing this in a few days after looking it over a few more times, but thanks for doing this. It is definitely ready for review. Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: overhead projection of lilypond scores
Just my $0.02 (USD) on the matter. 1) Black-on-white is not really as bad as everyone says it is for projection purposes (before digital projection systems, that's how virtually all projected images appeared, except for those on prepared 35mm slides or similar), Especially when it's something like music, which everyone is used to seeing as black-on-white. I think whenever I've seen music projected with the words, it's been black-on-white. 2) If you do want to change the background, you may be able to take advantage of the fact that when the lily file is compiled to PDF, the background is technically transparent. So, if you have a program that can handle PDF files as objects (such as the Keynote presentation app for Mac), you can just drop the PDF into that program (you'll probably want to adjust the sizing for optimal display anyway) and use the background in the program. An alternative is to do the same thing in software like Photoshop or GIMP and export the result. Carl Peterson -- Forwarded message -- > From: "Trevor Daniels" <[EMAIL PROTECTED]> > To: "Gerry Prosser" <[EMAIL PROTECTED]>, > Date: Mon, 13 Oct 2008 18:22:00 +0100 > Subject: Re: overhead projection of lilypond scores > Gerry > > It's possible, but not trivial. > > This snippet shows how to color the foreground of a score: > > http://lsr.dsi.unimi.it/LSR/Item?id=443 > > and this -user mail which I posted shows a very messy way of coloring the > background: > > http://lists.gnu.org/archive/html/lilypond-user/2008-09/msg00083.html > > No one came up with a better way :( > > HTH > > - Original Message - From: "Gerry Prosser" <[EMAIL PROTECTED]> > To: > Sent: Monday, October 13, 2008 6:01 PM > Subject: overhead projection of lilypond scores > > > when teaching a congregation a new worship song, it would be rather nice >> to project the melody line onto the screen as well as the words. But >> black-on-white is a projection disaster. It really needs to be yellow >> staff/text on a blue background. And probably a thicker text font than times >> new roman. Is this achievable, please ? >> >> >> ___ >> 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
Stemming and lyrics on combined parts
I'm trying to take advantage of automatic part combining to make it easier to set the songs for a hymnal. There are a couple of technical things I need assistance on. 1) Whenever two parts on the same staff are on the same note, the part combiner only prints one stem. Is there any way to get the part combiner to output two stems for a due notes? 2) Is there a way to bind the lyrics to the original (uncombined) parts without outputting the parts themselves? Thanks, Carl Peterson ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Moving guitar fingering orientations
That's a good idea, Trevor, thanks. Jon Trevor Daniels wrote: Hi Jon Looking at this section again (about a year after I wrote it) I see it doesn't mention using _ and ^ for manually placing single-note fingering. I'll change that too when I fix the warning. Trevor - Original Message - From: "Jonathan Kulp" <[EMAIL PROTECTED]> To: "Valentin Villenave" <[EMAIL PROTECTED]> Cc: Sent: Monday, October 13, 2008 5:21 PM Subject: Re: Moving guitar fingering orientations Sorry, I should have read more carefully. It actually does say explicitly in the text that single notes need chord angle brackets around them, but it might be useful to format this as a @warning anyway? Jon Jonathan Kulp wrote: Aha! I've already sent a revised snippet to Valentin that shows how a single note needs <> for setting the fingering orientations, but as I was punching holes in my newly printed Learning Manual, I noticed an example that already shows this in section 4.4.2 (or on pp. 104-105 of the .pdf version). It has several instances of single notes with fingerings and in each case the note and fingering is enclosed in a chord construct. There's not an explicit @warning about enclosing single notes in <>, but at least you can see it in the example. Could we add a @warning about this above the example? Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
square note heads for cluster
Hello. I need to notate some clusters using squared rhythmic note-heads, something along the lines of this figure: <> Its possible to set up a music-function to generate a square markup based on the pitches of a chord, but i think this way of notation clusters is pretty standard so maybe someone already have something lying around? If not, is there a good list of various 'ly:' -prepended info-grabbing functions returning ambitus, notes, pithces, note-lines, y-positiions and the like? Thanks. -anders ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Headword for unfretted-strings
On Sat, 11 Oct 2008 08:33:37 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> Graham, you wrote Saturday, October 11, 2008 12:41 AM
>
> > Not the MIDI version of string sounds, you don't. :)
>
> Strings are so expressive they can never be properly
> synthesized. I grant you that.
To be fair, I'd assume that this applies even more to vocal music
-- quite apart from the expressivity of voice, midi doesn't even
attempt to add lyrics.
> > Seriously, there's no reason to build the .midi files in
> > Documentation/user/out-www/. I can appreciate that you wanted to
>
> I wasn't thinking of people who build the docs; rather
> people who read them.
Erm. How many people actually click on the graphics? And how
many people actually click on the graphics, copy&paste the
*correct* material (ie not the entire .ly file!), and generate the
output themselves.
I think we're down to count-on-one-hand territory here... and
those people surely must have read LM 3 already and therefore know
how to add the \midi{} block themselves.
> But I'm not going to die in the ditch defending this
Well, neither am I. :) If you want to add \midi{} to all
headwords, go ahead. I'm firmly of the opinion that this will be
useful to at most three people in the world... but then again,
we've spent longer discussing this change than it would take to
make it in the first place, so I can't really play the
"efficiency" card here.
If one could copy&paste the *entire* file, I'd be more inclined to
believe that it might be useful. (that's been a technical TODO
for about three years)
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Notation Reference 1.8 "Text" : ready for review
On Mon, 6 Oct 2008 15:47:33 +0200 "Valentin Villenave" <[EMAIL PROTECTED]> wrote: > 2008/10/6 Graham Percival <[EMAIL PROTECTED]>: > > Well, your personal source of knowledge and wisdom sucks. > > Matter of generation: not everybody was lucky enough to live at the > glorious era of usenet, you know :-) I have no clue how you kids grow up without usenet. That's half of the reason I act grumpy -- *somebody* has to teach you whippersnappers how things work. > > If you can remove a word (or words) without changing the meaning > > of a sentence, kill it with glee. > > I now understand why you no longer want to be a composer... Eh? Because I know that concise documentation is easier to understand? Especially for non-native-English speakers? Just because I'm trying to be nice to people with poor English doesn't mean that I can't appreciate Feldman, you know. Now, as it happens, I *don't* appreciate Feldman... and I admit that I prefer contemporary music that's less than 5 minutes long... but that has nothing to do with writing docs. > > Editing documentation *is* boring. But I'll have you note that I > > processed 99% of doc updates within a 12 hours for the *whole > > year* that I was running GDP. And the remaining 1% was delayed > > for academic work, not because I was bored did fun stuff instead. > > Managing updates is definitely less unpleasant than writing doc stuff > on your own. You have no clue what you're talking about. Writing docs, at least as part of GDP, involves you working on material that you've expressed an interest in, and can be done at your leisure. Editing docs often invovles stuff you don't care about at all, and should be processed as soon as possible. If contributors have to wait a few days to see their changes in HTML and/or get feedback, they get bored and wander off. It's a job that includes anywhere from 0.5 to 4 hours of mostly boring work each day. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: overhead projection of lilypond scores
It's not hard to create a .png file with transparent background from lilypond source, and with this bit of scheme Trevor linked to you can easily make all the objects on the page yellow. If you can merge the transparent-background music image with a blank blue image, then you will have what you want. I imagine it's not hard to do with Gimp if you have some basic skills. (Or maybe paint the wall blue where you want to project it!?! ;-) ). The lily2image script that Patrick Horgan and I wrote is what I use for making png images with transparent backgrounds. It's posted here: http://www.mail-archive.com/lilypond-user@gnu.org/msg40940.html I've attached an image created with the script and using the scheme Trevor mentioned to make everything yellow. Jon Trevor Daniels wrote: Gerry It's possible, but not trivial. This snippet shows how to color the foreground of a score: http://lsr.dsi.unimi.it/LSR/Item?id=443 and this -user mail which I posted shows a very messy way of coloring the background: http://lists.gnu.org/archive/html/lilypond-user/2008-09/msg00083.html No one came up with a better way :( HTH - Original Message - From: "Gerry Prosser" <[EMAIL PROTECTED]> To: Sent: Monday, October 13, 2008 6:01 PM Subject: overhead projection of lilypond scores when teaching a congregation a new worship song, it would be rather nice to project the melody line onto the screen as well as the words. But black-on-white is a projection disaster. It really needs to be yellow staff/text on a blue background. And probably a thicker text font than times new roman. Is this achievable, please ? ___ 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 -- Jonathan Kulp http://www.jonathankulp.com <>___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: passing a Context to a scheme function (format-metronome-markup)
On Wed, 8 Oct 2008 00:30:55 -0300
"Han-Wen Nienhuys" <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 7, 2008 at 2:12 PM, Reinhold Kainhofer
> <[EMAIL PROTECTED]> wrote:
> >
> > (define-public (format-metronome-markup text dur count . context)
> > (let* ((ctx (and (pair? context) (car context)))
> > (hide-note (and ctx (eq? #t (ly:context-property
> > ctx 'tempoHideNote
> > (note-mark (if (and (not hide-note) (ly:duration? dur))
> > ...
> >
> > I don't know how useful this might be in general, but since it's
> > such an easy feature (and I don't think it breaks anything), I
> > prepared a patch:
>
> I prefer if you made the function take a boolean instead, and use
> another function (calling the one using the bool) to plug in to the
> engraver.
Thanks for the discussion and patch! However, I recently tested a
score with some musicians, and they universally disliked the
"tempo in poet header" hack. :( I still like it, but one of the
first rules of HCI (human-computer interaction) is not to argue
with your test subjects, so I'm dropping this idea.
However, what grob produces the tempo mark? Neither of these
(exaggerated) overrides produces any change.
\version "2.11.61"
\relative c' {
\override MetronomeMark #'padding = #8
\override RehearsalMark #'padding = #8
\tempo "Allegro" 4 = 120
c1
}
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Accidental besides trill
How to put an accidental besides trill?
I did this:
\override TextScript #'extra-offset = #'(3 . 0)
e\trill^\markup{\sharp}
The accidental is besides, but the trill is still above.
Thank you,
--
Marcos di Silva
http://www.marcosdisilva.net/
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Moving guitar fingering orientations
2008/10/13 Jonathan Kulp <[EMAIL PROTECTED]>: > That's a good idea, Trevor, thanks. So, what's the snippet in the end? :-) Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Headword for unfretted-strings
Quoting Graham Percival <[EMAIL PROTECTED]>: Strings are so expressive they can never be properly synthesized. I grant you that. To be fair, I'd assume that this applies even more to vocal music -- quite apart from the expressivity of voice, midi doesn't even attempt to add lyrics. Yes and no! The MIDI files from LilyPond indeed contain the lyrics in a form that can be used by some MIDI sequencers to show the lyrics in a Karaoke-like fashion. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Stemming and lyrics on combined parts
Quoting Carl Peterson <[EMAIL PROTECTED]>:
I'm trying to take advantage of automatic part combining to make it easier
to set the songs for a hymnal. There are a couple of technical things I need
assistance on.
1) Whenever two parts on the same staff are on the same note, the part
combiner only prints one stem. Is there any way to get the part combiner to
output two stems for a due notes?
It seems that you don't want to combine the parts, but rather to keep
them as two separate voices, typeset in the same staff.
Something like
soprano = \relative c'{ c d e f }
alto = \relative c' { c b e d }
\score{
\new Staff << \soprano \\ \alto >>
}
2) Is there a way to bind the lyrics to the original (uncombined) parts
without outputting the parts themselves?
Not if you use \partcombine, but indeed if you use the technique
described above (or even easier if you read section "Explicitly
intantiating
voice" in the manual).
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidental besides trill
Hi.
> How to put an accidental besides trill?
Try this:
e^\markup{\musicglyph #"scripts.trill" {\raise #1 \sharp}}
Best,
Gilles
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: passing a Context to a scheme function (format-metronome-markup)
On Mon, Oct 13, 2008 at 12:02 PM, Graham Percival <[EMAIL PROTECTED]> wrote:
>
> However, what grob produces the tempo mark? Neither of these
> (exaggerated) overrides produces any change.
>
> \version "2.11.61"
> \relative c' {
> \override MetronomeMark #'padding = #8
> \override RehearsalMark #'padding = #8
> \tempo "Allegro" 4 = 120
> c1
> }
Just a guess, but I believe these grobs are created at the Score level:
\version "2.11.61"
\relative c' {
\override Score.MetronomeMark #'padding = #8
\override Score.RehearsalMark #'padding = #8
\tempo "Allegro" 4 = 120
c1
}
HTH,
Patrick
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
overhead projection of lilypond scores
when teaching a congregation a new worship song, it would be rather nice to project the melody line onto the screen as well as the words. But black-on-white is a projection disaster. It really needs to be yellow staff/text on a blue background. And probably a thicker text font than times new roman. Is this achievable, please ? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Style picker, cookies, etc. (was: WANTED: Design for documentation ...)
On Mon, Oct 13, 2008 at 1:02 PM, Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > > Am Montag, 13. Oktober 2008 schrieb Kurt Kroon: >> On 2008/10/11 1:00 PM, "Patrick McCarty" <[EMAIL PROTECTED]> wrote: >> > >> > It sounds like you know how to implement this. Would you be willing >> > to work on it or look more into it? This would be a wonderful >> > "feature" to have. >> > >> > Thanks, >> > Patrick >> >> It's quite simple, really (he writes with tongue very firmly in cheek) -- >> just direct the server to send this cookie (or something like it) > > Aren't we talking about static html pages here? Yes, but we do have alternate stylesheets that can be made "persistent" with server-side scripting when the client selects one of these stylesheets. I believe this is what Kurt is referring to. -Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Moving guitar fingering orientations
It's the one I sent you. The bit in the learning manual is different, and I don't think it's considered a snippet. Jon Valentin Villenave wrote: 2008/10/13 Jonathan Kulp <[EMAIL PROTECTED]>: That's a good idea, Trevor, thanks. So, what's the snippet in the end? :-) Cheers, Valentin -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Keeping annotations when extracting parts from a score
Hey! I've got a song where several annotations like "Refrain" or "Verse" are set in the Vocals (because that's the voice at the top of the system). Now I'm starting to extract parts, and of course the annotations are only shown in the vocal part. is there any other way to have the annotations in each other part than to write it down for any voice but using tags to prevent them getting printed in the score? It would be nice if I could define for e.g. bar 3 independently of the instrument the part is for that the annotation "Refrain" has to be set at the upper right of the bar. Thanks for your ideas, Julian signature.asc Description: This is a digitally signed message part. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Headword for unfretted-strings
Graham, you wrote Monday, October 13, 2008 7:35 PM
On Sat, 11 Oct 2008 08:33:37 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
Graham, you wrote Saturday, October 11, 2008 12:41 AM
> Not the MIDI version of string sounds, you don't. :)
Strings are so expressive they can never be properly
synthesized. I grant you that.
To be fair, I'd assume that this applies even more to vocal music
-- quite apart from the expressivity of voice, midi doesn't even
attempt to add lyrics.
As Mats said, Lily does output lyrics to MIDI,
which reminded me that needs to be added to NR 3.5.
> Seriously, there's no reason to build the .midi files in
> Documentation/user/out-www/. I can appreciate that you wanted to
I wasn't thinking of people who build the docs; rather
people who read them.
Erm. How many people actually click on the graphics? And how
many people actually click on the graphics, copy&paste the
*correct* material (ie not the entire .ly file!), and generate the
output themselves.
I think we're down to count-on-one-hand territory here... and
those people surely must have read LM 3 already and therefore know
how to add the \midi{} block themselves.
I would agree, if that's all there was to it.
But the midiInstruments need to be added, and
the appropriate tempo.
But I'm not going to die in the ditch defending this
Well, neither am I. :) If you want to add \midi{} to all
headwords, go ahead. I'm firmly of the opinion that this will be
useful to at most three people in the world... but then again,
we've spent longer discussing this change than it would take to
make it in the first place, so I can't really play the
"efficiency" card here.
There -are- more urgent things to do, so I'll
leave this as one more TODO when everything
else has settled out.
Cheers,
- Graham
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Stemming and lyrics on combined parts
I do want to combine the parts. I want them to appear in chord form, except
when the voices are a 2nd apart or closer.
On Mon, Oct 13, 2008 at 4:54 PM, Mats Bengtsson <[EMAIL PROTECTED]>wrote:
> Quoting Carl Peterson <[EMAIL PROTECTED]>:
>
> I'm trying to take advantage of automatic part combining to make it easier
>> to set the songs for a hymnal. There are a couple of technical things I
>> need
>> assistance on.
>>
>> 1) Whenever two parts on the same staff are on the same note, the part
>> combiner only prints one stem. Is there any way to get the part combiner
>> to
>> output two stems for a due notes?
>>
>
> It seems that you don't want to combine the parts, but rather to keep them
> as two separate voices, typeset in the same staff.
> Something like
>
> soprano = \relative c'{ c d e f }
> alto = \relative c' { c b e d }
> \score{
> \new Staff << \soprano \\ \alto >>
> }
>
>
>> 2) Is there a way to bind the lyrics to the original (uncombined) parts
>> without outputting the parts themselves?
>>
> Not if you use \partcombine, but indeed if you use the technique described
> above (or even easier if you read section "Explicitly intantiating
> voice" in the manual).
>
> /Mats
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Headword for unfretted-strings
On Mon, 13 Oct 2008 22:50:54 +0200 Mats Bengtsson <[EMAIL PROTECTED]> wrote: > Quoting Graham Percival <[EMAIL PROTECTED]>: > >> Strings are so expressive they can never be properly > >> synthesized. I grant you that. > > > > To be fair, I'd assume that this applies even more to vocal music > > -- quite apart from the expressivity of voice, midi doesn't even > > attempt to add lyrics. > > Yes and no! The MIDI files from LilyPond indeed contain the lyrics > in a form that can be used by some MIDI sequencers to show the lyrics > in a Karaoke-like fashion. But, unless festival has improved tremendosly, those don't affect the sound output at all. That's what I was talking about -- audio output as opposed to png or pdfs. AFAIK singing lyrics is still an area of research and experimental programs (like the vocaloid software that's popular in Japan). It certainly isn't part of the typical MIDI sequencers found on normal computers. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: passing a Context to a scheme function (format-metronome-markup)
On Mon, 13 Oct 2008 14:05:32 -0700 "Patrick McCarty" <[EMAIL PROTECTED]> wrote: > On Mon, Oct 13, 2008 at 12:02 PM, Graham Percival <[EMAIL PROTECTED]> > wrote: > > > > However, what grob produces the tempo mark? Neither of these > > (exaggerated) overrides produces any change. > > > > \override MetronomeMark #'padding = #8 > > \override RehearsalMark #'padding = #8 > > Just a guess, but I believe these grobs are created at the Score > level: Mao. This is the definition of a "paper bag mistake". Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
insertion of UTF-8 characters
The documentation [/Lilypond notation reference.pdf/, “3.3.3 Text
encoding”, pdf p. 318.] states that UTF-8 coding is used in Ly and that
UTF-8 hex codes can be inserted into text. An example is given, and I
show it here using the code of interest to me - that for the Copyright sign:
#(ly:export (ly:wide-char->utf-8 #xc2a9))|
|This example has no context, and when I put it in one I cannot get it
to work. I suggest that the documentation be modified to give one.
Meanwhile, I need a solution to the problem of how to insert a Copyright
sign into the copyright line. Here's what I tried:
\header {...
copyright = "#(ly:export (ly:wide-char->utf-8 #xc2a9)) 2008"
...
It produced this in the PDF output:
#(ly:export (ly:wide-char->utf-8 #xc2a9)) 2008
Placing the UTF code export line outside of the quotes wouldn't even
compile.
Can anyone suggest how to do this?
Thanks!
Tom
||
--
~
Tom Cloyd, MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [EMAIL PROTECTED] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)
~
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: insertion of UTF-8 characters
forgot this: I'm running Ly 2.11.60, on Kubuntu Linux 8.04.1
Tom Cloyd wrote:
The documentation [/Lilypond notation reference.pdf/, “3.3.3 Text
encoding”, pdf p. 318.] states that UTF-8 coding is used in Ly and
that UTF-8 hex codes can be inserted into text. An example is given,
and I show it here using the code of interest to me - that for the
Copyright sign:
#(ly:export (ly:wide-char->utf-8 #xc2a9))|
|This example has no context, and when I put it in one I cannot get it
to work. I suggest that the documentation be modified to give one.
Meanwhile, I need a solution to the problem of how to insert a
Copyright sign into the copyright line. Here's what I tried:
\header {...
copyright = "#(ly:export (ly:wide-char->utf-8 #xc2a9)) 2008"
...
It produced this in the PDF output:
#(ly:export (ly:wide-char->utf-8 #xc2a9)) 2008
Placing the UTF code export line outside of the quotes wouldn't even
compile.
Can anyone suggest how to do this?
Thanks!
Tom
||
--
~
Tom Cloyd, MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [EMAIL PROTECTED] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)
~
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: insertion of UTF-8 characters
Try copying this character in there:
©
I tried the way the docs say, as well, and never got it to work. I
found that if I just copied an actual copyright symbol into my files and
made sure the editor was saving in utf-8 encoding, it all worked fine.
Jon
Tom Cloyd wrote:
forgot this: I'm running Ly 2.11.60, on Kubuntu Linux 8.04.1
Tom Cloyd wrote:
The documentation [/Lilypond notation reference.pdf/, “3.3.3 Text
encoding”, pdf p. 318.] states that UTF-8 coding is used in Ly and
that UTF-8 hex codes can be inserted into text. An example is given,
and I show it here using the code of interest to me - that for the
Copyright sign:
#(ly:export (ly:wide-char->utf-8 #xc2a9))|
|This example has no context, and when I put it in one I cannot get it
to work. I suggest that the documentation be modified to give one.
Meanwhile, I need a solution to the problem of how to insert a
Copyright sign into the copyright line. Here's what I tried:
\header {...
copyright = "#(ly:export (ly:wide-char->utf-8 #xc2a9)) 2008"
...
It produced this in the PDF output:
#(ly:export (ly:wide-char->utf-8 #xc2a9)) 2008
Placing the UTF code export line outside of the quotes wouldn't even
compile.
Can anyone suggest how to do this?
Thanks!
Tom
||
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
insertion of current date in text string
OK, I've exhausted myself trying to solve another problem
I understand that I can put a current date into a "\header{..." field
(or whatever they're called), by doing something like
date = #(strftime "%Y.%m.%d" (localtime (current-time)))
\header{
.
.
.
subsubtitle = \date
BUT, how do I do this:
subsubtitle = { "version " + \date}
I cannot find an example, and haven't been able to figure it out
empirically.
t.
--
~
Tom Cloyd, MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [EMAIL PROTECTED] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)
~
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: insertion of current date in text string
Wow, I didn't realize you could have the date put in automagically like
that! Pretty cool. Is it the Lilypond version number that you want to
insert? I don't know how to do it in the subsubtitle, but it always
appears in the last footer of the score by default, right? It does in
my scores anyway. Not sure how you'd capture that value and use it in
the subsubtitle...
Jon
Tom Cloyd wrote:
OK, I've exhausted myself trying to solve another problem
I understand that I can put a current date into a "\header{..." field
(or whatever they're called), by doing something like
date = #(strftime "%Y.%m.%d" (localtime (current-time)))
\header{
.
.
.
subsubtitle = \date
BUT, how do I do this:
subsubtitle = { "version " + \date}
I cannot find an example, and haven't been able to figure it out
empirically.
t.
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: insertion of current date in text string
On Mon, 13 Oct 2008 21:50:05 -0500
Jonathan Kulp <[EMAIL PROTECTED]> wrote:
> Tom Cloyd wrote:
> > BUT, how do I do this:
> >
> > subsubtitle = { "version " + \date}
> >
> > I cannot find an example, and haven't been able to figure it out
> > empirically.
You got to LSR and search for "version". It's the second item.
Alternately, look at the Snippet List of Text.
> Wow, I didn't realize you could have the date put in automagically
> like that! Pretty cool.
I highly recommend that you spend an hour someday just browsing
the Snippet List. You won't regret it. :)
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: insertion of current date in text string
Every time I spend five minutes doing this I find something cool. It might be overwhelming to spend an hour :) Jon Graham Percival wrote: On Mon, 13 Oct 2008 21:50:05 -0500 I highly recommend that you spend an hour someday just browsing the Snippet List. You won't regret it. :) Cheers, - Graham -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: insertion of current date in text string
Well, here's how I work: I have the PDF doc files for the Ly version I'm running all open (all except "Lilypond internals", which I'm not diving that deep). When I need something, I use my PDF program (in Kubuntu Linux, it's KPDF, and it excelent) do searches for everything I can think of which relates, which is a lot of stuff. Often I find it. I also keep extensive separate notes on what I've learned and am learning. The problem is simply that I keep raising the bar, as it were. Nowagain: I'm being misunderstood, and, strangely, it appears that no one is reading either the subject line of this thread or what I'm writing in the message body. Let me say it again: I want to combine current date (which I now have) with the text string "version" to output the version date OF THE BLOODY SCORE, not of the Lilypond version I'm running. All over the documentation, the authors are relentlessly single minded, as you both have been (ha!) in seeing "version" as referring IN THIS CONTEXT to Lilypond versions. It does not. Other things have versions, too, I assure you. In this case, it's my score(s). So...hopefully with that cleared up, let me assure you that I've searched all through all the documentation I can find/understand, and I don't see how to do this thing I'm trying to do... The more general problem is actually more interesting: I looked for a time for some way to combine user created variables (in this case my \date variable) with text strings, when setting up things like titling, etc. I couldn't find a single example of this, nor could I find a general discussion of how to do it. Yet, it must be possible, surely. Ergo...I need help. t. Jonathan Kulp wrote: Every time I spend five minutes doing this I find something cool. It might be overwhelming to spend an hour :) Jon Graham Percival wrote: On Mon, 13 Oct 2008 21:50:05 -0500 I highly recommend that you spend an hour someday just browsing the Snippet List. You won't regret it. :) Cheers, - Graham -- ~ Tom Cloyd, MS MA, LMHC - Private practice Psychotherapist Bellingham, Washington, U.S.A: (360) 920-1226 << [EMAIL PROTECTED] >> (email) << TomCloyd.com >> (website) << sleightmind.wordpress.com >> (mental health weblog) ~ ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: insertion of current date in text string
On Mon, 13 Oct 2008 20:43:26 -0700
Tom Cloyd <[EMAIL PROTECTED]> wrote:
> So...hopefully with that cleared up, let me assure you that I've
> searched all through all the documentation I can find/understand, and
> I don't see how to do this thing I'm trying to do...
Hmm. Maybe the tutorial? "Organizing pieces with variables"?
\version "2.11.62"
myversion = "1.1"
date = "I can't be bothered to look this up right now"
\header {
subtitle = \markup { \myversion \date}
}
{ c'4 }
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: insertion of current date in text string
Tom Cloyd wrote:
> OK, I've exhausted myself trying to solve another problem
>
> I understand that I can put a current date into a "\header{..." field
> (or whatever they're called), by doing something like
>
> date = #(strftime "%Y.%m.%d" (localtime (current-time)))
>
> \header{
> .
> .
> .
> subsubtitle = \date
>
>
> BUT, how do I do this:
>
> subsubtitle = { "version " + \date}
>
> I cannot find an example, and haven't been able to figure it out
> empirically.
Just add \markup.
subsubtitle = \markup{ version \date }
Paul Scott
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: overhead projection of lilypond scores
2008/10/13 Gerry Prosser <[EMAIL PROTECTED]>: > when teaching a congregation a new worship song, it would be rather nice to > project the melody line onto the screen as well as the words. But > black-on-white is a projection disaster. It really needs to be yellow > staff/text on a blue background. And probably a thicker text font than times > new roman. Is this achievable, please ? A bit a joke. I'd say it's quite easy to get dark (colored) text on light (colored) screen -- just paint a screen with some (light) color and then pick up an appropriate color for text. This will work :-) Won't work for dark screen and light text, though :-) -- Dmytro O. Redchuk ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
