So for now I will use this workaround :
\version "2.25.8"
tempoChange =
#(define-music-function (interval endscale thenscale music)
(ly:duration? scale? (scale? 1) ly:music?)
"Make a gradual tempo change over @var{music}, essentially changing
speed after
every duration of @var{interval},
M(core dumped)WE pretty please :
tempoChange =
#(define-music-function (interval endscale thenscale music)
(ly:duration? scale? (scale? 1) ly:music?)
"Make a gradual tempo change over @var{music}, essentially changing
speed after
every duration of @var{interval}, approaching a factor of
Well, I think my code structure is the problem.
The way I create parts is with this part generator this way :
#(typicalPart 'piccolo piccolo structure)
And for *every* part (instrument) it merges my \structure variable
(\mark, \tempo, i.e. what every body in the orchestra needs) with the
music
Not quite there yet.
Now I get :
warning: the property 'tempoWholesPerMinute' must be of type 'positive
moment with no grace part', ignoring invalid value '#'
Le mer. 23 août 2023, à 09 h 45, David Kastrup a écrit :
>
> Pierre-Luc Gauthier writes:
>
> > And what do you know :
> >
> > git diff
Pierre-Luc Gauthier writes:
> And what do you know :
>
> git diff to the rescue.
> -
> +\include "articulate.ly"
> -<<
> + \articulate <<
>
> I tried different avenues and \articulate seems to have creeped its
> way in in this floating point exception core dump…
>
> 'No idea why though nor
And what do you know :
git diff to the rescue.
-
+\include "articulate.ly"
-<<
+ \articulate <<
I tried different avenues and \articulate seems to have creeped its
way in in this floating point exception core dump…
'No idea why though nor do I need \articulate anyway. closing.
> > > No
> > No MWE for now but will provide if needed.
> Can you think of a case where it wouldn't be needed?
Silly me :-)
\version "2.25.8"
tempoChange =
#(define-music-function (interval endscale thenscale music)
(ly:duration? scale? (scale? 1) ly:music?)
"Make a gradual tempo change over
Pierre-Luc Gauthier writes:
> I'm not quite sure how to use it correctly yet but I suppose a typical
> usage would be :
>
> \time 6/8 % btw
>
> \tempoChange 8 1/2 0 {
> \skip 2.*4 |
> }
>
> ^ I.e. : To slow down every 8th during 2.*4 to reach (and keep (0)) a
> tempo half the speed it
I'm not quite sure how to use it correctly yet but I suppose a typical
usage would be :
\time 6/8 % btw
\tempoChange 8 1/2 0 {
\skip 2.*4 |
}
^ I.e. : To slow down every 8th during 2.*4 to reach (and keep (0)) a
tempo half the speed it was.
I get inconsistent results either :
-
Thank you all very much - yes, I know about potrace, although I haven't
used it yet. However, the \image command sounds like more the sort of
thing I wanted - just a cheap and dirty method of inserting images to see
(roughly) what they might look like.
cheers,
Alasdair
On Wed, 23 Aug 2023 at
Le mercredi 23 août 2023 à 13:57 +0200, Jean Abou Samra a écrit :
>
> The tool looks quite impressive. OTOH, in 2.25, there's \image to use
> a PNG file, so you don't necessarily need to convert the bitmap to a
> vector graphics form.
(And EPS can contain bitmaps too.)
signature.asc
Le mercredi 23 août 2023 à 11:40 +, Werner LEMBERG a écrit :
> > I am slowly creating a font to be used for tablature ... so far I
> > have bitmaps of a couple of characters. I'd like to try them out
> > and get an idea how they look. Is there any way I can replace a
> > character with a
> I am slowly creating a font to be used for tablature ... so far I
> have bitmaps of a couple of characters. I'd like to try them out
> and get an idea how they look. Is there any way I can replace a
> character with a small scaled bitmap?
Not directly. You would have to convert the bitmap
I am slowly creating a font to be used for tablature ... so far I have
bitmaps of a couple of characters. I'd like to try them out and get an
idea how they look. Is there any way I can replace a character with a
small scaled bitmap?
I know that Lilypond doesn't support bitmapped fonts, but as I
Hi Joseph,
On Mon, Aug 21, 2023 at 8:08 PM Joseph Srednicki
wrote:
> Hello:
>
> When coding organ pieces, I want the registration to appear following the
> header.
>
> In the following example, I inserted the registration in a markup block
> before the score block. When Lilypond renders the
15 matches
Mail list logo
