Re: Hungarian Gregorian
Hi Sister Judit,
I finally changed the ornament function (see attached modernGregorian.ily
).
Syntax is easy:
'note' -\tweak extra-offset #'(X .Y) \orn
2015-02-01 10:15 GMT+01:00 Rita Composer ritacompo...@gmail.com:
Another problem of us, taht we use
\language deutsch
which means we have h instead of b
Simply add :
melisma = #(define-music-function (parser location mus)
(ly:music?)
#{
{ \neume { $mus } h }
#})
In your file (or replace it in modernGregorian.ily).
Now it can cause a bit difficulty like this in the attechement.
Another not a big proble, just a bit :-) that when we write a music in A
mayor, outside the melisma we have to write cis
inside a melisma a c. Is it complicated to unite? Either cis or c ?
Yes I know this is anoying but, franckly speaking, not easy to achieve.
I'll thnik about it anyway. ;)
HTH,
Pierre
modernGregorian.ily
Description: Binary data
\version 2.19.15
\include modernGregorian.ily
%\pointAndClickOff
\language deutsch
melisma = #(define-music-function (parser location mus)
(ly:music?)
#{
{ \neume { $mus } h }
#})
\paper {
indent = 0
top-margin = 15
left-margin = 20
right-margin = 20
system-system-spacing = #'((minimum-distance . 16))
}
myMelody = \transpose c c' {
\clef G
\key a\major
\omit Stem
\melisma { e \lst a \sst f e \sst c \melisma { d \lst e } } e
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
\melisma { e \lst g r a \lst h } \melisma { \lst a g f e }
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
\melisma { e \lst a \sst f e \sst c \melisma d \lst e } e
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
e cis d
\bar \break
cis h, \melisma { d \lst f e } \melisma { d \lst e } e
\bar |
e gis a h a gis h a
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar | \break
\melisma { \lst g f e } \melisma { f \lst a }
\melisma { \lst e \sst c } \melisma { \lst d \melisma c } h,
\bar |
\melisma { d \lst f e } \melisma { d \lst e }
e -\tweak extra-offset #'(1.5 . -2) \orn
\melisma { e \lst g r a \lst h } \melisma { \lst a g f e }
\melisma { f \lst a \mst e \sst c \melisma d \lst e } e
\bar |\break
e gis a h a \melisma { \lst g f } e
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
fis a e cis \melisma { \lst d \melisma c \melisma h, d \lst f e }
\bar \break
\melisma { d \lst e } e
\bar |
\melisma { \lst e \sst c \melisma \lst d \melisma c \melisma h, d \lst f e }
\melisma { d \lst e } e
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
\melisma { e \lst g r a \lst h } \melisma { \lst a g f e }
\melisma {
f \lst a \mst e c \melisma \lst d \melisma c
\melisma h, -\tweak extra-offset #'(1 . -2.5) \orn
r r \lst f e f \lst g
}
\melisma { \lst f e }
\bar ||
}
myLyrics = \lyricmode {
\lal San -- ctus,
\lal San -- ctus,
\lal San -- ctus,
Dó -- mi -- nus
De -- us Sá -- ba -- oth.
Ple -- ni sunt cæ -- li et ter -- ra
gló -- ri -- a tu -- a.
Ho -- sán -- na \lal in \lal ex -- \lal cél -- sis.
Be -- ne -- dí -- ctus, qui ve -- nit
in nó -- mi -- ne \lal Dó --
mi -- ni.
\lal Ho -- sán -- na \lal in \lal ex -- \lal cél -- sis.
}
\score {
\cadenzaOn
\new Voice = MyMelody \myMelody
\new Lyrics \lyricsto MyMelody \myLyrics
\layout { }
\header {
piece = \markup {
\fontsize #9 \bold 601
\fontsize #2
\raise #2.3 {
\bold Sanctus
\italic (GrR VI. mise)
}
}
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Displaying scale position beside the note
On 2015-02-01 14:32, and...@andis59.se wrote: I want to display the scale position a long side the note. Ok, I found out that it's called *Scale Degree!* So I found the EZ_numbers_engraver! Case closed! A big thank you for who that created this! // Anders -- English isn't my first language. So any error or strangeness is due to the translation. Please correct my English so that I may become better. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.19.15 slur accidental collision (Paul Scott)
Message: 2
Date: Sat, 31 Jan 2015 13:31:14 -0700
From: Paul Scott waterho...@ultrasw.com
To: lilypond-user@gnu.org
Subject: 2.19.15 slur accidental collision
Message-ID: 20150131203114.GA12158@joy3
Content-Type: text/plain; charset=us-ascii
Hi,
I am trying to make a slur not collide with an accidental. Reading the
Learning Manual I find how to do:
\override Slur.avoid-slur = #'inside
or
\override Accidental.avoid-slur = #'inside
which doesn't seem to do the job.
From the LM and the IR I don't follow how to set a value for
accidental-collision. Using the LyricText example I thought that
\override Slur.accidental-collision = #20
would work but that gets an warning:
warning: cannot find property type-check for `accidental-collision'
(backend-type?). perhaps a typing error?
\version 2.19.15
\relative{
\override Slur.avoid-slur = #'inside
\override Accidental.avoid-slur = #'inside
\override Slur.accidental-collision = #20
\override Accidental.accidental-collision = #20
f'8( bes4)
}
TIA for any help with this,
How about:
\version 2.19.15
\relative{
\shape #'((-1.2 . 2.9) (0 . 2) (0 . 2) (0 . 0)) Slur
f'8( bes4)
}
Paul Scott
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hungarian Gregorian
Oups...
2015-02-01 12:44 GMT+01:00 Pierre Perol-Schneider
pierre.schneider.pa...@gmail.com:
Simply add :
melisma = #(define-music-function (parser location mus)
(ly:music?)
#{
{ \neume { $mus } h }
#})
In your file (or replace it in modernGregorian.ily).
In fact:
melisma = #(define-music-function (parser location mus)
(ly:music?)
#{
{ \neume { $mus } \omit Accidental h }
#})
Cheers,
Pierre
\version 2.19.15
\include modernGregorian.ily
%\pointAndClickOff
\language deutsch
melisma = #(define-music-function (parser location mus)
(ly:music?)
#{
{ \neume { $mus } \omit Accidental h }
#})
\paper {
indent = 0
top-margin = 15
left-margin = 20
right-margin = 20
tagline = ##f
%ragged-right = ##f
%ragged-last = ##t
}
myMelodyModern = \transpose c c' {
\clef G
\key f\major
\omit Stem
\repeat volta 2 {
f f \melisma { g \lst a } a
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
a g \melisma { \lst a g } \melisma { \lst e f }
g \melisma { \lst f e } d d
\hideNotes d
}
}
myMelodyStandard = \transpose c c' {
\clef G
\key f\major
\stemDown
\omit Stem
\repeat volta 2 {
f f \undo\omit Stem g a a
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
\omit Stem a g \undo\omit Stem a \tweak extra-offset #'(2.3 . 0) g
\tweak extra-offset #'(2.3 . 0) e f
\omit Stem g \undo\omit Stem
f \tweak extra-offset #'(2.3 . 0) e \omit Stem d d
\hideNotes d
}
}
myLyrics = \lyricmode {
\override LyricHyphen.minimum-distance = #5
\override LyricSpace.minimum-distance = #5
A -- le -- lu -- ja.
\repeat unfold 2 { a -- le -- lu -- ja. }
}
\markuplist {
\italic Standard notation:
\vspace #1
}
\score {
\cadenzaOn
\new Voice = MyMelody \myMelodyStandard
\new Lyrics \lyricsto MyMelody \myLyrics
\layout {
system-count = 1
\context {
\Lyrics
\override VerticalAxisGroup.staff-affinity = ##f
}
}
\header {
piece = \markup {
\lower #2.7 \fontsize #9 \bold 551
\column {
\bold Alleluja
(ÉE 432)
}
}
}
}
\markuplist {
\italic With 'modernGregorian':
\vspace #1
}
\score {
\cadenzaOn
\new Voice = MyMelody \myMelodyModern
\new Lyrics \lyricsto MyMelody \myLyrics
\layout {
system-count = 1
\context {
\Lyrics
\override VerticalAxisGroup.staff-affinity = ##f
}
}
\header {
piece = \markup {
\lower #2.7 \fontsize #9 \bold 551
\column {
\bold Alleluja
(ÉE 432)
}
}
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hungarian Gregorian
And ragged-right = ##f is ok now.
See new attached files.
Cheers,
Pierre
2015-02-01 14:12 GMT+01:00 Pierre Perol-Schneider
pierre.schneider.pa...@gmail.com:
Oups...
2015-02-01 12:44 GMT+01:00 Pierre Perol-Schneider
pierre.schneider.pa...@gmail.com:
Simply add :
melisma = #(define-music-function (parser location mus)
(ly:music?)
#{
{ \neume { $mus } h }
#})
In your file (or replace it in modernGregorian.ily).
In fact:
melisma = #(define-music-function (parser location mus)
(ly:music?)
#{
{ \neume { $mus } \omit Accidental h }
#})
Cheers,
Pierre
allelujaDeutch.pdf
Description: Adobe PDF document
\version 2.19.15
\include modernGregorian.ily
%\pointAndClickOff
\language deutsch
melisma = #(define-music-function (parser location mus)
(ly:music?)
#{
{ \neume { $mus } \omit Accidental h }
#})
\paper {
indent = 0
top-margin = 15
left-margin = 20
right-margin = 20
tagline = ##f
%ragged-right = ##f
%ragged-last = ##t
}
myMelodyModern = \transpose c c' {
\clef G
\key f\major
\omit Stem
\repeat volta 2 {
f f \melisma { g \lst a } a
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
a g \melisma { \lst a g } \melisma { \lst e f }
g \melisma { \lst f e } d d
\hideNotes d
}
}
myMelodyStandard = \transpose c c' {
\clef G
\key f\major
\stemDown
\omit Stem
\repeat volta 2 {
f f \undo\omit Stem g a a
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
\omit Stem a g \undo\omit Stem a \tweak extra-offset #'(2.3 . 0) g
\once\override Stem.extra-offset = #'(-1.3 . -.5) e f
\omit Stem g \undo\omit Stem
f \tweak extra-offset #'(2.3 . 0) e \omit Stem d d
\hideNotes d
}
}
myLyrics = \lyricmode {
\override LyricHyphen.minimum-distance = #5
\override LyricSpace.minimum-distance = #5
A -- le -- lu -- ja.
\repeat unfold 2 { a -- le -- lu -- ja. }
}
\markuplist {
\italic Standard notation:
\vspace #1
}
\score {
\cadenzaOn
\new Voice = MyMelody \myMelodyStandard
\new Lyrics \lyricsto MyMelody \myLyrics
\layout {
system-count = 1
ragged-right = ##f
\context {
\Lyrics
\override VerticalAxisGroup.staff-affinity = ##f
}
}
\header {
piece = \markup {
\lower #2.7 \fontsize #9 \bold 551
\column {
\bold Alleluja
(ÉE 432)
}
}
}
}
\markuplist {
\italic With 'modernGregorian':
\vspace #1
}
\score {
\cadenzaOn
\new Voice = MyMelody \myMelodyModern
\new Lyrics \lyricsto MyMelody \myLyrics
\layout {
system-count = 1
ragged-right = ##f
\context {
\Lyrics
\override VerticalAxisGroup.staff-affinity = ##f
}
}
\header {
piece = \markup {
\lower #2.7 \fontsize #9 \bold 551
\column {
\bold Alleluja
(ÉE 432)
}
}
}
}
modernGregorian.ily
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Displaying scale position beside the note
I want to display the scale position a long side the note.
Like this, but automatically!
I have tried to search for it, but not finding anything (which probably
is due to my lack of knowing what 'scale position' is called officially)
Is there something in Lilypond or a snippet or do I have to make it myself?
%% Start
\version 2.19.15
\score {
\new Staff {
\key g \major
\set fingeringOrientations = #'(right)
d'-2 a' -5
}
\layout { }
\midi { }
}
%% End
I just discovered that fingeringOrientations only work on chords so I
need something else to show the scale position, Or some tweak...
// Anders
--
English isn't my first language.
So any error or strangeness is due to the translation.
Please correct my English so that I may become better.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hungarian Gregorian
Hi All,
Really great.
Another problem of us, taht we use
\language deutsch
which means we have h instead of b
Now it can cause a bit difficulty like this in the attechement.
Another not a big proble, just a bit :-) that when we write a music in A
mayor, outside the melisma we have to write cis
inside a melisma a c. Is it complicated to unite? Either cis or c ?
Thank you!
Sister Judit
2015-02-01 0:22 GMT+01:00 Pierre Perol-Schneider
pierre.schneider.pa...@gmail.com:
Hi,
2015-01-31 21:15 GMT+01:00 Pierre Perol-Schneider
pierre.schneider.pa...@gmail.com:
2015-01-31 19:38 GMT+01:00 Rita Composer ritacompo...@gmail.com:
What if, we have 2 note with ledgerline in 1 melisma
like here: in Sanctus (after Kyrie)
https://drive.google.com/file/d/0B1x9jbJPH9FkbmN1ZVY3VzdsaEk/view
In the last but one version we could change the space after the c
I attached.
Ok, I'll take a look later on.
It looks fine for me.
See attached file.
However, there's a problem with the last ornament. I'll work on this asap.
Cheers,
Pierre
\version 2.19.15
\include modernGregorian.ily
%\pointAndClickOff
%%??%%
\language deutsch
\paper {
indent = 0
top-margin = 15
left-margin = 20
right-margin = 20
system-system-spacing = #'((minimum-distance . 16))
}
myMelody = \transpose c c' {
\clef G
\key a\major
\omit Stem
\melisma { e \lst a \sst f e \sst c \melisma { d \lst e } } e
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
\melisma { e \lst g r a \lst h } \melisma { \lst a g f e }
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
\melisma { e \lst a \sst f e \sst c \melisma d \lst e } e
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
e cis d
\bar \break
cis h, \melisma { d \lst f e } \melisma { d \lst e } e
\bar |
e gis a h a gis h a
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar | \break
\melisma { \lst g f e } \melisma { f \lst a }
\melisma { \lst e \sst c } \melisma { \lst d \melisma c } h,
\bar |
\melisma { d \lst f e } \melisma { d \lst e } \orn #1.5 e
\melisma { e \lst g r a \lst h } \melisma { \lst a g f e }
\melisma { f \lst a \mst e \sst c \melisma d \lst e } e
\bar |\break
e gis a h a \melisma { \lst g f } e
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
fis a e cis \melisma { \lst d \melisma c \melisma h, d \lst f e }
\bar \break
\melisma { d \lst e } e
\bar |
\melisma { \lst e \sst c \melisma \lst d \melisma c \melisma h, d \lst f e }
\melisma { d \lst e } e
\once\override Staff.BarLine.bar-extent = #'(0 . 2) \bar |
\melisma { e \lst g r a \lst h } \melisma { \lst a g f e }
\melisma { f \lst a \mst e c \melisma \lst d \melisma c \melisma h, r r \lst f e f \lst g }
\melisma { \lst f e }
\bar ||
}
myLyrics = \lyricmode {
\lal San -- ctus,
\lal San -- ctus,
\lal San -- ctus,
Dó -- mi -- nus
De -- us Sá -- ba -- oth.
Ple -- ni sunt cæ -- li et ter -- ra
gló -- ri -- a tu -- a.
Ho -- sán -- na \lal in \lal ex -- \lal cél -- sis.
Be -- ne -- dí -- ctus, qui ve -- nit
in nó -- mi -- ne \lal Dó --
mi -- ni.
\lal Ho -- sán -- na \lal in \lal ex -- \lal cél -- sis.
}
\score {
\cadenzaOn
\new Voice = MyMelody \myMelody
\new Lyrics \lyricsto MyMelody \myLyrics
\layout { }
\header {
piece = \markup {
\fontsize #9 \bold 601
\fontsize #2
\raise #2.3 {
\bold Sanctus
\italic (GrR VI. mise)
}
}
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Naming convention brainstorming
I am no native English speaker. How about “working mode”? Or “crafting mode” – if that has the same artistic/handicraft association that I assume. Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Naming convention brainstorming
I'm talking about the working, thinking and compiling mode when I'm working on the _content_ of a score and not it's final visual appearance. This mode is characterized for example by ... Originally we talked about it as draft mode but this doesn't seem to hit the spot. Nor do devel mode or preview mode. Before work gets published/committed/saved, it is often worked on in a ``sandbox''. Perhaps that term is appropriate. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
voiceOneStyle etc.
Hi,
the voiceOneStyle is defined in ly/property-init.ly.
It only overrides the NoteHead, Stem and Beam.
Is there a particular reason for this?
I wrote my own definitions for a project, including Rests (!), TextScript,
Script, Slur and Tie:
voiceStyleFour = {
\override NoteHead.style = #'harmonic-mixed
\override NoteHead.color = #(x11-color 'OrangeRed)
\override Stem.color = #(x11-color 'OrangeRed)
\override Beam.color = #(x11-color 'OrangeRed)
\override Rest.color = #(x11-color 'OrangeRed)
\override TextScript.color = #(x11-color 'OrangeRed)
\override Script.color = #(x11-color 'OrangeRed)
\override Slur.color = #(x11-color 'OrangeRed)
\override Tie.color = #(x11-color 'OrangeRed)
}
There are more, like Fingerings etc.
Would that be interesting to add to property-init.ly or not?
In addition (separated from the first proposal and clearly more subjective), I
find it rather old-fashioned to use the standard four colours for this (red
green blue magenta). How about a change here?
My personal settings are: firebrick RoyalBlue ForestGreen OrangeRed
for voice 1-4.
Cheers,
Joram
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.19.15 slur accidental collision (Paul Scott)
On 01/02/2015 13:15, Cynthia Karl wrote:
Message: 2
Date: Sat, 31 Jan 2015 13:31:14 -0700
From: Paul Scott waterho...@ultrasw.com
To: lilypond-user@gnu.org
Subject: 2.19.15 slur accidental collision
Message-ID: 20150131203114.GA12158@joy3
Content-Type: text/plain; charset=us-ascii
Hi,
I am trying to make a slur not collide with an accidental. Reading the
Learning Manual I find how to do:
\override Slur.avoid-slur = #'inside
or
\override Accidental.avoid-slur = #'inside
which doesn't seem to do the job.
From the LM and the IR I don't follow how to set a value for
accidental-collision. Using the LyricText example I thought that
\override Slur.accidental-collision = #20
would work but that gets an warning:
warning: cannot find property type-check for `accidental-collision'
(backend-type?). perhaps a typing error?
\version 2.19.15
\relative{
\override Slur.avoid-slur = #'inside
\override Accidental.avoid-slur = #'inside
\override Slur.accidental-collision = #20
\override Accidental.accidental-collision = #20
f'8( bes4)
}
TIA for any help with this,
How about:
\version 2.19.15
\relative{
\shape #'((-1.2 . 2.9) (0 . 2) (0 . 2) (0 . 0)) Slur
f'8( bes4)
}
Surely in this situation the simplest and most attractive option is to
reverse the direction of the slur:
\version 2.19.15
\relative{
f'8_( bes4)
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Emacs mode for files containing lyrics
Jakub Pavlík jkb.pavlik at gmail.com writes:
From the description I don't understand your problem. Why is the lilypond
mode not suitable for you purposes? The example seems to be just a regular
lilypond file ...
Jakub
2015-01-27 16:57 GMT+01:00 Craig Parker-Feldmann lipsticky at
magic.ms:I find it wonderful that some Emacs wizard(s) took the trouble to
write a
LilyPond mode for processing LilyPond files. My own ability in writing Emacs
Lisp, in particular: writing modes using Emacs Lisp, is at a very low level.
If the author(s) of the Emacs LilyPond mode could speak to me, I'd like to
have a special mode for files containing only lyrics.
Currently, if I have a file containing lyrics called min-lyrics.ly,
working on the file looks terrible when font-lock-mode is active.
/-/-/-/-/- min-lyrics.ly -/-/-/-/-/
LyricsSoprano = \lyricmode { When, for each lace bit in a cup, a dozen goats
reach mint family }
/-/-/-/-/- end of min-lyrics.ly -/-/-/-/-/
I looked in the file lilypond-font-lock.el, but the complexity is too much
for me.
___
lilypond-user mailing listlilypond-user at
gnu.orghttps://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user at gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
I wish to add functionality to Emacs. I desire a font-lock mode which does
not consider my minimal example to be musical notes. I am aware of how the
color enhancement applies to my minimal example; that is why I wrote it that
way.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Naming convention brainstorming
Hello Urs If I undestand correctly this is a type of debug mode. If so could it be a debug sub-set such as debug_structure when there is the possiblility of other debug modes. regards Peter Gentry ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: voiceOneStyle etc.
Noeck wrote Sunday, February 01, 2015 4:00 PM
the voiceOneStyle is defined in ly/property-init.ly.
It only overrides the NoteHead, Stem and Beam.
Is there a particular reason for this?
Yes. They were written specifically to support certain examples in the
documentation. Those particular grobs were the only ones used in those
examples.
I wrote my own definitions for a project, including Rests (!), TextScript,
Script, Slur and Tie:
voiceStyleFour = {
\override NoteHead.style = #'harmonic-mixed
\override NoteHead.color = #(x11-color 'OrangeRed)
\override Stem.color = #(x11-color 'OrangeRed)
\override Beam.color = #(x11-color 'OrangeRed)
\override Rest.color = #(x11-color 'OrangeRed)
\override TextScript.color = #(x11-color 'OrangeRed)
\override Script.color = #(x11-color 'OrangeRed)
\override Slur.color = #(x11-color 'OrangeRed)
\override Tie.color = #(x11-color 'OrangeRed)
}
There are more, like Fingerings etc.
Would that be interesting to add to property-init.ly or not?
In addition (separated from the first proposal and clearly more subjective), I
find it rather old-fashioned to use the standard four colours for this (red
green blue magenta). How about a change here?
My personal settings are: firebrick RoyalBlue ForestGreen OrangeRed
for voice 1-4.
Well, possibly, if you think it generally useful. However, if you change
the shape of the note head or the colours you'll have to change all the
text accompanying the examples which use them in the documentation.
And the colours will need to have clear names so the text reads
nicely. Red, Green, Blue are snappy, easily understood by non-English
readers, and clearly distinguished visually. Your suggested colours
might be prettier, but that is not the primary requirement here.
I think the main use is throughout this section
http://www.lilypond.org/doc/v2.19/Documentation/learning/voices-contain-music
but you'll need to do a proper search to be sure there are no more.
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.19.15 slur accidental collision (Paul Scott)
On Mon, Feb 02, 2015 at 06:35:34AM +1100, Nick Payne wrote:
On 01/02/2015 13:15, Cynthia Karl wrote:
Message: 2
Date: Sat, 31 Jan 2015 13:31:14 -0700
From: Paul Scott waterho...@ultrasw.com
To: lilypond-user@gnu.org
Subject: 2.19.15 slur accidental collision
Message-ID: 20150131203114.GA12158@joy3
Content-Type: text/plain; charset=us-ascii
Hi,
I am trying to make a slur not collide with an accidental. Reading the
Learning Manual I find how to do:
\version 2.19.15
\relative{
\shape #'((-1.2 . 2.9) (0 . 2) (0 . 2) (0 . 0)) Slur
f'8( bes4)
}
Surely in this situation the simplest and most attractive option is to
reverse the direction of the slur:
\version 2.19.15
\relative{
f'8_( bes4)
}
After seeing the results of the original answer to my question reversing
the slur direction is what I ended up doing.
I wasn't aware that slur direction could be changed with _ as
articulations can. I used \slurDown and \slurNeutral.
The original that I am making a new part from neatly attached the
beginning of the slur to the top of the flag of the first note.
I wonder if the \shape solution above would have to be recalculated for each
new situation.
Thank you,
Paul
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
set in layout block
Hi,
how can I put a set command in the layout block?
I am asking for the following beamExceptions and in general:
\version 2.18.2
% within the notes:
{
\set Timing.beamExceptions = #'()
a8 b a b
}
% in layout block:
{
a8 b a b
}
\layout{
\context{
\Staff
beamExceptions = #'()
}
}
Is that correct?
It seems to work but where has the ‘Timing’ gone?
How does it know about the Timing?
Is that a general rule, that \set commands have no dot-syntax in the \layout
block but only work with \context { \‘Context’ … } ?
TIA,
Joram
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.19.15 slur accidental collision (Paul Scott)
Paul, Paul Scott-4 wrote I wasn't aware that slur direction could be changed with _ as articulations can. I used \slurDown and \slurNeutral. Yes! You can also force the direction for beams (^[ and _[), ties, phrasing slurs, dynamics, text, markups, etc. Can't say I've tried it on everything, but those definitely work. Using \once \slurDown is basically the same as _(. The same philosophy applies to the other grobs. Paul Scott-4 wrote I wonder if the \shape solution above would have to be recalculated for each new situation. Well, the \shape command basically assigns a set of four extra-offset value-pairs for each control point in each curve (I say curve since it can be used for ties, slurs, and phrasing slurs, and each curve because it can be used for broken curves, or those that cross multiple systems). Using the same values over and over again is, therefore, not advisable since most curves that LilyPond ends up choosing are not shaped alike (since it is at this point the extra-offset value-pairs are applied). Therefore, if the \shape command is necessary, the value-pairs will need to be customized for each curve you desire to tweak. Happy Engraving, Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Re-2-19-15-slur-accidental-collision-Paul-Scott-tp171322p171336.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
