need to be
vetted, but calculating the t-values for a single curve is quite fast.
> This is an example of something that one would hope to benefit from if
> LilyPond were to go to Cairo.
>
Like David, I'm not sure that using or not using Cairo is relevant for
general use (i.e., for both tap
Carl Sorensen writes:
> But the issue of non-uniform t along the length of the bezier curve is
> a legitimate issue. I am looking into it to see if there are any
> readily available solutions.
>
> This is an example of something that one would hope to benefit from if
>
On 6/27/17 9:00 PM, "lilypond-devel on behalf of Carl Sorensen"
wrote:
>On 6/27/17 6:00 PM, "lilypond-devel on behalf of tisimst"
>
On 6/27/17 6:00 PM, "lilypond-devel on behalf of tisimst"
wrote:
>On Tue, Jun 27, 2017 at 3:20 PM, Kieren MacMillan [via Lilypond] <
>ml+s1069038n20417...@n5.nabble.com> wrote:
>
>> Hi all,
>>
>> >> Take
d-style-dashed-slur.pdf>
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/True-Hand-engraved-Dashed-Slurs-tp204138p204177.html
Sent from the Dev mailing list archive at Nabble.com.
___
lilypond-devel mailing list
lilypond-devel@gnu
Hi all,
>> Take my vote for having it as the default.
> Excellent! At least that makes two of us ;-) (and Kieren, I believe).
Yes.
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
Hi,
Am 27.06.2017 um 22:34 schrieb tisimst:
> Take my vote for having it as the default.
It is just my gut feeling and nothing I could prove, but I see (at
least) two use cases for dotted slurs:
1. The current default looks like what I would prefer for "optional
slurs". I.e. in songs with two
t.
>
Excellent! At least that makes two of us ;-) (and Kieren, I believe).
Best,
Abraham
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/True-Hand-engraved-Dashed-Slurs-tp204138p204171.html
Sent from the Dev mailing list archive at Nabble.com.
On 27.06.2017 22:15, tisimst wrote:
How often are these split slurs used?
I personally have never had a reason to use them, but I guess they must be
used somewhere.
They’re used in scientific editions e.g. if a slur is begun before the
line break, but not continued after in the source.
Any
48
% - dash-fraction = (d-t)/(d+g) = (0.12)/(0.48) = 0.25
oldSlurDashed = {
\override Slur.thickness = 0
\override Slur.line-thickness = 1.6
\override Slur.dash-definition = #((0 1 0.25 0.48))
}
%%
Thanks, again!
- Abraham
--
View this message in context:
http://lilypond.1
On 6/26/17 4:53 PM, "lilypond-devel on behalf of Abraham Lee"
wrote:
>Greetings, Devs!
>
>I have always wondered why dashed slurs look the way they do, especially
>when compared to the Barenreiter snippets
David Kastrup writes:
> Abraham Lee writes:
>
>> Greetings, Devs!
>>
>> I have always wondered why dashed slurs look the way they do, especially
>> when compared to the Barenreiter snippets found in the essay. The current
>> dashes look better than they
Abraham Lee writes:
> Greetings, Devs!
>
> I have always wondered why dashed slurs look the way they do, especially
> when compared to the Barenreiter snippets found in the essay. The current
> dashes look better than they used to, but I still think they look a bit
Greetings, Devs!
I have always wondered why dashed slurs look the way they do, especially
when compared to the Barenreiter snippets found in the essay. The current
dashes look better than they used to, but I still think they look a bit odd
compared to the fairly uniform thickness of the
14 matches
Mail list logo