Re: Exited with return code -1073741819.

[Andrew Bernard]

Can you send me the file to examine?

You have had problems like this before I have helped you with. I will wager
it is the same thing.

Happy to help.

Andrew


On 30 October 2016 at 19:49, MING TSANG  wrote:

> hi, lilyponders:
>
> (1).  What is the meaning of the following error message?
> I have SATB + piano score of 100 bars. Each SATB+pianoRH coded with 100
> bars. I started to code piano-LH and it was all compilable upto bar  45 (no
> error). But after coded bar 46, I got the error.
>
> (2)  Window 10 generate the Chinese character onto the file naming, why
> the error message cannot display the UTF-8 Chinese character?
>
> Thank for the help.
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: Slur too long

[Andrew Bernard]

Hi Ilja,

 

Like Harm, I do not think the slur is too long in this case. That is right that 
it extends past the stem and over the flag.

 

There is a very powerful slur shape function called \shapeII in the openlilylib 
project. You may want to look into this. It gives an easy way to attain a high 
degree of control over the shape of slurs and phrasing slurs, and is easier to 
use than the baseline \shape. It’s indispensable – I use it continuously in my 
scores.

 

Andrew

 

 

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

Re: Slur too long

[Thomas Morley]

2016-10-31 10:56 GMT+01:00 Ilja Panzer :
>
> Hello everybody,
>
> I recently ran across the following problem:
>
> \version "2.19.49"
> \markup "slurUp"
> {
>   \autoBeamOff \slurUp \stemUp g'8( c''16 b'16  c''8)
> }
>
> \markup "slurDown"
> {
>   \autoBeamOff \slurDown \stemUp g'8( c''16 b'16  c''8)
> }
>
> produces the attached output.
>
> With the \slurUp-command the slur is a bit too long. Is there a default 
> setting to correct that? I modify slurs regularly but this bit is from a 
> piece where it is the upper voice in a system which is also required to be 
> printed separately and I would like to keep the modifications to a minimum so 
> I don’t have to change all the parameters for the separate voices when 
> printed invidvidually.
>
> Maybe on of you has a hint
>
> Best regards and thanks for the amazing input and discussions in this list
> Ilja


Not sure I agree the Slur is too long.

Anyway, in this case you could try:

{
  \autoBeamOff \slurUp \stemUp
  \override Slur.details.edge-slope-exponent = 3.7 %% default is 1.7
  g'8( c''16 b'16  c''8)
}

Cheers,
  Harm

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

Re: Shape note font failures

[Thomas Morley]

2016-10-31 12:18 GMT+01:00 Jim Duke :
> I had already tried rendering it in the best form I could, and I first saw 
> the problem when working with the songs in printed form.  I also had zoomed 
> in on the notes in the PDF Viewer (I'm using the latest Acrobat Reader from 
> Adobe) and the errant notes were wrong at all zoom levels.
>
> Since Harm didn't have a problem, I thought that perhaps he was using a 
> different version of Lilypond than I was.  I was running 2.18.2; and I 
> suspect that Harm was running close to the latest version so I tested that.  
> 2.19.49 worked fine.  I don't know enough about the system to diagnose why.

>> The following example reproduces the problem:
>>
>> \version "2.18.2"
>>

Because you stated your version as being 2.18.2, I tested with this version!
I'm on Linux, though...

Glad to hear your problem was solved with 2.19.49

Cheers,
  Harm

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

Re: Exited with return code -1073741819.

[Bernhard Kleine]

I experienced the same error on  2016-10-19. I do not believe in
conincidences.

Regards

Bernhard


