Re: 13th chord?

msk...@ansuz.sooke.bc.ca writes: > On Sun, 26 Feb 2017, David Kastrup wrote: >> To me it would seem that the default mode of operation should be for >> them to have matched rules where feasible, in order to have least >> element of surprise. > > I agree, but A. it may not be feasible in some

Re: 13th chord?

2017-02-26 1:53 GMT+01:00 David Kastrup : > Thomas Morley writes: > >> Well, >> the printed output of >> >> m = >> \chordmode { >> >> c:11.13 >> %% unnecessarily verbose: >> c:1.3.5.7.9.11.13 >> } >> >> mII = >>

Re: 13th chord?

On Sun, 26 Feb 2017, David Kastrup wrote: > To me it would seem that the default mode of operation should be for > them to have matched rules where feasible, in order to have least > element of surprise. I agree, but A. it may not be feasible in some important cases, and B. even matched rules

Re: Fermata above and below bar line generates warnings

On Sat, Feb 25, 2017 at 2:07 PM, Thomas Morley wrote: > 2017-02-25 22:42 GMT+01:00 Knute Snortum : > > The following code produces the correct output of fermatas above and > below > > the bar line, but it also emits warnings. Is there another way to

Re: Fermata above and below bar line generates warnings

On Sat, Feb 25, 2017 at 2:02 PM, Jeffery Shivers wrote: > On Sat, Feb 25, 2017 at 4:42 PM, Knute Snortum wrote: > > The following code produces the correct output of fermatas above and > below > > the bar line, but it also emits warnings. Is there

Re: 13th chord?

msk...@ansuz.sooke.bc.ca writes: > On Sun, 26 Feb 2017, Wols Lists wrote: >> I'm guessing lily is taking *in* his request for "C 13", converting it >> into the chord, and then converting that chord *back* into what it >> thinks is called "C 9 13". With the result that lily's output does *not* >>

Re: 13th chord?

