Re: Emacs lilypond-mode

[Andrew Bernard]

Hi David,

Works very nicely. A sincere thank you for your work.

Now I can have a .dir-locals.el as follows:

;;; Directory Local Variables
;;; For more information see (info "(emacs) Directory Variables")

((LilyPond-mode
  (LilyPond-lilypond-command . "lilypond -I ~/lib/lilypond -I 
~/lib/openilylib")))

This sets the include path for lilypond for the project in the given directory, 
and behold, C-c C-l runs lilypond and compiles the source, without needing 
absolute paths for includes.

In LilyPond-mode, with C-c C-s able to run evince and have point and click 
feedback directly to the position in an emacsclient, I now have a dream 
lilypond coding environment on Ubuntu.

Andrew

> On 14 Oct 2015, at 00:19, David Kastrup  wrote:
> 
> Issue 4636 in our issue tracker.  Do you have a chance to try the patch
> at https://codereview.appspot.com/269320043> ?
> 
> -- 
> David Kastrup


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

Re: Thoughts on Frescobaldi...

[David Kastrup]

Edward Ardzinski  writes:

> As for snippets - so far I've added a generic variable, generic drum
> high/low variable, the code to set a midi instrument, a drum staff, and a
> comment break (just a percent sign followed by a bunch of asterisks).  As I
> have been working on an old tune of mine I also added a generic rhythmic
> framework for chords which simplified getting the backbone of the tune
> working.  Since I use a lot of these same rhythms a lot, it'll probably stay
> in the list - I'm likely to use that rhythm again.

If you are a rhythm guy (and use code for combining rhythms with music),
2.19 might appeal to you.  Check out
http://lilypond.org/doc/v2.19/Documentation/changes/> and scroll
down to the entry starting "Isolated durations".

> But all in all, I'm very pleased with both the new version of Lilypond
> and Frescobaldi.

Nice to hear.

-- 
David Kastrup

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

Re: Notes are doubled on forced beaming

[Noeck]

By the way, this was a syntax error in 2.18 because of the duration
after the beaming:

> \relative c' { c[8 d]}

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

Re: Notes are doubled on forced beaming

[Urs Liska]

Am 14.10.2015 um 00:30 schrieb Michał Konopacki:
>
> Hello List!
>
>  
>
> First of all thanks for all the community that emerged around this
> wonderful software. I’m occasional lilypond user.
>
> My question is:
>
>  
>
> \version "2.19.18"
>
> \relative c' { c[8 d]}
>

What you are doing here is a kind of shorthand notation.
Actually LilyPond interpretes this as:
- a c' without explicit duration: use c'4
- an explicit beam to that crotchet -> ignore that
- a duration (8) without a pitch -> repeat the previous pitch: take as c'8
- d'8 -> ignore the explicit beam, the two quavers are beamed anyway.

You can try the following expressions to see:

\relative c' { c 8 d } % nothing between the pitch and the duration
\relative c' { c \f 8 d } % anything between the pitch and the duration

HTH
Urs

>  
>
> The following code creates doubled c (and we have three notes c c d).
>
> If I change to:
>
> \version "2.19.18"
>
> \relative c' { c8[ d]}
>
>  
>
> We have normal output as suspected
>
>  
>
> Is it bug or feature, if feature - why is it so?
>
>  
>
> Thanks,
>
> Michał
>
>
>
> ___
> 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: Notes are doubled on forced beaming

[Noeck]

Hi Michał,

the order of note properties is: pitch, duration, beaming. Single
durations are allowed: c8 8 8 8.

> \relative c' { c[8 d]}

These are three notes:
c[  -> c4[  (the 8 is not read as duration of this as it comes too late)
8   -> c8   (pitch from last note)
d[  -> d8]  (duration from last note)

> \relative c' { c8[ d]}

These are 2 notes:
c8[ -> c8[
d]  -> d8]  (duration from last note)

Does this explain it to you?

Cheers,
Joram

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

Notes are doubled on forced beaming

[Michał Konopacki]

Hello List!

 

First of all thanks for all the community that emerged around this wonderful
software. I'm occasional lilypond user.

My question is:

 

\version "2.19.18"

\relative c' { c[8 d]}

 

The following code creates doubled c (and we have three notes c c d).

If I change to:

\version "2.19.18"

\relative c' { c8[ d]}

 

We have normal output as suspected

 

Is it bug or feature, if feature - why is it so?

 

Thanks, 

Michał

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

Thoughts on Frescobaldi...

[Edward Ardzinski]

WOW!  This is what I was trying to do with the editor I wrote 10 years ago
(which kept me tied to v2.6.5), if I had the programming skill/patience. 
There is so much available that I don't need to have the template file I
used to use anymore.

I'm still struggling a little bit with the output path, but it's not a big
deal since I was seriously contemplating using notepad.  The editor is also
not finding available variables inside of my drum variables.  Again not a
big deal since I'm pretty methodical about my variable names and have relied
on cut/paste for a long time (hence my initial idea to just use notepad).

As for snippets - so far I've added a generic variable, generic drum
high/low variable, the code to set a midi instrument, a drum staff, and a
comment break (just a percent sign followed by a bunch of asterisks).  As I
have been working on an old tune of mine I also added a generic rhythmic
framework for chords which simplified getting the backbone of the tune
working.  Since I use a lot of these same rhythms a lot, it'll probably stay
in the list - I'm likely to use that rhythm again.

There's still a lot for me to delve into with v2.18.2 and Frescobaldi...I'm
going to eventually get to working on adding lyrics, and have to re-learn
how to write alternative melodies and how to attach lyrics (seems there have
been some changes since 2.6.5), and deal with chord names and their
alternatives (I think chord name exceptions got better with v2.10?).  There
some volume tweaks I've seen with midi (the main thrust of what I do) that
I've seen briefly - I'll have to go back and read those sections a little
closer.  But nothing so far has been too difficult in 2.18.  And I'll
recover the files on my old hard drive eventually, then I can play with
convert ly.

But all in all, I'm very pleased with both the new version of Lilypond and
Frescobaldi.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Thoughts-on-Frescobaldi-tp182350.html
Sent from the User mailing list archive at Nabble.com.

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

Re: acciaccatura in grace

[Mario Moles]

In data martedì 13 ottobre 2015 22:08:33, Simon Albrecht ha scritto:
> On 12.10.2015 23:18, Mario Moles wrote:
> > Hi!
> > 
> > How do like the image?
> 
> Where is it from? Could be Chopin, he was always the guy for 
extreme
> notational constructs.
This is J. K. Mertz "Fantasia originale"
> 
> > This is not working:
> > 
> > 8[ \grace {fs'16( gs) fs es fs gs fs \acciaccatura {}
> > ds'} ds16. cs32]
> 
> Please, in future, always provide complete, _compilable_ 
examples, maybe
> even in attachment to prevent a mess in layout.
OK!
> Like:
> %%
> \version "2.19.28"
> \language "english"
> \relative {
>\voiceOne
>\key e \major
>8[ \grace {fs'16( gs) fs es fs gs fs \acciaccatura {}
> ds'} ds16. cs32]
> }
> %%
> Which gives wrong output (see attachment).
> 
> Might be a valid feature request, isn’t it?
Yes! It would be nice!
> 
> Yours, Simon


/oiram/bin/selom/
/Da ognuno secondo le proprie capacità ad ognuno secondo i propri 
bisogni./
/MIB-kernellinux-tester/
http://mariomoles.altervista.org/[1] 
Linux[2] 
MIB[3] Lilypond[4] Frescobaldi[5] Rosegarden[6] 


[1] http://mariomoles.altervista.org/
[2] https://www.kernel.org/
[3] http://mib.pianetalinux.org/blog/
[4] http://lilypond.org/
[5] http://www.frescobaldi.org/
[6] http://www.rosegardenmusic.com/
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Beam devide

[David Kastrup]

Simon Albrecht  writes:

> On 13.10.2015 21:34, David Kastrup wrote:
>> Helge  writes:
>>
>>> Am Tue, 13 Oct 2015 20:41:21 +0200
>>> schrieb Simon Albrecht :
>>>
\set Timing.beamExceptions = #'((end . (((1 . 8) . (4 4))
 ((1 . 12) . (3 3 3 3))
 ((1 . 24) . (3 3 3 3  3 3
 3 3)
>> Should be the same as
>>\set Timing.beamExceptions = \beamExceptions
>> { 8[ 8 8 8] 8[ 8 8 8] |
>>   \times 3/2 { 8[ 8 8] 8[ 8 8] 8[ 8 8] 8[ 8 8] } |
>>   \times 3/2 \repeat unfold 8 { 16[ 16 16] }
>> }
>>
>> which is possibly less cryptic to the musician.
>
> And less likely to work in 2.18 :-)

Uh, yes.  2.19.0, but still 2.19.

-- 
David Kastrup

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

Re: acciaccatura in grace

[Simon Albrecht]

On 12.10.2015 23:18, Mario Moles wrote:


Hi!

How do like the image?



Where is it from? Could be Chopin, he was always the guy for extreme 
notational constructs.



This is not working:

8[ \grace {fs'16( gs) fs es fs gs fs \acciaccatura {} 
ds'} ds16. cs32]




Please, in future, always provide complete, _compilable_ examples, maybe 
even in attachment to prevent a mess in layout.

Like:
%%
\version "2.19.28"
\language "english"
\relative {
  \voiceOne
  \key e \major
  8[ \grace {fs'16( gs) fs es fs gs fs \acciaccatura {} 
ds'} ds16. cs32]

}
%%
Which gives wrong output (see attachment).

Might be a valid feature request, isn’t it?

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

Re: Beam devide

[Simon Albrecht]

On 13.10.2015 21:34, David Kastrup wrote:

Helge  writes:


Am Tue, 13 Oct 2015 20:41:21 +0200
schrieb Simon Albrecht :


   \set Timing.beamExceptions = #'((end . (((1 . 8) . (4 4))
((1 . 12) . (3 3 3 3))
((1 . 24) . (3 3 3 3  3 3
3 3)

Should be the same as
   \set Timing.beamExceptions = \beamExceptions
{ 8[ 8 8 8] 8[ 8 8 8] |
  \times 3/2 { 8[ 8 8] 8[ 8 8] 8[ 8 8] 8[ 8 8] } |
  \times 3/2 \repeat unfold 8 { 16[ 16 16] }
}

which is possibly less cryptic to the musician.


And less likely to work in 2.18 :-)

Yours, Simon

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

Re: Beam devide

[David Kastrup]

Helge  writes:

> Am Tue, 13 Oct 2015 20:41:21 +0200
> schrieb Simon Albrecht :
>
>>   \set Timing.beamExceptions = #'((end . (((1 . 8) . (4 4))
>>((1 . 12) . (3 3 3 3))
>>((1 . 24) . (3 3 3 3  3 3
>> 3 3)

Should be the same as
  \set Timing.beamExceptions = \beamExceptions
   { 8[ 8 8 8] 8[ 8 8 8] |
 \times 3/2 { 8[ 8 8] 8[ 8 8] 8[ 8 8] 8[ 8 8] } |
 \times 3/2 \repeat unfold 8 { 16[ 16 16] }
   }

which is possibly less cryptic to the musician.

-- 
David Kastrup

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

Re: shapeII (openlilylib) with v2.19.25

[Simon Albrecht]

On 13.10.2015 20:49, Urs Liska wrote:

Can I assume that you two have looked enough on the code so I can merge
without further testing (I'd be glad in this case)?


Yes, the changes are minimally invasive and I’d be much surprised if 
there was any problem. Thanks for merging.




Looks plausible. However, I have one suggestion (not relevant to the
decision of merging the pull request but rather as a suggestion for the
future): This Pull Request has one and a half single significant change
(the switch at the end and the include at the beginning). However, the
commit *also* contains a number of modifications that are mere
reformattings. It would be preferrable if these two could be separated
into separate commits. As it is a reviewer has to carefully check all
the modified lines. If it were two commits (one "work" and one
"clean-up") it would be much more obvious.


That would be my bad then, and I’ll do better with subsequent work.

Yours, Simon

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

Re: shapeII (openlilylib) with v2.19.25

[Peter Crighton]

2015-10-13 20:49 GMT+02:00 Urs Liska :

> Can I assume that you two have looked enough on the code so I can merge
> without further testing (I'd be glad in this case)?
>

Looks good to me … with my limited understanding of how LilyPond works
internally. But it is a small change that makes sense to me, and in my
current score it works without flaws.


>
> Looks plausible. However, I have one suggestion (not relevant to the
> decision of merging the pull request but rather as a suggestion for the
> future): This Pull Request has one and a half single significant change
> (the switch at the end and the include at the beginning). However, the
> commit *also* contains a number of modifications that are mere
> reformattings. It would be preferrable if these two could be separated
> into separate commits. As it is a reviewer has to carefully check all
> the modified lines. If it were two commits (one "work" and one
> "clean-up") it would be much more obvious.


Sure, thanks, I’ll keep that in mind! This time I only copied what was
already there without thinking about that, sorry.


--
Peter Crighton | Musician & Music Engraver based in Mainz, Germany
http://www.petercrighton.de
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Beam devide

[Helge]

Am Tue, 13 Oct 2015 20:41:21 +0200
schrieb Simon Albrecht :

>   \set Timing.beamExceptions = #'((end . (((1 . 8) . (4 4))
>((1 . 12) . (3 3 3 3))
>((1 . 24) . (3 3 3 3  3 3
> 3 3)

Thanks for this help. It works. I will have to add this to my personal
snippets and this link to my favorits:
http://www.lilypond.org/doc/v2.19/Documentation/notation/beams#setting-automatic-beam-behavior

Regards
Helge

-- 
GnuPG fingerprint: EDCE F8C8 B727 6CC5 7006  05C1 BD3F EADC 8922 1F61

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

Re: shapeII (openlilylib) with v2.19.25

[Urs Liska]

Am 13.10.2015 um 20:22 schrieb Peter Crighton:
> 2015-10-13 19:19 GMT+02:00 Simon Albrecht  >:
> 
> On 13.10.2015 02:06, Peter Crighton wrote:
> 
> 2015-09-08 0:23 GMT+02:00 Simon Albrecht    >>:
> 
> 
> 
> Am 07.09.2015 um 22:52 schrieb Urs Liska:
> 
> 
> Simon,
> 
> please create an issue on GitHub with this information.
> 
> 
> 
> Should be updated with a version switch.
> 
> Done. I included the new file in the issue.
> 
> Is anything preventing that fix from being included into
> openLilyLib?
> 
> 
> Only my lack of experience with git/GitHub. I didn’t have the time
> to delve into the topic and create a pull request myself.
> 
> 
> It’s actually quite easy in the GitHub interface if you only need to
> alter one file (unless I did something wrong … I’m far from being an
> expert either):
> – find the file you want to update & click on Edit (the pencil symbol)
> – make changes, describe them & click on “propose file change”
> – click on “Create pull request”
> – add a comment if you want & once again click on “Create pull request”
>  
> 
> 
> 
> Or should I go ahead and create a pull request for it?
> 
> 
> Please do so.
> 
> 
> Done.

Thank you.

Can I assume that you two have looked enough on the code so I can merge
without further testing (I'd be glad in this case)?

Looks plausible. However, I have one suggestion (not relevant to the
decision of merging the pull request but rather as a suggestion for the
future): This Pull Request has one and a half single significant change
(the switch at the end and the include at the beginning). However, the
commit *also* contains a number of modifications that are mere
reformattings. It would be preferrable if these two could be separated
into separate commits. As it is a reviewer has to carefully check all
the modified lines. If it were two commits (one "work" and one
"clean-up") it would be much more obvious.

Best
Urs

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

Re: Beam devide

[Simon Albrecht]

Hello Helge,

try inserting the following:

On 13.10.2015 20:25, Helge wrote:

\version "2.18.0"

\relative c {

   \set tupletSpannerDuration = #(ly:make-moment 1 8)


  \set Timing.beamExceptions = #'((end . (((1 . 8) . (4 4))
  ((1 . 12) . (3 3 3 3))
  ((1 . 24) . (3 3 3 3  3 3 3 
3)




   \tuplet 3/2 {
 fis16 a d  fis[ a d]
 fis,,16 a d  fis a d
   }
}


This is documented in 
.


Yours, Simon

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

Beam devide

[Helge]

Hello,

I fear that this is asked before. But I don't find the answer. I have a
piece with lots of triplets of 16th notes. I managed to set the tuplet
spanner duration but I failed to divide the beams so that I can read
plain triples. 
In this example I got the desired result with manual bemaning in the
first figure. But I want to avoid the manual beaming.

Regards
Helge

\version "2.18.0"

\relative c {

  \set tupletSpannerDuration = #(ly:make-moment 1 8)

  \tuplet 3/2 {
fis16 a d  fis[ a d]  
fis,,16 a d  fis a d  
  }
}


-- 
GnuPG fingerprint: EDCE F8C8 B727 6CC5 7006  05C1 BD3F EADC 8922 1F61

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

Re: shapeII (openlilylib) with v2.19.25

[Peter Crighton]

2015-10-13 19:19 GMT+02:00 Simon Albrecht :

> On 13.10.2015 02:06, Peter Crighton wrote:
>
>> 2015-09-08 0:23 GMT+02:00 Simon Albrecht > simon.albre...@mail.de>>:
>>
>>
>>
>> Am 07.09.2015 um 22:52 schrieb Urs Liska:
>>
>>
>> Simon,
>>
>> please create an issue on GitHub with this information.
>>
>> 
>>
>> Should be updated with a version switch.
>>
>> Done. I included the new file in the issue.
>>
>> Is anything preventing that fix from being included into openLilyLib?
>>
>
> Only my lack of experience with git/GitHub. I didn’t have the time to
> delve into the topic and create a pull request myself.


It’s actually quite easy in the GitHub interface if you only need to alter
one file (unless I did something wrong … I’m far from being an expert
either):
– find the file you want to update & click on Edit (the pencil symbol)
– make changes, describe them & click on “propose file change”
– click on “Create pull request”
– add a comment if you want & once again click on “Create pull request”


>
>
> Or should I go ahead and create a pull request for it?
>>
>
> Please do so.


Done.


--
Peter Crighton | Musician & Music Engraver based in Mainz, Germany
http://www.petercrighton.de
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: shapeII (openlilylib) with v2.19.25

[Simon Albrecht]

On 13.10.2015 02:06, Peter Crighton wrote:
2015-09-08 0:23 GMT+02:00 Simon Albrecht >:




Am 07.09.2015 um 22:52 schrieb Urs Liska:


Simon,

please create an issue on GitHub with this information.



Should be updated with a version switch.

Done. I included the new file in the issue.

Is anything preventing that fix from being included into openLilyLib?


Only my lack of experience with git/GitHub. I didn’t have the time to 
delve into the topic and create a pull request myself.



Or should I go ahead and create a pull request for it?


Please do so.

Thanks, Simon

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

Re: [OT] Printer with or without Postscript

[Wols Lists]

On 13/10/15 11:09, Johan Vromans wrote:
> On Tue, 13 Oct 2015 10:39:35 +1100
> Andrew Bernard  wrote:
> 
>> > Whatever page description
>> > language your printer uses internally, the printer driver software on
>> > your computer will convert your file to that language format and print
>> > it.
>> > [...]
>> > Postscript itself is still highly relevant, PDF is essentially a
>> > Postscript description, and lilypond can generate postscript, which is
>> > rendered wth Ghostscript - a software RIP.
> While this is true, one may not underestimate the role of the printer
> driver or software RIP. PostScript is a full-fledged programming language
> and a PostScript RIP must carefully implement all programming language
> aspects in full. PDF (for printing) is a page description and hence easier
> to implement and to process. As a reference, there are several PDF RIPs
> (viewers) based on a number of PDF libraries, while there is only one
> PostScript RIP.
> 
> For this reason I switched to PDF several years ago, after having been
> writing PostScript generating tools since 1985. For the end user, a
> PostScript generating tool has a big and sometimes hard dependency: a good
> software or hardware RIP.

And this is why I hate Postscript - just another indirection layer to
screw things up :-)

Bit after your timescale - mid-1990s, we had a Canon photocopier and
FIRE rip unit, and when it went wrong it was a real pain. Once a
document broke the ripper, I could never fix it and the only solution
was to redo the document from scratch - I could never get it to print
again :-(

Cheers,
Wol

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

Re: Emacs lilypond-mode

[David Kastrup]

Andrew Bernard  writes:

> Thank you David!
>
> I just figured out the same logic. I see why you are using a makefile
> and M-x compile.
>
> But it would be good to have this, as I often compile a lot of
> different files that I don’t want to write makefile targets for.

Issue 4636 in our issue tracker.  Do you have a chance to try the patch
at https://codereview.appspot.com/269320043> ?

-- 
David Kastrup

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

Re: [OT] Printer with or without Postscript

[Johan Vromans]

On Tue, 13 Oct 2015 21:17:19 +1100
Andrew Bernard  wrote:

> I am not convinced evince is very good at anything at all. Would this not
> be an issue with evince, rather than other parts of the toolchain?

That could very well be the case. I was just referring to a common workflow
of 1. create a PDF document, 2. view it for visual inspection, and then
3. print it from the viewer.

> What if you do the same with say Mac OS X Preview?

Send me a Mac OS/X system and I'll let you know ;) .

-- Johan

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

Re: A title with a transposing note name

[Richard Shann]

On Tue, 2015-10-13 at 11:52 +0200, Thomas Morley wrote:
> 2015-10-13 10:50 GMT+02:00 Michael Gerdau :

> > I would expect that you can specifically override the font for the
[...]
> > But again I did not find a working solution.
> >
> > Kind regards,
> > Michael
> 
> 
> Try:
> 
> \new ChordNames { \override ChordName.font-name = "Purisa" f' }
> 
> With "Times New Roman" there is a problem, for more info search the 
> bug-tracker.
> Use "Times New Roman," instead.

Thank you! "Purisa" didn't do anything on my Debian system, but things
like Free Serif Bold did - and Times New Roman with a trailing comma
also worked. My problem now will be allowing users of different
operating systems to generate these transposable titles when I don't
know what fonts they may have installed... well, I see that 

 \new ChordNames {\override ChordName.font-family = #'roman \override 
ChordName.font-size = #1.0  a' }\layout{indent=0.0}
} minor

does work, and perhaps will work on windows too...

Richard





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

Re: Emacs lilypond-mode

[Johan Vromans]

On Mon, 12 Oct 2015 09:13:28 +0200
Urs Liska  wrote:

> The idea is that many users will have a default set of libraries they
> usually want to have available.

I have always wondered why LilyPond does not have an environment setting
for its library path, as most other tools do.

I have a collection of templates and snippets (include files) that I always
use, so I wrote a small wrapper script "lilypond" that boils down to:

  #!/bin/sh

  exec /usr/bin/lilypond \
--include=. \
--include=$HOME/lib/lilypond/ly \
--include=$HOME/lib/lilypond \
${1+"$@"}

This script is in my personal $HOME/bin directory, which is always first in
my $PATH.

-- Johan

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

Re: [OT] Printer with or without Postscript

[Andrew Bernard]

I am not convinced evince is very good at anything at all. Would this not be an 
issue with evince, rather than other parts of the toolchain? What if you do the 
same with say Mac OS X Preview?

Andrew

> On 13 Oct 2015, at 21:09, Johan Vromans  wrote:
> 
> See e.g. http://www.squirrel.nl/pub/xfer/lpev.png 
>  (two scans from
> the same document, printed directly (left) and from Evince (right)).

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

Re: A title with a transposing note name

[Thomas Morley]

2015-10-13 10:50 GMT+02:00 Michael Gerdau :
>> Yes, that is what I said: "while my version has it inside and this
>> causes an error",
>> The error message suggests putting it in a \layout block, but that also
>> is an error.
>> I can't help thinking that there must be something much simpler some
>> sort of music function that takes a note name (as a music e.g.
>> \transpose f g {cis}) and generates a markup (or rather whatever would
>> be valid inside \markup).
>
> I would expect that you can specifically override the font for the
> ChordNames. It has a font-family property. However I have no idea
> how that can be achieved. Namely I don't know which particular
> incantation needs to be invoked.
>
> I'd expect something along the line
> \version "2.19.25"
>
> \header {
>  title = \markup {Sonata in\score {
>  \new ChordNames { f' }
>  \layout{indent=0.0
>  \set ChordNames.font-family = "Times New Roman"
> }
>  but that doesn't do the trick.
>
> Or something like (in the above):
> ...
>  title = \markup {Sonata in\override some-property \roman \score {
> ...
>
> But again I did not find a working solution.
>
> Kind regards,
> Michael


Try:

\new ChordNames { \override ChordName.font-name = "Purisa" f' }

With "Times New Roman" there is a problem, for more info search the bug-tracker.
Use "Times New Roman," instead.

 Cheers,
  Harm

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

Re: [OT] Printer with or without Postscript

[Johan Vromans]

On Tue, 13 Oct 2015 10:39:35 +1100
Andrew Bernard  wrote:

> Whatever page description
> language your printer uses internally, the printer driver software on
> your computer will convert your file to that language format and print
> it.
> [...]
> Postscript itself is still highly relevant, PDF is essentially a
> Postscript description, and lilypond can generate postscript, which is
> rendered wth Ghostscript - a software RIP.

While this is true, one may not underestimate the role of the printer
driver or software RIP. PostScript is a full-fledged programming language
and a PostScript RIP must carefully implement all programming language
aspects in full. PDF (for printing) is a page description and hence easier
to implement and to process. As a reference, there are several PDF RIPs
(viewers) based on a number of PDF libraries, while there is only one
PostScript RIP.

For this reason I switched to PDF several years ago, after having been
writing PostScript generating tools since 1985. For the end user, a
PostScript generating tool has a big and sometimes hard dependency: a good
software or hardware RIP.

Having said all that, my printer is PostScript based (HP LasetJet 6MP). I
run my LilyPond output through ps2pdf ( = GhostScript RIP ) to create PDF
documents. There is (or maybe: was, haven't checked recently) a noticable
difference between sending LilyPond PostScript directly to the printer,
printing the PDF document from Evince, and sending the PDF directly to the
printer (which uses GhostScript to convert the PDF back into PostScript
again). See e.g. http://www.squirrel.nl/pub/xfer/lpev.png (two scans from
the same document, printed directly (left) and from Evince (right)).

So how to proceed? If you can find a printer with good PostScript support
that is not too expensive, buy it. Otherwise, convert a couple of LilyPond
output files to 600dpi PNG using GhostScript, and view with a good image
viewer. If the output looks good, you can trust your RIP and go for any
decent pixel-printer. If in doubt, Google is your friend.

-- Johan

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

Re: alternate endings without repeats

[Thomas Morley]

2015-10-13 6:01 GMT+02:00 David Kastrup :
> Thomas Morley  writes:
>
>> 2015-10-12 23:45 GMT+02:00 Juraj :
>>> http://thread.gmane.org/gmane.comp.gnu.lilypond.general/24012
>>>
>>> (8 years old) helped. But if there are news about, I'm interested in!
>>>
>>> Greetings
>>>
>>> Juro
>>
>>
>>
>> Well, there is no convincing user-interface for it.
>>
>> You can do:
>>
>>
>> voltaAdLib = \markup \normal-text { \fontsize #-1 what \italic  ever }
>> \allowVoltaHook "|"
>> \relative {
>>   c''1
>>   \once \override Score.VoltaBracket.shorten-pair = #'(0 . 0.2)
>>   %\set Score.repeatCommands = #(list(list 'volta voltaAdLib) 'start-repeat)
>>   %\set Score.repeatCommands = #`(,`(volta ,voltaAdLib))
>>   %\set Score.repeatCommands = #`(,`(volta ,#{ \markup \normal-text {
>> \fontsize #-1 what \italic  ever } #}))
>
> Oh come on, you don't need `, for every level.

I stand corrected ;)

>
>   %\set Score.repeatCommands = #`((volta ,voltaAdLib))
>   %\set Score.repeatCommands = #`((volta ,#{ \markup \normal-text {
>  \fontsize #-1 what \italic  ever } #}))
>
> --
> David Kastrup

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

Re: Repeat with alternatives [solved]

[David Kastrup]

David Wright  writes:

> Quoting s.p.korzil...@gmail.com (s.p.korzil...@gmail.com):
>
>> I’m trying to write a piece that has repeats with alternatives. It
>> seems that “
>> \repeat volta 2” is the way to go with supplying the alternatives in “\
>> alternative”. However, this seems to work only for alternative
>> endings, while I
>> have alternative middle parts.
>
> Hi again, thanks to
> http://lists.gnu.org/archive/html/lilypond-user/2015-10/msg00399.html
> I can now close the volta bracket with this undocumented feature,
> \allowVoltaHook, thus avoiding inkscape postprocessing.
>
> Be aware, however, that \allowVoltaHook is global and unresettable,
> at least at the level of \score. (I don't use \book myself.)

Appalling.  It's not totally global but per-session (file on the command
line).  But still seems like far too large a hammer.

-- 
David Kastrup

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

Re: alternate endings without repeats

[David Kastrup]

Thomas Morley  writes:

> 2015-10-12 23:45 GMT+02:00 Juraj :
>> http://thread.gmane.org/gmane.comp.gnu.lilypond.general/24012
>>
>> (8 years old) helped. But if there are news about, I'm interested in!
>>
>> Greetings
>>
>> Juro
>
>
>
> Well, there is no convincing user-interface for it.
>
> You can do:
>
>
> voltaAdLib = \markup \normal-text { \fontsize #-1 what \italic  ever }
> \allowVoltaHook "|"
> \relative {
>   c''1
>   \once \override Score.VoltaBracket.shorten-pair = #'(0 . 0.2)
>   %\set Score.repeatCommands = #(list(list 'volta voltaAdLib) 'start-repeat)
>   %\set Score.repeatCommands = #`(,`(volta ,voltaAdLib))
>   %\set Score.repeatCommands = #`(,`(volta ,#{ \markup \normal-text {
> \fontsize #-1 what \italic  ever } #}))

Oh come on, you don't need `, for every level.

  %\set Score.repeatCommands = #`((volta ,voltaAdLib))
  %\set Score.repeatCommands = #`((volta ,#{ \markup \normal-text {
 \fontsize #-1 what \italic  ever } #}))

-- 
David Kastrup

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

Re: Emacs lilypond-mode

[David Kastrup]

Andrew Bernard  writes:

> Hi David,
>
> Really helpful advice. Except I need a hint or two.
>
> If I create .dir-locals.el thus:
>
> ((LilyPond-mode
>   (LilyPond-lilypond-command . "lilypond -I /tmp")))
>
> when running C-c C-l then only the command ‘lilypond’ is run - the
> customisation is ignored. Do you have to customise the elisp
> definition in entirety?
>
> The idea is to just add -I for the include paths for the libraries of
> code that I have created.

This is rather awkward: all the commands refer to LilyPond-command-menu,
and LilyPond-command-menu evaluates the value of
LilyPond-lilypond-command when first loaded but not afterwards.  So any
subsequent change or customization is ignored until Emacs is restarted,
but directory locals are applied when a mode is loaded and consequently
will always come too late.  I'll take a look at the code and try fixing
it.  Since the code was lifted from a very early version of AUCTeX,
making it work like AUCTeX should likely do the trick.

-- 
David Kastrup

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

Re: alternate endings without repeats

[Thomas Morley]

2015-10-13 3:45 GMT+02:00 David Wright :
> Quoting Thomas Morley (thomasmorle...@gmail.com):

>
> Now I'm figuring out the relative merits of
>
>>   \set Score.repeatCommands = #`(,`(volta , ...
>
> and
>
>>   \set Score.repeatCommands = #'((volta ...

As there is no real user-interface, pure guile-syntax has to be used.
The former syntax allows entries of the list to be evaluated.
The latter simply quotes.

More info in the guile1.8-manual, section 5.13.1.1 Expression Syntax
or search for quote, quasiquote, unquote

Cheers,
  Harm

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

Re: Repeat with alternatives [solved]

[Thomas Morley]

2015-10-13 3:18 GMT+02:00 David Wright :
> Quoting s.p.korzil...@gmail.com (s.p.korzil...@gmail.com):
>
>> I’m trying to write a piece that has repeats with alternatives. It seems 
>> that “
>> \repeat volta 2” is the way to go with supplying the alternatives in “\
>> alternative”. However, this seems to work only for alternative endings, 
>> while I
>> have alternative middle parts.
>
> Hi again, thanks to 
> http://lists.gnu.org/archive/html/lilypond-user/2015-10/msg00399.html
> I can now close the volta bracket with this undocumented feature,
> \allowVoltaHook, thus avoiding inkscape postprocessing.
>
> Be aware, however, that \allowVoltaHook is global and unresettable,
> at least at the level of \score. (I don't use \book myself.)

Apart from being listed in available music-functions there is indeed
no documentation for `allowVoltaHook' and it is indeed global and
unresettable.
Probably best to changed it into a property. Another entry on my
(very) long TODO-list.

To get around the problem of `allowVoltaHook' being global you could
define a new bar-line (basically renaming):

\version "2.18.2"

#(define-bar-line "|-b" "|" #f "|")
\allowVoltaHook "|-b"

\relative {
  \override Score.VoltaBracket.shorten-pair = #'(0.2 . 0.2)
  c'1
  \set Score.repeatCommands = #'((volta "1a"))
  d1
  \bar "|-b"
  \set Score.repeatCommands = #'((volta #f) (volta "2a"))
  e1
  \set Score.repeatCommands = #'((volta #f))
  \bar "|-b"


  c'1
  \set Score.repeatCommands = #'((volta "2a"))
  d
  \set Score.repeatCommands = #'((volta #f) (volta "2b"))
  e
  \set Score.repeatCommands = #'((volta #f))
}


>
> I've also tidied up the code I sent previously, getting rid of the
> warning by removing the redundant (volta #f). Staff, \score and \time
> are also not required as they only redefine the defaults.
> Score.VoltaBracket.shorten-pair might be useful too. I've tried to
> indicate that the barlines both *terminate* the alternative part-
> measures by shifting the hooks.
>
> (I'm not convinced that part-measures are a good idea, but that's not
> my call.)
>
> Cheers,
> David.
>
> ___
> 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: A title with a transposing note name

[Michael Gerdau]

> Yes, that is what I said: "while my version has it inside and this
> causes an error",
> The error message suggests putting it in a \layout block, but that also
> is an error.
> I can't help thinking that there must be something much simpler some
> sort of music function that takes a note name (as a music e.g.
> \transpose f g {cis}) and generates a markup (or rather whatever would
> be valid inside \markup).

I would expect that you can specifically override the font for the
ChordNames. It has a font-family property. However I have no idea
how that can be achieved. Namely I don't know which particular
incantation needs to be invoked.

I'd expect something along the line
\version "2.19.25"

\header {
 title = \markup {Sonata in\score {
 \new ChordNames { f' }
 \layout{indent=0.0
 \set ChordNames.font-family = "Times New Roman" 
}
 but that doesn't do the trick.

Or something like (in the above):
...
 title = \markup {Sonata in\override some-property \roman \score {
...

But again I did not find a working solution.

Kind regards,
Michael
-- 
 Michael Gerdau   email: m...@qata.de
 GPG-keys available on request or at public keyserver

signature.asc
Description: This is a digitally signed message part.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: A title with a transposing note name

[Richard Shann]

On Tue, 2015-10-13 at 07:18 +0200, Federico Bruni wrote:
> Il giorno lun 12 ott 2015 alle 18:54, Richard Shann 
>  ha scritto:
> > I am trying to make a title (e.g. Sonata in F minor) which will
> > transpose when the music is transposed. I can do this by using
> > ChordNames for the name of the note in a markup using \score, thus:
> > 
> > \version "2.19.25"
> > 
> > \header {
> >   title = \markup {Sonata in\score {
> > \new ChordNames { f' }
> > \paper{
> > #(define fonts (make-pango-font-tree "Times New Roman" "Times New 
> > Roman""Luxi Mono" (/ staff-height pt 20)))
> > }
> > \layout{indent=0.0}
> > } minor}
> > }
> > 
> > \score {
> >   \new Voice { \clef treble s1 }
> >   \layout { }
> > }
> > 
> > In this I have tried to change the font of the ChordName (which 
> > defaults
> > to sans) by using the syntax at
> > http://www.lilypond.org/doc/v2.18/Documentation/notation/fonts#index-font-families_002c-setting
> > unfortunately the example has the \paper block outside the score block
> > while my version has it inside and this causes an error.
> 
> In your example the \paper block is inside the \header block. This is 
> not correct:
Yes, that is what I said: "while my version has it inside and this
causes an error",
The error message suggests putting it in a \layout block, but that also
is an error.
I can't help thinking that there must be something much simpler some
sort of music function that takes a note name (as a music e.g.
\transpose f g {cis}) and generates a markup (or rather whatever would
be valid inside \markup).

Richard



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