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

[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
>   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

[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 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: GSoC applications

[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 website. I assume Janek suggested a project on 
his own. 

>
>> I agree that this looks like a great GSoC project. However, to see it
>listed on the GSoC page you should lobby for someone volunteering as a
>primary mentor.
>
>I'll do that. Thanks!
>Kieren.
>
>
>Kieren MacMillan, composer
>‣ website: www.kierenmacmillan.info
>‣ email: i...@kierenmacmillan.info

___
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

[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 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

Am 15. Januar 2018 00:04:53 MEZ schrieb 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 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 
>> > To: David Kastrup , lilypond-user > > 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
>> 
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> =-=-=-=-=-=-=-=-=-=-=-=-=- 
>> 
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

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

[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 install on a new Ubuntu 17.10 pristine image. All
> >works fine as per the source installations now updated.
> >
> >A large vote of thanks to all who untangled this ball of wool. Despite
> >a
> >lifetime of software development experience, I kept going round in
> >circles
> >and never got it working. A big achievement and well done to you all.
> >
> >Andrew
> >
> >
> >
> >On 7 January 2018 at 20:38, Urs Liska  wrote:
> >
> >> I've done a new iteration on the Wiki page. I've also added a concise
> >> walkthrough at the end that leaves out all the explanations and
> >>
> >
> >___
> >lilypond-user mailing list
> >lilypond-user@gnu.org
> >https://lists.gnu.org/mailman/listinfo/lilypond-user
> >
> >
> >It's good to know it's possible. Does anyone know whether a failed
> >installation of Frescobaldi 3 endangers a working 2.20 installation?
> >
> >Vaughan
>
> More concrete information: it is perfectly possible to install both F2 and
> F3 side by side -wherever the necessary packages are available. All Ubuntus
> since 16.04, and Debian 8-9. Debian 10 doesn't support F2 anymore.
>
> I'll update the F2 wiki ASAP, although I don't consider supporting F2 a
> priority.
>
> Urs
>

Thanks Urs. As it turned out, I looked up my Debian version and realised
that Debian 9 was now stable. So I upgraded, not as carefully as I should
have, and got a non-booting version of Debian 9. It looked easier to
reinstall Debian 9, so after I did that
> sudo aptitude install frescobaldi
...installed Frescobaldi 3 flawlessly. So no need for Frescobaldi 2.But you
would only ever need one at a time.

Also, with a non-booting system, I spent some time on the Fedora partition
I use for testing. Frescobaldi 3 installed easily that too. So it seems
easy enough on “fresh” systems.

I have had similar problems to Andrew with VLC. After trying to install
some unusual codec or something I got stuck in an incompatible dependency
vortex that I couldn’t escape from. Not fun.

Vaughan
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: GSoC applications

[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 volunteering as a primary 
> mentor.

I'll do that. Thanks!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
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

[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 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 
> > To: David Kastrup , lilypond-user  > 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: optional Dynamics with tag#?

[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 any such rule in LilyPond.  Even in C, macros tend to
prefer putting

   do { ... } while (0)

around stuff so that

#define BLA(x) do { ++x; ++x; } while (0)

if (1)
  BLA (x);
else
  BLA (y);

works without "unexpected else" errors.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: GSoC applications

[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 somehow 
modularized, i.e. it should not be one monolithic feature that can just be 
completed or not. So if progress is slower there is simply less functionality 
completed rather than the whole thing failed.

I note that all the Lyric improvements are no longer listed as a GSoC project. 
What's the reason there?


Are you sure that this was really listed as GSoC project? I went through 
all git commits touching that page back to 2012 and couldn't find a 
reference to removing any Lyrics project. But anyway, all GSoC projects 
that are still considered valuable but don't explicitly have a mentor 
have been moved to the "attic" over the last years.




In addition to the stuff that Janek was actively working on — now quite a while ago — 
there was a flurry of discussion not too long about about whether LyricText could have 
some "fixed versus flexible" springs-and-rods mechanism(s), so that lyrics 
don't always distort note-spacing. I think this project would easily fill up three months 
of full-time work, but could also be modularized.

That would be the project I most want to see completed (or at least 
significantly tackled/advanced).


I agree that this looks like a great GSoC project. However, to see it 
listed on the GSoC page you should lobby for someone volunteering as a 
primary mentor.


Best
Urs



Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: optional Dynamics with tag#?

[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 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

[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 the rest I can look up in git.
And the versioning, I do with tags because I like it more than
hexadecimal hashes.

I have a tag for each year and each commit since then is counted, so
what I write on the score looks like:

   Version 2018.25

It's derived from `git describe`, the full command is:
git describe --long --dirty='+' | sed 's/-/./' | sed -r 's/-g[0-9a-f]+//g'

I like the combination of `git describe` and tags a lot. That's my
personal optimum between usefulness and beauty for both technical and
non-technical readers of the score.

Cheers,
Joram


[1]:
http://lilypondblog.org/2014/04/printing-git-versioning-info-in-a-score/

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

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

[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 installations now updated.
>
>A large vote of thanks to all who untangled this ball of wool. Despite
>a
>lifetime of software development experience, I kept going round in
>circles
>and never got it working. A big achievement and well done to you all.
>
>Andrew
>
>
>
>On 7 January 2018 at 20:38, Urs Liska  wrote:
>
>> I've done a new iteration on the Wiki page. I've also added a concise
>> walkthrough at the end that leaves out all the explanations and
>>
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
>It's good to know it's possible. Does anyone know whether a failed
>installation of Frescobaldi 3 endangers a working 2.20 installation?
>
>Vaughan

More concrete information: it is perfectly possible to install both F2 and F3 
side by side -wherever the necessary packages are available. All Ubuntus since 
16.04, and Debian 8-9. Debian 10 doesn't support F2 anymore. 

I'll update the F2 wiki ASAP, although I don't consider supporting F2 a 
priority. 

Urs

___
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

[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 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
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
___
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

[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 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,

I think I'll look for my enjoyment elsewhere.

-- 
David Kastrup

___
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

[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 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  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

[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 "/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.
>
> --
> David Kastrup



noone can help if you don't provide the needed information.
Your gitCommitish _may_ be the same as in
https://github.com/openlilylib/snippets/blob/master/editorial-tools/git-commands/
or not. Noone can tell.
A minimal working example with the used version would have been nice as well.


So for now I _guess_ you took it from there.

The problem then: `bookOutputSuffix' expects a string, but you provide
a markup. Can't work.
Different possibilities to proceed:
- catch what you need from the markup-command and write something
outputting a string
- markup->string

Cheers,
 Harm

___
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

[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 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.

-- 
David Kastrup

___
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

[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: 

\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  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

Re: Tempo Alignment Questions

[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 same tempo in the score and different parts. With the accidental issue
for instance the object is on the page so I assume there is some way to
tell it to align with that object.

-Jay
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Transposing in the Input file

[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 want to see if 
this is a systemic problem before putting too much effort it.


-k


Kale Good
Good Music Academy  ♫
4705 Baltimore Ave, Phila, PA 19143
phone: (215)260-5383

Facebook 
Google+ 
Read my article "The Seven Secrets to Six String Success 
" 
at GuitarNoise.com 


On 01/14/2018 09:34 AM, Jacques Menu Muzhic wrote:

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 écrit :


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 that I'd 
like to avoid using a transcribe block.


I was hoping that using a \transpose {} block with /lilypond 
--verbose/ would output the transposed notes somewhere in the STOUT 
stream, but no luck.


(My use-case: I'll be putting this into Anki's memorization tool and 
using it in my practicing routine. I'd like to keep the files as 
simple as possible so that I can edit mistakes or make changes easily 
while practicing. Having to think through an unnecessary 
transposition would really make that difficult.)


Thanks,

Kale

--

Kale Good
Good Music Academy  ♫
4705 Baltimore Ave, Phila, PA 19143
phone: (215)260-5383

Facebook 
Google+ 
Read my article "The Seven Secrets to Six String Success 
" 
at GuitarNoise.com 


___
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: Transposing in the Input file

[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 écrit :
> 
> 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 that I'd like to avoid using a transcribe 
> block. 
> I was hoping that using a \transpose {} block with lilypond --verbose would 
> output the transposed notes somewhere in the STOUT stream, but no luck. 
> (My use-case: I'll be putting this into Anki's memorization tool and using it 
> in my practicing routine. I'd like to keep the files as simple as possible so 
> that I can edit mistakes or make changes   easily while practicing. 
> Having to think through an unnecessary transposition would really make that 
> difficult.)
> 
> Thanks,
> 
> Kale
> -- 
> Kale Good
> Good Music Academy  ♫
> 4705 Baltimore Ave, Phila, PA 19143
> phone: (215)260-5383
> Facebook 
> Google+ 
> Read my article "The Seven Secrets to Six String Success 
> " at 
> GuitarNoise.com 
> ___
> 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

Transposing in the Input file

[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 that I'd like to avoid using a 
transcribe block.


I was hoping that using a \transpose {} block with /lilypond --verbose/ 
would output the transposed notes somewhere in the STOUT stream, but no 
luck.


(My use-case: I'll be putting this into Anki's memorization tool and 
using it in my practicing routine. I'd like to keep the files as simple 
as possible so that I can edit mistakes or make changes easily while 
practicing. Having to think through an unnecessary transposition would 
really make that difficult.)


Thanks,

Kale

--

Kale Good
Good Music Academy  ♫
4705 Baltimore Ave, Phila, PA 19143
phone: (215)260-5383

Facebook 
Google+ 
Read my article "The Seven Secrets to Six String Success 
" 
at GuitarNoise.com 


___
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

[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 nowadays.


If you want to manage your files by the complex git hash numbers, then 
why not check in the output to the commit as well? Then you can simply 
add tags to make it more humanly readable. You could add the tag name 
to the file name if you really so desired. Seems simpler that what you 
are asking to do.


I know this is not the answer you are looking for, but may be a way to go?


Generally it's straightforward to have LilyPond run Git during 
compilation and add any log output to the filename or the tagline. (As 
is already wrapped by my command linked to in the previous comment.


One thing to consider is that more often than not scores will be 
compiled with uncommitted changes being present, so the git committish 
may actually be misleading. (I have added several commands to handle 
that too).


Urs




Andrew



___
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

[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 hash numbers, then why
not check in the output to the commit as well? Then you can simply add tags
to make it more humanly readable. You could add the tag name to the file
name if you really so desired. Seems simpler that what you are asking to do.

I know this is not the answer you are looking for, but may be a way to go?

Andrew
___
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

[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: \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.


You should have a look at 
https://github.com/openlilylib/snippets/tree/master/editorial-tools/git-commands
I'm not sure if that's up-to-date, and IIRC it doesn't work on windows, 
but probably you can either use that directly throught the "snippets" 
package or copy the useful code.


HTH
Urs





Thanks in advance,

Ben





___
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

[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  
>
>   "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.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

independent horizontal spacing between staves

[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 included 
for reference only and horizontal alignment is not important. Fixing each 
instance of bad spacing manually via scaling would quickly become, even with 
edition-engraver. It seems that the simplest solution would be

(1) make the horizontal spacing of the larger staff independent of the smaller 
staves, but retain alignment among the smaller staves,

or if this is not possible the next best thing would be

(2) make the horizontal spacing of all staves independent of each other.

I have found some old threads saying that this is not possible, but thought I 
would see if this has changed by now.

Thanks,

Mason


___
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

[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 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

Re: GSoC applications

[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 
>> Subject: Re: GSoC applications
>>
>> ...
>>
>> Am 09.01.2018 um 19:36 schrieb Karlin High:
>>
>> I'm partial to Knut Petersen's video score features. There was once a
>> mention of combining these two projects somehow.
>>
>> However, think of all the dependencies that video-generation features
>> would bring in. (Say, FluidSynth for MIDI-to-Audio, FFMPEG for video
>> generation, etc) I expect a video score feature would end up as a
>whole
>> separate project closely connected to LilyPond, like Frescobaldi is
>now.
>>
>>
>> This sounds great.
>>
>> I suggest you start a new thread about that and discuss some outline
>of a
>> project. If you come up with a project description - and a mentor - I
>can
>> integrate it in the suggestions page.
>>
>> Urs
>>
>
>I'd consider being the mentor for this project.

Great! 

>
>I agree that, before it is GSoC-consumbale, I think there needs to be
>some
>discussion about how it fits together, and break it into parts, each
>appropriate for a project.
>
>I'm in the midst of writing up some notes and suggestions, but I
>figured
>I'd mention my interest first.


That's good. 
I suggest you create a new thread with these thoughts. When you have something 
concrete I can pick it up and add it to the website. 

There are two general deadlines:

Jan 23 is the deadline for mentoring organizations 'applications. From then 
Google staff may look at the proposals pages. However, as we are only part of 
GNU I don't think one project more or less is terribly important. 

Feb 12 the participating organizations will be announced. So from then students 
will browse the GSoC site and may land on our page. So by then we should have 
all the information online. 

Best
Urs

>
>
>
>David Elaine Alt
>415 . 341 .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