Thomas Morley writes: > Well, > the printed output of > > m = > \chordmode { > > c:11.13 > %% unnecessarily verbose: > c:1.3.5.7.9.11.13 > } > > mII = > \chordmode { > > c:13 > %%

Re: Making the Dedication field align left

Am 26.02.2017 um 00:47 schrieb Wols Lists: I've stuck that definition in its own .ily file, and I just %include that file at the start of my \paper definition. I think it would be slightly cleaner to write an entire \paper{} block in the .ily file and include the file on top level. Multiple

Re: 13th chord?

On Sun, 26 Feb 2017, Wols Lists wrote: > I'm guessing lily is taking *in* his request for "C 13", converting it > into the chord, and then converting that chord *back* into what it > thinks is called "C 9 13". With the result that lily's output does *not* > match the user's input. Frustrating!

Re: Force tuplet number above notes

Even better, thanks! --- Knute Snortum (via Gmail) On Sat, Feb 25, 2017 at 2:01 PM, wrote: > Am 2017-02-25 22:56, schrieb Knute Snortum: > > That works, thanks! >> > > I'm at the wrong computer so I can't double-check right now, but I think > the reason for this is that

Re: 13th chord?

On 25/02/17 23:47, Thomas Morley wrote: > Obviously it's _me_ not understanding the issue. As a complete outsider, I read it extremely simply ... The OP asked lilypond to print the chord name as "C 13". Lilypond ignored him and printed the name as "C 9 13". Everybody seems to have got fixated

Re: 13th chord?

On Sat, 25 Feb 2017, Rob Torop wrote: > 13 chord would be rendered as C13 in Ignatzek notation. My question is - is > there a way for me to omit the "9" in the chord name?  My experience is There's no "9" in the chord name "C13", so what are you really asking? Do you want to enter a chord name

Re: Making the Dedication field align left

On 25/02/17 20:59, Simon Albrecht wrote: > Am 25.02.2017 um 21:02 schrieb Chad Linsley: >> Hi all, >> >> I'm a Lilypond noob and am trying to customize the header. How do I >> override the "Dedication" so that it aligns left and not centre? > > The way I understand it you want the dedication

Re: 13th chord?

2017-02-26 0:38 GMT+01:00 David Kastrup : > Thomas Morley writes: > >> 2017-02-25 23:08 GMT+01:00 David Kastrup : >>> Rob Torop writes: >>> When I enter a 13th chord like this e:13, it renders with a 9 as well.

Re: 13th chord?

2017-02-26 0:20 GMT+01:00 Noeck : > Hi Harm, > > Am 25.02.2017 um 23:47 schrieb Thomas Morley: >> So no bug, but a design decision. >> >> To have the 11th included, one needs to explicitely state it: >> >> \chords { e:11.13 } >> >> If this is not done, the printing as E⁹ ¹¹

Re: 13th chord?

Thomas Morley writes: > 2017-02-25 23:08 GMT+01:00 David Kastrup : >> Rob Torop writes: >> >>> When I enter a 13th chord like this e:13, it renders with a 9 as well. >>> I know a 13 chord officially contains the 9 and 11, and that

Re: 13th chord?

Hi Harm, Am 25.02.2017 um 23:47 schrieb Thomas Morley: > So no bug, but a design decision. > > To have the 11th included, one needs to explicitely state it: > > \chords { e:11.13 } > > If this is not done, the printing as E⁹ ¹¹ is ok, imho. As far as I understood Rob, the question is not so

Re: 13th chord?

I'm pretty confused! According to http://lilypond.org/doc/v2.19/Documentation/notation/chord-name-chart, a 13 chord would be rendered as C13 in Ignatzek notation. My question is - is there a way for me to *omit* the "9" in the chord name? My experience is limited just to looking at jazz lead

Re: 13th chord?

2017-02-25 23:08 GMT+01:00 David Kastrup : > Rob Torop writes: > >> When I enter a 13th chord like this e:13, it renders with a 9 as well. >> I know a 13 chord officially contains the 9 and 11, and that lilypond >> by convention will omit the 11. But I don't

Re: 13th chord?

Rob Torop writes: > When I enter a 13th chord like this e:13, it renders with a 9 as well. > I know a 13 chord officially contains the 9 and 11, and that lilypond > by convention will omit the 11. But I don't really want to have the 9 > showing. Do I inadvertently have

Re: Fermata above and below bar line generates warnings

2017-02-25 22:42 GMT+01:00 Knute Snortum : > The following code produces the correct output of fermatas above and below > the bar line, but it also emits warnings. Is there another way to do this > without warnings, or can the warnings be suppressed? I got this code from: > >

Re: Fermata above and below bar line generates warnings

On Sat, Feb 25, 2017 at 4:42 PM, Knute Snortum wrote: > The following code produces the correct output of fermatas above and below > the bar line, but it also emits warnings. Is there another way to do this > without warnings, or can the warnings be suppressed? I got this

Re: Force tuplet number above notes

That works, thanks! --- Knute Snortum (via Gmail) On Sat, Feb 25, 2017 at 1:45 PM, Jeffery Shivers wrote: > On Sat, Feb 25, 2017 at 4:18 PM, Knute Snortum wrote: > > I am trying to get both tuplet numbers above the notes in the following > >

Re: Force tuplet number above notes

On Sat, Feb 25, 2017 at 4:18 PM, Knute Snortum wrote: > I am trying to get both tuplet numbers above the notes in the following > code. I've tried \override TupletNumber.direction = #UP, but evidently this > does not work. What's the correct way to do this? > > \version

Fermata above and below bar line generates warnings

The following code produces the correct output of fermatas above and below the bar line, but it also emits warnings. Is there another way to do this without warnings, or can the warnings be suppressed? I got this code from: http://lsr.di.unimi.it/LSR/Snippet?id=10 \version "2.19.55" \score {

13th chord?

When I enter a 13th chord like this e:13, it renders with a 9 as well. I know a 13 chord officially contains the 9 and 11, and that lilypond by convention will omit the 11. But I don't really want to have the 9 showing. Do I inadvertently have some setting on that is giving me this? [image:

Force tuplet number above notes

I am trying to get both tuplet numbers above the notes in the following code. I've tried \override TupletNumber.direction = #UP, but evidently this does not work. What's the correct way to do this? \version "2.19.55" \language "english" \relative { \omit TupletBracket \override

Re: Making the Dedication field align left

Am 25.02.2017 um 21:02 schrieb Chad Linsley: Hi all, I'm a Lilypond noob and am trying to customize the header. How do I override the "Dedication" so that it aligns left and not centre? The way I understand it you want the dedication field placed on the left of the page, right? For that you

Re: Making the Dedication field align left

On Sat, Feb 25, 2017 at 3:39 PM, Jeffery Shivers wrote: > > Have a look at ... > > http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Creating-titles Oops, I mean: http://lilypond.org/doc/v2.18/Documentation/notation/titles-and-headers -- Jeffery Shivers

Re: Making the Dedication field align left

On Sat, Feb 25, 2017 at 3:02 PM, Chad Linsley wrote: > Hi all, > > I'm a Lilypond noob and am trying to customize the header. How do I override > the "Dedication" so that it aligns left and not centre? Hi Chad, Have a look at ...

Re: UTF-8 in MIDI Lyrics

Joseph Austin: > > From: Karl Hammar > > ... > >> But if we are going to use a "private standard", we might as well > >> imitate the "official" standard and insert something like > >> FF 05 07 { @ U T F 8 } > >> And lobby AMEI/MMA to

Making the Dedication field align left

Hi all, I'm a Lilypond noob and am trying to customize the header. How do I override the "Dedication" so that it aligns left and not centre? C ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Png cropping

Hi, Thank you for your replies. Using a GUI like Frescobaldi is not really something I can do while programming. However, I can surely insert margins to the cropped png, which is definitely what I am going to do. Best regards, Renato ___

Re: Png cropping

Hi Simon, hi David, I am very sorry. I absolutely did not intend to make any sort of accusation. I did word the phrase badly, led by the too impulsive thought that I couldn't believe that LilyPond, even being so powerful, couldn't do what I thought it would be certainly able to do. Actually,

Re: UTF-8 in MIDI Lyrics

> On Feb 25, 2017, at 11:41 AM, lilypond-user-requ...@gnu.org wrote: > > Date: Sat, 25 Feb 2017 17:34:54 +0100 (CET) > From: Karl Hammar > > To: Joseph Austin > > > > And, rp26

Re: cross-voice ties and merging noteheads

Hi all, Am Samstag, den 25. Februar 2017 um 17:41:15 Uhr (+0100) schrieb Urs Liska: > Yes, but I think the issue is solved by now with Andrew's suggestion. it is indeed. Thanks Andrew! Yours, Orm -- Prof. Orm Finnendahl

Re: ghostscript fails on pdf generation

On Sat 25 Feb 2017 at 13:06:02 (+0100), N. Andrew Walsh wrote: > Hi List, > > so, I did some digging regarding this error I've been getting with pdf > output (see below). I found this note to lilypond-users from two years ago: >

Re: Png cropping

On Sat 25 Feb 2017 at 04:01:43 (-0700), renyhp wrote: > Hi, > Thank you for your answers. I am actually programming something automated (a > Telegram bot for LilyPond! If you are on Telegram you will find it at > @lilypondbot), so probably the best option will be to discard using > LilyPond's

Re: UTF-8 in MIDI Lyrics

sorry, last mail wrong from header. Joe Austen: > > Am 24.02.2017 um 02:15 schrieb Joseph Austin: > >> This raises another question. I'm working with MIDI files, > >> and it's not clear how to encode UTF-8 text in MIDI. > >> There must be some convention, but I haven't found an official RP for

Re: Png cropping

> renyhp wrote > > I read in the documentation that it is possible to create a cropped png by > > using "-dbackend=eps -dresolution=600 —png" and inserting this \paper > > block: > > > > However, I think the cropping is too heavy. How can I produce a png with > > some nonzero margins? Have you

Re: cross-voice ties and merging noteheads

Am 25.02.2017 um 17:21 schrieb Phil Holmes: > - Original Message - From: "Orm Finnendahl" > > To: > Sent: Saturday, February 25, 2017 2:45 PM > Subject: Re: cross-voice ties and merging noteheads > > >> Am Samstag, den 25.

Re: UTF-8 in MIDI Lyrics

Joe Austen: > > Am 24.02.2017 um 02:15 schrieb Joseph Austin: > >> This raises another question. I'm working with MIDI files, > >> and it's not clear how to encode UTF-8 text in MIDI. > >> There must be some convention, but I haven't found an official RP for it. ... > I don't have a

Re: cross-voice ties and merging noteheads

- Original Message - From: "Orm Finnendahl" To: Sent: Saturday, February 25, 2017 2:45 PM Subject: Re: cross-voice ties and merging noteheads Am Samstag, den 25. Februar 2017 um 14:25:52 Uhr (+0100) schrieb Urs Liska:

Re: Png cropping

On Sat 25 Feb 2017 at 02:26:53 (-0700), Klaus Blum wrote: > Hi Renato, hi Andrew, > > Andrew Bernard wrote > > why would you use backend = eps if you are generating a PNG file? I think > > you can omit that. > > The auto-cropping features only work with the EPS backend which can also be > used

Re: cross-voice ties and merging noteheads

Am Samstag, den 25. Februar 2017 um 14:25:52 Uhr (+0100) schrieb Urs Liska: > An image would be helpful to avoid misunderstandings. attached. I tried to keep the file size small. Let me know if you need it in better resolution. -- Orm ___

Re: UTF-8 in MIDI Lyrics

> On Feb 24, 2017, at 7:47 AM, lilypond-user-requ...@gnu.org wrote: > > Am 24.02.2017 um 02:15 schrieb Joseph Austin: >> This raises another question. I'm working with MIDI files, >> and it's not clear how to encode UTF-8 text in MIDI. >> There must be some convention, but I haven't found an

Re: Png cropping

renyhp wrote > I read in the documentation that it is possible to create a cropped png by > using "-dbackend=eps -dresolution=600 —png" and inserting this \paper > block: > > However, I think the cropping is too heavy. How can I produce a png with > some nonzero margins? If you use Frescobaldi,

Re: cross-voice ties and merging noteheads

Hi Orm, Use voices. Here's a rough outline answer sketched out quickly, without seeing the publication you refer to. Basically you can only tie across notes in the same voice, so that clues you in as to the way to set such music. Andrew == snip \score { \new Staff \with { tieWaitForNote =

Re: Png cropping

Am 25.02.2017 um 12:01 schrieb renyhp: It is a bit sad, though, that a so powerful tool like LilyPond can't adjust some simple things like png output margins. That’s not the best wording. LilyPond is a very powerful tool, because volunteers have invested their time and abilities to create

Re: cross-voice ties and merging noteheads

Am 25. Februar 2017 13:33:54 MEZ schrieb Orm Finnendahl : >Hi, > > in the example below (an excerpt of the left hand piano part of the >Schumann Song "Mondnacht") I'd like to resemble the rendering of >Clara Schumann's Edition in the Breitkopfärtel

cross-voice ties and merging noteheads

Hi, in the example below (an excerpt of the left hand piano part of the Schumann Song "Mondnacht") I'd like to resemble the rendering of Clara Schumann's Edition in the Breitkopfärtel print. %< \version "2.19.48" \score { \new Staff \with {

Re: ghostscript fails on pdf generation

Hi List, so, I did some digging regarding this error I've been getting with pdf output (see below). I found this note to lilypond-users from two years ago: https://lists.gnu.org/archive/html/lilypond-user/2014-01/msg00932.html The money line is to comment out the last line of

Re: Png cropping

Hi, Thank you for your answers. I am actually programming something automated (a Telegram bot for LilyPond! If you are on Telegram you will find it at @lilypondbot), so probably the best option will be to discard using LilyPond's cropping feature and try to find another way to crop it myself. It

Re: [ANN] LilyQuick 0.9beta - fast accurate Lilypond MIDI note entry for Linux

On Sat, 25 Feb 2017 10:33:11 +1100, Vaughan McAlley wrote: > Maybe your keyboard is interpreting F8 as something else rather than > the function key proper. It seems that lq isn't intercepting keystrokes at all. After uncommenting line 341 nothing is printed: $ sudo

Re: Png cropping

Hi Renato, hi Andrew, Andrew Bernard wrote > why would you use backend = eps if you are generating a PNG file? I think > you can omit that. The auto-cropping features only work with the EPS backend which can also be used to generate PNG or PDF output. Making use of \include