On 10/13/10 11:49 AM, James Bailey wrote:
On Oct 13, 2010, at 4:01 PM, Carl Sorensen wrote:
Any chance the full-measure/multi-measure problem will get fixed?
How can we merge a multi-measure rest with a part-measure rest?
Unless things have changed, even trying to merge multi-measure
On 10/11/10 6:22 PM, James Bailey wrote:
On Oct 11, 2010, at 11:22 PM, Graham Percival wrote:
On Mon, Oct 11, 2010 at 04:32:48PM -0400, James Wilkinson wrote:
On 9/23/10 6:00 PM, Vicente Solsona wrote:
if the dynamics are the same, it's better to write them just once. thus
you:
1) save
On 10/11/10 5:22 PM, Graham Percival wrote:
On Mon, Oct 11, 2010 at 04:32:48PM -0400, James Wilkinson wrote:
On 9/23/10 6:00 PM, Vicente Solsona wrote:
if the dynamics are the same, it's better to write them just once. thus
you:
1) save typing
2) help lilypond so it does't need to waste time
On 10/11/10 6:19 PM, James Bailey wrote:
2) In another measure the upper voice has a quarter rest followed
by a half note on the bottom line of the staff. The lower voice has
a dotted half rest. The problem here is that the half note in the
upper voice is so low on the staff that it prints
On 9/23/10 6:00 PM, Vicente Solsona wrote:
When I put two voices on the same staff that have identical markings
for dynamics and tempo, Lilypond prints them both, one above the
other.
[...]
Back to my original question: if Lilypond can see that one of these
things needs to be moved, how hard
So I finally separated the dynamics from the notes, and it works!
But I had a couple of problems:
1) Whenever both instruments have a rest, Lilypond stacks them
vertically. James Bailey sent me a link to a snippet that fixes that.
(How did he know that was going to be my next problem?)
On 10/11/10 5:22 PM, Graham Percival wrote:
On Mon, Oct 11, 2010 at 04:32:48PM -0400, James Wilkinson wrote:
On 9/23/10 6:00 PM, Vicente Solsona wrote:
if the dynamics are the same, it's better to write them just once. thus
you:
1) save typing
2) help lilypond so it does't need to waste time
On 10/3/10 3:45 PM, Carl Sorensen wrote:
It would seem desirable to have a warning message when a non-existent
property is set in a \paper{} block.
Why not whenever a non-existent property is set anywhere?
\version 2.13.34
I've got three percussion voices sharing a staff. When I made the
bottom two voices be \voiceTwo and \voiceFour, I got downward stems,
but each note had its own stem. Then I tried making them both be
\voiceTwo. That gave me the printed output that I wanted: when notes
Gets to the point of saying Applying conversion: and just stops
Others might understand this, but I haven't a clue what you're
saying. Could you be a little more specific about what you're doing
and what is happening?
(head hanging in shame; must have been getting late)
I was using
At 4:26 PM -0400 9/28/10, James Wilkinson wrote:
I was using Lilytool in jEdit. There's a button there to update
versions. When you do that it reports progress in a console window.
The last message that it printed was Applying conversion. Nothing
after that. It always worked before. The version
\version 2.13.31
When I put two voices on the same staff that have identical markings
for dynamics and tempo, Lilypond prints them both, one above the
other. Looking in the archives the other day I saw that the approved
solution is to pull these markings out and attach them to another
voice
Date: Fri, 24 Sep 2010 00:00:07 +0200
From: Vicente Solsona vice...@lavabit.com
Subject: Re: duplicate dynamics on same staff
To: lilypond-user@gnu.org, James Wilkinson ji...@cs.cofc.edu
Message-ID: op.vjh92hshql9...@vsd.localdomain
Content-Type: text/plain; charset=utf-8; format=flowed; delsp
Gets to the point of saying Applying conversion: and just stops
--
-
Jimmy Wilkinson| Professor Emeritus of Computer Science
ji...@cs.cofc.edu| The College of Charleston
(843) 953-8160 | Charleston SC
The d flat has both an accent and a staccato mark over it. Lilypond
wants to put he accent on top of the staccato. I wanted the staccato
on top of the accent. Here are four tries. Two of them work; two of
them don't. (no surprise there) Two seem to be according to the
manual page 96; two
the instrument name oboe does not print
\version 2.11.27
\include LoHow.ly
\context Staff { \set Staff.instrument = oboe \clef treble \alto}
If you look at the current docs, you'll see that the relevant
properties are now called instrumentName (for the name on the first
system) and
This still works just fine except that the instrument name oboe
does not print at the beginning of the first line. That part was
working just fine a year ago. Can anybody tell me what happened? I've
tried 2.11.27 and 2.10.33, and it doesn't work with either of them.
Ii can't remember what
My biggest problem in typing input is getting notes in the correct
octave. Relative mode doesn't help me that much because I have to
stop and think which direction is within a fourth of the previous
note.
The thing that's unambiguous is direction. If I'm on the b in the
middle of the
Message: 8
Date: Fri, 26 May 2006 16:46:56 -0400
From: James Wilkinson [EMAIL PROTECTED]
Subject: subdivided beams partially successful
I'm working on a piece that has a long run of triplet 16th notes. In
the original they are printed in groups of six which are subdivided
into subgroups
I couldn't get \pageBreak to work consistently in 2.7.27
I was doing something like this example from the web site:
title = Konzert Nr. 3 Es dur
subtitle = für Horn und Orchester
composer = Wolfgang Amadeus Mozart (1756-1791)
I had three movements, which I put into separate
include
I'm working on a piece that has a long run of triplet 16th notes. In
the original they are printed in groups of six which are subdivided
into subgroups of three. I.e. the top beam covers six stems, and
there are two bottom beams, one for the first three notes and one for
the second three
My original contains cues: small notes (played by someone else) near
the end of an extended rest that are there to help the player come
back in at the right time.
I suppose that my problem is that I don't know what such notes are
called in Europe. I couldn't find cue in the index.
thanks
--
While scrolling through the index I noticed an entry for The Feta
Font alphabetized by The in the T section. There is no
corresponding entry alphabetized by Feta in the F section.
This seems wrong on both counts.
--
-
Jimmy Wilkinson
From: Mats Bengtsson [EMAIL PROTECTED]
Subject: Re: combining files
What didn't work?
First of all, you can skip the \book command, which is implicitly
added around any LilyPond input file if you don't write it yourself.
Also, within each \score{...}, the music should come before the
I'm reporting this here because I don't know where else to report it.
The jEdit plugin gives you an autocompletion list when you type a \.
Some things appear to be missing from the list of choices. I've not
made an exhaustive search, but came across the following: \ \f
\!. What happens
I have an example in which the insertion of a crescendo in the music
causes the generated MIDI file to be bad. Removing the crescendo
fixes the problem. Is this a known problem? I'm using version 2.7.17
on Windows.
A second thing: \ and \f don't work the same way in jEdit as \p. It
looks
(ledger) line.
How do I get this effect in Lilypond?
Thanks in advance,
James.
--
James Wilkinson Home: [EMAIL PROTECTED]
For every complex problem, there is a solution that is simple, neat, and
wrong.
___
Lilypond-user mailing list
[EMAIL
27 matches
Mail list logo
