Re: simplifying chromatic scale notation

On 2016-01-25 21:35, Paul Morris wrote: On Jan 25, 2016, at 4:19 PM, musicus wrote: See attached. Comments, suggestions are very welcome ;) Hi musicus, I think you’re right that standard notation is not as good as it could be for such chromatic music, and you have an interesting approach for

Re: Compiling a file results in message: Exited with return code -1073741819.

HI Joe, Compiles fine on 2.19.35 on openSUSE Leap 42.1 (Linux). Extra notes work. Have you tried running with a higher revision of lilypond? [The development releases after 2.18.2 are of very high quality, in general.] What platform are you on? Andrew ___

Re: simplifying chromatic scale notation

> On Jan 25, 2016, at 4:19 PM, musicus wrote: > > See attached. Comments, suggestions are very welcome ;) Hi musicus, I think you’re right that standard notation is not as good as it could be for such chromatic music, and you have an interesting approach for improving it. I agree with what

Re: Henle app

Hi Boris, The Henle app is done by Touchpress, a software house, not an engraving firm. I would hazard a guess that the sizing is handled by rendering SVG – the whole point of which is that is is scalable and resizeable – output from whatever engraving program Henle uses. I doubt that the app i

Re[2]: simplifying chromatic scale notation

I suggest you try this on "Entry of the Gladiators" by Fučik. The lines will look very straightforward, but I suspect performers, particularly on "continuous" instruments like voice, theremin or trombone(?) would lose track of the tonality exactly because of that. -- David Kastrup Maybe the

Re: Subject: Compiling a file results in message: Exited with return code -1073741819

;001901d157cd$1a7a2620$4f6e7260$@verizon.net> Content-Type: text/plain; charset="us-ascii" Please see the attached file. Go to line 253. The file compiles cleanly up until this point. However, when I try to add more than one note to the line 253, I receive the error me

Re: simplifying chromatic scale notation

musicus writes: > @Simon: I was not aware of Clairnote, but that direction was not my > intention... > > @Kieren: I agree with you regarding reading... > my point is that this notation could help to understand and remember > the structure. > Especially in modern/ contemporary music there are many

Re: simplifying chromatic scale notation

Kieren MacMillan writes: > Hi musicus, > > This may just be the result of forty years of performing and composing > in the Western notation system (it’s always hard to overcome that kind > of inertia)… but I find it easier to read the standard notation than > your suggested alternative. For "Wes

Re: Compiling a file results in message: Exited with return code -1073741819.

Hi Joseph, Try to googlize "Exited with return code -1073741819" Some interesting things over there. HTH, Pierre 2016-01-26 1:08 GMT+01:00 Urs Liska : > > > Am 26.01.2016 um 01:04 schrieb Joseph N. Srednicki: > > Please see the attached file. > > > > Go to line 253. > > > > The file compiles cl

Re: Compiling a file results in message: Exited with return code -1073741819.

Am 26.01.2016 um 01:04 schrieb Joseph N. Srednicki: > > Please see the attached file. > > > > Go to line 253. > > > > The file compiles cleanly up until this point. > > > > However, when I try to add more than one note to the line 253, I > receive the error message: *Exited with return code

Compiling a file results in message: Exited with return code -1073741819.

Please see the attached file. Go to line 253. The file compiles cleanly up until this point. However, when I try to add more than one note to the line 253, I receive the error message: Exited with return code -1073741819. Please let me know if I am doing something wrong or if there

Re: simplifying chromatic scale notation

Am 26.01.2016 um 00:05 schrieb musicus: > @Simon: I was not aware of Clairnote, but that direction was not my > intention... > > @Kieren: I agree with you regarding reading... > my point is that this notation could help to understand and remember > the structure. > Especially in modern/ contempor

Re: Determining what parameters exist for an item

2016-01-25 21:00 GMT+01:00 David Nalesnik : > > > On Mon, Jan 25, 2016 at 1:47 PM, Kieren MacMillan > wrote: >> >> Hi Harm, >> >> > if a property is settable, this does not mean your setting takes any >> > effect. >> > I don't speak of user-errors in syntax, missing context, etc, but >> > sometime

Re: Henle app

Am 25.01.2016 um 23:11 schrieb Boris Lau: > Any idea what they use for engraving? Given the features for changing > staff sizes as well as individual note and fingerings, it's probably > done on-the-fly... I know that for their printed editions they use quite diverse tools: Sibelius, (I think Fi

Re: Henle app

Any idea what they use for engraving? Given the features for changing staff sizes as well as individual note and fingerings, it's probably done on-the-fly... Best, Boris On 25/01/16 22:49, Kieren MacMillan wrote: http://www.henle.de/blog/en/2016/01/25/%E2%80%9Chenle-library%E2%80%9D-app-redef

Henle app

http://www.henle.de/blog/en/2016/01/25/%E2%80%9Chenle-library%E2%80%9D-app-redefining-sheet-music/ Just an FYI, for those who didn’t see it. Cheers, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info __

