Re: opus conflict

2017-04-30 Thread Timothy Lanfear
On 29/04/17 23:34, Mark Stephen Mrotek wrote: Hello, In my \book \header I have fields of title, composer, and opus. The manual (2.18) states “The values of the fields filter down this hierarchy, with the values set higher in the hierarchy persisting unless they are over-ridden by a value se

Re: Unusual repeat/chorus structure

2017-04-30 Thread Richard Shann
On Sun, 2017-04-30 at 15:24 +1000, Don Gingrich wrote: > Hi, > > As part of an on-going project to convert all of the tunes that > I play regularly to Lilypond I'm trying to typeset a song with > the structure: > > verse - chorus > verse > verse - chorus > verse >

Re: Unusual repeat/chorus structure

2017-04-30 Thread Richard Shann
On Sun, 2017-04-30 at 12:05 +0100, Richard Shann wrote: > > This particular tune started in MuseScore and was exported > > as XML. The export/import did not go well, though I'd suggest > > that the problem was more likely to have been the export > > rather than the import. This is a complex structu

Re: Unusual repeat/chorus structure

2017-04-30 Thread Richard Shann
On Sun, 2017-04-30 at 12:05 +0100, Richard Shann wrote: > And I've made the repeat structure follow the typesetting norms - > whole > measure rests and repeat with upbeat. On further thoughts, the second repeat should perhaps be notated as in the attached. Richard Gingrich-Default Score Layout.

Re:Unusual repeat/chorus structure (Richard Shann)

2017-04-30 Thread Don Gingrich
Richard Shann wrote: > I occurred to me when I saw this that you almost certainly spent more > time trying to convert from your original than creating afresh with > Denemo. Attached is my re-setting of your piece using Denemo. It took > 16mins 12 seconds to create this with Denemo (I had your lyric

RE: opus conflict

2017-04-30 Thread Mark Stephen Mrotek
Timothy, Thank you for your response. Your time spent writing out a solution is greatly appreciate. I would like to have something that is consistent with the manual. Mark -Original Message- From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Timo

Re: opus conflict

2017-04-30 Thread Thomas Morley
2017-04-30 18:15 GMT+02:00 Mark Stephen Mrotek : > Timothy, > > Thank you for your response. Your time spent writing out a solution is > greatly appreciate. > I would like to have something that is consistent with the manual. > > Mark Hi Mark, defining a custom book/scoreTitleMarkup is explaine

RE: opus conflict

2017-04-30 Thread Mark Stephen Mrotek
Thomas, Thank you for your reply. One book, several scores, i.e., a collection of pieces (named) under one opus name. Attached is the code with which I am working. Mark -Original Message- From: Thomas Morley [mailto:thomasmorle...@gmail.com] Sent: Sunday, April 30, 2017 10:10 AM To: Mar

opus conflict

2017-04-30 Thread Mark Stephen Mrotek
Thomas, Attached is the pdf generated by my code. Thank you again. Mark opus.pdf Description: Adobe PDF document ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: opus conflict

2017-04-30 Thread Thomas Morley
2017-04-30 19:19 GMT+02:00 Mark Stephen Mrotek : > Thomas, > > Attached is the pdf generated by my code. > > Thank you again. > > Mark Your first \header is inside the book as well as the \paper (where you set print-all-headers = ##t). This \header contains settings which are read and printed by t

RE: opus conflict

2017-04-30 Thread Mark Stephen Mrotek
Thomas, Thank you for your detailed explanation. Your patient effort is appreciated. As I understand now, some of the header fields are controlled by the \book and some by the \score. Your colored version is very illustrative, yet note that the "opus" is under the first piece (subtitle) and not

Re: opus conflict

2017-04-30 Thread Thomas Morley
2017-04-30 21:04 GMT+02:00 Mark Stephen Mrotek : > Thomas, > > Thank you for your detailed explanation. Your patient effort is appreciated. > As I understand now, some of the header fields are controlled by the \book > and some by the \score. > Your colored version is very illustrative, yet note t

RE: opus conflict

2017-04-30 Thread Mark Stephen Mrotek
Thomas, Thank you for the alternatives. Since I have very limited knowledge as to how to customize (write Lilypond), I shall opt for 1) or 2). The result is more important than the method. Mark -Original Message- From: Thomas Morley [mailto:thomasmorle...@gmail.com] Sent: Sunday, April

Re: Unusual repeat/chorus structure

2017-04-30 Thread Jacques Menu Muzhic
Hello Don, Thanks for the invoice. With MuseScore 2.0.3 and musicxml2ly 2.19.55, I get the same as you: menu@macbookprojm:~/Documents/LaTeX/PartitionsLilypond/regular > musicxml2ly Mr_BojanglesJMI.xml musicxml2ly: Reading MusicXML from Mr_BojanglesJMI.xml ... musicxml2ly: warning: overfull mea

Re: opus conflict

2017-04-30 Thread Thomas Morley
2017-04-30 23:09 GMT+02:00 Mark Stephen Mrotek : > [...] I have very limited knowledge as to how to customize (write Lilypond), > [...] So here a little tutorial about writing custom book/scoreTitleMarkup % (1) % book/scoreTitleMarkup are predefined/customized markups. They need to be d

Re: Unusual repeat/chorus structure

2017-04-30 Thread Jacques Menu Muzhic
Ooops, that one escaped me…: In: JM > Le 1 mai 2017 à 01:00, Jacques Menu Muzhic a écrit : > > Hello Don, > > Thanks for the invoice. > > With MuseScore 2.0.3 and musicxml2ly 2.19.55, I get the same as you: > > menu@macbookprojm:~/Documents/LaTeX/PartitionsLilypond/regular > musicxml2ly

Re: Up and down arrows

2017-04-30 Thread Paul Napolitano
Thank you, David! > On Apr 28, 2017, at 11:09 PM, David Wright wrote: > > On Fri 28 Apr 2017 at 21:57:09 (-0500), Paul Napolitano wrote: >> Is there a way to put up and down arrows above the staff to indicate the >> down and up beats? > > c'4 ^\markup { ↓ } f'4 ^\markup { ↑ } > > Cheers, > Da