Re: Problem compiling: music-functions-init.ly

2018-11-13 Thread Urs Liska
Am 14. November 2018 05:53:07 MEZ schrieb Keizen Li Qian : >Hello again, I did a clean install of 2.18.2 in Ubuntu and am getting >the >error below when I compile. I checked the script against the >sourceforge >files and was wondering if anyone has any suggestions for compiling. I >would

Problem compiling: music-functions-init.ly

2018-11-13 Thread Keizen Li Qian
Hello again, I did a clean install of 2.18.2 in Ubuntu and am getting the error below when I compile. I checked the script against the sourceforge files and was wondering if anyone has any suggestions for compiling. I would appreciate detailed instructions. Thank you in advance! $ lilypond

Re: advice on orchestral parts and string Divisi

2018-11-13 Thread Xavier Scheuer
Hello, I use VerticalAxisGroup.remove-layer as described in input/regression/divisi-staves.ly http://lilypond.org/doc/v2.19/input/regression/a6/lily-436997bb.ly See more info on the bug tracker of issue 3518. https://code.google.com/archive/p/lilypond/issues/3518 Works very well but

Re: [ANN] LilyQuick 0.95beta - Quick note Lilypond entry using MIDI for Linux

2018-11-13 Thread Vaughan McAlley
On Wed, 19 Sep 2018 at 14:26, Chad Linsley wrote: > +1 for a cross-platform of LilyQuick! > > In fact, would there be any interest in including it in Denemo or > Frescobaldi? It’s absolutely brilliant and I would love to start using it > (Mac user). > > On Sun, Aug 13, 2017 at 11:43 PM Vaughan

Re: Edition Engraver in 2.19

2018-11-13 Thread Kieren MacMillan
Hi Reggie, > I was hoping EE could allow me to create full score and parts > with tweaks easy versus tags system. That is absolutely one of its strengths. > When you say learn by looking at examples what examples > only two usage examples ly files to go by? A couple of examples privately

Re: advice on orchestral parts and string Divisi

2018-11-13 Thread Reggie
Sorry is there a problem with Google translate please my apologies I fixed it now from now on. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org

Re: advice on orchestral parts and string Divisi

2018-11-13 Thread Reggie
Reggie wrote > Reggie wrote >> For those of you who engrave orchestral music in which the strings often >> have >> your typical divisi a2 or a3 >> >> Suppose a performance is coming up and you need to print parts from the >> full >> score. >> >> So when you go to engrave the individual parts for

Re: advice on orchestral parts and string Divisi

2018-11-13 Thread Reggie
Reggie wrote > For those of you who engrave orchestral music in which the strings often > have > your typical divisi a2 or a3 > > Suppose a performance is coming up and you need to print parts from the > full > score. > > So when you go to engrave the individual parts for any of the strings for

Re: Mapping pitches to other pitches when generating MIDI files for percussion?

2018-11-13 Thread Wolfling Vini
Hi Aaron, Thank you for replying. This could really help. I'm going to look at it when I get home, but what I can tell you right now is that I've experimented with making a custom pitch name language file — not remotely resembling your solution — and I came across one big problem: it was a

Re: Mapping pitches to other pitches when generating MIDI files for percussion?

2018-11-13 Thread Aaron Hill
On 2018-11-13 1:16 pm, Wolfling Vini wrote: This is only a problem because most of our pieces have one or two staves for flutes. So I have to keep the custom pitch names local; otherwise, every time I need to play a b, if I'm not mistaken, I'd need to type "trh" instead of "b" or "si".

Re: Edition Engraver in 2.19

2018-11-13 Thread Reggie
Kieren MacMillan wrote > Hi Reggie, > >> Can you show what exactly must be downloaded for working? > > 1. I’ve downloaded the following repositories: breaks, edition-engraver, > notation-fonts, ill-core, page-layout, and snippets. You may not need all > of them right away — but you’ll probably

Re: staff order

2018-11-13 Thread Noeck
Dear Sean, the Staff needs to start with a capital S: \new Staff LilyPond is case-sensitive. That’s all. Two other points: 1. You have some arbitrarily placed braces. I’d suggest to use them only where they are needed. 2. Are you really using LilyPond 2.14? That’s really old. I’d suggest to

Re: Edition Engraver in 2.19

2018-11-13 Thread Kieren MacMillan
Hi Reggie, > Can you show what exactly must be downloaded for working? 1. I’ve downloaded the following repositories: breaks, edition-engraver, notation-fonts, ill-core, page-layout, and snippets. You may not need all of them right away — but you’ll probably want all of them eventually, so why

Re: Edition Engraver in 2.19

2018-11-13 Thread Reggie
Kieren MacMillan wrote > Hi Reggie, > >> How do you install engraver from stage one? > > \include "oll-core/package.ily" > \loadPackage edition-engraver > > Works great for me. Are you sure you’ve got all the necessary files > downloaded (including oll-core), and placed correctly in your search

Re: Edition Engraver in 2.19

2018-11-13 Thread Kieren MacMillan
Hi Reggie, > How do you install engraver from stage one? \include "oll-core/package.ily" \loadPackage edition-engraver Works great for me. Are you sure you’ve got all the necessary files downloaded (including oll-core), and placed correctly in your search path? Cheers, Kieren.

