Re: How to append a git version to an output filename
Thanks URS, Another great idea for me to try! Cheers, Ben On Jan 16, 2018 08:37, "Urs Liska" <li...@openlilylib.org> wrote: > > > Am 16.01.2018 um 14:27 schrieb Ben Beeson: > > Hi, > > Wow, that looks very promising. I am looking at this note on my cell > phone right now, so I cannot test it just yet. I will try this later when I > get home and see what happens. > > > But you should also look into the openLilyLib files, create a copy of the > function and try removing the \markup wrapper. This \markup is added > explicitly so it seems more efficient not to do that in the first place > instead of removing it afterwards. > > Urs > > > Thanks very much for this! > > Cheers, > > Ben > > > > > On Jan 15, 2018 21:38, "Flaming Hakama by Elaine" < > ela...@flaminghakama.com> wrote: > > > > On Sun, Jan 14, 2018 at 4:10 PM, Urs Liska <li...@openlilylib.org> wrote: > >> Hi Ben, >> >> Actually I misread your original post and referred you to what you >> already had. >> >> Elaine's hint is true but won't bring you any further because that's what >> is already happening in the background when you use the \gitCommittish >> function. >> >> The point is (I think) that the function is explicitly making a markup >> from a string - and in order to concatenate a string for the file name you >> should simply avoid that step. >> >> Urs >> > > So, the \gitCommitish returns a markup, and it needs to be a string? > If so, does this help? > > http://lsr.di.unimi.it/LSR/Item?id=747 > > > %% http://lsr.di.unimi.it/LSR/Item?id=747 > %% see also http://lilypond.org/doc/v2.18/Documentation/notation/text > > %% TODO markup->string is in the source > %% test, if it can be deleted here > > % mup = markup argument > % conc = boolean whether to concat or not > #(define (markup->string mup conc) > (let ((result "")) > (map (lambda (x) > (begin > ;; if this is a concat-markup, do not insert > blanks between string > (if (eq? x concat-markup)(set! conc #t)) > (if (list? x) > (set! result > ;; if we are concatenating or we start > with an empty result, don't add a blank > (if (or conc (string=? result "")) > (string-append result > (markup->string x conc)) > (string-append result " " > (markup->string x conc) > (if (string? x) > (set! result > ;; if we are concatenating or we start > with an empty result, don't add a blank > (if (or conc (string=? result "")) > (string-append result x) > (string-append result " " x > result)) > mup) > result) > ) > #(define-markup-command (plain-text layout props arg)(markup?) > (interpret-markup layout props (markup > (markup->string arg #f > > > #(define output-suffix \plain-text \gitCommitish ... ) > > > > > > David Elaine Alt > 415 . 341 .4954 <%28415%29%20341-4954> > "*Confusion is highly underrated*" > ela...@flaminghakama.com > skype: flaming_hakama > Producer ~ Composer ~ Instrumentalist > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to append a git version to an output filename
Hi, Wow, that looks very promising. I am looking at this note on my cell phone right now, so I cannot test it just yet. I will try this later when I get home and see what happens. Thanks very much for this! Cheers, Ben On Jan 15, 2018 21:38, "Flaming Hakama by Elaine"wrote: On Sun, Jan 14, 2018 at 4:10 PM, Urs Liska wrote: > Hi Ben, > > Actually I misread your original post and referred you to what you already > had. > > Elaine's hint is true but won't bring you any further because that's what > is already happening in the background when you use the \gitCommittish > function. > > The point is (I think) that the function is explicitly making a markup > from a string - and in order to concatenate a string for the file name you > should simply avoid that step. > > Urs > So, the \gitCommitish returns a markup, and it needs to be a string? If so, does this help? http://lsr.di.unimi.it/LSR/Item?id=747 %% http://lsr.di.unimi.it/LSR/Item?id=747 %% see also http://lilypond.org/doc/v2.18/Documentation/notation/text %% TODO markup->string is in the source %% test, if it can be deleted here % mup = markup argument % conc = boolean whether to concat or not #(define (markup->string mup conc) (let ((result "")) (map (lambda (x) (begin ;; if this is a concat-markup, do not insert blanks between string (if (eq? x concat-markup)(set! conc #t)) (if (list? x) (set! result ;; if we are concatenating or we start with an empty result, don't add a blank (if (or conc (string=? result "")) (string-append result (markup->string x conc)) (string-append result " " (markup->string x conc) (if (string? x) (set! result ;; if we are concatenating or we start with an empty result, don't add a blank (if (or conc (string=? result "")) (string-append result x) (string-append result " " x result)) mup) result) ) #(define-markup-command (plain-text layout props arg)(markup?) (interpret-markup layout props (markup (markup->string arg #f #(define output-suffix \plain-text \gitCommitish ... ) David Elaine Alt 415 . 341 .4954 <(415)%20341-4954> "*Confusion is highly underrated*" ela...@flaminghakama.com skype: flaming_hakama Producer ~ Composer ~ Instrumentalist -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-user Digest, Vol 182, Issue 55
Thanks Urs! Cheers, Ben On Sun, 2018-01-14 at 19:25 -0500, lilypond-user-requ...@gnu.org wrote: > Send lilypond-user mailing list submissions to > lilypond-user@gnu.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.gnu.org/mailman/listinfo/lilypond-user > or, via email, send a message with subject or body 'help' to > lilypond-user-requ...@gnu.org > > You can reach the person managing the list at > lilypond-user-ow...@gnu.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of lilypond-user digest..." > Today's Topics: > >1. Re:GSoC applications (Kieren MacMillan) >2. Re:New information (success report) for Frescobaldi 3 and the > Ubuntu 16.04 repositories (Vaughan McAlley) >3. Re:How to append a git version to an output filename (Urs > Liska) >4. Re:GSoC applications (Urs Liska) >5. Re:lilypond-user Digest, Vol 182, Issue 50 (Ben Beeson) > ___ > 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: lilypond-user Digest, Vol 182, Issue 50
Hi Urs, Thank you for your note. I am using the tools you provided. My thanks to you and Lars for providing those tools. My main reason for using version control is to have a way to tell if someone in the band has the most current setting for the tunes and to go back to a previous edition if needed when ideas for new changes come out from the boss. Regarding your comment about uncommitted changes, I am aware of that and have been burned once or twice due to that as well. As a work around, I only provide committed scores to the band that I scribe for. It's not a perfect system, but it seems to work so far. Andrew, Your idea to tag the output pdf in the repository is a worthy idea as well. Thanks for that suggestion! Cheers, Ben On Sun, 2018-01-14 at 09:31 -0500, lilypond-user-requ...@gnu.org wrote: > Send lilypond-user mailing list submissions to > lilypond-user@gnu.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.gnu.org/mailman/listinfo/lilypond-user > or, via email, send a message with subject or body 'help' to > lilypond-user-requ...@gnu.org > > You can reach the person managing the list at > lilypond-user-ow...@gnu.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of lilypond-user digest..." > Today's Topics: > >1. independent horizontal spacing between staves (Mason Hock) >2. Re:How to append a git version to an output filename > (David Kastrup) >3. Re:How to append a git version to an output filename (Urs > Liska) >4. Re:How to append a git version to an output filename > (Andrew Bernard) >5. Re:How to append a git version to an output filename (Urs > Liska) >6. Transposing in the Input file (Kale Good) > ___ > 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: How to append a git version to an output filename
Good evening all, I have attached an example that I hope helps. Thomas, the gitCommitish I am using is the same as the one linked at: https://github.com/openlilylib/snippets/blob/master/editorial-tools/git -commands/ So after committing the LilyPond files to the repository, the current git version will appear in the tagline when you rebuild the pdf since that value is extracted in the tagline entry. What I seek is a way to get that value appended automatically to the generated pdf so that the generated pdf would have a filename such as: CommitishExample-0490435.pdf. Using \bookOutputSuffix seemed like a good place to start, but as Thomas has pointed out, \bookOutputSuffix "\gitCommitish" or \bookOutputSuffix \gitCommitish does not work. Elaine has a good idea to extract that information at the shell and then append it to the filename using shell functions. I had not thought of that method before. I will work on a shell script for that and see what come out of that. David, My apologies for referring you to the place where the git definitions I used were. I thought that was information you were looking for. Thanks to all for your help, Ben On Sun, 2018-01-14 at 12:17 -0800, Flaming Hakama by Elaine wrote: > > -- Forwarded message ------ > > From: Ben Beeson <bwbe...@gmail.com> > > To: David Kastrup <d...@gnu.org>, lilypond-user <lilypond-user@gnu.o > > rg> > > Subject: Re: How to append a git version to an output filename > > Hi David, > > > > ... > > > > What I seek is a way to append whatever the current git version is > > to the pdf filename that is generated so I don't have to open the > > pdf and check the tagline to see what version it is when searching > > for a specific version. Appending the git version to the filename > > would make it easier to know which version is represented by the > > pdf when searching through the directory. > > > > > > I'm unclear on what you want the git version of. I can only assume > it is one of the lilypond source files. > > In any case, if it something to do with the git commit version of a > file, you can get that from the command line, such as using something > like: > > > > > > > > > > git log $file | head -1 | sed 's/commit //' > > > > And then there is a way to execute a shell command from within > lilypond, and assign it to a variable. Which I'm not familiar with, > but I've read on this list about people doing so. I'd bet you could > find that in the mail archives. > > > > > The Guile information I have seen so far online has not been too > > helpful for this particular question. If anyone has any ideas, I > > would enjoy seeing those. > > Cheers, > > Ben > > > HTH, > > David Elaine Alt > 415 . 341 .4954 "Confusion > is highly underrated" > ela...@flaminghakama.com > skype: flaming_hakama > Producer ~ Composer ~ Instrumentalist > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > =-=-=-=-=-=-=-=-=-=-=-=-=- > \version "2.19.80" \include "/home/ben/workspace/GitHub_BagPipeTunes/include/gitDefinitions.ily" filename = "~/CommitishExample.ly" tunesetVersion = "Version 1" source = "" \header { title = "Commitish Example" composer = "" arranger = "" meter = "" tagline = \markup { \filename " " \source " " git Version: \gitCommitish Committed: \gitDateTime Engraved: \simple #(strftime "%d - %b - %Y - %H%M " (localtime (current-time))) % with \with-url #"http://lilypond.org/; % \line { LilyPond \simple #(lilypond-version) (http://lilypond.org/) } } } \book { %\bookOutputSuffix what to put here to get the suffix to be the git version "0490435" or whatever the latest version is??? \bookOutputName "CommitishExample" \score { \new GrandStaff << \new Staff = "GHB" << \new Voice { \time 4/4 \relative c''{ c4 d4 e4 f4 | } \break } >> >> } } \paper { #(set-paper-size "letter" 'portrait) page-breaking = #ly:minimal-breaking } CommitishExample.pdf Description: Adobe PDF document ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to append a git version to an output filename
Hi David, It has been a while since I visited the site, but more information on using git with scores is available at: http://lilypondblog.org/2014/04/printing-git-versioning-info-in-a-score / Urs Liska and Lars Haulin provide some excellent tools and commentary with a link to the current definitions.ily file at: http://lilypondblog.org/wp-content/uploads/2014/04/definitions.ily in the snippets repository available at: https://github.com/openlilylib/snippets . To find the definitions file, click through snippets-> editorial-tools -> git-commands. Enjoy, Ben On Sun, 2018-01-14 at 17:26 +0100, David Kastrup wrote: > Ben Beeson <bwbe...@gmail.com> writes: > > > Hi David, > > Here is how I get the \gitCommitish in the tagline. First, include > > the > > "gitDefinitions.ily" file. > > What is that? > > > I use something like this: > > > > \include "/home/workspace/include/gitDefinitions.ily" > > > > Then in the header declaration, add the \gitCommitish and any other > > items desired to the tagline entry: > > > > \header { > > title = "Title" > > composer = "" > > arranger = "" > > meter = "" > > tagline = \markup { \filename " " \source " " git > > Version: > > \gitCommitish Committed: \gitDateTime > > Engraved: > > \simple #(strftime "%d - %b - %Y - %H%M " (localtime > > (current-time))) > >} > > } > > > > An example tagline from a score I am editing presently looks like > > this: > > > > > > Here \source is just a note to remind me where I got the > > information i > > used. This could be person's name or whatever. For the tagline > > above, > > \source is "null", so that value is missing from the tagline. I > > hope > > that the above is helpful to others. > > > > Regarding your comment about adding an expression to > > \bookOutputSuffix > > -- that is what I am trying to do. That said, > > > > \bookOutputSuffix "\gitCommitish" or \bookOutputSuffix = > > \gitCommitish does not work as expected. > > What about > > \bookOutputSuffix \gitCommitish > > then? > > > The Guile information I have seen so far online has not been too > > helpful for this particular question. > > string-append and similar functions exist. > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to append a git version to an output filename
Hi David, Here is how I get the \gitCommitish in the tagline. First, include the "gitDefinitions.ily" file. I use something like this: \include "/home/workspace/include/gitDefinitions.ily" Then in the header declaration, add the \gitCommitish and any other items desired to the tagline entry: \header { title = "Title" composer = "" arranger = "" meter = "" tagline = \markup { \filename " " \source " " git Version: \gitCommitish Committed: \gitDateTime Engraved: \simple #(strftime "%d - %b - %Y - %H%M " (localtime (current-time))) } } An example tagline from a score I am editing presently looks like this: Here \source is just a note to remind me where I got the information i used. This could be person's name or whatever. For the tagline above, \source is "null", so that value is missing from the tagline. I hope that the above is helpful to others. Regarding your comment about adding an expression to \bookOutputSuffix -- that is what I am trying to do. That said, \bookOutputSuffix "\gitCommitish" or \bookOutputSuffix = \gitCommitish does not work as expected. What I seek is a way to append whatever the current git version is to the pdf filename that is generated so I don't have to open the pdf and check the tagline to see what version it is when searching for a specific version. Appending the git version to the filename would make it easier to know which version is represented by the pdf when searching through the directory. The Guile information I have seen so far online has not been too helpful for this particular question. If anyone has any ideas, I would enjoy seeing those. Cheers, Ben On Sun, 2018-01-14 at 11:37 +0100, David Kastrup wrote: > Ben Beeson <bwbe...@gmail.com> writes: > > > Hello all, > > > > I am using git to keep track of edits to scores and am presently > > using > > > > > > \bookOutputName "score-filename" > > > > to write the output filename for the pdf that is generated in the > > LilyPond "ly" file. I am also using > > > > "git Version: \gitCommitish " > > > > in the tagline so the generated pdf has the git version information > > included in the score that is generated. > > How would that work? > > > I am wondering if there is a way to include \gitCommitish in > > \bookOutputSuffix so that the output filename looks like: > > > > "score-filename-gitversion.pdf". > > > > So far I have not been able to figure out how to do that or find an > > existing solution in the snippets, forum or elsewhere. If anyone > > has > > a solution, please share it. > > It's easy to use any Guile string expression as argument to > \bookOutputSuffix but I have no idea how you manage to get the > Commitish > into the tagline. > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
How to append a git version to an output filename
Hello all, I am using git to keep track of edits to scores and am presently using \bookOutputName "score-filename" to write the output filename for the pdf that is generated in the LilyPond "ly" file. I am also using "git Version: \gitCommitish " in the tagline so the generated pdf has the git version information included in the score that is generated. I am wondering if there is a way to include \gitCommitish in \bookOutputSuffix so that the output filename looks like: "score-filename-gitversion.pdf". So far I have not been able to figure out how to do that or find an existing solution in the snippets, forum or elsewhere. If anyone has a solution, please share it. Thanks in advance, Ben ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
How does one add an "x" or some other mark within the staff where a note normally goes?
Hi, I am looking at a handwritten score that contains some extra marks in the staff that I would like to include in a LilyPond score. In the bottom part of the score linked here http://www.altpibroch.com/PrimarySources/185-K1_5-Lament_for_Catherine. pdf you can see where the author as written in some "x's" in the staff at the C or A note location. What I would like to do is replicate that marking in the LilyPond score. I have tried markup, but that does not place the "x" in the right spot. Is there a way to make a note have zero time value and then replace the note with a letter or other symbol? Thanks in advance for your help, Ben ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Trouble Combining Repeats and Closing Bars in tunes
Thanks David, This is just what I needed! Regards, Ben On Mon, 2016-10-17 at 23:52 -0500, David Wright wrote: > On Mon 17 Oct 2016 at 23:24:51 (-0400), Ben Beeson wrote: > > > > I am looking at a 4 - part tune where the first and third parts are > > repeated and the second and fourth parts are not repeated. Try as I > > may, I cannot get Lilypond to put the repeats and closing bars in > > the > > right place when engraving the tune. The following is just about as > > simple as I can get it and still show the issue. > > > > % BarExample.ly > > \version "2.19.48" > > > > example = { \time 2/4 > > \relative c''{ > > \repeat volta 2 { a8 a8 a8 a8 | a8 a8 > > a8 > > a8 | \break } > > \bar ".|" d8 d8 d8 d8 > > > > > > d8 d8 d8 d8 | \bar "|." \break > > \repeat volta 2 { a8 a8 a8 a8 | a8 a8 > > a8 > > a8 | \break } > > \bar ".|" d8 d8 d8 > > d8 | > > d8 d8 d8 d8 | \bar "|." \break } > > } > > > > > > \score > > { > > \new Staff << > > > > \new Voice { > > \example > > } > > >> > > } > > % end BarExample.ly > > > > This produces the following which is clearly not what I intended > > since > > the first and third lines should be repeated and the second and > > fourth > > lines are not repeated. > > > > > > What am I doing wrong and what is the best way to fix it short of > > using separate score blocks for each part? > > Just let LP choose the barline types. > > Cheers, > David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Trouble Combining Repeats and Closing Bars in tunes
Hi, I am looking at a 4 - part tune where the first and third parts are repeated and the second and fourth parts are not repeated. Try as I may, I cannot get Lilypond to put the repeats and closing bars in the right place when engraving the tune. The following is just about as simple as I can get it and still show the issue. % BarExample.ly \version "2.19.48" example = { \time 2/4 \relative c''{ \repeat volta 2 { a8 a8 a8 a8 | a8 a8 a8 a8 | \break } \bar ".|" d8 d8 d8 d8 | d8 d8 d8 d8 | \bar "|." \break \repeat volta 2 { a8 a8 a8 a8 | a8 a8 a8 a8 | \break } \bar ".|" d8 d8 d8 d8 | d8 d8 d8 d8 | \bar "|." \break } } \score { \new Staff << \new Voice { \example } >> } % end BarExample.ly This produces the following which is clearly not what I intended since the first and third lines should be repeated and the second and fourth lines are not repeated. What am I doing wrong and what is the best way to fix it short of using separate score blocks for each part? Thanks in advance for your help, Ben ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Help with double bar lines
Hi all, I am noticing that placing a double bar line at the end of a part requires a separate \score {} for each part to get the desired results. What I would like to know is how to write one \score {} that has all the coding for a multi-part tune and shows the double bar lines at the appropriate places for the end of each part and start of the next part. I can make this work by adding a separate \score{} for each part, but it just seems like there ought to be an easier way to do this. I am attaching an example ly file and the output that hopefully shows what I am trying to do. If I am missing something obvious or this can't be done, please let me know. Thanks in advance for your help, Ben \version 2.18 \include bagpipe.ly \paper { #(set-paper-size letter 'landscape ) system-count = #2 } \header { title = Bar Test subtitle = I want the double bar line at the end of every 8 bars. } BarTest = { \bar \set Timing.measurePosition = #(ly:make-moment -1 8) e8 \bar .| | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 \bar |. | \break \bar .| a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 \bar |. | \break } BarTest_One = { \bar \set Timing.measurePosition = #(ly:make-moment -1 8) e8 \bar .| | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 \bar |. | \break } BarTest_Two = { \bar \set Timing.measurePosition = #(ly:make-moment -1 8) e8 \bar .| | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 | a4 a4 a4 a4 \bar |. | \break } \score { \new GrandStaff \new Staff = GHB \new Voice { \time 4/4 \BarTest } \header{ piece = In this example, the closing double bar line is at the last line only but the opening double bar line is present both times. } } \score { \new GrandStaff \new Staff = GHB \new Voice { \time 4/4 \BarTest_One } \header{ piece = This example works, but requires a separate \score {} for each grouping of 8 bars to show the closing double bar line. } } \score { \new GrandStaff \new Staff = GHB \new Voice { \time 4/4 \BarTest_Two } } bartest.pdf Description: Adobe PDF document ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Help with double bar lines
Hi Harm, That is a very clever idea and it does exactly what I was looking to do! Thanks for your help! Ben On 07/26/2014 01:16 PM, Thomas Morley wrote: 2014-07-26 21:51 GMT+02:00 Ben Beeson bwbe...@wavecable.com: Hi all, I am noticing that placing a double bar line at the end of a part requires a separate \score {} for each part to get the desired results. What I would like to know is how to write one \score {} that has all the coding for a multi-part tune and shows the double bar lines at the appropriate places for the end of each part and start of the next part. I can make this work by adding a separate \score{} for each part, but it just seems like there ought to be an easier way to do this. I am attaching an example ly file and the output that hopefully shows what I am trying to do. If I am missing something obvious or this can't be done, please let me know. Thanks in advance for your help, Ben In a construct like: \bar |. \break \bar .| the second command will override the first, because both are applied at the same musical moment. There is no predefined barline withe the behaviour you want, instead you need to define a special barline yourself: \version 2.18 #(define-bar-line |.-b |. .| |.) \relative c'' { \partial 8 e8 \bar .| \repeat unfold 32 a,4 \bar |.-b \break \repeat unfold 32 a4 \bar |. | } HTH, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Getting LilyPond code with included files into LyX
Hi all, I decided that I wanted to compile a tune book using LyX. I have collected up several tunes that I want in the tune book and these tunes are all engraved with LilyPond. Now I need to figure out how to get these tunes into a LyX file so I can compile the tune book. I have figured out how to get some music notes such as a scale into a LyX document using the LilyPond module. Now I need to figure out how to make that work when your LilyPond code needs an included file such as bagpipe.ly to render the music correctly. So far I am not having much luck with including bagpipe.ly and the LyX documentation has not helped much in that regard. I am missing something that will tell LyX to send the instructions for the include files to LilyPond when it builds the file. I am hoping there is a simple fix for this, but I have not found it yet. If anyone knows how to get the LyX LilyPond module to include bagpipe.ly or some other path/to/some/file.ly when building a document with LilyPond to work, I would appreciate a short note to help explain that. Cheers and thanks in advance, Ben ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Is the LilyPond website up today?
Hi all, I am getting error Unable to load the webpage becuase the server sent no data at the LilyPond.org since today. Is the site down? Thanks, Ben ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Proposed tweak to bagpipe.ly
Hi all, Today I decided to transcribe the Kilberry setting for "The Desparate Battle". While I was working on that I created a small piece of code that you may consider useful enough to include in the next version of bagpipe.ly for the LilyPond world. The code is below and represents a way to mark the Taorluath, Taorluath A Mach, Crunluath, and Crunluath A Mach symbols as the Kilberry book does for "The Desparate Battle". This code follows other piobaireachd notation examples already in bagpipe.ly, so hopefully it will be straightforward to add this if the maintainer/author agrees. *** code snippet here txtaortaoramcruncrunam = \markup { \override #'(baseline-skip . 1.0) \column { \center-align "T" \center-align \scale #'(-1 . -1) "T" \lower #2.5 \center-align "C" \lower #1 \center-align \scale #'(-1 . -1) "C" } } *** end snippet ** Here is a snapshot of the result. Cheers, Ben ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Is there a way to split a score across two sheets?
Hi Sven, Thanks for asking about what I am trying to do. Perhaps I could explain this a bit differently. Let me know if this is not clear and I will try again. You asked about why \pageBreak doesn't do what I want. \pageBreak splits a tune across a sheet dividing a top from a bottom. You get whole lines when you do this. What I want to do is split a tune into a left side and a right side. Consider that if you open a book, there are two pages facing each other, usually an even numbered page on the left and an odd numbered page on the right. Imagine a sheet of music printed in landscape orientation on a piece of paper that is the same size as the two facing pages in a book. When you fold this sheet of music down the middle, you would have the first bars of each line on the left facing page and the last bars of each line on the right facing page. Now add the print margins to the middle for binding etc. So if you did this in a book, the tune takes two facing pages in the book for each page of the tune. The idea could be thought of as using two letter pages to create an equivalent of a C sized US sheet, or similarly, two A4 sheets into an equivalent A2 sheet. What I am wanting to do is to print the tune on paper in a size readable when standing back from the music stand by splitting a tune across two sheets of paper that become facing pages in a book. I'd like to do this without splitting the notes into a left and right score in a ly file if possible. Thanks in advance, Ben On Thu, 17 Oct 2013 14:31:47 +0200 Sven Axelsson sven.axels...@gmail.com wrote: I'm afraid I don't understand the distinction you make between page and sheet. Apparently \pageBreak doesn't do what you want, so please clarify how what you want differs. On 17 October 2013 06:12, Ben Beeson bwbe...@wavecable.com wrote: Hi, I use LilyPond for bagpipe music. I find LilyPond and the included bagpipe.ly file to work very well for that task. Thanks! I looked in the documents and in other places online for help and did not find anything on how to split a score across two sheets, so Iam hoping the list can provide some insight. What I am looking to do is to easily split a score across two sheets much like you can make a score use two pages instead of one with a \pageBreak at the appropriate place. For example, the tune Cabar Feidh is much easier to read from a single sheet if printed landscape as opposed to printing portrait. This is just because some of the bars are more busy with doublings and throws etc. than others making certain parts a bit crowded when printing this tune in portrait orientation. I realize I could create two separate scores, one for each sheet, but that becomes cumbersome if you ever decide to display the tune differently. So I was wondering if there was an easy way to split a score across two sheets when printing so the tune essentially puts the first two bars on the left sheet and the last two bars of each line on the right sheet of an open book? Thanks in advance, Ben ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- Sven Axelsson ++[+ -].+..+.+.-.+... +++.-.++..++.++.... ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Is there a way to split a score across two sheets?
Kieren, Sven, and Robin, Thanks each of you for your great ideas. I will try those tonight after band practice and see what happens. Thanks again, Ben On Thu, 17 Oct 2013 13:06:57 -0400 Kieren MacMillan kieren_macmil...@sympatico.ca wrote: Hello Ben, Maybe use the \extractMusic function(s) to jigsaw the music across multiple pages? Hope this helps! Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Is there a way to split a score across two sheets?
Hi, I use LilyPond for bagpipe music. I find LilyPond and the included bagpipe.ly file to work very well for that task. Thanks! I looked in the documents and in other places online for help and did not find anything on how to split a score across two sheets, so Iam hoping the list can provide some insight. What I am looking to do is to easily split a score across two sheets much like you can make a score use two pages instead of one with a \pageBreak at the appropriate place. For example, the tune Cabar Feidh is much easier to read from a single sheet if printed landscape as opposed to printing portrait. This is just because some of the bars are more busy with doublings and throws etc. than others making certain parts a bit crowded when printing this tune in portrait orientation. I realize I could create two separate scores, one for each sheet, but that becomes cumbersome if you ever decide to display the tune differently. So I was wondering if there was an easy way to split a score across two sheets when printing so the tune essentially puts the first two bars on the left sheet and the last two bars of each line on the right sheet of an open book? Thanks in advance, Ben ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Grace note spacing and barcheck difficulty in bagpipe music
Hi Trevor, Thanks for pointing that out to me. I will remember that. Cheers and Thanks Again, Ben On Fri, 2012-12-21 at 09:06 +, Trevor Daniels wrote: Ben you wrote Friday, December 21, 2012 5:29 AM I am stumped, but happy. I say that because LilyPond renders the tune correctly and does not error on bar checks etc unless you have the second \time 3/4 in the score block. I know that removing the second \time 3/4 from the score block fixed the problem, and that adding it back recreated the problem. I thought this was odd since the LilyPond manual in the section on Changing time signatures inside a polymetric section using \scaleDurations appears to show an example that has more than one time signature in the score block. For now I will try to remember to minimize the use of \time X/Y in the scores to avoid collisions in the future. A second \time will cause no problems if it occurs at the same musical moment as the first one. In your case it doesn't, due to the different timing of the grace notes in the two parts. As only one \time command is needed at any point in a score (unless it is polymetric) it is best to stick to one at a time. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Grace note spacing and barcheck difficulty in bagpipe music
Hi David, Thanks for pointing me to the issue 34 link. I did not know about that before. After reading all that material late last night, I am realizing that the fix is going to be a tough one. I guess I was hoping that I just missed something simple. Who knew that I was about to walk into a minefield? Wow... I will see what I can do with the \grace { s8 } idea you suggested. So far that idea is not playing nicely with the bagpipe.ly file. Thanks again, Ben On Tue, 2012-12-18 at 09:54 +0100, David Kastrup wrote: Ben Beeson bwbe...@wavecable.com writes: Hi, I have been struggling with how to get harmonies to align with the main line of a tune when inputting seconds for bagpipe music. The goal is to get the main tune on one staff with the seconds on a separate staff. I also want the seconds aligned with the main tune in the other staff. Most of the time this works the way it should in that you enter the music and all is well. The problem occurs when one part of the tune starts with a different length of grace note embellishment from the other part. Then don't do this. Pad all starting graces with spacer rests (like s8) to have the same length, if necessary, adding just \grace { s8. }. It is a problem documented in the manual, and is one of the earliest standing issues in the bug tracker, the infamous issue 34 URL:http://code.google.com/p/lilypond/issues/detail?id=34. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user