Re: Absolute Beginners
I finally sat down and read through the beginners' guide, and I like it! Good work. Two minor comments: On Tue 26 December 2006 01:57, Manuel wrote: > You change the clef changing the term "treble" to > > > alto > tenor > bass etc. Perhaps you should include "G_8" too - it's certainly the clef I use most often (for guitar scores and tenor parts). > Working fine? Then let's go for sharps and flats. Just add > > is > > to the name of a note to make it a sharp, like this: > > [snip] > > (Please note that this is not necessarily the way you are used to > naming the notes, just a quick, logical and easy way to work with > LilyPond.) This makes it sound like the is/es system is something that was invented for LP - you might want to indicate that it's the german(ic) way, perhaps also that it can be changed. If I knew nothing about the is/es system before, and read this paragraph, I would think: 'so they invented a new system which nobody has heard about before, and calls it logical?!? Give me a break - I'm not setting foot in THAT program...!" I'm exaggerating, of course... :-) -- It must be awful to be a girl. I'm sure it's frustrating knowing that men are bigger, stronger and better at abstract thought than women. Really, if you are a girl, what would make you go on living? --Calvin, Dictator-For-Life, of GROSS (Get Rid Of Slimy girlS) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: combined tenuto + accent
Thank you for you concern. I thought this request lost in the limbs, I'm glad to see I was wrong ^^ I'm looking forward to hearing news 'til then merry Christmas dudes On 12/24/06, Graham Percival <[EMAIL PROTECTED]> wrote: Thanks for the report, entered as http://code.google.com/p/lilypond/issues/detail?id=186 Please note that this is a feature request which is much harder to implement than it may initially appear; it may be a while until this new feature is added. Cheers, - Graham yota moteuchi wrote: > Hi, > > I am looking for a way to print an articulation made of the combination > of an accent (>) and a tenuto (_) > of course if I put I get an ugly result where the > accent is much wider than the tenuto. > > If it's not yet the case these articulations > http://www.dolmetsch.com/musictheory21.htm should be added as entities. > As the already existing tenuto + staccato. > Else, the documentation should mention it. > > Any clue ? > > Yota > > > > > ___ > 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: osx intel broken?
Trevor Bača escreveu: > On 12/25/06, Sean Reed <[EMAIL PROTECTED]> wrote: >> >> >> after unpacking the archives, they appear to be PPC programs that >> >> won't run on my new iMac. I know I've used this software on this >> >> computer before I re-installed it, so am I missing something? Or >> >> is the file that is downloaded from the intel link actually a ppc >> >> program? >> > >> > The frontend of the intel version claims to be ppc, but the actual >> > processing is done in native intel code. It works fine here. >> > Please try double-clicking the intel version. >> > >> > - Graham >> >> hi graham, hi james, >> >> i've been experiencing a similar situation since i started work on a >> macIntel, which coincided with 2.11.x coming out. >> >> the stable macIntel version 2.10.x runs fine on my intel macbook pro >> (10.4.8). >> >> however, the macIntel 2.11.x versions will run a few times, but after >> a certain number of measures it doesn't seem to complete the >> compilation process. (i haven't found a pattern to it yet, the >> current score i'm working on compiles fine up to 29 measures). >> >> the console stops producing any feedback suddenly and opens the .pdf >> in Preview immediately after the "Preprocessing graphical objects..." >> statement with no changes to the output. the "date modified" of >> the .ps and .pdf files doen't appear to change either. when i go back >> and comment out everything but the first few measures, it works fine >> again. > > Hi Sean, > > I run into this exact situation every so often. Almost every time > there winds up being something quite spectacularly off in my rhythmic > input. > > I separate stuff into lots of voices and I use lots of tuplets. The > mid-graphic-object-preprocessing hang tends to show up when I > accidentally add or remove a couple of tuplet elements somewhere, > causing the math not to work out between the different layered voices. > > Probably lots of other things can cause this same problem, but you > might try checking your rhythmic input starting right about measure > 28. I think you're hitting on crashes that are triggered due to your unorthodox rhythms. The process log window in the macos X version is not so sophisticated, so it doesn't properly print error messages for core dumps and similar. Still, if you can manage to reproduce any of this, please send me an offending input. Another option is that we're hitting compiler bugs. I'm using a GCC prerelease version that might not work reliably. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Absolute Beginners
Geoff, I took away plainchant. Should I mention other things, like
proportional notation or whatever?
David, I did just that and changed the sentence.
Eyolf, I included a reference to "chiavettes" with "G_8".
You change the clef changing the term "treble" to
Would "word" be better than "term"? Also, the most recent preceding
example used an alto clef. If the examples are numbered, you could
refer to the one you want.
I went back to "word".
You can amuse yourself writing all possible and also impossible
examples of simple melodies, and see what happens. Don't worry,
whatever you type, you can't break it...
I would change that last sentence, because it is easy enough to type
things that won't compile, and a new user might well regard that as
"breaking it".
I changed the whole paragraph and put it in the end, where it is more
appropriate, I think.
(Please note that this is not necessarily the way you are used to
naming the notes, just a quick, logical and easy way to work with
LilyPond.)
Can you perhaps add something like: "If you would prefer to use more
familiar names, see the section in the manual on "note names in other
languages.""?
I did.
So here's again.
Manuel
LilyPond's
Beginners Guide
for the
Absolute Beginner
(Mac OS X version)
Chapter One.
Open a new LilyPond window.
Then type this inside:
{ c' d' e' f' g' a' b' c' ' }
Save the file and then select "Typeset file" from the "Compile" menu.
A small window will open, where you can follow the proceedings, and
then a ".pdf" document will appear, with this result:
(insert graphic here)
It is a little C-major scale. Let us consider it:
The so-called "curly braces"
{
and
}
are essential. You must always write your music inside such braces.
Also, LilyPond is "case sensitive", which means that in our little
example, "c" (that's lower case) is right, but "C" (that's upper
case) would be wrong.
LilyPond has certain pre-set values, called "defaults", which will
apply whenever you do not ask for something different. In our present
example, for instance: the treble clef, 4/4 time signature, quarter
notes (or "crotchets", for non-American English speakers).
You can, of course, change these and all other defaults; indeed you
can engrave contemporary notation, orchestral scores, do MIDI files,
and more. But all that lies further down the road. For the moment, we
will teach you how to engrave a simple melody.
First, we'll give you a very useful tool to input your notes, called
the "relative mode".
In our example, we have written each note with an octave
denomination: one apostrophe:
'
for the so-called "first octave", which is the octave immediately
above and including the middle c - that's the central c in the piano
keyboard - and two apostrophes:
''
for the "second octave", the one immediately above the first octave.
But now, using the "relative mode", you will save yourself a lot of
work. Erase what you wrote before in the LilyPond window and write
this instead:
\relative
{ c d e f g a b c }
Note that the \relative command comes before and outside the { } .
Also, be very precise in the way you write this and all other
commands: don't allow a space between the backslash and the word,
since for instance:
\ relative
will not work, and only
\relative
will be fine.
Save the file again, close the .pdf and select "Typeset file" from
the "Compile" menu. The result will be the same C-major scale:
(insert graphic here)
But now, with the
\relative
command, the first note is automatically engraved as close as
possible to the middle c and every further note will be engraved as
close as possible to the previous note. "As close as possible" means
calculating the smallest interval. Thus if you modify your input to
this:
\relative
{ e g c b g f d c }
(Don't forget to always save the file and close the previous .pdf
before compiling)
You will get this result:
(insert graphic here)
You can analyze the exercise and see that the first note e appears a
third above middle c rather than a sixth below; the same happens with
the following g, a third above in relation to the preceding e; then
comes the c that is a fourth above the g instead of a fifth below, an
so forth.
Now in this mode, when you add an apostrophe, it makes the note
appear one octave higher than it would have appeared without the
apostrophe. Two apostrophes make for two octaves, and so forth.
To make a note one octave lower than it would otherwise appear, add a
comma:
c,
or two or more for more octaves:
c,,,
See it here:
\relative
{ c' g e' d c c, d c }
(insert graphic here)
Good. Now let's see how to select the following:
Clefs
Time signatures
Keys major and minor
Rhythmic values
Sharps and flats
Double bars and repeat bars.
These are simple things to do. Write this example:
\relative
{
\clef treble
\key c \m
Re: Absolute Beginners
Geoff, I took away plainchant. Should I mention other things, like proportional notation or whatever? I don't know--I've never used proportional notation (at least not knowingly). comes the c that is a fourth above the g instead of a fifth below, an so forth. "and so forth" (yet another one that spellcheck won't find) You set the clef naming the one you want: in the preceeding example, we wrote "alto" instead of "treble". Other clefs are called: "by naming" instead of just "naming" You can amuse yourself writing away melodies, trying things and see how they look. Don't worry, if what you write is impossible and does not compile, you will get an instructive error message in the little "process log window" we mentioned at the beginning and no printout, but you won't crash the program. Actually, it is sometimes possible to crash the program, but that indicates a bug in LilyPond; I believe the developers are committed to making hard crashes extinct. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Absolute Beginners
Am 26/12/2006 um 15:14 schrieb Geoff Horton: comes the c that is a fourth above the g instead of a fifth below, an so forth. "and so forth" (yet another one that spellcheck won't find) I anded the an to an and. You set the clef naming the one you want: in the preceeding example, we wrote "alto" instead of "treble". Other clefs are called: "by naming" instead of just "naming" I byed the by name by a by. Actually, it is sometimes possible to crash the program, but that indicates a bug in LilyPond; I believe the developers are committed to making hard crashes extinct. Let's not bug the beginners with bugs. But I do think that LilyPond developers are quite a hell of a team! (I understand that "hell" means "very good" in this case). Manuel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book in two-column mode?
Mats Bengtsson wrote:
I tried to change the first line to
\documentclass[a4paper,twocolumn,landscape]{article}
and couldn't notice any problems. If you use dvips and ps2pdf,
I hope you remember to add the flag
dvips -t landscape
Thanks for the tip Mats, added to git.
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \parallelMusic and PianoStaff, again
Palmer, Ralph wrote: I modified the snippet to make it a little more readable in the score. Would this be a candidate for the LSR? If so, I'll go ahead and submit it. Is there any standard format? I've added this to the manual. It may still be useful to have in LSR, though. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: stupid substitution
Nicolas Sceaux wrote:
Mats is right. But just for the record: music functions with no argument
still have their use, for instance:
displayBarNum =
#(define-music-function (parser location) ()
(if (eq? #t (ly:get-option display-bar-numbers))
#{ \once \override Score.BarNumber #'break-visibility = ##f #}
#{#}))
Then, having used \displayBarNum inside the score, the actual displaying
of bar numbers is triggered by a command line option:
lilypond -d display-bar-numbers foo.ly
Thanks, added to git.
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: osx intel broken?
after unpacking the archives, they appear to be PPC programs that
won't run on my new iMac. I know I've used this software on this
The frontend of the intel version claims to be ppc, but the actual
processing is done in native intel code. It works fine here.
however, the macIntel 2.11.x versions will run a few times, but
after
a certain number of measures it doesn't seem to complete the
compilation process. (i haven't found a pattern to it yet, the
the console stops producing any feedback suddenly and opens the .pdf
in Preview immediately after the "Preprocessing graphical
objects..."
statement with no changes to the output. the "date modified" of
I run into this exact situation every so often. Almost every time
there winds up being something quite spectacularly off in my rhythmic
input.
I think you're hitting on crashes that are triggered due to your
unorthodox
rhythms. The process log window in the macos X version is not so
sophisticated,
so it doesn't properly print error messages for core dumps and
similar.
Still, if you can manage to reproduce any of this, please send me
an offending
input.
Well, I found the offending input, and it appears to be something
completely different all together:
It appears to be unterminated slurs that are the offending input, but
only as of lilypond 2.11.x, and only at bar lines.
Here's an example:
Using 2.11.5, lilypond stops at the "Preprocessing graphical
objects..." and outputs no .ps/.pdf when compiling this expression:
{d'4 cis' d' cis'(}
However, THIS expression (slur beginning moved back one note) results
in only a warning in the console about an unterminated slur, but
the .ps/.pdf is created and displayed:
{d'4 cis' d'( cis'}
Using 2.10.5, both of these expressions are compiled to completion
and the .pdf is opened. Both return the "unterminated slur" warning,
but finish anyway. In the case where the slur is begun on the last
note of the measure using 2.10.5, the slur is merely not drawn on the
output.
This issue made itself evident to me because my scores are often
hundreds of measures long, and when tweaking them I often comment out
all but 5 or 10 bars at a time.
Hope this is of some significance for you.
-Sean
---
Sean Reed
Dublin
www.seanreed.ie
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: osx intel broken?
Sean Reed wrote:
Using 2.11.5, lilypond stops at the "Preprocessing graphical objects..."
and outputs no .ps/.pdf when compiling this expression:
{d'4 cis' d' cis'(}
Thanks!
http://code.google.com/p/lilypond/issues/detail?id=198
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Absolute Beginners
Why don't you put your tutorial on the wiki[1]? This way people can make small changes without all the back-and-forth on the mailing list. Also, you get automatic version control and it allows you to easily divide your tutorial into multiple sections. [1] http://lilypondwiki.tuxfamily.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Absolute Beginners
I have now incorporated (I hope) all the latest corrections and
suggestions. However, I thought that the ability to write simple
melodies should include the possibility of anacrusis, so I wrote a
little more at the end of the text.
About wiki, I don't think so. Especially as a newbie, I respect the
existing working structure of the LilyPond project. I assume that
there are people in charge of organising the tutorials and other
documentation. I suggest the inclusion of this first chapter of
"absolute beginners' " help. But I don't like the idea of posting it
by myself anywhere (outside this mailing list). After all, though I
provided the bones and incorporated the corrections and suggestions
which were made, this is obviously a collective piece of work.
Here is again the latest with the anacrusis bit.
Manuel
LilyPond's
Beginners Guide
for the
Absolute Beginner
(Mac OS X version)
Chapter One.
Open a new LilyPond window.
Then type this inside:
{ c' d' e' f' g' a' b' c' ' }
Save the file and then select "Typeset file" from the "Compile" menu.
A small window will open, where you can follow the proceedings, and
then a ".pdf" document will appear, with this result:
(insert graphic here)
It is a little C-major scale. Let us consider it:
The so-called "curly braces"
{
and
}
are essential. You must always write your music inside such braces.
Also, LilyPond is "case sensitive", which means that in our little
example, "c" (that's lower case) is right, but "C" (that's upper
case) would be wrong.
LilyPond has certain pre-set values, called "defaults", which will
apply whenever you do not ask for something different. In our present
example, for instance: the treble clef, 4/4 time signature, quarter
notes (or "crotchets", for non-American English speakers).
You can, of course, change these and all other defaults; indeed you
can engrave contemporary notation, orchestral scores, do MIDI files,
and more. But all that lies further down the road. For the moment, we
will teach you how to engrave a simple melody.
First, we'll give you a very useful tool to input your notes, called
the "relative mode".
In our example, we have written each note with an octave
denomination: one apostrophe:
'
for the so-called "first octave", which is the octave immediately
above and including the middle c - that's the central c in the piano
keyboard - and two apostrophes:
''
for the "second octave", the one immediately above the first octave.
But now, using the "relative mode", you will save yourself a lot of
work. Erase what you wrote before in the LilyPond window and write
this instead:
\relative
{ c d e f g a b c }
Note that the \relative command comes before and outside the { } .
Also, be very precise in the way you write this and all other
commands: don't allow a space between the backslash and the word,
since for instance:
\ relative
will not work, and only
\relative
will be fine.
Save the file again, close the .pdf and select "Typeset file" from
the "Compile" menu. The result will be the same C-major scale:
(insert graphic here)
But now, with the
\relative
command, the first note is automatically engraved as close as
possible to the middle c and every further note will be engraved as
close as possible to the previous note. "As close as possible" means
calculating the smallest interval. Thus if you modify your input to
this:
\relative
{ e g c b g f d c }
(Don't forget to always save the file and close the previous .pdf
before compiling)
You will get this result:
(insert graphic here)
You can analyze the exercise and see that the first note e appears a
third above middle c rather than a sixth below; the same happens with
the following g, a third above in relation to the preceding e; then
comes the c that is a fourth above the g instead of a fifth below,
and so forth.
Now in this mode, when you add an apostrophe, it makes the note
appear one octave higher than it would have appeared without the
apostrophe. Two apostrophes make for two octaves, and so forth.
To make a note one octave lower than it would otherwise appear, add a
comma:
c,
or two or more for more octaves:
c,,,
See it here:
\relative
{ c' g e' d c c, d c }
(insert graphic here)
Good. Now let's see how to select the following:
Clefs
Time signatures
Keys major and minor
Rhythmic values
Sharps and flats
Double bars and repeat bars.
These are simple things to do. Write this example:
\relative
{
\clef treble
\key c \major
\time 4/4
c d e f g a b c }
The result is our first example of a C-major scale:
(insert graphic here)
but this time you see the way some defaults are set. Change them
easily, like this:
\relative
{
\clef alto
\key cis \minor
\time 2/2
c d e f g a b c }
This should look thus:
(insert graphic here)
Don't worry just yet about the naturals. We'll explain
Re: Absolute Beginners
On 12/26/06, Manuel <[EMAIL PROTECTED]> wrote: About wiki, I don't think so. Especially as a newbie, I respect the existing working structure of the LilyPond project. I'm not sure I understand your objection. The wiki exists exactly for this sort of thing. I assume that there are people in charge of organising the tutorials and other documentation. Our documentation guru is also our bug meister, so he tends to be somewhat busy. The advantage of the wiki for things like this is that it allows changes to be made easily, immediately, and without requiring the interference of any of the developers. It's not that we don't like to be involved, it's just that there's so much other stuff to do also. After all, though I provided the bones and incorporated the corrections and suggestions which were made, this is obviously a collective piece of work. Once again, this is exactly the strength of the wiki. Collective work is what wikis are all about. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Absolute Beginners
Am 26/12/2006 um 18:41 schrieb Joe Neeman: Our documentation guru is also our bug meister Who is he? the interference of any of the developers. But that's part of my point. I write "do this for that purpose", then somebody else suggests a change, and so forth. But will it really work always? How do I know? I need and want the developers. Manuel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midi2ly doesn't respect the --key
> "Graham" == Graham Percival <[EMAIL PROTECTED]> writes: Graham> I'm not surprised; MIDI files only specifies the pitch number, not the Graham> actual note (i.e. bes and ais are both note 58). midi2ly is not Graham> intelligent enough to pick notes out of the same key. Then what does the --key feature do? If it doesn't decide that note 58 is a bes in F major but an ais in B major, what does it do? I thought it might put the correct \key statement into the .ly file, but it doesn't seem to do that, either. If it's going to be a complete no-op, it should be removed. I had thought that this used to work, but can't verify it by checking midi2ly 2.0.3. Graham> I doubt that this will ever be implemented; I think the Graham> best way to improve our importing abilities is to work on Graham> the musicxml importing. Best as in the theoretically best way to transfer information between full-featured notation programs, yes. Best as in the best way to get information off the web and into lilypond for typesetting, no. Has anyone ever found an XML file on the internet that they wanted to typeset? I very frequently find ABC and MIDI files that I want to use. So abandoning abc2ly and midi2ly, or even etf2ly, doesn't seem to me like a way to increase the utility of lilypond. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: midi2ly doesn't respect the --key
Laura Conrad wrote: "Graham" == Graham Percival <[EMAIL PROTECTED]> writes: Graham> I'm not surprised; MIDI files only specifies the pitch number, not the Graham> actual note (i.e. bes and ais are both note 58). midi2ly is not Graham> intelligent enough to pick notes out of the same key. Then what does the --key feature do? Oops, sorry. I confess that I wrote the above without actually having a clue. If it doesn't decide that note 58 is a bes in F major but an ais in B major, what does it do? It looks like it _is_ supposed to do that. There's some code in the script that claims to do this, but I'm not certain if it's correct. Could you construct a minimal example of this problem so I can add it to the bug tracker? - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Absolute Beginners
Graham, I see that you are in charge of documentation. I suggest that the little "Absolute Beginners' " help we have been tossing around for the last couple of days be included in the documentation. What is your opinion? Manuel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Absolute Beginners
Wikis are good at this type of thing. Give it a try and see what it looks like in a week. There will be a lot of quick changes, with should change a good description to a better one. "Joe Neeman" <[EMAIL PROTECTED]> writes: >On 12/26/06, Manuel <[EMAIL PROTECTED]> wrote: > > About wiki, I don't think so. Especially as a newbie, I respect the > existing working structure of the LilyPond project. > >I'm not sure I understand your objection. The wiki exists exactly for this >sort of thing. > > I assume that > there are people in charge of organising the tutorials and other > documentation. > >Our documentation guru is also our bug meister, so he tends to be somewhat >busy. The advantage of the wiki for things like this is that it allows >changes to be made easily, immediately, and without requiring the >interference of any of the developers. It's not that we don't like to be >involved, it's just that there's so much other stuff to do also. > > After all, though I > provided the bones and incorporated the corrections and suggestions > which were made, this is obviously a collective piece of work. > >Once again, this is exactly the strength of the wiki. Collective work is >what wikis are all about. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Absolute Beginners
Kevin, Probably because I don't really know or understand the wiki thing (not yet at least), I don't feel comfortable with it. I have just asked Graham for his opinion about including the "Absolute Beginners" help in the LilyPond's documentation. Let's see what he thinks. Manuel Am 26/12/2006 um 21:16 schrieb [EMAIL PROTECTED]: Wikis are good at this type of thing. Give it a try and see what it looks like in a week. There will be a lot of quick changes, with should change a good description to a better one. "Joe Neeman" <[EMAIL PROTECTED]> writes: On 12/26/06, Manuel <[EMAIL PROTECTED]> wrote: About wiki, I don't think so. Especially as a newbie, I respect the existing working structure of the LilyPond project. I'm not sure I understand your objection. The wiki exists exactly for this sort of thing. I assume that there are people in charge of organising the tutorials and other documentation. Our documentation guru is also our bug meister, so he tends to be somewhat busy. The advantage of the wiki for things like this is that it allows changes to be made easily, immediately, and without requiring the interference of any of the developers. It's not that we don't like to be involved, it's just that there's so much other stuff to do also. After all, though I provided the bones and incorporated the corrections and suggestions which were made, this is obviously a collective piece of work. Once again, this is exactly the strength of the wiki. Collective work is what wikis are all about. ___ 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
command line lilypond, midi to stdout
Howdy, I'm wondering if there is a way to have command-line lilypond produce midi on stdout. My typical use is to feed a .ly file into lilypond to create a .midi output, then take thatinto garage band (a mac program which I would describe as a midi recorder and track editor). Unfortunately lilypond sets the velocity of every note to the max, 127, and for instruments like a bass or a guitar garage band plays vel=127 as sort of a temporary pitch shift (like a very hard string pluck and maybe some motion on the fret). To work around this, I wrote a simple command-line program to receive a midi file on stdin, change all the note-on velocities to a specified value, and spit the result out on stdout. I was hoping to combine lilypond with this on the command line like this: cat mysong.ly | lilypond - | velchanger | mysong.midi Unfortunatley, it appears lilypond provides no way to output on stdout. Instead it creates -.midi, requiring a second command line to process the result. Anybody have any ideas how I can accomplish that in a single command? My cycle is edit,convert-to-midi,listen-in-garage-band, and I'm trying to get it down to as few steps as possible to go from the edit to hearing it. Thanks, Bob H ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
midi2ly key and rests
Hello, #include "German.ly" ;-) I have a MIDI file, that with all patches one semitone too high. It sounds in Cis . I have converted it with midi2ly to Lilypond format and transposed each voice with \transpose to C so I can play it much better. But this gives Ces instead of H and Fes instead of E. I gave the switch --key at midi2ly, but this changed the output of midi2ly in any way. Also -output has no effect to midi2ly. Another annoying thing is that all rests are silent rests. This makes it difficult to read & play the music. What is the best way to get the preferred pitch and readable rests? Regards, Helge ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
