Hi Harm,
> sorry for the late reply.
No worries!
> You likely mean this thread:
> http://lilypond.1069038.n5.nabble.com/improving-Janek-s-dynamic-function-for-combo-dynamics-td205071.html
Yes — sorry I didn’t link.
> I hardly find time to work with or on LilyPond these days.
Our loss. =)
>
Hi Kieren,
sorry for the late reply.
Am So., 8. Sept. 2019 um 21:29 Uhr schrieb Kieren MacMillan
:
>
> Hi Harm,
>
> Three questions on this [seemingly-ancient!] thread about your (wonderful)
> "dynamics on the fly" function:
You likely mean this thread:
http://lilypond.1069038.n5.nabble.com/imp
Hi Harm,
Three questions on this [seemingly-ancient!] thread about your (wonderful)
"dynamics on the fly" function:
1. Have you, as you implied might happen, found better ways to do the same
thing(s) in light of recent development efforts in the basecode?
2. How can I eliminate the resulting g
Hi Harm,
> Well, it's a sketch of an idea.
> Elaborating it will blow up the amount of needed code again.
> Right now, predicting any performance of a possible final state is not
> possible.
Understood.
> At least I'd expect no need for string searching/selection
> and at least less list-select
2017-09-12 21:58 GMT+02:00 Kieren MacMillan :
> Hi Harm,
>
> Is
>
> \dynamicH "text only"
>
> (or something like that) supposed to work?
Well, it did work in a previous version. So it's a regression.
Thanks spotting it.
For a quick fix, change here:
#(define (get-list-parts lst dyn-indices
2017-09-12 2:03 GMT+02:00 Kieren MacMillan :
> Harm,
>
>> A very first shot.
>
> You never cease to amaze me!
>
> 1. Is this, speed-wise, any more or less efficient [e.g., on very large
> scores with lots of combo dynamics] than your other approach?
Well, it's a sketch of an idea.
Elaborating it
2017-09-12 13:57 GMT+02:00 Kieren MacMillan :
> Hi David,
>
>>> 1. Is this, speed-wise, any more or less efficient [e.g., on very
>>> large scores with lots of combo dynamics] than your other approach?
>>
>> So much for:
>>
No security, no conditions, don't use it for typesetting serious
2017-09-12 10:08 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> 2017-09-12 1:23 GMT+02:00 Kieren MacMillan :
>>> Hi Harm,
>>>
you could already use 'details.markup-commands
to add space to _both_ sides of a dynamic:
>>>
>>> um… Which version does this require? With 2.19.65, I get
2017-09-12 9:25 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> 2017-09-10 14:43 GMT+02:00 David Kastrup :
>>
>>> More like a nightmare. Some markup expression with some \etc somewhere
>>> in the middle? How many arguments is it supposed to stand for? And
>>> which markup command is it s
Hi Harm,
Is
\dynamicH "text only"
(or something like that) supposed to work? I know I could use
#(make-dynamic-script …) to define a dynamic without any real dynamic font/text
in it — and that's what I'll do in the short-term — but I'd prefer a single
interface for all dynamics, if it's n
Hi David,
>> 1. Is this, speed-wise, any more or less efficient [e.g., on very
>> large scores with lots of combo dynamics] than your other approach?
>
> So much for:
>
>>> No security, no conditions, don't use it for typesetting serious
>>> stuff, just an idea:
>
> Throwing out stuff is just d
Thomas Morley writes:
> 2017-09-12 1:23 GMT+02:00 Kieren MacMillan :
>> Hi Harm,
>>
>>> you could already use 'details.markup-commands
>>> to add space to _both_ sides of a dynamic:
>>
>> um… Which version does this require? With 2.19.65, I get
>>
>> error: syntax error, unexpected '='
>>
Kieren MacMillan writes:
> Harm,
>
>> A very first shot.
>
> You never cease to amaze me!
>
> 1. Is this, speed-wise, any more or less efficient [e.g., on very
> large scores with lots of combo dynamics] than your other approach?
So much for:
>> No security, no conditions, don't use it for type
Thomas Morley writes:
> 2017-09-10 14:43 GMT+02:00 David Kastrup :
>
>> More like a nightmare. Some markup expression with some \etc somewhere
>> in the middle? How many arguments is it supposed to stand for? And
>> which markup command is it supposed to complete? And when is the
>> definitio
Hi Harm,
> Ah, sorry.
> The syntax needs next release. I'm on current master, i.e. 2.21.0.
Cool.
> Below should work:
It does.
Many thanks!!
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
Harm,
> A very first shot.
You never cease to amaze me!
1. Is this, speed-wise, any more or less efficient [e.g., on very large scores
with lots of combo dynamics] than your other approach?
2. If it's [much] more efficient, how easily can the "center-align-on-dynamic"
be implemented? Given th
2017-09-10 14:43 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> 2017-09-03 18:30 GMT+02:00 Thomas Morley :
>>
>>> I think I know how to proceed,
>>
>> @Kieren
>> Attached the newest and heavily revised version.
>> Please read comments for usage.
>>
>> @David
>> For one example I use predef
2017-09-12 1:23 GMT+02:00 Kieren MacMillan :
> Hi Harm,
>
>> you could already use 'details.markup-commands
>> to add space to _both_ sides of a dynamic:
>
> um… Which version does this require? With 2.19.65, I get
>
> error: syntax error, unexpected '='
> \markup customize-dyn
>
Hi Harm,
> you could already use 'details.markup-commands
> to add space to _both_ sides of a dynamic:
um… Which version does this require? With 2.19.65, I get
error: syntax error, unexpected '='
\markup customize-dyn
=
> Though, this gives sufficient output o
2017-09-12 0:03 GMT+02:00 Thomas Morley :
> Hi Xavier,
>
> 2017-09-11 22:05 GMT+02:00 Xavier Scheuer :
>> Thank you Thomas for working on this.
>>
>> Personally I came recently to think that "Doing The Right Thing™"
>> would be to have on option to **align** texts on dynamics.
>>
>> Something like
Hi Xavier,
2017-09-11 22:05 GMT+02:00 Xavier Scheuer :
> Thank you Thomas for working on this.
>
> Personally I came recently to think that "Doing The Right Thing™"
> would be to have on option to **align** texts on dynamics.
>
> Something like
>
> \override TextScript.align-on-simultaneous-dyna
2017-09-11 18:08 GMT+02:00 Kieren MacMillan :
> One new question: Is there an easy way to increase the kerning between a
> dynamic and any non-dynamic text that follows it? (I find the current space
> just a little narrow.) I looked through the code to try to find the right
> place to add a sma
Hi Xavier,
> Personally I came recently to think that "Doing The Right Thing™"
> would be to have on option to **align** texts on dynamics.
>
> Something like
>
> \override TextScript.align-on-simultaneous-dynamic = ##t
>
> and then
>
> c'1\mp_\markup \italic "dolce" % would give "mp dolc
Thank you Thomas for working on this.
Personally I came recently to think that "Doing The Right Thing™"
would be to have on option to **align** texts on dynamics.
Something like
\override TextScript.align-on-simultaneous-dynamic = ##t
and then
c'1\mp_\markup \italic "dolce" % would give "
Hi Harm,
I've had a chance to test some of this new code… and it seems to be working
great! Thank you so much for your amazing work. I'll keep testing and get back
to you.
One new question: Is there an easy way to increase the kerning between a
dynamic and any non-dynamic text that follows it?
Thomas Morley writes:
> 2017-09-03 18:30 GMT+02:00 Thomas Morley :
>
>> I think I know how to proceed,
>
> @Kieren
> Attached the newest and heavily revised version.
> Please read comments for usage.
>
> @David
> For one example I use predefined markup-commands like
> \markup with-red = \markup
2017-09-03 18:30 GMT+02:00 Thomas Morley :
> I think I know how to proceed,
@Kieren
Attached the newest and heavily revised version.
Please read comments for usage.
@David
For one example I use predefined markup-commands like
\markup with-red = \markup \with-color #red \etc
I seem to remember
Hi Kieren,
I now found a conveniant method to adjust the fontsize for
italic/dynamic-font-parts separately.
Ofcourse the aligning was based on the same fontsize for both and is
broken now. So this is next on my TODO-list.
Not sure when I'll have the time to continue, though. I have to work
this we
Hi Harm,
One correction to my answers from last time:
> Will you ever want to have this parts to be not italic but sth else?
>> Ideally, I suppose, all 'usual' text properties could be adjusted… but in my
>> use-cases, I set the main document font, the dynamic 'normal-text' font is
>> always it
2017-09-03 18:14 GMT+02:00 Kieren MacMillan :
> Hi Harm,
>
>> The current structure makes it impossible in a convenient way.
>
> =(
>
>> Tbh, I didn't think of this.
>
> Neither has the Lilypond development team, as far as I can tell: I don't know
> of any way to do it currently (i.e., independent
Hi Harm,
> The current structure makes it impossible in a convenient way.
=(
> Tbh, I didn't think of this.
Neither has the Lilypond development team, as far as I can tell: I don't know
of any way to do it currently (i.e., independent of your new functionality).
> You want to change fontsize
2017-09-03 17:16 GMT+02:00 Kieren MacMillan :
> Hi Harm,
>
> First question: What's the best way to change the font size of the normal
> text *independently* of the font size of the dynamics?
>
> I need (a.k.a. would like) to use this function in different stylesheets
> (with different base fonts
Hi Harm,
First question: What's the best way to change the font size of the normal text
*independently* of the font size of the dynamics?
I need (a.k.a. would like) to use this function in different stylesheets (with
different base fonts), and would prefer to be able to tweak that with a
param
Hi Harm,
> I've now taken this route. Full working code/pdf attached,
> though, there's surely wide room to improve it.
> Usage should be clear from comments and example,
> I'm too tired to do verbose explanations.
This is amazing!
Thank you so much for the hard work — and thanks to everyone who
2017-08-29 14:27 GMT+02:00 Thomas Morley :
> 2017-08-27 22:34 GMT+02:00 David Kastrup :
>
>> You are right that fold-matches is probably not worth the trouble in
>> brain contortion here: processing the result from list-matches should be
>> good enough without overflowing memory.
>
[...]
>
> Though
Hi David,
> I like the chutzpah of this off-the-cuff approximation, though.
Agreed!
As I recall, Graham was never known for a conspicuous lack of chutzpah… ;)
Cheers,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmac
Kieren MacMillan writes:
> Hi Xavier,
>
>> For correct alignment of "dynamic + text" (or "text + dynamic") I used
>> to rely on Graham's "make-dynamic-extra" function, which worked well.
>
> It's hardly perfect, though — for example, the dynamic isn't centred
> correctly here:
>
> %%% SNIPPET B
Hi Xavier,
> For correct alignment of "dynamic + text" (or "text + dynamic") I used
> to rely on Graham's "make-dynamic-extra" function, which worked well.
It's hardly perfect, though — for example, the dynamic isn't centred correctly
here:
%%% SNIPPET BEGINS
\version "2.19.64"
#(define (make-
On 16 August 2017 at 03:50, Kieren MacMillan
wrote:
>
> Hello all,
>
> The snippet below includes Janek's \dynamic function, which has a rather
lovely interface.
> Unfortunately, it doesn't align leading dynamics as expected (i.e.,
centered on the notehead).
>
> What's the easiest way to fix the f
2017-08-29 14:27 GMT+02:00 Thomas Morley :
> 2017-08-27 22:34 GMT+02:00 David Kastrup :
>
>> You are right that fold-matches is probably not worth the trouble in
>> brain contortion here: processing the result from list-matches should be
>> good enough without overflowing memory.
>
>
>
> I now come
2017-08-27 22:34 GMT+02:00 David Kastrup :
> You are right that fold-matches is probably not worth the trouble in
> brain contortion here: processing the result from list-matches should be
> good enough without overflowing memory.
I now come up with (only markup again):
#(define-markup-command
Thomas Morley writes:
> 2017-08-27 11:56 GMT+02:00 David Kastrup :
>
>> I was more thinking along the lines of
>>
>> #(define-markup-command (dyn-test layout props strg) (markup?)
>> (define (fixstring arg)
>> (let ((res (fold-matches "\\{[^{}*\\}" arg '(0)
>> (lambda (m prev)
2017-08-27 11:56 GMT+02:00 David Kastrup :
> I was more thinking along the lines of
>
> #(define-markup-command (dyn-test layout props strg) (markup?)
> (define (fixstring arg)
> (let ((res (fold-matches "\\{[^{}*\\}" arg '(0)
> (lambda (m prev) ...
> (define (fixtree arg)
>
Thomas Morley writes:
> 2017-08-26 21:35 GMT+02:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> 2017-08-26 20:24 GMT+02:00 David Kastrup :
Uh, this was a proposal for a user interface that does not need to look
at punctuation etc but rather goes by [...] for figuring out where
2017-08-27 10:40 GMT+02:00 Thomas Morley :
> #(define (split-string strg char-pair)
> ;; split a string at all occurrences of both characters in char-pair
> ;; remark: with guilev2 string-split accepts a char-set as second argument
> (append-map
> (lambda (s) (string-split s #\}))
> (str
2017-08-26 21:35 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> 2017-08-26 20:24 GMT+02:00 David Kastrup :
>>>
>>> Uh, this was a proposal for a user interface that does not need to look
>>> at punctuation etc but rather goes by [...] for figuring out where the
>>> "true" dynamics are, lik
Thomas Morley writes:
> 2017-08-26 20:24 GMT+02:00 David Kastrup :
>>
>> Uh, this was a proposal for a user interface that does not need to look
>> at punctuation etc but rather goes by [...] for figuring out where the
>> "true" dynamics are, likely defaulting to taking the first pair for
>> alig
2017-08-26 20:24 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> 2017-08-26 16:10 GMT+02:00 David Kastrup :
>>> Thomas Morley writes:
>>
the here so far proposed codes fail, if punctuation comes into the game.
\new Staff { c''\dynamic "poco f, but p sub. ma non troppo" }
>>>
>>>
Thomas Morley writes:
> 2017-08-26 16:10 GMT+02:00 David Kastrup :
>> Thomas Morley writes:
>
>>> the here so far proposed codes fail, if punctuation comes into the game.
>>> \new Staff { c''\dynamic "poco f, but p sub. ma non troppo" }
>>
>> \dynamic "poco [f], but [p] sub. ma non troppo" ?
>
2017-08-26 16:10 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>> the here so far proposed codes fail, if punctuation comes into the game.
>> \new Staff { c''\dynamic "poco f, but p sub. ma non troppo" }
>
> \dynamic "poco [f], but [p] sub. ma non troppo" ?
Hi David,
not sure what you want
Thomas Morley writes:
> 2017-08-25 0:01 GMT+02:00 Kieren MacMillan :
>> Hi Saul,
>>
>>> Personally, I think the behavior would be better if it aligned on
>>> the first dynamic to appear in the markup, rather than default to
>>> left.
>>
>> Perhaps better if this is a preference/parameter, with th
2017-08-25 0:01 GMT+02:00 Kieren MacMillan :
> Hi Saul,
>
>> Personally, I think the behavior would be better if it aligned on the first
>> dynamic to appear in the markup, rather than default to left.
>
> Perhaps better if this is a preference/parameter, with the default being
> *left-aligned* n
Hi Saul,
> Personally, I think the behavior would be better if it aligned on the first
> dynamic to appear in the markup, rather than default to left.
Perhaps better if this is a preference/parameter, with the default being
*left-aligned* not *dynamic-aligned*.
(I would personally keep it left-
Thanks for putting that together. I'm no Scheme expert, but it looks good
to me.
Personally, I think the behavior would be better if it aligned on the first
dynamic to appear in the markup, rather than default to left. With
something like "poco f", it can be visually unclear where the f is suppose
Hello,
I'm almost embarassed to post this as it's the ugly result of "trying to
learn scheme and lilypond internals all at the same time" - but at least it
seems to work. I've tried to achieve exactly what you described: _If_ the
first word is a dynamic expression, then Shevek's adjustment is appl
Hi Shevek,
> I posted a snippet to do correct custom dynamic alignment a month or so ago.
Yes, I know. I like the alignment very much.
But I prefer Janek's interface, which offers the ability to put an arbitrary
string (e.g., "poco f, but p sub. ma non troppo") and it Does The Right Thing™…
we
I posted a snippet to do correct custom dynamic alignment a month or so ago.
I haven't had time to integrate it into the OpenLilyLib snippet, but here's
my code:
\version "2.18.2"
dynText = #(define-event-function (parser location dyn expr) (markup?
markup?)
(let* (
Hello all,
The snippet below includes Janek's \dynamic function, which has a rather lovely
interface.
Unfortunately, it doesn't align leading dynamics as expected (i.e., centered on
the notehead).
What's the easiest way to fix the function so that it does?
Thanks,
Kieren.
%%% SNIPPET BEGINS
58 matches
Mail list logo