Re: simplifying chromatic scale notation

Hi musicus, This may just be the result of forty years of performing and composing in the Western notation system (it’s always hard to overcome that kind of inertia)… but I find it easier to read the standard notation than your suggested alternative. Best, Kieren. _

Re: simplifying chromatic scale notation

On 25.01.2016 22:19, musicus wrote: I just struggled with studying a complex music piece and thought that all the chromatic lines are horrible to read in standard notation. Especially the "enharmonic problem" is distracting the musician from a very simple musical structure. So I tried some of m

simplifying chromatic scale notation

Dear Lilyponders, I just struggled with studying a complex music piece and thought that all the chromatic lines are horrible to read in standard notation. Especially the "enharmonic problem" is distracting the musician from a very simple musical structure. So I tried some of my ideas and can

Re: Square note head style

Hi Caio, How about: \version "2.18.2" #(define (my-note-head grob) (let ((duration (ly:grob-property grob 'duration-log))) (if (>= duration 2) (grob-interpret-markup grob #{ \markup \filled-box #'(-0.5 . 0.5) #'(-0.5 . 0.5) #0 #})

Hello I'm a new member of this list.

Hello everybody: I', a new member of this list. I'd like use a lilypond on latext. I don't speak spanish, but i realize my best effort to explain me and read the messages from list. Thanks Debianermx ___ lilypond-user mailing list lilypond-user@gnu.or

Re: Font of accidentals changes after line break

Am 25. Januar 2016 21:20:38 MEZ, schrieb Robert Schmaus : >Unfortunately, it doesn't work ... LP v2.19.34 exits ungracefully with >an error message "fatal error: cannot find font: `LilyJAZZ-11'" > >Well, the font is there, as the output of >lilypond -dshow-available-fonts x >shows. This shows t

Re: Font of accidentals changes after line break

Am 25.01.2016 um 21:20 schrieb Robert Schmaus: > Unfortunately, it doesn't work ... LP v2.19.34 exits ungracefully with > an error message "fatal error: cannot find font: `LilyJAZZ-11'" > > Well, the font is there Where exactly? LilyPond looks only at the directory where Emmentaler/Feta is loca

Re: Font of accidentals changes after line break

Unfortunately, it doesn't work ... LP v2.19.34 exits ungracefully with an error message "fatal error: cannot find font: `LilyJAZZ-11'" Well, the font is there, as the output of lilypond -dshow-available-fonts x shows. I'll just stick to the old \include method after all, and try to get rid of

Square note head style

Hi, I'm needing a note head style with square note heads. Ideally it should be filled for black note heads and open for white notes. I'm struggling to understand how to change the note head stencil, let alone change it according to note duration. Con someone, please, help? Thanks! Caio

Re: Determining what parameters exist for an item

On Mon, Jan 25, 2016 at 1:47 PM, Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi Harm, > > > if a property is settable, this does not mean your setting takes any > effect. > > I don't speak of user-errors in syntax, missing context, etc, but > > sometimes an engraver does not listen

Re: Determining what parameters exist for an item

Hi Harm, > if a property is settable, this does not mean your setting takes any effect. > I don't speak of user-errors in syntax, missing context, etc, but > sometimes an engraver does not listen to a certain property, maybe > because it's hard-coded or not really needed or for other good reasons.

Re: Remove system separator

Many thanks Abraham. That helps perfectly. ~Pierre 2016-01-25 19:50 GMT+01:00 tisimst : > Pierre, > > On Mon, Jan 25, 2016 at 8:31 AM, Schneidy [via Lilypond] <[hidden email] > > wrote: > >> Hi All, >> >> I need to typeset an orchestral piece

Re: Determining what parameters exist for an item

On 25.01.2016 10:19, David Kastrup wrote: e.g. ‘Offset KeyCancellation’s X-extent by #'(0 . 2) (so it will have >two units whitespace at the right), regardless of how wide it would >normally be’. That would be a very powerful use case for \offset, if >also the technical limitations might be non-t

Re: Remove system separator

Pierre, On Mon, Jan 25, 2016 at 8:31 AM, Schneidy [via Lilypond] < ml-node+s1069038n186401...@n5.nabble.com> wrote: > Hi All, > > I need to typeset an orchestral piece showing system separators together > with solo scores without the system separator. > Any idea ? > > %% Snippet: %% > \ve

Remove system separator

Hi All, I need to typeset an orchestral piece showing system separators together with solo scores without the system separator. Any idea ? %% Snippet: %% \version "2.19.35" #(set-default-paper-size "a6landscape") instruOne = \new Staff { \set Staff.instrumentName = "Inst. 1" \repeat

Re: \offset documentation

David Sumbler writes: > Yes, I now see that it is indexed as "offset", with a link to "A.19 > Available music functions", but it is not indexed as "\offset". Other > music functions are indexed both with and without the preceding > back-slash. > > I had looked for "\offset" in the section of the