Am 31.10.2016 um 21:50 schrieb MING TSANG:
> Hi, Christ van Willegen,
>
> Thank for the info.
>
> The score is SATB + piano.
> I coded soprano first 100 bars, the alto 100 bars, then tenor 100 bars
> and bass 100 bars.  I compile the score every 5 bars added.  No error.   
> The I coded LH-piano 100 bars and no error.  I code LH-piano to bar
> 45, no error.  I coded 46, 47, 48,49 and 50 --- comile giving me the
> error.  I remove bar 50 compile error, I remove bar 49, compile error,
> I remove bar 48, compile error. Remove bar 47, compile error. Remove
> bar 46, compile error.  Remove 46, compile OK.   This is all done in
> lilypond 2.19.46.
>
> I saw there is lilypond 2.19.49 available. I download and install.
>  Now when code bar 46, compile OK; Code bar 47, compile error.
>
> I don't know what to do now.  Help is appreciated.
>
> Immanuel,
> Ming.
>
>
> 
> *From:* Christ van Willegen 
> *To:* MING TSANG 
> *Cc:* Lilypond-usermailinglist 
> *Sent:* Monday, October 31, 2016 2:47 PM
> *Subject:* Re: Exited with return code -1073741819.
>
> Hello,
>
> On Sun, Oct 30, 2016 at 9:49 AM, MING TSANG  > wrote:
> > Exited with return code -1073741819.
>
>
> A quick Google search led to this:
> http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_security/file-system-error-1073741819-on-windows-10/30f76ed6-bac1-4863-bfc0-fddb746af898
>
> Perhaps a registry error or a file system error?
>
> Does 'rolling back' to less bars of music make the error go away?
>
> HTH!
>
> Christ van Willegen
> -- 
> 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
>
>
>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
spitzhalde9
D-79853 lenzkirch
bernhard.kle...@gmx.net
www.b-kleine.com, www.urseetal.net
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09



signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Exited with return code -1073741819.

[MING TSANG]

Hi, Christ van Willegen,
Thank for the info.
The score is SATB + piano.I coded soprano first 100 bars, the alto 100 bars, 
then tenor 100 bars and bass 100 bars.  I compile the score every 5 bars added. 
 No error.   The I coded LH-piano 100 bars and no error.  I code LH-piano to 
bar 45, no error.  I coded 46, 47, 48,49 and 50 --- comile giving me the error. 
 I remove bar 50 compile error, I remove bar 49, compile error, I remove bar 
48, compile error. Remove bar 47, compile error. Remove bar 46, compile error.  
Remove 46, compile OK.   This is all done in lilypond 2.19.46.
I saw there is lilypond 2.19.49 available. I download and install.  Now when 
code bar 46, compile OK; Code bar 47, compile error.
I don't know what to do now.  Help is appreciated.
Immanuel,Ming.

  From: Christ van Willegen 
 To: MING TSANG  
Cc: Lilypond-usermailinglist 
 Sent: Monday, October 31, 2016 2:47 PM
 Subject: Re: Exited with return code -1073741819.
   
Hello,

On Sun, Oct 30, 2016 at 9:49 AM, MING TSANG  wrote:
> Exited with return code -1073741819.

A quick Google search led to this:
http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_security/file-system-error-1073741819-on-windows-10/30f76ed6-bac1-4863-bfc0-fddb746af898

Perhaps a registry error or a file system error?

Does 'rolling back' to less bars of music make the error go away?

HTH!

Christ van Willegen
-- 
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0


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

Re: Drawing an Oval around a group of notes

[Klaus Blum]

Hi Harm, 

Thomas Morley-2 wrote
> Maybe David Nalesnik's frame-engraver could be forced to do so as well.

I could not resist to try that... David's tool is a really cool thing. 
The most recent code I know of is here: 
http://lilypond.1069038.n5.nabble.com/box-around-notes-td35581.html#a170648

Here's a first result: 
box-to-ellipse.ly
   
box-to-ellipse.pdf
  

It's only a first step and not yet usable for any case.
I simply replaced the (rectangular) boxes by ellipses. However, not
everything inside the rectangle is covered by the ellipse. There is a
property "padding" that can be used to generally increase the size of the
ellipses. 
Also, there is no support for line breaks so far, as a "broken" ellipse will
result in two separate ellipses. 

Cheers, 
Klaus



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Drawing-an-Oval-around-a-group-of-notes-tp195873p195915.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: Shape note font failures

[Jim Duke]

I was running 2.18.2 on Windows 10 and on Windows 7 on two separate computers.  
Installing 2.19.49 worked on those same two computers.  It does appear to be 
the wrong glyph.  By the way, before trying 2.19.49, I used:

\set shapeNoteStyles = ##(do reThin miMirror fa sol la ti)

I basically copied the aikenHead definition from property-init.ly and chose a 
different glyph for RE.  It's not as nice looking as the proper RE half note 
glyph, but at least you could tell it apart from the quarter note.  But the 
2.19.49 version works fine for me on my computers; so that hack wasn't needed.

On my Windows computers, the problem showed up for sizes 17, 18, 19, and 20.  
Below that range, and above that range had no issues.
 
-Original Message-
From: David Wright [mailto:lily...@lionunicorn.co.uk] 
Sent: Monday, October 31, 2016 3:19 PM
To: Jim Duke 
Cc: Phil Holmes ; Thomas Morley 
; lilypond-user@gnu.org
Subject: Re: Shape note font failures