Re: Edition Engraver in 2.19

2018-11-13 Thread Reggie
Jan-Peter Voigt wrote > Hi all, > > just a few hours away ... ;-) > Kieren already mentioned, the edition engraver is an external library. > It is part of my own toolchain, but once made its way into public, > because it fitted a question/a use case of Kieren. So I started to make > it available.

Re: Configuring home/bin PATH directory

2018-11-13 Thread Keizen Li Qian
That worked! Thanks for walking me through it. Keizen they/them On Tue, Nov 13, 2018 at 6:38 AM David Bowen wrote: > Keizen, > >Having the ${PATH}: at the beginning defeats the whole point of the > change. The directories in the PATH will be searched in the order they > occur. So putting

Re: Edition Engraver in 2.19

2018-11-13 Thread Kieren MacMillan
Hi Martin, > I guess the question is: How complex a LilyPonds score has to be before EE > really starts making things easier instead of just adding more difficulties? Excluding MWEs for this list, I would say I use the EE on >95% of the scores I engrave — even in (e.g.) a lead sheet (i.e., one

Re: staff order

2018-11-13 Thread Carl Sorensen
From: sean read Date: Tuesday, November 13, 2018 at 2:45 AM To: Subject: staff order I'm trying to make my first multi staff lilypond file and finding that I can't figure out how to control the order of the staves. When I use \version "2.14.1" \score { \new StaffGroup << \new staff { \key

Re: staff order

2018-11-13 Thread Pierre Perol-Schneider
Hi Sean, You have to write "\New Staff" instead of "\New staff": \score { \new StaffGroup << \new Staff { \key ees \major g''2 f8 g8~ | } \new Staff { \key ees \major aes'8 ees'8 c'2 | } >> } \score { \new StaffGroup << \new Staff { \key ees \major

Re: staff order

2018-11-13 Thread Ralph Palmer
On Tue, Nov 13, 2018 at 9:29 AM sean read wrote: > I'm trying to make my first multi staff lilypond file and finding that I > can't figure out how to control the order of the staves. When I use > > > \version "2.14.1" > \score { > \new StaffGroup << > \new staff { > \key ees \major g''2 f8 g8~ |

staff order

2018-11-13 Thread sean read
I'm trying to make my first multi staff lilypond file and finding that I can't figure out how to control the order of the staves. When I use \version "2.14.1" \header { title = "Wedding song" composer = "Ari Hoenig" } \score { \new StaffGroup << \new staff { \time 3/4 {\key ees \major g''2

staff order

2018-11-13 Thread sean read
I'm trying to make my first multi staff lilypond file and finding that I can't figure out how to control the order of the staves. When I use \version "2.14.1" \score { \new StaffGroup << \new staff { \key ees \major g''2 f8 g8~ | } \new staff { \key ees \major aes'8 ees'8 c'2 | } >> } The

staff order

2018-11-13 Thread sean read
I'm trying to make my first multi staff lilypond file and finding that I can't figure out how to control the order of the staves. When I use \version "2.14.1" \score { \new StaffGroup << \new staff { \time 3/4 {\key ees \major g''2 f8 g8~ | } } \new staff { {\key ees \major aes'8 ees'8 c'2 |

Edition Engraver in 2.19

2018-11-13 Thread Jan-Peter Voigt
Hi all, just a few hours away ... ;-) Kieren already mentioned, the edition engraver is an external library. It is part of my own toolchain, but once made its way into public, because it fitted a question/a use case of Kieren. So I started to make it available. Now there came Urs' OpenLilyLib

Re: Configuring home/bin PATH directory

2018-11-13 Thread Urs Liska
Am 13.11.18 um 10:08 schrieb J Martin Rushton: On 13/11/18 08:31, Martin Tarenskeen wrote: On Mon, 12 Nov 2018, Keizen Li Qian wrote: Hello, I installed 2.18.2 on a drive with a partitioned home directory which had an old ~home/bin/lilypond. Somewhere the path had been set to this

Re: Configuring home/bin PATH directory

2018-11-13 Thread J Martin Rushton
On 13/11/18 08:31, Martin Tarenskeen wrote: > > > On Mon, 12 Nov 2018, Keizen Li Qian wrote: > >> Hello,  >> >> I installed 2.18.2 on a drive with a partitioned home directory which >> had an old ~home/bin/lilypond. Somewhere the path had been set to this >> directory so even after convert-ly

Re: Edition Engraver in 2.19

2018-11-13 Thread Urs Liska
Hi Marten, Am 13.11.18 um 08:30 schrieb m.tarensk...@zonnet.nl: Hi, I, like the original poster, was also intrigued, by people's enthusiastic comments about the power of OpenLilyLib and the Edition Engraver. And like the O.P. I never really got started. I guess the question is: How complex a

Re: Configuring home/bin PATH directory

2018-11-13 Thread Martin Tarenskeen
On Mon, 12 Nov 2018, Keizen Li Qian wrote: Hello,  I installed 2.18.2 on a drive with a partitioned home directory which had an old ~home/bin/lilypond. Somewhere the path had been set to this directory so even after convert-ly successfully converted my old files to 2.18, running lilypond