RE: multiple tempi in a single piece
Kieran,
Can you provide some hints on how to make this even easier
to find in the manual? If you read the section on Creating
MIDI files, it says The tempo can be specified using the \tempo
command within the actual music, see Metronome marks.
and if you follow the link to Metronome marks, you will see
exactly the type of solution described below.
Trevor, why do you include the \override Score.MetronomeMark #'padding = #3.0
setting? Since you just set the metronome marks transparent, they will
still influence the staff spacing and if you increase
the padding, the spacing will be even wider. If you don't want
the tempo changes to influence the printed layout, I would rather
recommend to use
\override MetronomeMark #'stencil = ##f
instead of transparent = ##t, which removes them completely, not
just makes them transparent.
/Mats
Quoting Trevor Daniels [EMAIL PROTECTED]:
Hi Kieran
The following shows how I change the Midi tempi - you can
easily adapt this example to do what you want:
TempiA= {
\override Score.MetronomeMark #'padding = #3.0
%Page 1 System 1 Bar 1
\tempo 2=80 s1 | s | s | s | s | s | s |
%Page 1 System 2 Bar 8
% the following tempo changes implement the fermata in bar
9
\override Score.MetronomeMark #'transparent = ##t % hide
the marks
s1 | \tempo 2=50 s | \tempo 2=80 s | s1 | s | s | s | s | s
|
%Page 1 System 3 Bar 17
% the following tempo changes implement the fermata in bar
18
s1 | \tempo 2=50 s | \tempo 2=80 s | s | s | s | s | s |
}
I simply insert this in parallel with the music.
Trevor
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Kieran Coulter
Sent: 10 July 2007 01:51
To: lilypond-user@gnu.org
Subject: multiple tempi in a single piece
Hi everyone,
I am sure there is a way to do this, but maybe someone here
has already faced this challenge and can help show me how it
can be done.
My example is the Bach Sinfonia from Partita #2. It has a
Grave, Andante, and Allegro, but the MIDI file plays all the
sections at the same speed, 120bpm. I am looking for a way
to modify the .ly file so that it generats a MIDI file that
plays the Grave at say 40bpm, the Andante at 80bpm, and only
the Allegro at 120bpm.
I would greatly appreciate any help to discover how to do
this!
Thanks,
Kieran Coulter
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: multiple tempi in a single piece
Mats said:
Trevor, why do you include the \override
Score.MetronomeMark #'padding = #3.0
setting? Since you just set the metronome marks
transparent, they will
still influence the staff spacing and if you increase
the padding, the spacing will be even wider. If
you don't want
the tempo changes to influence the printed
layout, I would rather
recommend to use
\override MetronomeMark #'stencil = ##f
instead of transparent = ##t, which removes them
completely, not
just makes them transparent.
You're quite right - removing the stencil would be better
for the tempo changes which implement the fermata.
To explain the padding: the first metronome mark shown here
and some later ones (in other tempi variables) are meant to
be printed. These set the tempi of the sections of the
piece. The increased padding prevents collisions with
dynamic marks which often occur at the same time.
/Mats
Trevor
Quoting Trevor Daniels [EMAIL PROTECTED]:
Hi Kieran
The following shows how I change the Midi tempi
- you can
easily adapt this example to do what you want:
TempiA= {
\override Score.MetronomeMark #'padding = #3.0
%Page 1 System 1 Bar 1
\tempo 2=80 s1 | s | s | s | s | s | s |
%Page 1 System 2 Bar 8
% the following tempo changes implement the
fermata in bar
9
\override Score.MetronomeMark #'transparent = ##t % hide
the marks
s1 | \tempo 2=50 s | \tempo 2=80 s | s1 | s | s
| s | s | s
|
%Page 1 System 3 Bar 17
% the following tempo changes implement the
fermata in bar
18
s1 | \tempo 2=50 s | \tempo 2=80 s | s | s | s | s | s |
}
I simply insert this in parallel with the music.
Trevor
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:lilypond-user-bounces+t.daniels=treda.co.u
[EMAIL PROTECTED]
On Behalf Of Kieran Coulter
Sent: 10 July 2007 01:51
To: lilypond-user@gnu.org
Subject: multiple tempi in a single piece
Hi everyone,
I am sure there is a way to do this, but maybe someone
here
has already faced this challenge and can help show me how
it
can be done.
My example is the Bach Sinfonia from Partita #2. It has a
Grave, Andante, and Allegro, but the MIDI file plays all
the
sections at the same speed, 120bpm. I am looking for a way
to modify the .ly file so that it generats a MIDI file
that
plays the Grave at say 40bpm, the Andante at 80bpm, and
only
the Allegro at 120bpm.
I would greatly appreciate any help to discover how to do
this!
Thanks,
Kieran Coulter
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: new display for warnings
Graham wrote: What do you think of the new warnings in the manual? In the Learning Manual, see 2.1.1 Compiling a file 2.3.1 Music expressions explained As always, look at the new docs on http://opihi.cs.uvic.ca/~gperciva/ I quite like them, although perhaps we should reserve them for the really important reminders so that they retain their impact. Like Eyolf, I think NB: (nota bene) or Remember!: might be better than Warning: - Graham Trevor D ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: new display for warnings
Eyolf Østrem wrote: On 03.10.2007 (17:07), Graham Percival wrote: What do you think of the new warnings in the manual? In the Learning Manual, see 2.1.1 Compiling a file 2.3.1 Music expressions explained I definitely like it. I'm not sure about the word Warning, though... makes it sound dangerous... In Norwegian I would have used NB -- I don't know how that would work? Yes, it's a good idea. +1 to N.B. instead of Warning though. (And notice that the sentence immediately after the warning box in 2.1.1 contradicts the warning itself...) -- Mark Knoop ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 3 Sided Box?
Hello Mats, Thanks so much for this. Sorry it took me so long to get to it -- I've been just crazy busy and had to put LilyPond on hold for a while. Your solution works great, although very easy to add one ... I'm not sure I would say very. I don't understand most of the details of the code. It doesn't seem as symmetrical as I would have thought for a box. But I figured out how to remove whatever side I want and I can just include these box functions in a separate file. It was quite a nice feeling to have posted a question and have it answered / solved so quickly. I don't have to wait for the next version of the program to see if my concern had been addressed. Thanks again, Jeff. On 26-Sep-07, at 5:34 AM, Mats Bengtsson wrote: Quoting fedge [EMAIL PROTECTED]: Hello, I'm new to using Lilypond, and Finale for that matter. I'm trying to decide which is better. So far, what I like about Lilypond is that I seem to be able to do just about anything I want ... except this: I like the \box option around a text markup, but I would really like it if it only had three sides (LEFT, TOP and RIGHT -- or, LEFT, BOTTOM and RIGHT). Is there anyway to customize this? Or maybe I have to write some function that draws three lines, but will bound itself around some text? Right, there's no such function in LilyPond by default, but it's very easy to add one. I just added an example in our snippet repository, LSR, see http://lsr.dsi.unimi.it/LSR/Item?u=1id=330 /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: new display for warnings
Mark Knoop wrote: Yes, it's a good idea. +1 to N.B. instead of Warning though. Everybody likes N.B., so I'm happy to change that... but does everybody understand the term? I'm thinking of somebody with a shaky understanding of English. Of course, having it in the box kind-of already says warning, so I'm relatively confident that we can change this without introducing confusion. (And notice that the sentence immediately after the warning box in 2.1.1 contradicts the warning itself...) Technically it says should be, not must be, so it's not contradicting. :P Yeah, yeah, I fixed it. :) Cheers - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
rolls in Irish Traditional Music
Please, rolls in Irish traditional music are normally indicated by a ~ over the note. But these are not written to the midi file as rolls, at least, Timidity does not play them. Do I have to articulate the rolls fully in lily, or is there some other short cut way of doing it ? -- Thanks Joe Mc Cool Snark, currently LEYC 028 37548074, 07802572441 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
is it possible to glue two staff's together? (hymn solution)
For the longest time, there has been a problem in Lilypond that affects the typesetting of hymns. In a hymn, there will be all the verses. And then quite often there is a refrain. In hymn typesetting, the refrain is nicely centered between the bass and treble clefs. If it were possible to glue two staffs together, end to end, that would solve the problem. I could attach the refrain lyrics to the second staff, and put the verses of the hymn into the first staff. So, is this already possible somehow? The only alternative right now, which is icky, is to make the refrain start on a new line, all the time. This is wasteful of space. Ted -- There's a party in your skull. And you're invited! Name:Ted Walther Phone: 778-320-0644 Email: [EMAIL PROTECTED] Skype: tederific Address: 3422 Euclid Ave, Vancouver, BC V5R4G4 (Canada) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Scheme code for extracting LilyPond header properties?
Carl Sorensen wrote: This is a great example of how to work with Scheme code. It should be added to the docs, IMO. Please go through LSR first; that makes it much easier for everybody involved. Perhaps also to the LSR. Please do so. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: rolls in Irish Traditional Music
Joe Mc Cool wrote: rolls in Irish traditional music are normally indicated by a ~ over the note. But these are not written to the midi file as rolls, at least, Timidity does not play them. Midi support in lilypond is quite limited, and this is not likely to change in the near future. Sorry, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond-book -- almost there... round III
On 04.10.2007 (16:19), Graham Percival wrote:
Eyolf Østrem wrote:
I made a last attempt, with minimal files included, which look like
this:
I'm now going to commit the sin of jumping into a long discussion without
having read the intermediate steps (with GDP going on, I've been pretty
much ignoring -user), so please ignore if this is totally off-base...
playground/book.tex:
\documentclass{article}
\begin{document}
\include{out/lpb-file}
\end{document}
playground/lpb-file.lytex:
\lilypondfile{music.ly}
... why? Just not stick
\lilypnodfile{out/music.ly
in your main book.tex? That's what I do. Call it book.lytex, run it
through lilypond-book, then run the generated .tex through texinfo. Or
pdflatex.
I'll look into that, but I think -- to the extent that I'm able to, at
these hours -- that the answer is that in real life, the included file
does not just contain the ly-file, but is a full chapter of its own,
so it needs to be kept in a separate file altogether. I think...
This example was just to make it as minimal as possible. So while your
solution is certainly a workaround which works to some extent, it also
shows that the output=out thing has its limits.
But thanks for your input (or should that be include...? :-)
Now, is this how it's supposed to be, or is there a way to work around
this? As I said, I'm happy to keep all the output files in the main
folder -- now it's become almost a matter of principle: I want to find
out if I've overlooked something...
This is related to a current bug (or enhancement request) about \includes
in pure lilypond files. All the filenames are relative to the first file
called, not the first file. Err, the bug summary has a better summary
than this.
I understand. I hope it will be fixed.
Eyolf
--
The one-eyed view of our universe says you must not look far afield for
problems. Such problems may never arrive. Instead, tend to the wolf within
your fences. The packs ranging outside may not even exist.
-- The Azhar Book; Shamra I:4
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
C Cleft
If I make a song with \clef c a flat on the top staff the notes are 1/2 line off from where they are expected to be. will setting the clef to tenor or mezzosoprano move the note the 1/2 line it needs to move ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
GDP: pitches rewrite
I've done some updates on Pitches, and considered all the discussion. Here's the list of tasks for other people to tackle: - key signature: what should be done about the warning about expecting \key g \major f4 to produce fis ? rewrite section? - FORMATTING - finish setting up new tables in note names in other languages - add @lsrdir links. See Writing pitches for an example. (yes, it's just that easy!) - REWRITE: - check - octave check - transpose - instrument transposition First-come, first-serve. Let us know if you claim a task, so that nobody else starts working on the same thing. Files in the normal places. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: multiple tempi in a single piece
Hi Mats,
I think it belongs here,
http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Creating-MIDI-files#Creating-MIDI-files
Where it mentions how to set the default tempo (which I assume is the global
tempo for most pieces that don't change tempo).
I would then distinguish between wanting simply for the metronome markings
present, wanting the markings and the correct tempo changes, and wanting the
tempo changes but not caring about markings (as is the case for Trevor). Also,
make it as clear as possible when a way of working with Lilypond has the effect
of managing metronome marks, and when it affects the tempi within the MIDI file
itself.
In my case, we are requiring that we indicate default tempo expectations so
that we can allow users to start with that tempo (we will try and make it as
appropriate as possible) or adjust to a tempo that is comfortable for them,
relative to a known tempo.
Although it is of course most fitting in many older pieces to only have the
Italian indication, we have need for the special case I mentioned above, and we
will be sure to say wherever appropriate that these are not our personal
recommendations, just that we need to define the default tempi so that rhythm
tracking works properly!
Also if we don't include tempo changes within the file itself, and instead
resort to modifier tables, it's just an extra table to embed into the per-piece
database structure. With this figured out would still have 4 out of 5 tables
left to integrate, if we are going to try and fight to get a better MIDI file
standard some more (although it looks like we will finally be getting around to
it!).
Thanks for the tip Trevor, I will try it out!
So just to be totally sure,
1) you add the tempo map, killing time with s's, as its own voice?
2) Do you still need to add the global default tempo in the MIDI block if you
do this?
tempoWholesPerMinute = #(ly:make-moment 72 4)
3) If so, and you also explicitly add a tempo in measure 1 of your tempo voice,
and they are different, does it produce an error or does one override the other?
Thanks again!
Kieran
--- Original Message Follows ---
From: Mats Bengtsson [EMAIL PROTECTED]
To: Trevor Daniels [EMAIL PROTECTED]
Cc: Kieran Coulter [EMAIL PROTECTED], lilypond-user@gnu.org
Subject: RE: multiple tempi in a single piece
Date: Thu, 04 Oct 2007 08:58:11 +0200
Kieran,
Can you provide some hints on how to make this even easier
to find in the manual? If you read the section on Creating
MIDI files, it says The tempo can be specified using the \tempo
command within the actual music, see Metronome marks.
and if you follow the link to Metronome marks, you will see
exactly the type of solution described below.
Trevor, why do you include the \override Score.MetronomeMark #'padding
= #3.0
setting? Since you just set the metronome marks transparent, they will
still influence the staff spacing and if you increase
the padding, the spacing will be even wider. If you don't want
the tempo changes to influence the printed layout, I would rather
recommend to use
\override MetronomeMark #'stencil = ##f
instead of transparent = ##t, which removes them completely, not
just makes them transparent.
/Mats
Quoting Trevor Daniels [EMAIL PROTECTED]:
Hi Kieran
The following shows how I change the Midi tempi - you can
easily adapt this example to do what you want:
TempiA= {
\override Score.MetronomeMark #'padding = #3.0
%Page 1 System 1 Bar 1
\tempo 2=80 s1 | s | s | s | s | s | s |
%Page 1 System 2 Bar 8
% the following tempo changes implement the fermata in bar
9
\override Score.MetronomeMark #'transparent = ##t % hide
the marks
s1 | \tempo 2=50 s | \tempo 2=80 s | s1 | s | s | s | s | s
|
%Page 1 System 3 Bar 17
% the following tempo changes implement the fermata in bar
18
s1 | \tempo 2=50 s | \tempo 2=80 s | s | s | s | s | s |
}
I simply insert this in parallel with the music.
Trevor
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Kieran Coulter
Sent: 10 July 2007 01:51
To: lilypond-user@gnu.org
Subject: multiple tempi in a single piece
Hi everyone,
I am sure there is a way to do this, but maybe someone here
has already faced this challenge and can help show me how it
can be done.
My example is the Bach Sinfonia from Partita #2. It has a
Grave, Andante, and Allegro, but the MIDI file plays all the
sections at the same speed, 120bpm. I am looking for a way
to modify the .ly file so that it generats a MIDI file that
plays the Grave at say 40bpm, the Andante at 80bpm, and only
the Allegro at 120bpm.
I would greatly appreciate any help to discover how to do
this!
Thanks,
Kieran Coulter
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