On Mon 31 Oct 2016 at 11:18:39 (+), Jim Duke wrote:
> I had already tried rendering it in the best form I could, and I first saw 
> the problem when working with the songs in printed form.  I also had zoomed 
> in on the notes in the PDF Viewer (I'm using the latest Acrobat Reader from 
> Adobe) and the errant notes were wrong at all zoom levels.
> 
> Since Harm didn't have a problem, I thought that perhaps he was using a 
> different version of Lilypond than I was.  I was running 2.18.2; and I 
> suspect that Harm was running close to the latest version so I tested that.  
> 2.19.49 worked fine.  I don't know enough about the system to diagnose why.

(I removed   \override NoteHead.   from the source you provided.)
This problem exists in Debian jessie's 2.18.2 version for 19-21.
It's in neither 2.18.2 nor 2.19.44 from lilypond.org, nor in Debian wheezy's 
2.14.2. It looks as if the wrong glyph is in the font.

This is reminiscent of Debian squeeze's problem (2.12.3) with G-clefs at sizes 
around 18/19. They would be printed with the top loop filled in and something 
sticking out the side.

Cheers,
David.

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

Re: Shape note font failures

[David Wright]

On Mon 31 Oct 2016 at 11:18:39 (+), Jim Duke wrote:
> I had already tried rendering it in the best form I could, and I first saw 
> the problem when working with the songs in printed form.  I also had zoomed 
> in on the notes in the PDF Viewer (I'm using the latest Acrobat Reader from 
> Adobe) and the errant notes were wrong at all zoom levels.
> 
> Since Harm didn't have a problem, I thought that perhaps he was using a 
> different version of Lilypond than I was.  I was running 2.18.2; and I 
> suspect that Harm was running close to the latest version so I tested that.  
> 2.19.49 worked fine.  I don't know enough about the system to diagnose why.

(I removed   \override NoteHead.   from the source you provided.)
This problem exists in Debian jessie's 2.18.2 version for 19-21.
It's in neither 2.18.2 nor 2.19.44 from lilypond.org, nor in Debian
wheezy's 2.14.2. It looks as if the wrong glyph is in the font.

This is reminiscent of Debian squeeze's problem (2.12.3) with G-clefs
at sizes around 18/19. They would be printed with the top loop filled in
and something sticking out the side.

Cheers,
David.

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

Re: automatic beams over rests?

[David Kastrup]

Tobin Chodos  writes:

> Is there no way to set beams to go over rests globally?