Re: \offset documentation (was: Determining what parameters exist for an item)

On Mon, 2016-01-25 at 11:57 +0100, David Kastrup wrote: > David Sumbler writes: > > > On Mon, 2016-01-25 at 10:26 +0100, David Kastrup wrote: > >> David Sumbler writes: > >> > >> >> From: David Nalesnik > >> > > >> > > >> >> \offset only works on properties that have a default value listed in

\offset documentation (was: Determining what parameters exist for an item)

David Sumbler writes: > On Mon, 2016-01-25 at 10:26 +0100, David Kastrup wrote: >> David Sumbler writes: >> >> >> From: David Nalesnik >> > >> > >> >> \offset only works on properties that have a default value listed in >> >> the grob pages in the IR (derived from the alist in >> >> scm/defin

Hairpin offset when broken

I am trying to offset a hairpin that is broken across lines. It appears that only the second part is affected. What’s wrong here? Andrew — snip \version "2.19.35" treble = { \clef treble \time 4/4 c'' c'' c'' c'' c'' c'' c'' c'' \break c'' c'' c'' c'' } bass = { \clef bass \time

Re: Font of accidentals changes after line break

Hi Malte, Thanks for the reply! That sounds very good, actually - I'll give it a try tonight. Best, Robert > On 25 Jan 2016, at 10:21, Malte Meyn wrote: > > > >> Am 25.01.2016 um 10:00 schrieb Robert Schmaus: >> >> One more thought: My original approach of simply \include-ing LilyJAZZ

Re: Determining what parameters exist for an item

On Mon, 2016-01-25 at 10:26 +0100, David Kastrup wrote: > David Sumbler writes: > > >> From: David Nalesnik > > > > > >> \offset only works on properties that have a default value listed in > >> the grob pages in the IR (derived from the alist in > >> scm/define-grobs.scm). There is no default

Re: lilypond-user Digest, Vol 158, Issue 140

David Sumbler writes: >> From: David Nalesnik > > >> \offset only works on properties that have a default value listed in >> the grob pages in the IR (derived from the alist in >> scm/define-grobs.scm). There is no default value listed for >> KeyCancellation.X-extent, hence the warning. > > >

Re: Font of accidentals changes after line break

Am 25.01.2016 um 10:00 schrieb Robert Schmaus: > > One more thought: My original approach of simply \include-ing LilyJAZZ should > be the standard way of using it. Which makes me think, that there's either > something missing in LilyJAZZ to work in v2.19 ... or a bug in Lilypond. Since versi

Re: Determining what parameters exist for an item

Simon Albrecht writes: > On 25.01.2016 00:55, David Nalesnik wrote: >> >> \offset only works on properties that have a default value listed in >> the grob pages in the IR (derived from the alist in >> scm/define-grobs.scm). There is no default value listed for >> KeyCancellation.X-extent, hence

Re: Font of accidentals changes after line break

Am 25.01.2016 um 10:00 schrieb Robert Schmaus: > One more thought: My original approach of simply \include-ing LilyJAZZ should > be the standard way of using it. Which makes me think, that there's either > something missing in LilyJAZZ to work in v2.19 ... or a bug in Lilypond. > Shouldn't I n

Re: lilypond-user Digest, Vol 158, Issue 140

2016-01-25 9:40 GMT+01:00 David Sumbler : >> From: David Nalesnik > > >> \offset only works on properties that have a default value listed in >> the grob pages in the IR (derived from the alist in >> scm/define-grobs.scm). There is no default value listed for >> KeyCancellation.X-extent, hence t

Re: lilypond-user Digest, Vol 158, Issue 140

On 25.01.2016 09:40, David Sumbler wrote: This "\offset" sounds very interesting. But I can find nothing about it in the documentation. It isn't indexed in any of the Lilypond manuals. Is it work in progress, added in a later version than my 2.19.30? No, it’s a 2.19 addition, but older than

Re: Determining what parameters exist for an item

On 25.01.2016 00:55, David Nalesnik wrote: \offset only works on properties that have a default value listed in the grob pages in the IR (derived from the alist in scm/define-grobs.scm). There is no default value listed for KeyCancellation.X-extent, hence the warning. Well, the point was t

Re: Font of accidentals changes after line break

One more thought: My original approach of simply \include-ing LilyJAZZ should be the standard way of using it. Which makes me think, that there's either something missing in LilyJAZZ to work in v2.19 ... or a bug in Lilypond. Shouldn't I notify the bug team of this and if so, how do I do that?

Re: lilypond-user Digest, Vol 158, Issue 140

> From: David Nalesnik > \offset only works on properties that have a default value listed in > the grob pages in the IR (derived from the alist in > scm/define-grobs.scm). There is no default value listed for > KeyCancellation.X-extent, hence the warning. This "\offset" sounds very interesti