Hi Thomas,
> I would like to, but I guess I would have to know GUILE/Scheme and/or C++ in
> order to do that
Not really… Just Lilypond.
What are the features/behaviours you want? I'm sure we can quickly build it
together.
Cheers,
Kieren.
___
lilypond
Hi,
In some piano music, you may have three different levels, as it were, e.g.
> a melodic line in the treble, played by the right hand, a deep bass
> consisting of long notes in the left hand, and in between chords filling in
> the time between the bass notes, also played by the left hand. In suc
Hi David,
On 27/4/12 10:34 AM, David Kastrup wrote:
Thomas Ruedas writes:
i.e., my main concern here is the situation where you may have more
than two staves, which is a much more common situation.
Why would you be using a PianoStaff for those?
I'm not sure I understand what you are wondering
Hi Kieren,
On 27/4/12 3:41 AM, Kieren MacMillan wrote:
It should be easy to define a custom context (e.g. MultiStaffPiano) to behave
this way — perhaps when you've got it worked out as you think it should behave,
you can add it to the codebase?
I would like to, but I guess I would have to know GU
Thomas Ruedas writes:
> Hi Kieren,
> On 27/4/12 3:00 AM, Kieren MacMillan wrote:
>>> I doubt that this new default behavior reflects common practice, though
>> As a pianist, I can tell you it absolutely does reflect common engraving
>> practice for piano staves: It is a very rare piano score (per
Hi Thomas,
> i.e., my main concern here is the situation where you may have more than two
> staves, which is a much more common situation. The case I wanted to make in
> the first place is to drop empty staves beyond the second staff, and in the
> piano scores I have (e.g. Debussy or Messiaen),
Hi Kieren,
On 27/4/12 3:00 AM, Kieren MacMillan wrote:
I doubt that this new default behavior reflects common practice, though
As a pianist, I can tell you it absolutely does reflect common engraving
practice for piano staves: It is a very rare piano score (perhaps 1/10 of 1%)
that contains only
Hi Thomas,
> I doubt that this new default behavior reflects common practice, though
As a pianist, I can tell you it absolutely does reflect common engraving
practice for piano staves: It is a very rare piano score (perhaps 1/10 of 1%)
that contains only a single staff. That is precisely the re
Hi Choan and Harm,
thanks for the prompt reply.
On 27/4/12 2:28 AM, Thomas Morley wrote:
this is a new feature with 2.14.
The "Keep_alive_together_engraver": Per default a PianoStaff is
removed only when all staves are empty. A single staff isn't deleted
any more.
If you want this behaviour, remo
Am 27. April 2012 01:51 schrieb Thomas Ruedas :
> Hi again,
> I have a piano score in which there are sometimes two, sometimes three
> staves, and I want the empty third staff to disappear during long stretches
> in which it is empty. This used to work in an earlier version (2.10) but
> after havin
On 4/27/12 01:51 , Thomas Ruedas wrote:
Hi again,
I have a piano score in which there are sometimes two, sometimes three
staves, and I want the empty third staff to disappear during long
stretches in which it is empty. This used to work in an earlier version
(2.10) but after having converted to 2
Hi again,
I have a piano score in which there are sometimes two, sometimes three
staves, and I want the empty third staff to disappear during long
stretches in which it is empty. This used to work in an earlier version
(2.10) but after having converted to 2.14.2, it doesn't anymore. Below
foll
12 matches
Mail list logo
