Hi Kieren,
for-some-music does not return music. It works on music in-place. So
the last thing in your music function must not be for-some-music but
rather the music that you have been working on.
So…
%%% SNIPPET BEGINS
adjustPitch =
#(define-music-function (pitchIn pitchOut music) (ly:pitc
Hi David,
If you don't want to call upon undocumented internals of LilyPond (the
(@@ (lily) ...) bit), you can just use
[with-output-to-string]
Wow, thanks! I hadn't encountered this possibility yet.
Also thanks for pointing out the possibility of in-place modification.
Lukas
The last "m" in your innermost (if ...) is unnecessary: As with the
difference between "for" and "map" in plain Scheme, the return value of
the lambda function in for-some-music gets discarded ("for" functions
are supposed to _do_ something, not _return_ something).
No, it doesn't. It is a boole
Hi Lukas!
Thanks for the patient and helpful tutorial(s). :)
> The last "m" in your innermost (if ...) is unnecessary: As with the
> difference between "for" and "map" in plain Scheme, the return value of the
> lambda function in for-some-music gets discarded ("for" functions are
> supposed t
Wondering if it's possible to override the behavior of the glide line such that
the glide will draw to the next fingering regardless of what the second number
is.
- Fennel
On Thursday, May 30th, 2024 at 12:28 AM, Werner LEMBERG wrote:
>
>
> > I was looking for something like "shift line"
Am So., 23. Juni 2024 um 19:48 Uhr schrieb Fennel :
>
>
> Wondering if it's possible to override the behavior of the glide line such
> that the glide will draw to the next fingering regardless of what the second
> number is.
>
> - Fennel
It's not possible. Think of chords with multiple fingering
The LSR looks like it's down. I don't know who is responsible for it so I
thought I'd just post here.
--
Knute Snortum
> The LSR looks like it's down. I don't know who is responsible for
> it so I thought I'd just post here.
Thanks. I've written an e-mail to Sebastiano.
Werner