Not with reasonable amount of effort (you'd need to write a replacement
for the Auto_beam_engraver: the built-in one doesn't beam over rests).

-- 
David Kastrup

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

Re: Exited with return code -1073741819.

[Christ van Willegen]

Hello,

On Sun, Oct 30, 2016 at 9:49 AM, MING TSANG  wrote:
> Exited with return code -1073741819.

A quick Google search led to this:
http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_security/file-system-error-1073741819-on-windows-10/30f76ed6-bac1-4863-bfc0-fddb746af898

Perhaps a registry error or a file system error?

Does 'rolling back' to less bars of music make the error go away?

HTH!

Christ van Willegen
-- 
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

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

automatic beams over rests?

[Tobin Chodos]

Is there no way to set beams to go over rests globally?
Thanks again - new to this list but learning a lot.
Tobin
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Drawing an Oval around a group of notes

[Klaus Blum]

Hi John, 

John Zeweniuk wrote
> Can anybody give me some suggestions  of how I would draw an oval around a
> group of notes on the staff?

the function provided by Robin could serve to adapt snippet 960:
http://lsr.di.unimi.it/LSR/Item?id=960

Here's the result: 
 
% --
colorOval =
#(define-music-function (parser location y-lower y-upper color)
   (number? number? color?)
   #{
 \once \override HorizontalBracket.Y-offset = #0
 \once \override HorizontalBracket.stencil =
 $(lambda (grob)
(let* (
(area (ly:horizontal-bracket::print grob))
(xext (ly:stencil-extent area X))
(xpos (/ (+ (cdr xext) (car xext)) 2))
(xrad (/ (- (cdr xext) (car xext)) 2))
(ypos (/ (+ y-upper y-lower) 2))
(yrad (/ (- y-upper y-lower) 2))
(thick (ly:grob-property grob 'thickness 0.05)))
  (ly:stencil-translate
   (ly:make-stencil (list 'ellipse xrad yrad thick #f))
   (cons xpos ypos
 % Use the following properties to modify the appearance:
 \once \override HorizontalBracket.layer = #-10 
 \once \override HorizontalBracket.color = $color
 \once \override HorizontalBracket.thickness = #0.5
 \once \override HorizontalBracket.shorten-pair = #'(-1.5 . -1.5)
   #})

\score {
  {
R1
\colorOval #-5 #1 #green   % call this before the first note
c'2\startGroup g' c'\stopGroup
r2
  }
  \layout {
\context {
  \Voice
  \consists "Horizontal_bracket_engraver"
}
  }
}
% --

It can be used to "mark" a sequence of several notes. Lower and upper border
must be given as parameters, zero = middle line.

Cheers, 
Klaus



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Drawing-an-Oval-around-a-group-of-notes-tp195873p195907.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: midi \p \f volume

[Sirius Barras]

Thank you Vaughan, it works great!
g.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Grace notes and doubled bar line

[David Sumbler]

On Mon, 2016-10-31 at 23:35 +1100, Andrew Bernard wrote:
> Hi David,
> 
> You have stumbled upon a known lilypond issue with grace notes. Have
> a read of the 'known issues and warnings' section under Grace Notes
> in the NR, Section 1.2.6 which explains this and what to do, which
> you have effectively discovered yourself.
> 
> Andrew

Thanks for that.  The solution is simple, but as usual I thought I must
have done something stupid, rather than that a Lilypond bug was at
work.

David

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

Re: midi \p \f volume

[Vaughan McAlley]

On 31 October 2016 at 18:52, Gianmaria Lari  wrote:
> If you don't use the dynamic mark from \p to \f but you limit
> yourseft from \p to \f, the midi output is often too tight.
>
> Is there any (easy) way to make the range from \p to \f playing as \p to
> \f?
> Thank you, g.
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>

Hi Gianmaria,

It looks like you can redefine the Scheme list of dynamics:

%%%
\version "2.18.2"

% Redefine what was set in ../scm/midi.scm
#(set! absolute-volume-alist
   (append
'(
("f" . 0.95)
("mf" . 0.75)
("mp" . 0.55)
("p" . 0.35)
)
absolute-volume-alist))

\score {
 \relative c' { c4\p d\mp e\mf f\f }
 \layout {}
 \midi {}
}



You can set the numbers to anything you like between 0 and 1.

Cheers,
Vaughan

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

RE: Grace notes and doubled bar line

[Andrew Bernard]

Hi David,

You have stumbled upon a known lilypond issue with grace notes. Have a read of 
the 'known issues and warnings' section under Grace Notes in the NR, Section 
1.2.6 which explains this and what to do, which you have effectively discovered 
yourself.

Andrew




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

Grace notes and doubled bar line

[David Sumbler]

\version "2.19.48"

\language "english"

vn =
\new Staff \relative g'' { 
  g1 \bar "||" \time 6/8 \tempo "Vivace"
  R2. | \grace { g16( a } g4.) g |
}

vc =
\new Staff \relative g' {
  g2 g \bar "||" \time 6/8 \tempo "Vivace"
  \grace { g16( a } g2.) ~ | g |
}

\score {
  \new StaffGroup <<
\vn
\vc
  >>
}

The above compiles to give two double bars at the time change, each
complete with new time signature and tempo marking.  The grace notes in
the lower part are printed between the 2 barlines.  I want the grace
notes to appear after the barline as usual.

The funny thing is that if I change the second line of the upper part
to "\grace { g16( a } g4.) g | R2. |", so that the upper and lower
parts both have grace notes immediately following the double bar, it
compiles as I would wish.

Where am I going wrong?

David 



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

RE: Shape note font failures

[Jim Duke]

I had already tried rendering it in the best form I could, and I first saw the 
problem when working with the songs in printed form.  I also had zoomed in on 
the notes in the PDF Viewer (I'm using the latest Acrobat Reader from Adobe) 
and the errant notes were wrong at all zoom levels.

Since Harm didn't have a problem, I thought that perhaps he was using a 
different version of Lilypond than I was.  I was running 2.18.2; and I suspect 
that Harm was running close to the latest version so I tested that.  2.19.49 
worked fine.  I don't know enough about the system to diagnose why.

Thanks for all the help

-Original Message-
From: Phil Holmes [mailto:m...@philholmes.net] 
Sent: Monday, October 31, 2016 5:06 AM
To: Thomas Morley ; Jim Duke 
Cc: lilypond-user@gnu.org
Subject: Re: Shape note font failures

- Original Message - 
From: "Thomas Morley" 
To: "Jim Duke" 
Cc: 
Sent: Monday, October 31, 2016 8:52 AM
Subject: Re: Shape note font failures


2016-10-31 3:20 GMT+01:00 Jim Duke :
> I’m typesetting some A Capella music for congregational singing the uses 
> the
> 7-note (Aiken) shape note system.  I’ve found that based on the system 
> size
> some of the half note heads for RE (d in the example) are 
> indistinguishable
> from quarter notes.  Basically the interior of the note head is filling 
> in.
> The following example reproduces the problem:
>
>
>
> \version "2.18.2"
>
>
>
> \score {
>
>   \relative c' {
>
> \aikenHeads
>
> \override NoteHead.
>
> c2 d2 e2 f2 g2 a2 b2 c2
>
>   }
>
>   \layout {
>
> #(layout-set-staff-size 21)
>
>   }
>
> }
>
>
>
> \score {
>
>   \relative c' {
>
> \aikenHeads
>
> c2 d2 e2 f2 g2 a2 b2 c2
>
>   }
>
>   \layout {
>
> #(layout-set-staff-size 22)
>
>   }
>
> }
>
>
>
> The D in the first system (at staff size 21) has the note head filled in.
> The D in the second system (with staff size 22) has the note head hollow 
> as
> it should be.
>
>
>
> I’m not sure how to proceed with fixing this.  I can artificially enlarge
> the note heads; but that is an unsatisfactory fix that I’d like to avoid 
> if
> possible.  I’m afraid the real fix would involve a change in the font
> definitions.  It seems the pen size is a bit too large.  Is there a way
> short of changing the font definition of controlling that?


No problem here. See attached.

So I can't help.

-Harm






Sometimes PDF viewers don't display shapes accurately on screen.  Jim - have 
you tried printing out a problem score, or viewing it much enlarged?

--
Phil Holmes 

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

RE: Pango warning

[Andrew Bernard]

Hi Jean,

I don't think it is as simple as you imagine. I am using 2.19.49 in Windows 10. 
The same exact file compiles with no error using 2.19.49 on Linux Mint. Also, 
still, the very long compile times (40 seconds before anything happens) happen 
to me on every run. There is something unstable about font handling in lilypond 
the last few development releases.

I will move this thread to the bug list.

Andrew




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

Re: Question for a FLOSS licensing session

[David Kastrup]

Urs Liska  writes:

> Am 31. Oktober 2016 01:43:26 GMT-07:00, schrieb David Kastrup :
>>Carl Sorensen  writes:
>>
>>> To make what I consider an apt analogy, using gcc doesn't require any
>>> programs you create to be GPL'd.
>>
>>GCC has a special exception in the licensing exempting the startup
>>stubs
>>and other fixed material it might place into the code from requiring
>>licensing.  The generated code as such is exempt from requiring a
>>license anyway.
>>
>>Similar concerns for LilyPond would hold for library/LSR code bundled
>>into the PDF file as source (we have an option for that or an issue for
>>creating such an option).  And fonts in extractable forms of embedding.
>>
>>So it's not a no-brainer, but the concerns voiced by Urs are mostly
>>incorrect.
>
> Maybe not concretely enough, so I'll give a concrete example. Imagine
> the following project:
>
> An edition project is to be made available as
> - printed copies
> - PDF files 
> - a Git repository
>
> The repository contains among others
> - encoded music
> - Scheme functions created for the project
> - Scheme functions created using included code from LilyPond and GPLed
> openLilyLib
> - Scheme functions created by modifying functions copied from LilyPond

Only the very last item is relevant if by "included code" you mean
"\include ...".

> Doesn't the GPL prevent me from making that repository available
> under, say, a non-free CC license or under a no-license like "you may
> read the code and use it to produce scores but you may not
> redistribute a modified version"?

The GPL applies only with the very last item.  All the rest is
irrelevant.  Note that the principal distribution is not a modified
version of LilyPond but a document and stuff particular to creating that
document with the help of LilyPond, but "with the help of LilyPond" does
not imply LilyPond as a component of the project, just as a tool
required for it.

With Elisp files for Emacs, I'd still draw the line at the same place
(but the legal precedence is muddy enough that the FSF does not commit
to stating Elisp libraries being covered by Emacs' GPL as being
unaffected, but they will also likely not venture to court for it).  But
here the "application" involves running Emacs, and the actual
_application_ of a music score, namely making use of the PDF or Midi
file, does not involve running LilyPond.

> I don't think one can that easily say "it's all documents and the
> license doesn't apply to that".

And who said that?  I think that we have enough real people on the list
that we don't need to invent straw men.

-- 
David Kastrup

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

Slur too long

[Ilja Panzer]

Hello everybody,

I recently ran across the following problem:

\version "2.19.49"
\markup "slurUp"
{
  \autoBeamOff \slurUp \stemUp g'8( c''16 b'16  c''8)
} 

\markup "slurDown"
{
  \autoBeamOff \slurDown \stemUp g'8( c''16 b'16  c''8)
} 

produces the attached output.


With the \slurUp-command the slur is a bit too long. Is there a default setting 
to correct that? I modify slurs regularly but this bit is from a piece where it 
is the upper voice in a system which is also required to be printed separately 
and I would like to keep the modifications to a minimum so I don’t have to 
change all the parameters for the separate voices when printed invidvidually.

Maybe on of you has a hint

Best regards and thanks for the amazing input and discussions in this list
Ilja

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

Re: Question for a FLOSS licensing session

[Urs Liska]

Am 31. Oktober 2016 01:43:26 GMT-07:00, schrieb David Kastrup :
>Carl Sorensen  writes:
>
>> To make what I consider an apt analogy, using gcc doesn't require any
>> programs you create to be GPL'd.
>
>GCC has a special exception in the licensing exempting the startup
>stubs
>and other fixed material it might place into the code from requiring
>licensing.  The generated code as such is exempt from requiring a
>license anyway.
>
>Similar concerns for LilyPond would hold for library/LSR code bundled
>into the PDF file as source (we have an option for that or an issue for
>creating such an option).  And fonts in extractable forms of embedding.
>
>So it's not a no-brainer, but the concerns voiced by Urs are mostly
>incorrect.

Maybe not concretely enough, so I'll give a concrete example. Imagine the 
following project:

An edition project is to be made available as
- printed copies
- PDF files 
- a Git repository

The repository contains among others
- encoded music
- Scheme functions created for the project
- Scheme functions created using included code from LilyPond and GPLed 
openLilyLib
- Scheme functions created by modifying functions copied from LilyPond


Doesn't the GPL prevent me from making that repository available under, say, a 
non-free CC license or under a no-license like "you may read the code and use 
it to produce scores but you may not redistribute a modified version"?

I don't think one can that easily say "it's all documents and the license 
doesn't apply to that". 

Urs

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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

Re: Pango warning

[Jean Brefort]

Le lundi 31 octobre 2016 à 19:01 +1100, Andrew Bernard a écrit :
> Hi Jean
> 
> Then what does it mean to be 'not correctly utf-8 encoded' and why
> has this always compiled before? What is an example of text not
> correctly encoded? I fail to understand.
> 
> Andrew
> 
> 
> -Original Message-
> From: Jean Brefort 
> Sent: Monday, 31 October 2016 5:37 PM
> 
> 
> It just means what it says, there is at least one string which is not
> correctly utf-8 encoded in the source file.
> 
> Jean
> 
Some codes are not valid as UTF-8, such as C0 which never appears, see 
https://tools.ietf.org/html/rfc3629 for details. If your file compiled
and does not compile anymore, then it must have need corrupted somehow.
Hard to say what is wrong without access to the file.

Jean

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

Re: Question for a FLOSS licensing session

[Urs Liska]

Am 31. Oktober 2016 01:41:54 GMT-07:00, schrieb Thomas Morley 
:
>2016-10-31 3:39 GMT+01:00 David Kastrup :
>
>> And of course
>> the _corresponding_ source code which will in general be under
>control
>> of the user.  There are some considerations when LSR code and similar
>> gets copied into documents: in that case, the source code of the
>> document might come under the licensing reign of the LSR code (do we
>> specify anything for it?).
>
>In
>http://lsr.di.unimi.it/LSR/html/whatsthis.html
>you could read:
>
>"Who owns LSR?
>
>You, me, and everybody. LSR is based on free tools (see the next
>section) and all the supporting code is free software distributed
>under the GNU General Public License.
>
>The content of the database is public domain, so you can use it, copy
>it, modify and redistribute it with no obligation."
>
>
>When entering a new snippet first thing you read is:
>
>"Important: By entering your snippet, you are placing it in the public
>domain. This includes also snippets taken from the Lilypond manual
>(the manual authors grant you their permission to do so)."
>
>

Hm.
The people from the FSF and Software Freedom Conservancy were just explaining 
why "placing in the public domain" is a bad idea because it's more or less 
impossible under most jurisdictions. Anyone using such code is facing the risk 
that the copyright owner may revoke that within 25 years. 

Best
Urs

>Cheers,
>  Harm

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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

Re: Shape note font failures

[Phil Holmes]

- Original Message - 
From: "Thomas Morley" 

To: "Jim Duke" 
Cc: 
Sent: Monday, October 31, 2016 8:52 AM
Subject: Re: Shape note font failures


2016-10-31 3:20 GMT+01:00 Jim Duke :
I’m typesetting some A Capella music for congregational singing the uses 
the
7-note (Aiken) shape note system.  I’ve found that based on the system 
size
some of the half note heads for RE (d in the example) are 
indistinguishable
from quarter notes.  Basically the interior of the note head is filling 
in.

The following example reproduces the problem:



\version "2.18.2"



\score {

  \relative c' {

\aikenHeads

\override NoteHead.

c2 d2 e2 f2 g2 a2 b2 c2

  }

  \layout {

#(layout-set-staff-size 21)

  }

}



\score {

  \relative c' {

\aikenHeads

c2 d2 e2 f2 g2 a2 b2 c2

  }

  \layout {

#(layout-set-staff-size 22)

  }

}



The D in the first system (at staff size 21) has the note head filled in.
The D in the second system (with staff size 22) has the note head hollow 
as

it should be.



I’m not sure how to proceed with fixing this.  I can artificially enlarge
the note heads; but that is an unsatisfactory fix that I’d like to avoid 
if

possible.  I’m afraid the real fix would involve a change in the font
definitions.  It seems the pen size is a bit too large.  Is there a way
short of changing the font definition of controlling that?



No problem here. See attached.

So I can't help.

-Harm






Sometimes PDF viewers don't display shapes accurately on screen.  Jim - have 
you tried printing out a problem score, or viewing it much enlarged?


--
Phil Holmes 



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

Re: Question for a FLOSS licensing session

[Thomas Morley]

2016-10-31 9:48 GMT+01:00 David Kastrup :
> Thomas Morley  writes:
>
>> When entering a new snippet first thing you read is:
>>
>> "Important: By entering your snippet, you are placing it in the public
>> domain. This includes also snippets taken from the Lilypond manual
>> (the manual authors grant you their permission to do so)."
>
> Is that a special permission for the LSR or does it hold for everything
> from the manual?

That I don't know.
Iirc, this sentence is there since I started using LilyPond, so maybe
since the LSR was set up.

Cheers,
  Harm

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

Re: Shape note font failures

[Thomas Morley]

2016-10-31 3:20 GMT+01:00 Jim Duke :
> I’m typesetting some A Capella music for congregational singing the uses the
> 7-note (Aiken) shape note system.  I’ve found that based on the system size
> some of the half note heads for RE (d in the example) are indistinguishable
> from quarter notes.  Basically the interior of the note head is filling in.
> The following example reproduces the problem:
>
>
>
> \version "2.18.2"
>
>
>
> \score {
>
>   \relative c' {
>
> \aikenHeads
>
> \override NoteHead.
>
> c2 d2 e2 f2 g2 a2 b2 c2
>
>   }
>
>   \layout {
>
> #(layout-set-staff-size 21)
>
>   }
>
> }
>
>
>
> \score {
>
>   \relative c' {
>
> \aikenHeads
>
> c2 d2 e2 f2 g2 a2 b2 c2
>
>   }
>
>   \layout {
>
> #(layout-set-staff-size 22)
>
>   }
>
> }
>
>
>
> The D in the first system (at staff size 21) has the note head filled in.
> The D in the second system (with staff size 22) has the note head hollow as
> it should be.
>
>
>
> I’m not sure how to proceed with fixing this.  I can artificially enlarge
> the note heads; but that is an unsatisfactory fix that I’d like to avoid if
> possible.  I’m afraid the real fix would involve a change in the font
> definitions.  It seems the pen size is a bit too large.  Is there a way
> short of changing the font definition of controlling that?


