Re: Color of hyphens when LyricText color is changed with override command

Kieren MacMillan wrote: > need for granular control of all graphical elements in a score, I would > assume. > [...] > text, hyphen, and extender are all different > parts of the presentation of lyrics [...]. Note also that this > distinction holds for ANY override (extra-offset, transparent,

Re: Augmentation dot positioning

On 9/18/16 4:00 PM, "Carl Sorensen" wrote: >Chris, > >Here's a patch. But as Werner pointed out, it's not quite done yet. I >think I need to improve the badness scoring in order to get better >configurations from which to remove excess dots. There are two comments in the

Re: Augmentation dot positioning

On 9/18/16 10:37 AM, "werner.lemb...@gmx.de on behalf of Werner LEMBERG" wrote: > >This looks very good, but there are two glitches, namely 13b and 23b, >which can't be right. 23c looks wrong, too. Clearly 23 is wrong. I need to investigate

Re: What to do wanting a 4th order Bézier?

On 19.09.2016 00:07, Urs Liska wrote: Am 18.09.2016 um 22:16 schrieb Thomas Morley: Hi all, I have my doubts we will ever find a possibility to do it reasonable automatic. That's probably right. But I don't think that should necessarily prevent us from including it as a built-in tool. This

Re: What to do wanting a 4th order Bézier?

Urs Liska writes: > Am 18.09.2016 um 20:54 schrieb David Kastrup: >> >> Do you know how to split a bezier at a given ratio into equivalent >> beziers? It's a comparatively simple operation and I think it's already >> somewhere in the C++ code though without access from

Re: What to do wanting a 4th order Bézier?

On 9/18/16 12:54 PM, "David Kastrup" wrote: > >Do you know how to split a bezier at a given ratio into equivalent >beziers? It's a comparatively simple operation and I think it's already >somewhere in the C++ code though without access from Scheme. see scm/bezier-tools.scm for

Re: What to do wanting a 4th order Bézier?

Am 18.09.2016 um 22:16 schrieb Thomas Morley: > 2016-09-18 20:26 GMT+02:00 Urs Liska : >> Am 18.09.2016 um 18:28 schrieb Simon Albrecht: >>> May I incorporate that into the LSR version? >>> >>> >> I suggest not to do anything right now. I assume that once I'll come up >>

Re: Augmentation dot positioning

On 9/18/16 11:09 AM, "Chris Yate" wrote: >Hi Carl, thanks! I'll take a look later today. Would you be happy to send >me a patch for the current source code HEAD? (Or just the modified file). >I was looking at the current code on Friday to try and understand it, so >it

2.19.48 on Mac OS 10.11

From an unsecured network, out of town… Had hopes for 2.19.48 but if anything, it is even slower on Mac OS 10.11.6 than was 2.19.47. Have to revert (again) to 2.19.46. From what I’ve read, my experience is not unique. Shouldn’t this be noted on the web page? I’ll help any way I can when I

Re: What to do wanting a 4th order Bézier?

Am 18.09.2016 um 20:54 schrieb David Kastrup: > Urs Liska writes: > >> I'm currently experimenting with this, giving it a somewhat more >> straightforward interface similar to \shape, i.e. using offsets from the >> automatic non-compound slur. >> >> My idea is to provide

Re: What to do wanting a 4th order Bézier?

Urs Liska writes: > I'm currently experimenting with this, giving it a somewhat more > straightforward interface similar to \shape, i.e. using offsets from the > automatic non-compound slur. > > My idea is to provide options that specify the angle and the length of > the

Re: Problem with partial measure at the beginning of the piece

Please keep conversations on the list! I was too concise, I guess. Your score notates a \partial 16*4, a 'pickup' of 4 16th notes. If I look at your notes, I presume a 'pickup' of a duration of 5 16th notes makes more sense. Hence, replace your \partial 16*4 with \partial 16*5, and have a

Re: What to do wanting a 4th order Bézier?

2016-09-18 20:26 GMT+02:00 Urs Liska : > Am 18.09.2016 um 18:28 schrieb Simon Albrecht: >> May I incorporate that into the LSR version? >> >> > > I suggest not to do anything right now. I assume that once I'll come up > with the next iteration there will be more things to be

Re: What to do wanting a 4th order Bézier?

Am 18.09.2016 um 18:28 schrieb Simon Albrecht: > May I incorporate that into the LSR version? > > I suggest not to do anything right now. I assume that once I'll come up with the next iteration there will be more things to be discussed. I suggest to bring that to an end before deciding what to

Re: What to do wanting a 4th order Bézier?

Am 18.09.2016 um 19:28 schrieb David Kastrup: > Simon Albrecht writes: > >> May I incorporate that into the LSR version? >> >> >> On 18.09.2016 16:04, Urs Liska wrote: >>> >>> Am 18.09.2016 um 16:01 schrieb Urs Liska: (cps

Re: What to do wanting a 4th order Bézier?

Simon Albrecht writes: > May I incorporate that into the LSR version? > > > On 18.09.2016 16:04, Urs Liska wrote: >> >> Am 18.09.2016 um 16:01 schrieb Urs Liska: >>>(cps (ly:slur::calc-control-points grob)) >>>(cps1

Re: Augmentation dot positioning

On 18 Sep 2016 17:37, "Werner LEMBERG" wrote: > > > > OK, I have rewritten the code for augmentation dot positioning. > > Great, and thanks a lot! > > > Personally, I like the results of this code better than the Gould > > recommendations. I would use this code, and make the

Re: Augmentation dot positioning

> OK, I have rewritten the code for augmentation dot positioning. Great, and thanks a lot! > Personally, I like the results of this code better than the Gould > recommendations. I would use this code, and make the default value > of chord-dots-limit be 1. I agree. > I'm attaching a copy of

Re: What to do wanting a 4th order Bézier?

May I incorporate that into the LSR version? On 18.09.2016 16:04, Urs Liska wrote: Am 18.09.2016 um 16:01 schrieb Urs Liska: (cps (ly:slur::calc-control-points grob)) (cps1 (first contr-pts)) (cps2 (second

Re: BendSpanner-engraver

Hi Harm, Am 18.09.2016 um 12:38 schrieb Thomas Morley: Hi Marc, 2016-09-13 22:41 GMT+02:00 Thomas Morley : 2016-09-13 8:33 GMT+02:00 Marc Hohl : The dashed line would also be great in cases like those: c'\3\startBend d'\3\stopBend~ d'\3 % bend

Re: What to do wanting a 4th order Bézier?

Am 18.09.2016 um 16:01 schrieb Urs Liska: > (cps (ly:slur::calc-control-points grob)) > (cps1 (first contr-pts)) > (cps2 (second contr-pts)) > (cp2-2 (mirror-point (fourth cps1) (third cps1)))

Re: What to do wanting a 4th order Bézier?

Hi Simon, > I added the new version to the LSR Wonderful! Thanks, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info

Re: What to do wanting a 4th order Bézier?

Hi Urs, > There's another improvement I'm right now experimenting with: Not having > to type the second control point of the second spline but calculating > that mirroring it from the third one of the first spline. I <3 U. =) > After that I would like to suggest looking for a solution that

Re: What to do wanting a 4th order Bézier?

Am 18.09.2016 um 15:49 schrieb Urs Liska: > > Am 18.09.2016 um 15:38 schrieb Simon Albrecht: >> On 18.09.2016 15:15, Kieren MacMillan wrote: And finally with a better user interface >>> Under what circumstances would you NOT want the end of one curve to >>> match precisely the beginning of

Re: What to do wanting a 4th order Bézier?

Am 18.09.2016 um 15:38 schrieb Simon Albrecht: > On 18.09.2016 15:15, Kieren MacMillan wrote: >>> And finally with a better user interface >> Under what circumstances would you NOT want the end of one curve to >> match precisely the beginning of the next one? >> If “none”, then I would say an

Re: What to do wanting a 4th order Bézier?

On 18.09.2016 15:15, Kieren MacMillan wrote: And finally with a better user interface Under what circumstances would you NOT want the end of one curve to match precisely the beginning of the next one? If “none”, then I would say an even better user interface would not require typing that set

Re: What to do wanting a 4th order Bézier?

Hi Simon, > And finally with a better user interface Under what circumstances would you NOT want the end of one curve to match precisely the beginning of the next one? If “none”, then I would say an even better user interface would not require typing that set of coordinates twice. In any

[OT] Re: What to do wanting a 4th order Bézier?

Hi Andrew, Quite independent of the actual question in this thread, thank you for the wonderful link on Bezier curves! I have bookmarked it, in anticipation of reading it in depth one day. Best, Kieren. > Just because this is so well written and one of the best elementary > expositions of

Re: Color of hyphens when LyricText color is changed with override command

Hi Colin, > How did this situation come about? The need for granular control of all graphical elements in a score, I would assume. > Surely the hyphens in the lyrics are part of the LyricText. Not really… they are part of the PRESENTATION of the lyric text (a.k.a. LyricText). They are,

Re: Color of hyphens when LyricText color is changed with override command

Colin Tennyson writes: > In a score that I am preparing I have used the following command to change > the color of the LyricText element: > > \override Lyrics.LyricText.color = #grey > > I noticed that the hyphens in the LyricText were still black. > > It occurred to

Re: What to do wanting a 4th order Bézier?

On 18.09.2016 13:54, Andrew Bernard wrote: Hello Simon, Others have of course already replied, but when I look at your attached sample I only see a slightly curved slur. What makes you say you want a quartic bezier curve? I can’t quite see it. Are you sure that’s what you want in any case?

Re: Color of hyphens when LyricText color is changed with override command

Hi Colin, ... > Surely the hyphens in the lyrics are part of the LyricText. ... Are they? Have you tried: \override Lyrics.LyricHyphen.color = #grey ? Cheers, Pierre 2016-09-18 14:29 GMT+02:00 Colin Tennyson : > In a score that I am preparing I have used the

Color of hyphens when LyricText color is changed with override command

In a score that I am preparing I have used the following command to change the color of the LyricText element: \override Lyrics.LyricText.color = #grey I noticed that the hyphens in the LyricText were still black. It occurred to me that maybe the color of the hyphens has to be set separately.

Re: What to do wanting a 4th order Bézier?

Hello Simon, Others have of course already replied, but when I look at your attached sample I only see a slightly curved slur. What makes you say you want a quartic bezier curve? I can’t quite see it. Are you sure that’s what you want in any case? Quickly scanning through some of the maths of

Re: BendSpanner-engraver

Hi Marc, 2016-09-13 22:41 GMT+02:00 Thomas Morley : > 2016-09-13 8:33 GMT+02:00 Marc Hohl : >> The dashed line would also be great in cases like those: >> >> c'\3\startBend d'\3\stopBend~ d'\3 >> % bend up, no release, bent note is tied >> >>

Re: BendSpanner-engraver

2016-09-14 3:07 GMT+02:00 David Nalesnik : > On Sun, Sep 11, 2016 at 4:53 AM, Thomas Morley > wrote: > >> >> Though, currently it's pretty slow in compilation. The reason for this >> slugginess >> is the feature not to bend open strings and to

Re: Ladder-style C clef for TTBB men's chorus

Here's another possibility including clef changes: \version "2.19.48" %% clef C ladder style #(define-markup-command (C_ladder-path layout props thk mlt) (number? number?) (interpret-markup layout props (markup (#:stencil (make-path-stencil '(M 0.000 -1.500 L

Re: Problem with partial measure at the beginning of the piece

I guess you want \partial 16*5 Rutger On 09/18/2016 09:47 AM, Serious Fun wrote: right = \relative c'' { \global % Music follows here. \partial 16 * 4 e,16 \noBeam \tuplet 3/2 {g8 e g} | a8. [a16] r4 r8. a,16 \noBeam d8.c16 | cs8. c16 } left = \relative c' { \global % Music follows

Problem with partial measure at the beginning of the piece

Sorry this is a long snippet can't get c16 into the first whole measure. right = \relative c'' { \global % Music follows here. \partial 16 * 4 e,16 \noBeam \tuplet 3/2 {g8 e g} | a8. [a16] r4 r8. a,16 \noBeam d8.c16 | cs8. c16 } left = \relative c' { \global % Music follows here.