Re: minor chords (and a possible transition to a new topic)
Am 22.03.2014 02:45, schrieb Anthony Youngman:
And I don't tend to dig deep into all the esoteric settings - there
are so many of them that I don't understand, that I tend to shy away
from them. I shouldn't, but I'd rather just use standard bells and
whistles - when I need to use all sorts of fancy over-ride tricks to
achieve effects that I see in pretty much *all* the printed music I
play, it puts me off.
Well, redefining paper variables is actually not really advanced.
If you want to understand better what LilyPond does and how you can
alter the output, you’ll be well advised to read in the Notation
Reference on the website and collect what information you need – in most
cases there is an explanation there, except for more extravagant wishes.
Of course this costs time until you have an overview, but it will reward
the effort.
That said, I'll play with this and see what it does - I've got a piece
I've been working on that I had to muck about with and force.
Oh - and sorry Phil, page-count = 1 didn't work. Although iirc I put
it in \layout{} not \paper{}. Unless that was the wrong place to put it?
Yes. page-count is a paper variable and can only be set in \paper {}.
That's another place for confusion - I get the impression that some
settings work fine in either, others only seem to work in the layout
section, maybe others only work in the paper section?
Cheers,
Wol
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Generating Interest in LilyPond through Kickstarter
On Mar 22, 2014, at 4:21 AM, Paul Tannous ptann...@hotmail.com wrote: Lilyponders, I am considering starting a Kickstarter project to engrave a major choral work in LilyPond that is in the public domain. The idea is to raise funds to pay for the LilyPond engraving, proofreading, contributor premiums, etc. The LilyPond source would then be put into the public domain. Rather than make PDFs available, the LilyPond source could be put on a web site with the URL for LilyPond. Anyone wanting a printed copy, could download and install LilyPond if they didn't have it already. The idea would be to generate interest in LilyPond. Premiums for contributors could be PDFs of some of the parts of the engraved choral work or even the whole score for large contributors. From what I've seen of Kickstarter, typically the smallest premium that is attractive enough to generate contributions is a T-Shirt. So, this could be one of our premiums. If you have ideas for other premiums, they would be appreciated. If this project is successful, other projects for different works could be started. A successful project might spawn imitators making even more LilyPond source works available. I have talked to several choir directors about what to use for a first project. Handel's 'Messiah' was suggested by all of them. I am aware of Nicolas Sceaux's fine work in engraving 'Messiah', but the choir directors who spoke with me prefer to use a different version for their performances. All comments regarding this project will be appreciated. Thank you, Paul Tannous Sounds like a great idea! Make sure to e-mail choir directors across the US to see what may interest them - even if they cannot contribute financially to the project, it will have more chances of success if you have concerts lined up to which donors can go, a recording that they can receive, a program in which their name appears, etc.. All the best and good luck! Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Generating Interest in LilyPond through Kickstarter
Am 22.03.2014 08:57, schrieb Mike Solomon: On Mar 22, 2014, at 4:21 AM, Paul Tannous ptann...@hotmail.com wrote: Lilyponders, I am considering starting a Kickstarter project to engrave a major choral work in LilyPond that is in the public domain. The idea is to raise funds to pay for the LilyPond engraving, proofreading, contributor premiums, etc. The LilyPond source would then be put into the public domain. Rather than make PDFs available, the LilyPond source could be put on a web site with the URL for LilyPond. Anyone wanting a printed copy, could download and install LilyPond if they didn't have it already. The idea would be to generate interest in LilyPond. Premiums for contributors could be PDFs of some of the parts of the engraved choral work or even the whole score for large contributors. From what I've seen of Kickstarter, typically the smallest premium that is attractive enough to generate contributions is a T-Shirt. So, this could be one of our premiums. If you have ideas for other premiums, they would be appreciated. If this project is successful, other projects for different works could be started. A successful project might spawn imitators making even more LilyPond source works available. I have talked to several choir directors about what to use for a first project. Handel's 'Messiah' was suggested by all of them. I am aware of Nicolas Sceaux's fine work in engraving 'Messiah', but the choir directors who spoke with me prefer to use a different version for their performances. All comments regarding this project will be appreciated. Thank you, Paul Tannous Sounds like a great idea! Make sure to e-mail choir directors across the US to see what may interest them - even if they cannot contribute financially to the project, it will have more chances of success if you have concerts lined up to which donors can go, a recording that they can receive, a program in which their name appears, etc.. I recently made a similar suggestion with the Winterreise, and some commented it problematic to create new free editions of pieces that already exist in good free editions. Urs BTW: Did you see http://igg.me/at/free-fried? All the best and good luck! Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- Urs Liska www.openlilylib.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Generating Interest in LilyPond through Kickstarter
Paul Tannous ptann...@hotmail.com writes: Anyone wanting a printed copy, could download and install LilyPond if they didn't have it already. The idea would be to generate interest in LilyPond. That's a noble idea, but aren't you afraid that it will have the opposite effect and scare people away? I don't see many vanilla computer using musicians jump through the hoops of building and installing LilyPond just to get some score PDFs. Wouldn't something like this work better (amounts are arbitrary): - for 5$ or more you get the source - for 10$ or more you get the PDF - for 50$ or more you get a printed copy mailed -- Johan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Generating Interest in LilyPond through Kickstarter
On Sat, 2014-03-22 at 03:21 +, Paul Tannous wrote: The LilyPond source would then be put into the public domain. Rather than make PDFs available, the LilyPond source could be put on a web site with the URL for LilyPond. Anyone wanting a printed copy, could download and install LilyPond if they didn't have it already. The idea would be to generate interest in LilyPond. Presumably someone will generate a set of PDFs and put them on IMSLP. And people who are not prepared to read the LilyPond sources - they just want the printed score - will get those, and would be wise to do so, since someone malicious could generate an altered version the the LilyPond sources to do bad things. While LilyPond is a specialized interest thing malicious files are not going to happen, except by pranksters, but it is something to bear in mind. (I hate to sound a note of caution). Richard ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: minor chords (and a possible transition to a new topic)
On 22/03/2014 07:50, Simon Albrecht wrote: Am 22.03.2014 02:45, schrieb Anthony Youngman: And I don't tend to dig deep into all the esoteric settings - there are so many of them that I don't understand, that I tend to shy away from them. I shouldn't, but I'd rather just use standard bells and whistles - when I need to use all sorts of fancy over-ride tricks to achieve effects that I see in pretty much *all* the printed music I play, it puts me off. Well, redefining paper variables is actually not really advanced. If you want to understand better what LilyPond does and how you can alter the output, you’ll be well advised to read in the Notation Reference on the website and collect what information you need – in most cases there is an explanation there, except for more extravagant wishes. Of course this costs time until you have an overview, but it will reward the effort. Well, I've put in a fair bit of time and effort over the years. The problem, as always, is finding time to play, and also remembering what worked last time :-) Many moons ago, I proofread the entire main manual about three times! I've dug into the code and tried to contribute. Unfortunately, like most power tools, lily is not very friendly to light users - that's just the nature of the beast. That said, I think now I know about Kieren's page-break-permission = ##f, coupled with putting page = 1 in the right place, I think it'll work fine. Then I'll have to see if those two work together to force two pages ... :-) I need to find some time to play ... :-) Cheers, Wol ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: minor chords (and a possible transition to a new topic)
- Original Message -
From: Anthony Youngman anth...@youngman.org.uk
To: Kieren MacMillan kieren_macmil...@sympatico.ca;
lilypond-user@gnu.org
Sent: Saturday, March 22, 2014 1:45 AM
Subject: Re: minor chords (and a possible transition to a new topic)
Oh - and sorry Phil, page-count = 1 didn't work. Although iirc I put
it in \layout{} not \paper{}. Unless that was the wrong place to put it?
That's another place for confusion - I get the impression that some
settings work fine in either, others only seem to work in the layout
section, maybe others only work in the paper section?
Cheers,
Wol
If you look in the Notation Reference index under page-count it will tell
you all you need to make it work.
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: short Musikmesse minutes
On 20/03/2014 10:30, Urs Liska wrote: I think that LilyPond's main strength is transformative use: different page formats, different media, different transpositions, individual variations. Yes, and I have/had the impression that it _is_ possible now to promote this feature. Of course I don't expect the final outcome to match my current enthusiasm, but I'll surely keep you informed about my progress. Given my experience of buying some pieces, this is actually an extremely useful use. Okay, my experience is old, but I bought some pieces by P.D.Q.Bach. For a small score (ten pages?) the number of transcription errors between the score and parts was amazing. Iirc the score was correct, but the parts had errors galore. Cheers, Wol ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
passing parameter
Hi, lilyponders,
How can I combine the nrS nbS into one by passing color parameter ( red, blue
or green)?
Is there a Dots #'layer in lily?
\version 2.19.3
nrS = { \override NoteHead #'layer = #2
\override NoteHead.color = #red
\override Stem.color = #red
\override Beam.color = #red
\override Tie #'color = #red
\override Slur.color = #red
\override Dots #'layer = #2
\override Dots #'color = #red
\override Rest.color = #red
}
nbS = { \override NoteHead #'layer = #2
\override NoteHead.color = #blue
\override Stem.color = #blue
\override Beam.color = #blue
\override Tie #'color = #blue
\override Slur.color = #blue
\override Dots #'layer = #2
\override Dots #'color = #blue
\override Rest.color = #blue
}
Thank you.
Emmanuel,
Ming.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: passing parameter
Am 22.03.2014 12:43, schrieb MING TSANG:
Hi, lilyponders,
How can I combine the nrS nbS into one by passing color parameter ( red, blue
or green)?
Is there a Dots #'layer in lily?
\version 2.19.3
nrS = { \override NoteHead #'layer = #2
\override NoteHead.color = #red
\override Stem.color = #red
\override Beam.color = #red
\override Tie #'color = #red
\override Slur.color = #red
\override Dots #'layer = #2
\override Dots #'color = #red
\override Rest.color = #red
}
nbS = { \override NoteHead #'layer = #2
\override NoteHead.color = #blue
\override Stem.color = #blue
\override Beam.color = #blue
\override Tie #'color = #blue
\override Slur.color = #blue
\override Dots #'layer = #2
\override Dots #'color = #blue
\override Rest.color = #blue
}
Thank you.
Emmanuel,
Ming.
nS =
#(define-music-function (parser location color)(color?)
#{
\override NoteHead #'layer = #2
\override NoteHead.color = $color
\override Stem.color = #blue
\override Beam.color = #blue
\override Tie #'color = #blue
\override Slur.color = #blue
\override Dots #'layer = #2
\override Dots #'color = #blue
\override Rest.color = #blue
#})
\relative c' {
c d \nS #red e( f) \nS #blue g1
}
You may consider using \temporary \override (rather new syntax)
And you should add another function that \revert-s the properties.
HTH
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: passing parameter
Urs Liska u...@openlilylib.org writes:
nS =
#(define-music-function (parser location color)(color?)
#{
\override NoteHead #'layer = #2
\override NoteHead.color = $color
\override Stem.color = #blue
\override Beam.color = #blue
\override Tie #'color = #blue
\override Slur.color = #blue
\override Dots #'layer = #2
\override Dots #'color = #blue
\override Rest.color = #blue
#})
\relative c' {
c d \nS #red e( f) \nS #blue g1
}
You may consider using \temporary \override (rather new syntax)
\temporary \override basically only makes sense when you are doing a
corresponding \revert in the same command.
Note that you can with the above definition still write
\temporary \nS #red c d e f \undo \nS #red
in order to make a temporary change.
And you should add another function that \revert-s the properties.
nSrevert = \undo \nS #red
It's not even cheesy but rather the main purpose of \undo.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Generating Interest in LilyPond through Kickstarter
it would be more sensible to sell the .ly file at a higher cost. It is certainly the more valuable entity, both in terms of work in and future utility. Shane On Sat, Mar 22, 2014 at 5:27 AM, Johan Vromans jvrom...@squirrel.nl wrote: Paul Tannous ptann...@hotmail.com writes: Anyone wanting a printed copy, could download and install LilyPond if they didn't have it already. The idea would be to generate interest in LilyPond. That's a noble idea, but aren't you afraid that it will have the opposite effect and scare people away? I don't see many vanilla computer using musicians jump through the hoops of building and installing LilyPond just to get some score PDFs. Wouldn't something like this work better (amounts are arbitrary): - for 5$ or more you get the source - for 10$ or more you get the PDF - for 50$ or more you get a printed copy mailed -- Johan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
alternating left/right margins
No doubt I've missed it, but I cannot find a place in the manuals helping me to alternate left and right margin widths to accomodate inserting a printed copy into a 3-hole punched notebook. Thanks! Mark ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: alternating left/right margins
Hi Mathias, maybe you're looking for this: http://lilypond.org/doc/v2.16/Documentation/notation/horizontal-spacing-_005cpaper-variables#_005cpaper-variables-for-two_002dsided-mode ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
python-ly
Hi, python-ly is a very usable Python package. One remark though: I have installed it on Linux Fedora $ python-pip install python-ly installs the python 2.x version $ python3-pip install python-ly installs the python 3.x version But if I want to install both a problem rises: the /usr/bin/ly tool will be overwritten. To solve this I first installed the python3 version. Then I renamed /usr/bin/ly to /usr/bin/ly3. And finally I installed the python2 version. Why I need both versions? I don't, I am just a curious person who wants to try everything - which is good for betatesters and bugreporters :-) -- MT ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: python-ly
2014-03-22 18:01 GMT+01:00 Martin Tarenskeen m.tarensk...@zonnet.nl: Hi, python-ly is a very usable Python package. One remark though: I have installed it on Linux Fedora $ python-pip install python-ly installs the python 2.x version $ python3-pip install python-ly installs the python 3.x version But if I want to install both a problem rises: the /usr/bin/ly tool will be overwritten. To solve this I first installed the python3 version. Then I renamed /usr/bin/ly to /usr/bin/ly3. And finally I installed the python2 version. Why I need both versions? I don't, I am just a curious person who wants to try everything - which is good for betatesters and bugreporters :-) you should use a virtualenv? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Generating Interest in LilyPond through Kickstarter
Urs Liska wrote: I recently made a similar suggestion with the Winterreise, and some commented it problematic to create new free editions of pieces that already exist in good free editions. Urs BTW: Did you see http://igg.me/at/free-fried? If you start a project, be sure and give the URL on the list as Urs did. I looked at his project and contributed. Chris ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Generating Interest in LilyPond through Kickstarter
Am 22.03.2014 19:23, schrieb Chris Crossen: Urs Liska wrote: I recently made a similar suggestion with the Winterreise, and some commented it problematic to create new free editions of pieces that already exist in good free editions. Urs BTW: Did you see http://igg.me/at/free-fried? If you start a project, be sure and give the URL on the list as Urs did. And don't be shy and do that more than once ;-) I looked at his project and contributed. Thank you very much! Already noticed :-) Chris ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: storing and manipulating multi-chunk texts
Hi Kieren, 2014-03-17 3:24 GMT+01:00 Kieren MacMillan kieren_macmil...@sympatico.ca: Hi Harm, do you already have results from your real-world testings? If 'line-parts' is useful, I'd like to turn it into a patch. Or do you notice some issues? Haven't had the chance to stress-test it yet -- sorry. Give me a few days, and I'll get back to you with the results. Meanwhile I found a use case where line-parts gave unexpected output. Additionally I thought it would be nice not only being able to reformat a given markup or list, but to edit it as desired. Therefore I wrote the markup-list-commands: delete-lines extract-lines lines-tail lines-head Together with the fixed line-parts in the attached file. Cheers, Harm \version 2.19.1 %#(use-modules (ice-9 pretty-print)) %#(use-modules (srfi srfi-1)) #(define (get-certain-list-elts number-list lst) (cond ((null? number-list) lst) ((or (number? number-list) (number-list? number-list)) (let* ((new-number-list (if (number? number-list) (list number-list) number-list)) (sorted-number-list (sort new-number-list ))) (if (or ( (car sorted-number-list) (length lst)) (= (car (last-pair sorted-number-list)) 0)) (ly:error The deserved line is not part of the markup.) (map (lambda (x) (list-ref lst (- x 1))) new-number-list (else (ly:error number-list has to be a single number or a list of numbers. #(define-markup-list-command (line-parts layout props args)(markup-list?) (let* ((make-stencil-list (lambda (a) (let ((fromproperty-markup? (lambda (m) (if (procedure? m) (eq? 'fromproperty-markup (procedure-name m)) #f))) (line-markup? (lambda (m) (if (procedure? m) (eq? 'line-markup (procedure-name m)) #f (cond ;; what to do, if the argument is not of type ;; fromproperty/line-markup: ((and (list? a) (not (null? a)) ;; hmm, can arg ever be null? (not (fromproperty-markup? (car a))) (not (line-markup? (car a (interpret-markup-list layout props (list a))) ;; fromproperty-markup needs to be special-cased, because it's ;; argument is not a line-markup, but a symbol, looked up in ;; props. ;; ;; hmm, do I need to do: ;; (cons ;; (list ;; (cons symbol `(,property-recursive-markup ,symbol))) ;; props) ;; again? (it's already done in the fromproperty-def) ((and (list? a) (not (null? a)) ;; hmm, can the argument ever be null? (fromproperty-markup? (car a))) (let* ((prop-arg (chain-assoc-get (last a) props)) (fromprop-arg (if (not (list? prop-arg)) (list prop-arg) prop-arg))) (if prop-arg (interpret-markup-list layout props (if (procedure? (car fromprop-arg)) (last fromprop-arg) fromprop-arg)) (list empty-stencil ;; what to do with a line-markup: ((and (list? a) (not (null? a)) (line-markup? (car a))) (interpret-markup-list layout props (last a))) ;; in any other case return empty-stencil. ;; hmm, are other cases thinkable at all? (else (list empty-stencil))) (flatten-list (map make-stencil-list args #(define-markup-list-command (extract-lines layout props whichs args) (number-or-pair? markup-list?) (let ((stil-list (line-parts-markup-list layout props args))) (get-certain-list-elts whichs stil-list))) #(define-markup-list-command (delete-lines layout props whichs args) (number-or-pair? markup-list?) (let* ((stil-list (line-parts-markup-list layout props args)) (lines-to-delete (get-certain-list-elts whichs stil-list))) (lset-difference eq? stil-list lines-to-delete))) #(define-markup-list-command (lines-head layout props which args) (number?
Re: minor chords (and a possible transition to a new topic)
Am 22.03.2014 11:01, schrieb Anthony: Well, I've put in a fair bit of time and effort over the years. The problem, as always, is finding time to play, and also remembering what worked last time :-) Many moons ago, I proofread the entire main manual about three times! I've dug into the code and tried to contribute. Unfortunately, like most power tools, lily is not very friendly to light users - that's just the nature of the beast. True. To dig deeper, one also needs experience with or interest in programming – that is, in some kind of mathematical/logical thinking. And since most (or many) people have a pronounced dislike against maths and are happy to never have to look below the surface of their OS, this is an important point… Well, there are the templates in Frescobaldi which make it easy as long as one follows the exact path indicated, but this is rarely a long time… ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Using custom fonts and unicodes
I am currently trying to access custom unicode characters via:
\markup{\override #'(font-name . Blissymbolics) \char ##x1234}
Where 1234 is the unicode hexadecimal code, however this is giving me
incorrect, foreign characters, which leads me to believe that the font I'm
trying to access isn't visible to lilypond.
Is this correct? And how do I fix it so that I can access any individual
character from any individual font I'd like.
Thank you.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Using custom fonts and unicodes
On 23/03/14 16:07, Joey Di Nardo wrote:
I am currently trying to access custom unicode characters via:
\markup{\override #'(font-name . Blissymbolics) \char ##x1234}
Where 1234 is the unicode hexadecimal code, however this is giving me
incorrect, foreign characters, which leads me to believe that the font
I'm trying to access isn't visible to lilypond.
Is this correct? And how do I fix it so that I can access any
individual character from any individual font I'd like.
Does lilypond -dshow-available-fonts show that font. i.e.:
lilypond -dshow-available-fonts 21 | grep Blissymbolics
The font name inside the markup command has to match what lilypond shows
for the family name with -dshow-available-fonts.
As an aside, why does lilypond direct the output from commands such as
this to stderr rather than stdout? It means having to redirect stderr to
stdout so that the shell can pipe the output to grep's stdin.
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