No problem here. See attached.

So I can't help.

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

Re: Question for a FLOSS licensing session

[David Kastrup]

Thomas Morley  writes:

> When entering a new snippet first thing you read is:
>
> "Important: By entering your snippet, you are placing it in the public
> domain. This includes also snippets taken from the Lilypond manual
> (the manual authors grant you their permission to do so)."

Is that a special permission for the LSR or does it hold for everything
from the manual?  I don't like special permissions.

In the Notation Reference I can only find the GFDL in an appendix
without qualification and even without a statement which software it
applies to.  Maybe I've not looked thoroughly enough.

-- 
David Kastrup

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

Re: Question for a FLOSS licensing session

[David Kastrup]

Carl Sorensen  writes:

> To make what I consider an apt analogy, using gcc doesn't require any
> programs you create to be GPL'd.

GCC has a special exception in the licensing exempting the startup stubs
and other fixed material it might place into the code from requiring
licensing.  The generated code as such is exempt from requiring a
license anyway.

Similar concerns for LilyPond would hold for library/LSR code bundled
into the PDF file as source (we have an option for that or an issue for
creating such an option).  And fonts in extractable forms of embedding.

So it's not a no-brainer, but the concerns voiced by Urs are mostly
incorrect.

-- 
David Kastrup

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

