Re: Question re: CadenzaOn
On 19 September 2010 08:11, Joshua Armenta wrote: > > Hello, > I have a score with multiple staves. One instrument enter into unmetered > timing and performs a cadenza, the other five instruments rest. The problem > is that when the file is compiled, the barlines in the output is completely > thrown off, even when the same measure is put into a Cadenza on statement in > every stave. I have tried with a whole rest and with using the cadenza notes > as a model and replacing note names with R (Thus preserving the values) but > the output iisn't fixed either way > I can't seem to find any answers. Any help would be very much appreciated. Pu the cadenza in a separate variable and use #(ly:export (mmrest-of-length MyCadenza)) as explained in NR 1.2.6 Special rhythmic concerns > Aligning to cadenzas http://lilypond.org/doc/v2.13/Documentation/notation/special-rhythmic-concerns.html#aligning-to-cadenzas Cheers, Xavier -- Xavier Scheuer ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
piano staves and lyrics
Hello,
I've included a minimal example below; why doesn't it work and how do I
correct it?
(It works fine without the alto and tenor parts.)
Many thanks yet again,
Gerard
\version "2.12.2"
\score {
\new PianoStaff {
<<
\new Staff {
<<
\new Voice="soprano" { \voiceOne
\time 2/2
\key d \major
\relative c' { fis2 e}
}
\new Voice="alto" { \voiceTwo
\relative c' { d2 d4( cis) }
}
>>
}
\addlyrics { please help }
% \lyricsto soprano { please help } also fails
\new Staff {
\clef bass
<<
\new Voice="tenor" { \voiceOne
\time 2/2
\key d \major
\relative c' { a2 g }
}
\new Voice="bass" { \voiceTwo
\relative c { d2 ais }
}
>>
}
>>
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
question about bar lines
I am having a problem with bar lines, if I put the following around a staff break \bar "||" \break \bar "|:" I get the repeat sign on the start of the staff, but not the double bar on the end of the previous staff. I am using partial bars before and after the break, but through experimentation, this doesn't seem to change much. If I remove the open repeat, the double bar appears on the first staff. Anyone have any ideas what I'm doing wrong? Thanks very much! -akj ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: question about bar lines
On 2010-09-19 15:38, Alex Jones wrote: I am having a problem with bar lines, if I put the following around a staff break \bar "||" \break \bar "|:" I get the repeat sign on the start of the staff, but not the double bar on the end of the previous staff. [...] Anyone have any ideas what I'm doing wrong? Use \bar "||:" \break. Cheers, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: piano staves and lyrics
Check your inbox for the answer to this question you were sent yesterday.
--
Phil Holmes
- Original Message -
From: Gerard McConnell
To: lilypond-user@gnu.org
Sent: Saturday, September 18, 2010 12:41 PM
Subject: piano staves and lyrics
Hello,
I've included a minimal example below; why doesn't it work and how do I
correct it?
(It works fine without the alto and tenor parts.)
Many thanks yet again,
Gerard
\version "2.12.2"
\score {
\new PianoStaff {
<<
\new Staff {
<<
\new Voice="soprano" { \voiceOne
\time 2/2
\key d \major
\relative c' { fis2 e}
}
\new Voice="alto" { \voiceTwo
\relative c' { d2 d4( cis) }
}
>>
}
\addlyrics { please help }
% \lyricsto soprano { please help } also fails
\new Staff {
\clef bass
<<
\new Voice="tenor" { \voiceOne
\time 2/2
\key d \major
\relative c' { a2 g }
}
\new Voice="bass" { \voiceTwo
\relative c { d2 ais }
}
>>
}
>>
}
}
--
___
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: best practices
Graham Percival gmail.com> > We *have* a set of "best practices". They're LM 5 Working on > LilyPond projects. I wrote them two years ago, and AFAIK nobody > has ever read them. Where exactly are they, please? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
- Original Message - From: "aliteralmind" To: Sent: Sunday, September 19, 2010 4:01 PM Subject: Re: best practices Graham Percival gmail.com> We *have* a set of "best practices". They're LM 5 Working on LilyPond projects. I wrote them two years ago, and AFAIK nobody has ever read them. Where exactly are they, please? Um. Learning Manual 5. Entitled "Working on LilyPond projects". -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: question about bar lines
Thanks a lot!!! -akj On Sep 19, 2010, at 10:11 AM, Alexander Kobel wrote: > On 2010-09-19 15:38, Alex Jones wrote: >> I am having a problem with bar lines, if I put the following around a staff >> break >> >> \bar "||" >> \break >> \bar "|:" >> >> I get the repeat sign on the start of the staff, but not the double bar on >> the end of the previous staff. [...] >> Anyone have any ideas what I'm doing wrong? > > Use \bar "||:" \break. > > > Cheers, > Alexander -- Alex K. Jones - clarinet www.jeffsys.net/~akjones/music 847-372-8999 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
Phil Holmes philholmes.net> writes: > > Where exactly are they, please? > > Um. Learning Manual 5. Entitled "Working on LilyPond projects". I read the learning manual. I didn't find the words "best practices" in it, and thought there was something else I was missing. I don't appreciate the condescending response. This is my first experience feeling UNwelcome as a LilyPond newbie. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
On Sep 19, 2010, at 6:09 PM, aliteralmind wrote: > Phil Holmes philholmes.net> writes: >>> Where exactly are they, please? >> >> Um. Learning Manual 5. Entitled "Working on LilyPond > projects". > > I read the learning manual. I didn't find the words "best > practices" in it, and thought there was something else I > was missing. > > I don't appreciate the condescending response. So, because the words "best practices" aren't there, you didn't understand the section "working on lilypond projects" to be a set of best practices for how to organize your lilypond projects? What did you understand that section of the learning manual to be? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
On Sun, Sep 19, 2010 at 5:09 PM, aliteralmind wrote: > Phil Holmes philholmes.net> writes: >> > Where exactly are they, please? >> >> Um. Learning Manual 5. Entitled "Working on LilyPond > projects". > > I read the learning manual. I didn't find the words "best > practices" in it, and thought there was something else I > was missing. My response was "They're LM 5 Working on LilyPond project". Granted, I missed the word "in", but why would you expect to find the word "best practices"? > I don't appreciate the condescending response. We don't appreciated condescending responses either, but we volunteer hours each week to improve the documentation, bug handling, and reply to condescending users who want to be hand-fed. > This is my first experience feeling UNwelcome as a > LilyPond newbie. Ironically, Phil was replying to you so that *I* wouldn't reply; I'm well-known for being condescending to users who complain about silly things and make the devel team feel bad. I think that anything which makes volunteers less likely to work on lilypond should be discouraged. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
Ok. I give I give. I have been studying the documentation intensely and thought there was something I missed. I already read it. It was a genuine question and I was surprised by the response. Devs don't want to be pin pricked, and newbies don't want to be fearful. I appreciate and am amazed by all your work. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
- Original Message - From: "aliteralmind" To: Sent: Sunday, September 19, 2010 5:34 PM Subject: Re: best practices Ok. I give I give. I have been studying the documentation intensely and thought there was something I missed. I already read it. It was a genuine question and I was surprised by the response. Devs don't want to be pin pricked, and newbies don't want to be fearful. I appreciate and am amazed by all your work. I'm generally normally quite helpful (or try to be). It was just that Graham had given you all the information you needed - you just needed to read it and spend a little while wondering what LM could stand for. As he said - it was a good job I got there before him! :-) -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
Graham Percival wrote Sunday, September 19, 2010 5:22 PM On Sun, Sep 19, 2010 at 5:09 PM, aliteralmind wrote: Phil Holmes philholmes.net> writes: > Where exactly are they, please? Um. Learning Manual 5. Entitled "Working on LilyPond projects". I read the learning manual. I didn't find the words "best practices" in it, and thought there was something else I was missing. My response was "They're LM 5 Working on LilyPond project". Granted, I missed the word "in", but why would you expect to find the word "best practices"? Perhaps aliteralmind is reading the 2.13 docs. In those there is no section 5 in the Learning Manual. You moved it to Application Usage, remember? I think you also changed the section name, I think to "Suggestions for writing files". Perhaps you and Phil replied too hastily to a newcomer. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
- Original Message - From: "Trevor Daniels" To: "Graham Percival" ; "aliteralmind" Cc: Sent: Sunday, September 19, 2010 6:20 PM Subject: Re: best practices Graham Percival wrote Sunday, September 19, 2010 5:22 PM On Sun, Sep 19, 2010 at 5:09 PM, aliteralmind wrote: Phil Holmes philholmes.net> writes: > Where exactly are they, please? Um. Learning Manual 5. Entitled "Working on LilyPond projects". I read the learning manual. I didn't find the words "best practices" in it, and thought there was something else I was missing. My response was "They're LM 5 Working on LilyPond project". Granted, I missed the word "in", but why would you expect to find the word "best practices"? Perhaps aliteralmind is reading the 2.13 docs. In those there is no section 5 in the Learning Manual. You moved it to Application Usage, remember? I think you also changed the section name, I think to "Suggestions for writing files". Perhaps you and Phil replied too hastily to a newcomer. See my other post to him, but I think from his follow-up we can assume he was reading 2.12. He said he'd already read the passage cited, but hadn't associated it explicitly with a "best practice" guide. And anyway, I only said "Um" :-) -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
> >>> Phil Holmes philholmes.net> writes: > And anyway, I only said "Um" It was an angry Um! :) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
"Phil Holmes" writes: > I'm generally normally quite helpful (or try to be). It was just that > Graham had given you all the information you needed - you just needed > to read it and spend a little while wondering what LM could stand for. It is agreed-upon best practice _not_ to use those abbreviations on the general user list. Because it is disingenuous to play guessing games with unsuspecting beginning users. Personally, I consider it also a turnoff on the developer list, but at least on this list, we agreed on not using unexplained abbreviations. It was likely an oversight in Graham's initial posting (he probably, judging from the replies, is not even aware that "LM" is not self-explanatory on _this_ list, or that he used it here), but then everybody and his dog jumps in barking at the newcomer who did not understand Graham's absolutely cryptic remark (imagine not being into lilypond-devel slang and try reading any sense into it), giving him the full "unpaid volunteers, scurvy dog" treatment. Get real. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
On Sun, Sep 19, 2010 at 09:36:21PM +0200, David Kastrup wrote: > "Phil Holmes" writes: > > > I'm generally normally quite helpful (or try to be). It was just that > > Graham had given you all the information you needed - you just needed > > to read it and spend a little while wondering what LM could stand for. > > It is agreed-upon best practice _not_ to use those abbreviations on the > general user list. Yes. However, I must clarify that the email in which I said "They're LM 5 Working on LilyPond projects" was written in June 2008. Over TWO YEARS ago! http://lists.gnu.org/archive/html/lilypond-user/2008-06/msg00588.html This was: - before that material was moved into Usage in 2.13 - before 2.13 even existed -- this was during the 2.11 period! - before we agreed not to use LM abbreviations. > Because it is disingenuous to play guessing games with unsuspecting > beginning users. Agreed. This was part of the motivation for the redesigned website. Users now see "Learning" in a number of places, including the navigation bars. > but then > everybody and his dog jumps in barking at the newcomer who did not > understand Graham's absolutely cryptic remark (imagine not being into > lilypond-devel slang and try reading any sense into it), giving him the > full "unpaid volunteers, scurvy dog" treatment. - user replies to a 26-month-old email - Phil Holmes clarifies it: "Um. Learning Manual 5. Entitled "Working on LilyPond projects". http://lists.gnu.org/archive/html/lilypond-user/2010-09/msg00471.html - user says "I don't appreciate the condescending response. This is my first experience feeling UNwelcome as a LilyPond newbie." http://lists.gnu.org/archive/html/lilypond-user/2010-09/msg00473.html - I get pissed off because Phil was being completely helpful, and I'm supposed to be the newbie-bashing guy. Was my reaction overblown? Perhaps. But was Phil's "Um." really all that condescending? Does three letters (well, two letters and a punctuation) really imply a "UNwelcome" feeling? Get real. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
On Sun, 19 Sep 2010, David Kastrup wrote: "Phil Holmes" writes: Graham had given you all the information you needed - you just needed to read it and spend a little while wondering what LM could stand for. It is agreed-upon best practice _not_ to use those abbreviations on the general user list. I agree, but: Since many people use these abbreviations, Would it be an an idea to mention those abreviations on manuals.html and in the titles at the top of the manuals. something like: LilyPond - Notation Reference (NR) Just an idea to make more people happy. -- Martin Tarenskeen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
- Original Message - From: "David Kastrup" To: Sent: Sunday, September 19, 2010 8:36 PM Subject: Re: best practices "Phil Holmes" writes: I'm generally normally quite helpful (or try to be). It was just that Graham had given you all the information you needed - you just needed to read it and spend a little while wondering what LM could stand for. It is agreed-upon best practice _not_ to use those abbreviations on the general user list. Because it is disingenuous to play guessing games with unsuspecting beginning users. Personally, I consider it also a turnoff on the developer list, but at least on this list, we agreed on not using unexplained abbreviations. It was likely an oversight in Graham's initial posting (he probably, judging from the replies, is not even aware that "LM" is not self-explanatory on _this_ list, or that he used it here), but then everybody and his dog jumps in barking at the newcomer who did not understand Graham's absolutely cryptic remark (imagine not being into lilypond-devel slang and try reading any sense into it), giving him the full "unpaid volunteers, scurvy dog" treatment. Get real. Can I just say that I'm quite impressed that I can start such a vibrant thread as such a newbie and with so few characters in my reply... -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
On Sun, Sep 19, 2010 at 10:07:28PM +0200, Martin Tarenskeen wrote: > > On Sun, 19 Sep 2010, David Kastrup wrote: > > >It is agreed-upon best practice _not_ to use those abbreviations on the > >general user list. > > I agree, but: Since many people use these abbreviations, Would it be > an an idea to mention those abreviations on manuals.html and in the > titles at the top of the manuals. something like: > > LilyPond - Notation Reference (NR) > > Just an idea to make more people happy. We tried that briefly in the first half of 2008, but the (NR) stuff wasn't visible enough, and we still had questions. I think the best solution is just to remind people not to do this. Users replying to emails from 2-4 years ago will still encounter these cryptic abbreviations, but this happens fairly rarely. As long as we try to avoid words like "Um." or "err." or "erm" or "eto" (in Japanese) when clarifying those old emails, I think we'll be ok. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: piano staves and lyrics
Sorry about that, brief problem with my email that resulted in double-posting. Excellent answer sorted my question out immediately, thanks again. Gerard On Sun, Sep 19, 2010 at 3:17 PM, Phil Holmes wrote: > Check your inbox for the answer to this question you were sent yesterday. > > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
How to include a file/definition temporarily?
Hi all,
I have several files with definitions of guitar fret diagrams for
various chord shapes (e.g. c-shape.ly, a-shape.ly, g-shape.ly, e-
shape.ly and d-shape.ly). I can't include all of these files at the
same time in the main file as quite a few chord alternatives start on
the same pitch. How can I use those definitions only temporarily? I
tried this:
cShape = { \include "c-shape.ly" }
aShape = { \include "a-shape.ly" }
music = \chordmode {
\cShape
c1
\aShape
c1
}
Unfortunately this way the a-shape definitions overrule the c-shape
definitions. If anybody knows a solution please let me know.
Thanks for any hint!
patrick
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to include a file/definition temporarily?
On 9/19/10 3:46 PM, "Patrick Schmidt" wrote:
> Hi all,
>
> I have several files with definitions of guitar fret diagrams for
> various chord shapes (e.g. c-shape.ly, a-shape.ly, g-shape.ly, e-
> shape.ly and d-shape.ly). I can't include all of these files at the
> same time in the main file as quite a few chord alternatives start on
> the same pitch. How can I use those definitions only temporarily? I
> tried this:
>
> cShape = { \include "c-shape.ly" }
> aShape = { \include "a-shape.ly" }
>
> music = \chordmode {
>\cShape
>c1
>\aShape
>c1
> }
>
> Unfortunately this way the a-shape definitions overrule the c-shape
> definitions. If anybody knows a solution please let me know.
This is probably not possible right now. With some modifications to the
code, it could be fixed.
Right now, predefined fretboards are all saved in one table with the fixed
name of fretboard-table. This is seen in ly/predefined-fretboards-init.ly.
It should be possible to adjust the code so that we save predefined
fretboards in a table whose name has been selected in a .ly file.
Once we do that, then we could do something like
#(define a-fretboard-table (make-hash-table 100))
\set predefinedDiagramTable = #a-fretboard-table
\storePredefinedDiagram .
#(define c-fretboard-table (make-hash-table 100))
\set predefinedDiagramTable = #c-fretboard-table
\storePredefinedDiagram .
Then, in order to use the a-fretboard-table, we just do
\set predefinedDiagramTable = #a-fretboard-table
and to use the c-fretboard-table, we do
\set predefinedDiagramTable = #c-fretboard-table
I don't have time to make the changes to allow this right now; it might be
next weekend before I can get to it. I'm not sure exactly the scheme syntax
that will be required, but I'm confident I can get it to work.
If you want to work on it in the meantime, I'd be happy to have you do so
and give you any guidance I can.
Thanks,
Carl
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: best practices
Graham Percival writes: > On Sun, Sep 19, 2010 at 10:07:28PM +0200, Martin Tarenskeen wrote: >> >> I agree, but: Since many people use these abbreviations, Would it be >> an an idea to mention those abreviations on manuals.html and in the >> titles at the top of the manuals. something like: >> >> LilyPond - Notation Reference (NR) >> >> Just an idea to make more people happy. > > We tried that briefly in the first half of 2008, but the (NR) > stuff wasn't visible enough, and we still had questions. Well, some help is better than none. Unless it prompts more "why didn't you look at?" remarks. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
