Re: Exited with return code -1073741819.

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

RE: Slur too long

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

Re: Slur too long

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

Re: Shape note font failures

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 >

Re: Exited with return code -1073741819.

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

Re: Exited with return code -1073741819.

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

Re: Drawing an Oval around a group of notes

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

RE: Shape note font failures

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

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 >

Re: automatic beams over rests?

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

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:

automatic beams over rests?

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

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:

Re: midi \p \f volume

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

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

Re: midi \p \f volume

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 >

RE: Grace notes and doubled bar line

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

Grace notes and doubled bar line

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

RE: Shape note font failures

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

RE: Pango warning

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

Re: Question for a FLOSS licensing session

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

Slur too long

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

Re: Question for a FLOSS licensing session

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

Re: Pango warning

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

Re: Question for a FLOSS licensing session

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

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

Re: Question for a FLOSS licensing session

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

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

Re: Question for a FLOSS licensing session

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

Re: Question for a FLOSS licensing session

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

Re: Question for a FLOSS licensing session

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

Re: Changing voice order...

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

RE: Pango warning

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

midi \p \f volume

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

Re: Pango warning

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 warning

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