Re: Question for a FLOSS licensing session

[Thomas Morley]

2016-10-31 3:39 GMT+01:00 David Kastrup :

> And of course
> the _corresponding_ source code which will in general be under control
> of the user.  There are some considerations when LSR code and similar
> gets copied into documents: in that case, the source code of the
> document might come under the licensing reign of the LSR code (do we
> specify anything for it?).

In
http://lsr.di.unimi.it/LSR/html/whatsthis.html
you could read:

"Who owns LSR?

You, me, and everybody. LSR is based on free tools (see the next
section) and all the supporting code is free software distributed
under the GNU General Public License.

The content of the database is public domain, so you can use it, copy
it, modify and redistribute it with no obligation."


When entering a new snippet first thing you read is:

"Important: By entering your snippet, you are placing it in the public
domain. This includes also snippets taken from the Lilypond manual
(the manual authors grant you their permission to do so)."


Cheers,
  Harm

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

Re: Changing voice order...

[David Kastrup]

Dan Eble  writes:

> On Oct 28, 2016, at 05:01 , David Kastrup  wrote:
>> 
>> Well, there is still the question of what 1/2/3 should _mean_.
>> Currently they are connected with \voiceOne, \voiceTwo,
>> \voiceThree... and the meaning of those is "topmost", "lowest", "below
>> topmost" ...
>> 
>> I find this both disturbing and hard to remember and so for me the
>> question is what the most satisfactory way to change that would be in
>> the long term.
>
> Maybe let << \sopOne \\ \alto \\ \sopTwo >> work as it works and add a
> function to reorder?
>
> e.g.  \highToLow << \sopOne \\ \sopTwo \\ \alto >>

