Re: \articulate command and rit. was: Re: lilypond-user Digest, Vol 147, Issue 102
Speaking only for myself:
I regard LilyPond as a music-_typesetting_-program.
I don't care much about midi.
Nevertheless, the NR clearly states:
A MIDI file is a series of notes in a number of tracks. It is not an
actual sound file [...]
Pieces of music can be converted to MIDI files, so you can listen to
what was entered. This is convenient for checking the music; octaves
that are off or accidentals that were mistyped [...]
And that's the best one can say about midi. Any simple midi from
computer generated music sounds terrible. It has _nothing_ to do with
music.
The articulate-script tries to improve the simple midi, but is not
very mature yet, imho.
2015-02-14 22:34 GMT+01:00 Cynthia Karl pck...@mac.com:
Message: 5
Date: Sat, 14 Feb 2015 20:20:37 +0100
From: Thomas Morley thomasmorle...@gmail.com
To: Patrick Karl patrickk...@me.com
Cc: lilypond-user lilypond-user@gnu.org
Subject: Re: lilypond-user Digest, Vol 137, Issue 62
Message-ID:
cabsfgywvb0td_yi6tkg-_tkndlcocqxpxj8mgek0fdcqa+5...@mail.gmail.com
Content-Type: text/plain; charset=UTF-8
2015-02-14 18:18 GMT+01:00 Patrick Karl patrickk...@me.com:
I have run into a couple of anomalies with the \articulate command and the
abbreviation rit.
First,
\version 2.19.15
\include articulate.ly
\score{
\unfoldRepeats \articulate
^^
\new ChoirStaff
\new Staff c-rit.
\new Staff c-rit.
\layout { }
\midi { }
}
throws a warning: warning: Two simultaneous tempo-change events,
junking this one
warning: Previous tempo-change event here
If rit. is replaced with \markup { rit. }, no warning is thrown.
Section 1.8.1 Writing text pretty much implies that those two ways of
generating text are equivalent.
I don't think this warning should occur. Isn't it a common thing to place
such a notation in all staves so that if parts are generated, each part
will have the notation.
http://www.lilypond.org/doc/v2.18/Documentation/notation/repeats-in-midi
When creating a score file using \unfoldRepeats for MIDI, it is
necessary to make two \score blocks: one for MIDI (with unfolded
repeats) and one for notation (with volta, tremolo, and percent
repeats). For example,
\score {
?music?
\layout { ? }
}
\score {
\unfoldRepeats ?music?
\midi { ? }
}
Yes, I knew that. But I didn't think it was necessary if my music didn't
contain any \repeat volta's. Is that wrong?
In a certain way, yes.
\articulate needs the \unfoldRepeats-command to work with all coded cases.
The NR says (in my wording): if \unfoldRepeats is used, _always_ use two scores.
I'd recommend to use two score every time for \layout and \midi.
(Apart from most simple use-cases)
Do you think that doing the midi in a separate score will cure the rit.
problem? I tried it, it doesn't.
It cures the warning triggered by \layout.
The midi will be build as the articulate-script does. This might not
result in convincing output.
Though, have a look _in_ articulate.ly and view the (long) TODO-list
on top of it.
Maybe you can answer a question about \articulate: if I generate a pdf file
for the score containing the \midi block, why doesn't the pdf file reflect
what is in the midi file? For example, the pdf file generated by my original
snippet shows a time signature of 4/4, but each measure actually contains 8
quarter-note beats.
The articulate-script heavily changes the entered music and therefore
the visual output by scaling durations, inserting (scaled) rests and
spacers and the like.
If you generate a pdf from this changed music you will see strange things.
Here two examples, with and without \articulate only regarding the
printed output.
Example 1
\version 2.19.15
m = { \time 2/4 c''4-. c''-! }
\score {
\displayMusic \m
}
returns:
(make-music
'SequentialMusic
'elements
(list (make-music
'TimeSignatureMusic
'beat-structure
'()
'denominator
4
'numerator
2)
(make-music
'NoteEvent
'articulations
(list (make-music
'ArticulationEvent
'midi-extra-velocity
4
'midi-length
#procedure #f (len context)
'articulation-type
staccato))
'duration
(ly:make-duration 2)
'pitch
(ly:make-pitch 1 0))
(make-music
'NoteEvent
'articulations
(list (make-music
'ArticulationEvent
'midi-extra-velocity
6
'midi-length
#procedure #f (len context)
'articulation-type
staccatissimo))
'duration
(ly:make-duration 2)
'pitch
(ly:make-pitch 1 0
In short, you see some notes with
Re: [Announce] Boulez anyone?
2015-02-13 21:38 GMT+01:00 Thomas Morley thomasmorle...@gmail.com: 2015-02-13 12:15 GMT+01:00 Noeck noeck.marb...@gmx.de: Thanks a lot Abraham, it is just great to see all these styles. You know that, but for all who don't: straight flags and other flag styles can also be easily set in LilyPond for fonts that support it like the default font: http://www.lilypond.org/doc/v2.19/Documentation/snippets/rhythms#rhythms-using-alternative-flag-styles Cheers, Joram This snippet should demonstrate flat-flags as well. I have to blame - myself: commit baa9a1f25594917e9817aba61585a1a9caeeb217 Author: Thomas Morley thomasmorle...@gmail.com Date: Wed Oct 2 23:31:50 2013 +0200 Making flat flags available Issue 3591 The markup-command 'note-ny-number' and the relvant regression- tests are extended, too. The sippet 'using-alternative-flag-styles.ly' from Documentation/snippets/new/ isn't changed for now, will be tackled in a follow up. ^ I completely forgot it. Will do asap. hopefully... Cheers, Harm I changed the the snippet in LSR. It will show up after next LSR-import. Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lengthening broken ties
Hi Werner,
On Sun, Feb 15, 2015 at 8:09 AM, Werner LEMBERG w...@gnu.org wrote:
If it's convenient, have a look at the attached patch/sketch. It
adds a property, minimum-length-left-broken, which lets you adjust
broken bits that start a line.
Excellent! What an improvement with just a few lines of code!
Thanks a lot.
Now that the change is in the repository, I've recompiled lilypond to
try it out with real-world code. Unfortunately, it doesn't work as
expected. Consider this snippet (together with the attached image).
\paper {
line-width = 50\mm
}
\relative c'' {
bes des e g1 ~ \break q \break
\once\override Tie.minimum-length-after-break = 10
bes des e g1 ~ \break q \break
\time 4/4 bes des e g1 ~ \break \time 3/4 q2. \break
\once\override Tie.minimum-length-after-break = 10
\time 4/4 bes des e g1 ~ \break \time 3/4 q2. \break
}
In bar 2 you can see the effect of `minimum-length-after-break'.
You mean bar 4--bar 2 is the default.
However, in bar 8, nothing changes! Value 10 is obviously too small
to get an effect if the line starts with a time signature – it seems
that the horizontal space of the time signature must be taken into
account also.
Any chance to fix this? BTW, if you compare bar 2 with bar 6, you see
exactly the opposite effect w.r.t. the default tie length: with a time
signature the tie looks OK but without it is far too short...
If you change 'minimum-length-after-break to 'minimum-length, you'll get
exactly the same result with the second half of each tied chord. This
isn't a problem with the patch, as I changed nothing relating to the
reference points from which the distances are reckoned.
From your analysis it appear that LilyPond is taking the entire
NonMusicalPaperColumn into account rather than just the right extent. I'll
have a look. (This could be major!)
--David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cue notes with lyrics?
On 02/14/2015 02:48 PM, Thomas Morley wrote:
2015-02-14 13:27 GMT+01:00 Rutger Hofman rut...@cs.vu.nl:
Good morning list,
I would like to create cue notes with lyrics. I added lyric-event to the
Score.quotedCueEventTypes but that gave me no lyrics. How should I go about
this?
Thanks,
Rutger Hofman
Amsterdam
Hi,
best I can currently think of is the code below.
Though, there is a _big_ drawback with it: You have to specify the
durations of the lyrics. Using \lyricsto will not work, as far as I
can tell.
\version 2.18.2
cueLyr =
#(define-music-function
(parser location what main-music) (string? ly:music?)
(_i Insert contents of quote @var{what} corresponding to @var{main-music},
in Lyrics oriented by @var{dir}.)
(make-music 'QuoteMusic
'element main-music
'quoted-context-type 'CueLyrics
'quoted-context-id cue-lyr
'quoted-music-name what
))
\layout {
\context {
\Score
\accepts CueLyrics
quotedCueEventTypes =
#'(note-event rest-event tie-event
beam-event tuplet-span-event
dynamic-event slur-event lyric-event)
}
%% maybe other contexts have to accept CueLyrics as well!
\context {
\ChoirStaff
\accepts CueLyrics
}
\context{
\Lyrics
\name CueLyrics
\alias Lyrics
fontSize = #-4
}
}
oboeNotes = \relative c'' {
c2 r8 d16\f f e g f a
g8 g16 g g2.
}
\addQuote oboe { \oboeNotes }
lyr = \lyricmode {
xy2 \skip8
a16 b c d e f g8 a16 h i
}
\addQuote lyr { \lyr }
\new Staff \oboeNotes
\new Lyrics \lyr
\new Staff
\new Voice
\relative c'' {
c2
\cueDuring #oboe #UP { r2 }
\cueLyr #lyr { r2 }
g2 c,
}
Thanks Harm!
I will (also) study your code, there is a lot that will be instructive
in any context.
Rutger
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Line Length
William Marchant wrote: How can I control the length of the [bottom] line Have a look at answers in a similar thread last July: http://lists.gnu.org/archive/html/lilypond-user/2014-07/msg00341.html http://lists.gnu.org/archive/html/lilypond-user/2014-07/msg00371.html Cheers, Robin [bottom] ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lengthening broken ties
If it's convenient, have a look at the attached patch/sketch. It
adds a property, minimum-length-left-broken, which lets you adjust
broken bits that start a line.
Excellent! What an improvement with just a few lines of code!
Thanks a lot.
Now that the change is in the repository, I've recompiled lilypond to
try it out with real-world code. Unfortunately, it doesn't work as
expected. Consider this snippet (together with the attached image).
\paper {
line-width = 50\mm
}
\relative c'' {
bes des e g1 ~ \break q \break
\once\override Tie.minimum-length-after-break = 10
bes des e g1 ~ \break q \break
\time 4/4 bes des e g1 ~ \break \time 3/4 q2. \break
\once\override Tie.minimum-length-after-break = 10
\time 4/4 bes des e g1 ~ \break \time 3/4 q2. \break
}
In bar 2 you can see the effect of `minimum-length-after-break'.
However, in bar 8, nothing changes! Value 10 is obviously too small
to get an effect if the line starts with a time signature – it seems
that the horizontal space of the time signature must be taken into
account also.
Any chance to fix this? BTW, if you compare bar 2 with bar 6, you see
exactly the opposite effect w.r.t. the default tie length: with a time
signature the tie looks OK but without it is far too short...
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: rit. in Midi - was: Re: lilypond-user Digest, Vol 137, Issue 62
From: Patrick Karl patrickk...@me.com
Date: Sat, 14 Feb 2015 11:18:49 -0600
I think the most disturbiing thing is that \articulate is interpreting
rit. to mean ritenuto rather than ritardando, which I think is
the most common interpretation of rit.. It would be great if the
tempo would ramp down gradually to 4=36 at the end.
It's true that articulate.ly does not handle gradual tempo changes as
one would expect.
I get around this, and simultaneously give myself control over the
contour of the rit. or accel. by writing another invisible stave just
for the midi, and containing nothing but rests and tempo markings. And
I use a modified version of articulate.ly with the lines
#(define ac:rallFactor (ly:make-moment 60/100)) % 40% slowdown
#(define ac:pocoRallFactor (ly:make-moment 90/100)) % 10% slowdown
changed to
#(define ac:rallFactor (ly:make-moment 100/100)) % no slowdown
#(define ac:pocoRallFactor (ly:make-moment 100/100)) % no slowdown
so that rit. markings have no effect.
Then I add additional tempo markings in the midi stave (there is no
actual stave) to produce what is in fact a stepped change of tempo. You
can add as many tempo changes as you need to give the illusion of a
gradual tempo change, and if you want more rit. towards the end, or at
the beginning, you can control that too by altering the figures.
For instance:
\version 2.18.0
\include articulate.ly
mid = {
\tempo 4 = 120 r1 | r1 |
\tempo 4 = 115 r4 \tempo 4 = 110 r4 \tempo 4 = 104 r4 \tempo 4 = 98
r4 |
\tempo 4 = 90 r4 \tempo 4 = 82 r4 \tempo 4 = 36 r2 |
}
music = \new Staff \with { midiInstrument = trumpet }
\relative c' { \tempo Allegro 4 = 120
c8 d e f g a b c | d e f g a b c b |
a g f e d c b a | g f e d c2\fermata |
}
\score {
\music
\layout { }
}
\score {
\articulate
\mid
\music
\midi { }
}
Even the length of the pause at the end can be adjusted.
I have not put a rit. marking in the music here, because using the
unmodified version of articulate.ly it would confuse things. But with
the alterations I suggested, rits and ralls in the score will not affect
the midi output.
I also find it useful to change the values of staccatoFactor,
normalFactor and other variables in the articulate script to produce a
better result. Dynamics. too, can be changed.
David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
\articulate command doesn't handle {c4 4}
The Notation Manual seems to allow a naked duration to represent the last pitch
with that duration. The following extract from the NM shows what I'm talking
about:
(you'd think that since we're only on p6, it would be easy to find the explicit
permission to do this, but I can't find it. Maybe it's somewhere later in the
NM. You'd probably also think that since the difference between absolute and
relative pitch entry has already been discussed this snippet should read:
cis''1~ 1~ \break cis''.)
Another illustration of this use of naked duration occurs on NM p371:
which produces:
If examples such as this are modified by the \articulate command, the midi file
is non-representative of the LP input. For example,
\version 2.19.15
\include articulate.ly
\score { {
\unfoldRepeats \articulate
\new Staff {cis''1~ 1~ \break cis''}
}
\midi { }
}
produces a midi file which consists of 4 beats of cis'' folowed by 4 beats of
rest or silence followed by 4 beats of cis''.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
repeat tremolo - warning message
lily ponders,
I ran the following lily code and got a warning message.The first and 2nd
\repeat tremolo are the same except the pitch. (1) Why the second \repeat
tremolo return a warning message.?(2) How can I adjust the \repeat tremolo so
that it display in the middle of two pitches - ie slanted upwards toward the
high note?I have problem to attach .png, lilypond-user rejected my email saying
it is too big.
Immanuel,Ming
%% lily code starts \version 2.19.15\language englishsi = { \time
4/4c'c''2 e'16 g' a' c'' g' a' c'' d'' |%m52\override Beam.gap = #2\repeat
tremolo 8 { e'' e''' } |%m53 -28\repeat tremolo 8 { b' b''} |%m54 -29\repeat
tremolo 4 { a' a''} g'g''4 a''8 g'' |\break%m55 -30}ai = { \clef bassc8 g c'
d' c'4 g |%m52c8 g c' d' e'4 c' |%m53e8 b e' b g'4 e' |%m54f8 c' f'4 g d'f'2
|%m55}\score {\new Staff \si\new Staff \ai\layout { }}%%lily code ends
Warning message:9:27 warning: weird stem size, check for narrow beams\repeat
tremolo 8 { b'b''} |%m54 -29
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: repeat tremolo - warning message
http://code.google.com/p/lilypond/issues/detail?id=1444
--
Phil Holmes
- Original Message -
From: MING TSANG
To: lilypond-user@gnu.org
Sent: Sunday, February 15, 2015 2:48 PM
Subject: repeat tremolo - warning message
lily ponders,
I ran the following lily code and got a warning message.
The first and 2nd \repeat tremolo are the same except the pitch.
(1) Why the second \repeat tremolo return a warning message.?
(2) How can I adjust the \repeat tremolo so that it display in the middle of
two pitches - ie slanted upwards toward the high note?
I have problem to attach .png, lilypond-user rejected my email saying it is
too big.
Immanuel,
Ming
%% lily code starts
\version 2.19.15
\language english
si = { \time 4/4
c'c''2 e'16 g' a' c'' g' a' c'' d'' |%m52
\override Beam.gap = #2
\repeat tremolo 8 { e'' e''' } |%m53 -28
\repeat tremolo 8 { b' b''} |%m54 -29
\repeat tremolo 4 { a' a''} g'g''4 a''8 g'' |\break%m55 -30
}
ai = { \clef bass
c8 g c' d' c'4 g |%m52
c8 g c' d' e'4 c' |%m53
e8 b e' b g'4 e' |%m54
f8 c' f'4 g d'f'2 |%m55
}
\score {
\new Staff \si
\new Staff \ai
\layout { }
}
%%lily code ends
Warning message:
9:27 warning: weird stem size, check for narrow beams
\repeat tremolo 8 { b'
b''} |%m54 -29
--
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Uncorrect (?) beams
Hi all, I want to make http://lilypond.1069038.n5.nabble.com/file/n171918/Beam01.jpg But using \autobeamon, \autobeamoff IO get http://lilypond.1069038.n5.nabble.com/file/n171918/Beam02.jpg Where am I wrong? Thanks. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Uncorrect-beams-tp171918.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
Re: Uncorrect (?) beams
It seems that you have to apply \autoBeamOff BEFORE a beam group starts. You
can manually start/stop beams by using brackets:
% --
\version 2.18.2
\relative c'' {
c4 b a \autoBeamOff g16[ b] a8
}
% --
Cheers,
Klaus
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Uncorrect-beams-tp171918p171922.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
Re: Uncorrect (?) beams
Hi,
\relative c'' {
c4 b a g16 b a8\noBeam
}
should do fine too.
Cheers,
Pierre
2015-02-15 18:15 GMT+01:00 Klaus Blum benbigno...@gmx.de:
It seems that you have to apply \autoBeamOff BEFORE a beam group starts.
You
can manually start/stop beams by using brackets:
% --
\version 2.18.2
\relative c'' {
c4 b a \autoBeamOff g16[ b] a8
}
% --
Cheers,
Klaus
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Uncorrect-beams-tp171918p171922.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
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: repeat tremolo - warning message
2015-02-15 16:56 GMT+01:00 Phil Holmes m...@philholmes.net:
http://code.google.com/p/lilypond/issues/detail?id=1444
--
Phil Holmes
- Original Message -
From: MING TSANG
To: lilypond-user@gnu.org
Sent: Sunday, February 15, 2015 2:48 PM
Subject: repeat tremolo - warning message
lily ponders,
I ran the following lily code and got a warning message.
The first and 2nd \repeat tremolo are the same except the pitch.
(1) Why the second \repeat tremolo return a warning message.?
(2) How can I adjust the \repeat tremolo so that it display in the middle
of two pitches - ie slanted upwards toward the high note?
I have problem to attach .png, lilypond-user rejected my email saying it is
too big.
Immanuel,
Ming
%% lily code starts
\version 2.19.15
\language english
si = { \time 4/4
c'c''2 e'16 g' a' c'' g' a' c'' d'' |%m52
\override Beam.gap = #2
\repeat tremolo 8 { e'' e''' } |%m53 -28
\repeat tremolo 8 { b' b''} |%m54 -29
\repeat tremolo 4 { a' a''} g'g''4 a''8 g'' |\break%m55 -30
}
ai = { \clef bass
c8 g c' d' c'4 g |%m52
c8 g c' d' e'4 c' |%m53
e8 b e' b g'4 e' |%m54
f8 c' f'4 g d'f'2 |%m55
}
\score {
\new Staff \si
\new Staff \ai
\layout { }
}
%%lily code ends
Warning message:
9:27 warning: weird stem size, check for narrow beams
\repeat tremolo 8 { b'
b''} |%m54 -29
Hi,
please always try to boil down your code to a minimal example, like:
\version 2.19.15
\repeat tremolo 8 { b'16 b'' }
Anyway, part of the problem are the Stems.
Yes, whole notes _do_ have a Stem in LilyPond. Look at the terminal-output of:
\relative c'' {
\override Stem.after-line-breaking =
#(lambda (grob) (newline) (format #t \n\tStem found: ~a\n grob))
c1
}
In your use-case you can deal with it, setting stem-direction explecitely.
Though, overrides for 'gap and 'positions of Beam may trigger more
warnings, which can be surpressed as shown below:
\version 2.19.15
%% The overrides for 'gap _and_ 'positions, both may trigger a warning,
%% depending on the used values
%% Uncomment one or both of the following lines to get rid of it
% #(ly:expect-warning (_ weird stem size, check for narrow beams))
% #(ly:expect-warning (_ weird stem size, check for narrow beams))
{
\override Beam.gap = #1.5 % a value of 2 will cause warnings
\override Beam.positions = #'(1.6 . 2.8)
\repeat tremolo 8 { \stemUp b'16 \stemDown b'' \stemNeutral }
}
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Uncorrect (?) beams
On Sun, Feb 15, 2015 at 10:42 AM, Son_V vincenzo.a...@gmail.com wrote: Hi all, I want to make http://lilypond.1069038.n5.nabble.com/file/n171918/Beam01.jpg But using \autobeamon, \autobeamoff IO get Capitalization is important: it's \autoBeamOn and \autoBeamOff. --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Uncorrect (?) beams
I'm using Frescobaldi, so I can't make this kind of mistakes, :-) , I wrote these commands meaning I'm using them in the right way ... I'm writing a score from a printed one made in the beginning of the '900 ... -- View this message in context: http://lilypond.1069038.n5.nabble.com/Uncorrect-beams-tp171918p171920.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
Re: Uncorrect (?) beams
On Sun, Feb 15, 2015 at 11:05 AM, Son_V vincenzo.a...@gmail.com wrote: I'm using Frescobaldi, so I can't make this kind of mistakes, :-) , I wrote these commands meaning I'm using them in the right way ... I'm writing a score from a printed one made in the beginning of the '900 ... If you want help with this, you'll have to post your LY code. Best, David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \articulate command doesn't handle {c4 4}
Hello,
the support for standalone durations was one of the first (and most
important?) changes made in 2.19 (see
http://lilypond.org/doc/v2.19/Documentation/changes/index.html. But
indeed, it seems to be a bug if \articulate can't handle them.
Yours, Simon
Am 15.02.2015 15:26, schrieb Cynthia Karl:
The Notation Manual seems to allow a naked duration to represent the
last pitch with that duration. The following extract from the NM
shows what I'm talking about:
(you'd think that since we're only on p6, it would be easy to find the
explicit permission to do this, but I can't find it. Maybe it's
somewhere later in the NM. You'd probably also think that since the
difference between absolute and relative pitch entry has already been
discussed this snippet should read: cis''1~ 1~ \break cis''.)
Another illustration of this use of naked duration occurs on NM p371:
which produces:
If examples such as this are modified by the \articulate command, the
midi file is non-representative of the LP input. For example,
\version 2.19.15
\include articulate.ly http://articulate.ly
\score { {
\unfoldRepeats \articulate
\new Staff {cis''1~ 1~ \break cis''}
}
\midi { }
}
produces a midi file which consists of 4 beats of cis'' folowed by 4
beats of rest or silence followed by 4 beats of cis''.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Uncorrect (?) beams
THANKS. What I was missing was to put the note between brackets, like in your example: [ b] ... Thanks again. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Uncorrect-beams-tp171918p171926.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
Re: Git/Lilypond workflow
Am 2015-02-15 15:19, schrieb RomanticStrings: What is the benefit of using Git? I understand that it keeps track of changes, so you can check your log and even retrieve previous versions(?). I use my home MacBook Pro and my work (sacred music director) PC laptop, and I have both a Dropbox and Google Drive account. It seems like Git doesn't work nicely with the latter, though I have much more space in it. Is there any reason I should consider using Git to manage my files, or is there a way to create an off-site(?) server to maintain my files so that I can access them on two computers? I am currently using Dropbox with a symbolic link to access the files I need on both computers (with the hard file on my laptop, which stays at home). Basically, what is the purpose of using Git other than keeping track of changes? As suggested you may have a look at http://lilypondblog.org/tag/version-control/ (maybe taking this as a starter: http://lilypondblog.org/2014/01/why-use-version-control-for-engraving-scores/) Generally Git doesn't work well with _any_ service like Dropbox or Google Drive (anything that touches your files independently from yourself). You can create an account at (e.g.) GitHub (only open source repositories are free) or (e.g.) BitBucket, where you can have free private repositories with up to five collaborators. There are other providers but I can't comment on them, and you can create your own GitLab clone like Gitlab - but when you're not even sure whether you'd need Git at all that's definitely nothing for you yet. As to your final question: The purpose of using Git is keeping track of changes. And that makes the difference. I always say: making the move to use version control for authoring documents (scores and text) is like learning to read or learning to walk. Best Urs ~Conor Cook -- View this message in context: http://lilypond.1069038.n5.nabble.com/Git-Lilypond-workflow-tp171764p171935.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 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \articulate command doesn't handle {c4 4}
2015-02-15 18:25 GMT+01:00 Simon Albrecht simon.albre...@mail.de:
Hello,
the support for standalone durations was one of the first (and most
important?) changes made in 2.19 (see
http://lilypond.org/doc/v2.19/Documentation/changes/index.html
http://lilypond.org/doc/v2.19/Documentation/changes/index.html. But
indeed, it seems to be a bug if \articulate can’t handle them.
Yours, Simon
Am 15.02.2015 15:26, schrieb Cynthia Karl:
For example,
\version 2.19.15
\include articulate.ly
\score { {
\unfoldRepeats \articulate
\new Staff {cis''1~ 1~ \break cis''}
}
\midi { }
}
produces a midi file which consists of 4 beats of cis'' folowed by 4
beats of rest or silence followed by 4 beats of cis''.
Isolated durations are working copying the previous note or chord, the
result is a _NoteEvent_ without 'pitch (not an EventChord, even if the
previous event was an EventChord).
Look at the terminal-output of 1. example
Otoh, the articulate-script _needs_ to have all relevant events as
EventChords.
Though, wrapping a NoteEvent without pitch into an EventChord will result
in rubbish even without \articulate.
Look at the printed and terminal output of 2. example.
\version 2.19.15
mus = { dis'' fis''1 1 }
%% 1. example
\displayMusic
\mus
%% 2. example
\displayMusic
$(map-some-music
(lambda (m)
(event-chord-wrap! m parser))
mus)
Have a look into articulate.ly again. You'll find:
% CHANGELOG
% * David Kastrup: basic 2.15.28 compatibility by using event-chord-wrap!
%This should really be done by rewriting the code more thoroughly.
Seems David was prophetic again.
Pease write a bug-report.
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Git/Lilypond workflow
What is the benefit of using Git? I understand that it keeps track of changes, so you can check your log and even retrieve previous versions(?). I use my home MacBook Pro and my work (sacred music director) PC laptop, and I have both a Dropbox and Google Drive account. It seems like Git doesn't work nicely with the latter, though I have much more space in it. Is there any reason I should consider using Git to manage my files, or is there a way to create an off-site(?) server to maintain my files so that I can access them on two computers? I am currently using Dropbox with a symbolic link to access the files I need on both computers (with the hard file on my laptop, which stays at home). Basically, what is the purpose of using Git other than keeping track of changes? ~Conor Cook -- View this message in context: http://lilypond.1069038.n5.nabble.com/Git-Lilypond-workflow-tp171764p171935.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
Re: Uncorrect (?) beams
Hi, What I was missing was to put the note between brackets, like in your example: [ b]” This may not be the best way of thinking about it. Rather, think that you need to put the [ immediately after the first note in the beam group, and the ] immediately after the last note in the beam group, e.g. a[ b] a[ b c] a[ b] c[ d e] etc. This is the same for slurs, e.g. a( b) a( b c) a( b) c( d e) etc. Hope this helps you, and anyone else who reads this thread in the future! Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \sustainOff\sustainOn produces inconsistent MIDI results
I have the same problem too. As a quick solution, I split the note into two with a tie, one for sustainOff and one for sustainOn. If there are no real solutions, I guess someone may write a function to automatically achieve this, say, \sustainOffOn -- View this message in context: http://lilypond.1069038.n5.nabble.com/sustainOff-sustainOn-produces-inconsistent-MIDI-results-tp171356p171904.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
Re: Git/Lilypond workflow
Am 15.02.2015 21:19, schrieb RomanticStrings: What is the benefit of using Git? I understand that it keeps track of changes, so you can check your log and even retrieve previous versions(?). I use my home MacBook Pro and my work (sacred music director) PC laptop, and I have both a Dropbox and Google Drive account. It seems like Git doesn't work nicely with the latter, though I have much more space in it. Is there any reason I should consider using Git to manage my files, or is there a way to create an off-site(?) server to maintain my files so that I can access them on two computers? I am currently using Dropbox with a symbolic link to access the files I need on both computers (with the hard file on my laptop, which stays at home). Basically, what is the purpose of using Git other than keeping track of changes? I think Urs wrote some rather euphorical posts on lilypondblog.org on this topic (search for version control), which should summarise the reasons quite well. Yours, Simon ~Conor Cook -- View this message in context: http://lilypond.1069038.n5.nabble.com/Git-Lilypond-workflow-tp171764p171935.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 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Git/Lilypond workflow
Thanks for this thread. I'm find this of real interest to me, for several reasons. I've had the question myself, and turned away from Git-engagement because I couldn't see the light. I'm off to read the blog post. Should be interesting! Tom On Sun, Feb 15, 2015 at 5:16 PM, u...@openlilylib.org wrote: Am 2015-02-15 15:19, schrieb RomanticStrings: What is the benefit of using Git? I understand that it keeps track of changes, so you can check your log and even retrieve previous versions(?). I use my home MacBook Pro and my work (sacred music director) PC laptop, and I have both a Dropbox and Google Drive account. It seems like Git doesn't work nicely with the latter, though I have much more space in it. Is there any reason I should consider using Git to manage my files, or is there a way to create an off-site(?) server to maintain my files so that I can access them on two computers? I am currently using Dropbox with a symbolic link to access the files I need on both computers (with the hard file on my laptop, which stays at home). Basically, what is the purpose of using Git other than keeping track of changes? As suggested you may have a look at http://lilypondblog.org/tag/ version-control/ (maybe taking this as a starter: http://lilypondblog.org/2014/ 01/why-use-version-control-for-engraving-scores/) Generally Git doesn't work well with _any_ service like Dropbox or Google Drive (anything that touches your files independently from yourself). You can create an account at (e.g.) GitHub (only open source repositories are free) or (e.g.) BitBucket, where you can have free private repositories with up to five collaborators. There are other providers but I can't comment on them, and you can create your own GitLab clone like Gitlab - but when you're not even sure whether you'd need Git at all that's definitely nothing for you yet. As to your final question: The purpose of using Git is keeping track of changes. And that makes the difference. I always say: making the move to use version control for authoring documents (scores and text) is like learning to read or learning to walk. Best Urs ~Conor Cook -- View this message in context: http://lilypond.1069038.n5.nabble.com/Git-Lilypond- workflow-tp171764p171935.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 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- ~ Love is the only force which can make things one without destroying them. … Some day, after mastering the winds, the waves, the tides and gravity, we shall harness.. the energies of love, and then, for the second time in the history of the world, man will have discovered fire. ~ Pierre Teilhard de Chardin ~ Tom Cloyd, MS MA LMHC (WA) Psychotherapist (therapist, training, research) Spokane, Washington, U.S.A: (435) 272-3332 t...@tomcloyd.com (email) TomCloyd.com (website) ~ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: repeat tremolo - warning message
Thank you, Thomas PhilImmanuel,Ming
On Sunday, February 15, 2015 1:06 PM, Thomas Morley
thomasmorle...@gmail.com wrote:
2015-02-15 16:56 GMT+01:00 Phil Holmes m...@philholmes.net:
http://code.google.com/p/lilypond/issues/detail?id=1444
--
Phil Holmes
- Original Message -
From: MING TSANG
To: lilypond-user@gnu.org
Sent: Sunday, February 15, 2015 2:48 PM
Subject: repeat tremolo - warning message
lily ponders,
I ran the following lily code and got a warning message.
The first and 2nd \repeat tremolo are the same except the pitch.
(1) Why the second \repeat tremolo return a warning message.?
(2) How can I adjust the \repeat tremolo so that it display in the middle
of two pitches - ie slanted upwards toward the high note?
I have problem to attach .png, lilypond-user rejected my email saying it is
too big.
Immanuel,
Ming
%% lily code starts
\version 2.19.15
\language english
si = { \time 4/4
c'c''2 e'16 g' a' c'' g' a' c'' d'' |%m52
\override Beam.gap = #2
\repeat tremolo 8 { e'' e''' } |%m53 -28
\repeat tremolo 8 { b' b''} |%m54 -29
\repeat tremolo 4 { a' a''} g'g''4 a''8 g'' |\break%m55 -30
}
ai = { \clef bass
c8 g c' d' c'4 g |%m52
c8 g c' d' e'4 c' |%m53
e8 b e' b g'4 e' |%m54
f8 c' f'4 g d'f'2 |%m55
}
\score {
\new Staff \si
\new Staff \ai
\layout { }
}
%%lily code ends
Warning message:
9:27 warning: weird stem size, check for narrow beams
\repeat tremolo 8 { b'
b''} |%m54 -29
Hi,
please always try to boil down your code to a minimal example, like:
\version 2.19.15
\repeat tremolo 8 { b'16 b'' }
Anyway, part of the problem are the Stems.
Yes, whole notes _do_ have a Stem in LilyPond. Look at the terminal-output of:
\relative c'' {
\override Stem.after-line-breaking =
#(lambda (grob) (newline) (format #t \n\tStem found: ~a\n grob))
c1
}
In your use-case you can deal with it, setting stem-direction explecitely.
Though, overrides for 'gap and 'positions of Beam may trigger more
warnings, which can be surpressed as shown below:
\version 2.19.15
%% The overrides for 'gap _and_ 'positions, both may trigger a warning,
%% depending on the used values
%% Uncomment one or both of the following lines to get rid of it
% #(ly:expect-warning (_ weird stem size, check for narrow beams))
% #(ly:expect-warning (_ weird stem size, check for narrow beams))
{
\override Beam.gap = #1.5 % a value of 2 will cause warnings
\override Beam.positions = #'(1.6 . 2.8)
\repeat tremolo 8 { \stemUp b'16 \stemDown b'' \stemNeutral }
}
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
CueDuringWithClef problems
Hello folks,
I can’t get the slurs in « Largo_Flute » nor R2 in the argument to
\cueDuringWithClef to be displayed in the following example.
Here is the log contents:
Starting lilypond 2.19.15 [CueVoiceExample.ly]...
Traitement de «
/Users/menu/Documents/LaTeX/PartitionsLilypond/CueVoiceExample.ly »
Analyse...
Interprétation en cours de la musique...
Interprétation en cours de la musique...
/Users/menu/Documents/LaTeX/PartitionsLilypond/CueVoiceExample.ly:18:58:
Avertissement : échec du contrôle de mesure (barcheck) à 1/2
\cueDuringWithClef #Largo_Flute #UP #treble { R1 |
R2 }
Pré-traitement des éléments graphiques...
Interprétation en cours de la musique...
/Users/menu/Documents/LaTeX/PartitionsLilypond/CueVoiceExample.ly:18:58:
Avertissement : échec du contrôle de mesure (barcheck) à 1/2
\cueDuringWithClef #Largo_Flute #UP #treble { R1 |
R2 }
Sortie MIDI vers « CueVoiceExample.midi »...
Détermination du nombre optimal de pages...
Répartition de la musique sur une page...
Dessin des systèmes...
Sortie mise en page vers « CueVoiceExample.ps »...
Conversion à « ./CueVoiceExample.pdf »...
Compilation menée à son terme, avec succès.
Completed successfully in 1.1.
Thanks for you help!
JM
\version 2.19.15
Largo_Flute = \relative g'' {
d32 [ ( c32 d32 es32 ) f8 -! ] r4
c32 [ ( a32 c32 e32 ) f8 -! ] r4 | % 144
bes,32 [ ( g32 bes32 d32 ) es!8 -! ] r4
}
\addQuote Largo_Flute { \Largo_Flute }
Largo = \relative d'' {
\clef alto \key bes \major \time 4/4 | % 1
\tempo Largo
\new CueVoice {
\set instrumentCueName = Fl.
}
\cueDuringWithClef #Largo_Flute #UP #treble { R1 | R2 }
r16 c,16 [ f16 c16 ] a16 [ a32 bes32 c16 a16 ] \break | % 3
}
\score {
\new Staff
\set Staff.quotedEventTypes = #'(note-event articulation-event
crescendo-event rest-event
slur-event dynamic-event)
\context Staff
\context Voice = Largo { \Largo }
\layout {}
% To create MIDI output, uncomment the following line:
\midi {}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lengthening broken ties
In bar 2 you can see the effect of `minimum-length-after-break'. You mean bar 4--bar 2 is the default. Of course. Typo. Any chance to fix this? BTW, if you compare bar 2 with bar 6, you see exactly the opposite effect w.r.t. the default tie length: with a time signature the tie looks OK but without it is far too short... If you change 'minimum-length-after-break to 'minimum-length, you'll get exactly the same result with the second half of each tied chord. This isn't a problem with the patch, as I changed nothing relating to the reference points from which the distances are reckoned. Well, it wasn't my intention to insinuate a faulty patch :-) It's certainly a problem with lilypond proper. From your analysis it appear that LilyPond is taking the entire NonMusicalPaperColumn into account rather than just the right extent. I'll have a look. (This could be major!) Thanks in advance! Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
