[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Chapter "Collision resolution"
From: |
David Kastrup |
Subject: |
Re: Chapter "Collision resolution" |
Date: |
Wed, 12 Jan 2011 16:40:46 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
"Trevor Daniels" <address@hidden> writes:
> David Kastrup wrote Wednesday, January 12, 2011 2:24 PM
>
>> Hi, I'm taking a look at the notation manual under "Collision
>> Resolution".
>>
>> The first beat on the second bar in the example has bad output
>> (merges
>> an eighth and a half note while inexplicably keeping the eighth's
>> note
>> head).
>
> This is bad! But it is not a problem caused by merging
> notes in different voices, almost the opposite. It is
> caused by the \oneVoice predef in voice 3 at the start of
> bar 2, which removes the shift normally associated with
> voiceThree. As there is no shift the notes are simply
> printed one on top of the other. \oneVoice is intended
> to be used when polyphony is not required, so it is being
> misused here.
Polyphony is not required here, as a proper notehead merge will do the
trick, like the fourth example shows. The fourth example is correct
after shifting an _unrelated_ notehead.
But \mergeDifferentlyHeadedOn is used in the two examples before
already. Why does it only start working correctly in the fourth
example?
>> Can we do better?
>
> Yes. A better example should be found.
I think we should first figure out why \mergeDifferentlyHeadedOn does
not work properly without shifting a note head _unrelated_ with the
collision.
After we get \mergeDifferentlyHeadedOn to work properly on examples two
and three, example four is a step backwards, and we should indeed find
something better.
But not while \mergeDifferentlyHeadedOn misbehaves.
--
David Kastrup
- Chapter "Collision resolution", David Kastrup, 2011/01/12
- Re: Chapter "Collision resolution", Trevor Daniels, 2011/01/12
- Re: Chapter "Collision resolution",
David Kastrup <=
- Re: Chapter "Collision resolution", Trevor Daniels, 2011/01/12
- Re: Chapter "Collision resolution", David Kastrup, 2011/01/12
- Re: Chapter "Collision resolution", Trevor Daniels, 2011/01/12
- Re: Chapter "Collision resolution", David Kastrup, 2011/01/13
- Re: Chapter "Collision resolution", Trevor Daniels, 2011/01/13
- Re: Chapter "Collision resolution", David Kastrup, 2011/01/13