Re: lilypond-user Digest, Vol 182, Issue 55

2018-01-14 Thread Ben Beeson
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 >

Re: lilypond-user Digest, Vol 182, Issue 50

2018-01-14 Thread Ben Beeson
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

Re: GSoC applications

2018-01-14 Thread Urs Liska
Am 15. Januar 2018 00:28:00 MEZ schrieb Kieren MacMillan : >Hi Urs, > >> Are you sure that this was really listed as GSoC project? > >https://www.google-melange.com/archive/gsoc/2012/orgs/gnu/projects/janek_warchol.html > >?? This is not from the Lily Pond

Re: How to append a git version to an output filename

2018-01-14 Thread Urs Liska
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

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

2018-01-14 Thread Vaughan McAlley
On 15 January 2018 at 07:58, Urs Liska wrote: > > > Am 11. Januar 2018 05:38:29 MEZ schrieb Vaughan McAlley < > vaug...@mcalley.net.au>: > >On 8 Jan 2018 12:35 p.m., "Andrew Bernard" > >wrote: > > > >Hi Urs and All, > > > >A totally successful

Re: GSoC applications

2018-01-14 Thread Kieren MacMillan
Hi Urs, > Are you sure that this was really listed as GSoC project? https://www.google-melange.com/archive/gsoc/2012/orgs/gnu/projects/janek_warchol.html ?? > I agree that this looks like a great GSoC project. However, to see it listed > on the GSoC page you should lobby for someone

Re: How to append a git version to an output filename

2018-01-14 Thread Ben Beeson
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

Re: optional Dynamics with tag#?

2018-01-14 Thread David Kastrup
Vaughan McAlley writes: > On 11 Jan 2018 3:00 a.m., "David Kastrup" wrote: > > omit { } which can only be used around sequential music, not post events. > > > So the “If in doubt, put curly brackets around it” rule doesn't always > work I wasn't aware of

Re: GSoC applications

2018-01-14 Thread Urs Liska
Hi Kieren, Am 13.01.2018 um 21:15 schrieb Kieren MacMillan: Hi Urs, In theory the answer is simple: A good project for GSoC is something a student can achieve with three months of full-time work. Not more, but also not less. Generally, for larger projects it's beneficial if it can be

Re: optional Dynamics with tag#?

2018-01-14 Thread Vaughan McAlley
On 11 Jan 2018 3:00 a.m., "David Kastrup" wrote: omit { } which can only be used around sequential music, not post events. So the “If in doubt, put curly brackets around it” rule doesn't always work ;-) Vaughan ___ lilypond-user

Re: How to append a git version to an output filename

2018-01-14 Thread Noeck
Hi, when I've seen the inclusion of git information on lilypondblog [1], I liked it and adapted it to my taste: Of course one can include a whole git log in the score, but the only thing I was interested in is this: If I have a printed score or a PDF, I want to know which version that was. All

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

2018-01-14 Thread Urs Liska
Am 11. Januar 2018 05:38:29 MEZ schrieb Vaughan McAlley : >On 8 Jan 2018 12:35 p.m., "Andrew Bernard" >wrote: > >Hi Urs and All, > >A totally successful install on a new Ubuntu 17.10 pristine image. All >works fine as per the source

Re:How to append a git version to an output filename

2018-01-14 Thread Flaming Hakama by Elaine
> > -- Forwarded message -- > From: Ben Beeson > To: David Kastrup , lilypond-user > 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

Re: How to append a git version to an output filename

2018-01-14 Thread David Kastrup
Ben Beeson writes: > 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

Re: How to append a git version to an output filename

2018-01-14 Thread Ben Beeson
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

Re: How to append a git version to an output filename

2018-01-14 Thread Thomas Morley
Hi Ben, 2018-01-14 17:26 GMT+01:00 David Kastrup : > Ben Beeson 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

Re: How to append a git version to an output filename

2018-01-14 Thread David Kastrup
Ben Beeson 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

Re: How to append a git version to an output filename

2018-01-14 Thread Ben Beeson
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:

Re: Tempo Alignment Questions

2018-01-14 Thread Jay Anderson
On Sat, Jan 13, 2018 at 9:53 PM, Shane Brandes wrote: > \override Score.MetronomeMark.extra-offset = #'(x . -y) that will do > it you will have to iterate a few guesses to get what you want. > Right. I want a more general solution. It gets annoying to have to tweak the

Re: Transposing in the Input file

2018-01-14 Thread Kale Good
That is possible with the previous version of Audiveris. However, that relies on an earlier version of the tesseract OCR program. While I might try that in the end, I preferred this route to messing around with conflicting dependencies. Also, I've only done this with a single page so far. I

Re: Transposing in the Input file

2018-01-14 Thread Jacques Menu Muzhic
Hello Kale, According to my experience, your best bet is to be able to edit the result of the scan in Audiveris before producing the MusicXML. I don’t know Audiveris: is that at all possible, as it is in PhotoScore Ultimate? JM > Le 14 janv. 2018 à 14:59, Kale Good a

Transposing in the Input file

2018-01-14 Thread Kale Good
Hello, I've used Audiveris to get a musicXML file. However, it misidentified a clef. So I've got the correct (relative) note names, but the pitches are all off for a line or two. I was wondering if there is a tool or script to transpose notes in the the input.ly file. My use-case is such

Re: How to append a git version to an output filename

2018-01-14 Thread Urs Liska
Am 14.01.2018 um 11:44 schrieb Andrew Bernard: Hi Ben, I think the desire to add git version information to files is a hangover from earlier days when people used to do this with SCCS, CVS, RCS, and all those antique systems. With git, due to its model, that's not so commonly done

Re: How to append a git version to an output filename

2018-01-14 Thread Andrew Bernard
Hi Ben, I think the desire to add git version information to files is a hangover from earlier days when people used to do this with SCCS, CVS, RCS, and all those antique systems. With git, due to its model, that's not so commonly done nowadays. If you want to manage your files by the complex git

Re: How to append a git version to an output filename

2018-01-14 Thread Urs Liska
Hi Ben, Am 14.01.2018 um 03:17 schrieb Ben Beeson: 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:

Re: How to append a git version to an output filename

2018-01-14 Thread David Kastrup
Ben Beeson 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 > >

independent horizontal spacing between staves

2018-01-14 Thread Mason Hock
I have a piece in which each performer reads from a score with the other players' staves shrunk. I have determined that the different staff sizes are the cause of some very bad horizontal spacing that is especially noticeable when players have different simultaneous tuplets. The other parts are

How to append a git version to an output filename

2018-01-14 Thread Ben Beeson
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

Re: GSoC applications

2018-01-14 Thread Urs Liska
Hi Elaine, Am 13. Januar 2018 23:30:16 MEZ schrieb Flaming Hakama by Elaine : >> -- Forwarded message -- >> From: Urs Liska >> To: Carlo Stemberger >> Cc: lilypond-user >>