There is a point in the development course from stable to next stable,
where people should move to the current development release and forget
the old one. These days too many people uses 2.10 and its old
documentation. If a new user wants to start using LilyPond, I
undoubtedly send him to
Jonathan Kulp wrote:
I imagine that the reason many people still start out with 2.10.33 (on
Linux at least) is because 2.10.33 is the version in the repositories or
is even pre-installed in the distro (e.g. Ubuntu Studio). For these
cases there should perhaps be a warning about correct
2008/11/16 Jonathan Kulp [EMAIL PROTECTED]:
There is a point in the development course from stable to next stable,
where people should move to the current development release and forget
the old one. These days too many people uses 2.10 and its old
documentation. If a new user wants to start
For what it's worth, remember that as documented on this forum, you
shouldn't have to uninstall 2.10 on Ubuntu Studio before you install a
newer version if you install in your home directory. The 'lilypond'
command calls LilyPond from the home directory before it looks for it
elsewhere. After
On Sun, Nov 16, 2008 at 6:03 PM, David Stocker
[EMAIL PROTECTED] wrote:
For what it's worth, remember that as documented on this forum, you
shouldn't have to uninstall 2.10 on Ubuntu Studio before you install a newer
version if you install in your home directory. The 'lilypond' command calls
I have a piece written for Eb Alto Sax and would like to transpose it to
Bass Clef Trombone. I've read a bunch of posts in the archives and am
now more confused than ever. It should be relatively easy, as the bass
clef bone should be able to read the notes as written, but just change
the key
For transposing from E-flat to concert pitch, see the docs on
transposition, here:
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-big-page#Transpose
To change it to bass clef, just use a command
\clef bass
The easiest way to put put music into a different clef/register is to
Jonathan Kulp wrote:
For transposing from E-flat to concert pitch, see the docs on
transposition, here:
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-big-page#Transpose
To change it to bass clef, just use a command
\clef bass
The easiest way to put put music into a different
Correct me if I'm wrong, but I don't think that is all there is to it. I
changed the clef to Bass and in doing so the notes change position on
the staff. I want to have the notes remain in the same positions on the
staff in bass clef as they are in treble clef. Only the key signature
should
wrote:
Correct me if I'm wrong, but I don't think that is all there is to it. I
changed the clef to Bass and in doing so the notes change position on
the staff. I want to have the notes remain in the same positions on the
staff in bass clef as they are in treble clef. Only the key signature
should
don't think that is all there is to
it. I changed the clef to Bass and in doing so the notes change
position on the staff. I want to have the notes remain in the same
positions on the staff in bass clef as they are in treble clef. Only
the key signature should change. The Alto Sax part
On Sat, Nov 15, 2008 at 10:04:47PM -0700, chip wrote:
caused by this code -
... lots of stuff in the copy/pasted section below ...
\bar |.
}
\score {
\new
I have read the bloody manuals, all of them. I finally found the part I
need in the part I skipped over because it didn't apply to my work - 3.4
An Orchestral Part. I found the code I needed to see by clicking on the
picture of the score fragment, then I saw that the \transpose was in
front of
Ah, I see the problem. You were looking at the 2.10 docs, which
are approximately a thousand hours older than the 2.11 docs. As
you might expect from 1,000 hours of work, the 2.11 docs are much
easier to read.
- Graham
On Sat, Nov 15, 2008 at 10:38:07PM -0700, chip wrote:
I have read the
So even though I am using 2.10.33 (latest stable I believe) I should be
looking at the 2.11 docs?
--
Chip
Graham Percival wrote:
Ah, I see the problem. You were looking at the 2.10 docs, which
are approximately a thousand hours older than the 2.11 docs. As
you might expect from 1,000 hours
It's a bug in JPedal that is fixed in the current development release of
LilyPondTool. I'll make a release soon.
Bert
ian_hulin írta:
I think this is one for Bert.
If I use the Lilypond Tool Viewer to look at/print pdf files produced by
Lilypond V2.10-1 the treble clef is wrapped around
Citerar Annette [EMAIL PROTECTED]:
I noticed that when I do the examples in the tutorial, the stems in the
treble
clef go up in your examples and yet when I do them, the stems go down.
The only time I can make them go up is when I did that example of deciding
where to draw the beam
101 - 117 of 117 matches
Mail list logo
