Hi Harm, On Sat, Oct 29, 2011 at 9:47 AM, Thomas Morley < [email protected]> wrote:
>
> To make it possible to enter the same arguments to both,
> featherDurationTest and grow-dir-var, I added some conditions to the
> turnaround-argument and the end-multiplier.
>
Good idea -- thank you for doing this!
>
>
>> If you notice any problems or think of a way to make this more
>> effective/less tangled please let me know!
>>
>
> I would have expected that the pattern is displayed every time I use
> \featherDurationTest but it only occurs once. Why?
>
When I do the following, I get the same result with each group:
\relative c'' {
\repeat unfold 5 {
\featherDurationsTest #(ly:make-moment 1 2) #8
{ c32[ c c c c c c c c c c c c c c c] } c2
\break
}
}
>
> And there is a strange thing I had to notice: If \featherDurationTest is
> used a second (or third) time, the second (or third) setting changes and
> disturbs the first. Or, if I use a high turnaround-value with the first,
> the next settings are changed. I can't explain or fix this behaviour.
>
I'm speculating, but I think this odd behavior has something to do with the
way the durations are modified by both functions, and the demands this must
put on the spacing engine.
The attached file shows what happens to moments when you run
\featherDurations on successively longer groups. The numbers very quickly
get to be unmanageable since the process is geometric. And somehow the
total of these adjusted values (also shown in the log) needs to be scaled
to fit the original length. ( \featherDurationsTest does the same thing,
simply reversing the process at the turnaround point.)
I wonder if it's possible to create a feature in Lilypond which allows the
user to place notes at exact horizontal positions--I think this would be
useful with feathered values. (Years ago, I created a proportional
notation piece with Score this way--too long ago to remember if there were
any drawbacks to this method other than the manual calculation involved!)
> P.S.: In harm-feathered-beams-align-to-stems-rev_04.ly I forgot to apply
> dir-peak to mark-a. I integrated the correction into the attached file.
>
>
I'll be able to look at this some more in the upcoming days, and I'll let
you know if I think of anything!
Best,
David
featherDurations-data.ly
Description: Binary data
_______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