The default should be brainless and easy to remember.  It's the more
special cases that should require specific invocation and/or option
setting.  It's likely going to end up more as a per-parser setting than
a music function, to simplify conversion.

-- 
David Kastrup

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

RE: Pango warning

[Andrew Bernard]

Hi Jean

Then what does it mean to be 'not correctly utf-8 encoded' and why has this 
always compiled before? What is an example of text not correctly encoded? I 
fail to understand.

Andrew


-Original Message-
From: Jean Brefort 
Sent: Monday, 31 October 2016 5:37 PM


It just means what it says, there is at least one string which is not correctly 
utf-8 encoded in the source file.

Jean


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

midi \p \f volume

[Gianmaria Lari]

If you don't use the dynamic mark from \p to \f but you limit
yourseft from \p to \f, the midi output is often too tight.

Is there any (easy) way to make the range from \p to \f playing as \p
to \f?
Thank you, g.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Pango warning

[Jean Brefort]

Le lundi 31 octobre 2016 à 17:16 +1100, Andrew Bernard a écrit :
> Any idea what this may mean?
>  
> As per usual, no line numbers or location info given in the message.
>  
> Preprocessing graphical objects...
> (lilypond.exe:9308): Pango-WARNING **: Invalid UTF-8 string passed to
> pango_layout_set_text()
>  
> (lilypond.exe:9308): Pango-WARNING **: Invalid UTF-8 string passed to
> pango_layout_set_text()
>  
> Andrew
>  
>  
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

It just means what it says, there is at least one string which is not
correctly utf-8 encoded in the source file.

Jean

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

Pango warning

[Andrew Bernard]

Any idea what this may mean?

 

As per usual, no line numbers or location info given in the message.

 

Preprocessing graphical objects...

(lilypond.exe:9308): Pango-WARNING **: Invalid UTF-8 string passed to
pango_layout_set_text()

 

(lilypond.exe:9308): Pango-WARNING **: Invalid UTF-8 string passed to
pango_layout_set_text()

 

Andrew

 

 

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