I've attached the snippet I use for metric modulation markings. Hopefully
others find it useful.
To use it you would write something like:
\metricMark { \tuplet 3/2 { r8*2 c8 } } { c16 r16*3 } "Più tranquillo" #108
FYI – there are some issues with spacing if the marking is at a line break.
On
On 12/20/2018 2:27 PM, Ld2020 wrote:
I am notating some rhythms that use metric modulations (a.k.a. tempo
modulations).
I am indicating that a triplet quarter becomes the new quarter note.
What I want is a single quarter note with a triplet mark over it (3
and a bracket, spaced in such a way as
I am notating some rhythms that use metric modulations (a.k.a. tempo
modulations).
I am indicating that a triplet quarter becomes the new quarter note.
What I want is a single quarter note with a triplet mark over it (3
and a bracket, spaced in such a way as to make it obvious this is one
third
Am 19.12.18 um 21:56 schrieb Michael Gerdau:
First step would be running Frescobaldi from its Git repository
(and at that occasion test if the description is accurate and also works
for Windows 10):
https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-from-Git-on-Windows
Commenting as
On Thu, 20 Dec 2018 at 13:35, David Kastrup wrote:
> Gianmaria Lari writes:
>
> >> Uh, there is a difference between \markup and \mark .
> >
> >
> > I put \mark just to make things more interesting. I'm joking.
> > Shit! I made the usual stupid mistake that's perfect to complicate
> >
Gianmaria Lari writes:
>> Uh, there is a difference between \markup and \mark .
>
>
> I put \mark just to make things more interesting. I'm joking.
> Shit! I made the usual stupid mistake that's perfect to complicate
> things :(
>
>
>> Once you fixed
>> that, your counter will be reset
> Uh, there is a difference between \markup and \mark .
I put \mark just to make things more interesting. I'm joking.
Shit! I made the usual stupid mistake that's perfect to complicate
things :(
> Once you fixed
> that, your counter will be reset to 0 for each invocation of the
>
Urs Liska writes:
>>>(set! counter (1+ counter))
>
> And it must be
>
> (set! counter (+ 1 counter))
>
> (first the procedure "+", then the arguments)
Have you tried? 1+ is defined as a function taking one argument.
Scheme has a lot less restrictions on identifier names than some
On Thu, 20 Dec 2018 at 13:12, Gianmaria Lari
wrote:
>
>
> On Thu, 20 Dec 2018 at 13:10, Urs Liska wrote:
>
>>
>>
>> Am 20. Dezember 2018 13:02:22 MEZ schrieb David Kastrup :
>> >Gianmaria Lari writes:
>> >
>> >> %alternate version
>> >> \version "2.19.82"
>> >> nextcount =
>> >> #(let
On Thu, 20 Dec 2018 at 13:10, Urs Liska wrote:
>
>
> Am 20. Dezember 2018 13:02:22 MEZ schrieb David Kastrup :
> >Gianmaria Lari writes:
> >
> >> %alternate version
> >> \version "2.19.82"
> >> nextcount =
> >> #(let ((counter 0))
> >> (lambda ()
> >>(set! counter (1+ counter))
Am 20. Dezember 2018 13:02:22 MEZ schrieb David Kastrup :
>Gianmaria Lari writes:
>
>> %alternate version
>> \version "2.19.82"
>> nextcount =
>> #(let ((counter 0))
>> (lambda ()
>>(set! counter (1+ counter))
>>(number->string counter)))
>>
>> \markup #(nextcount)
>>
Gianmaria Lari writes:
> %alternate version
> \version "2.19.82"
> nextcount =
> #(let ((counter 0))
> (lambda ()
>(set! counter (1+ counter))
>(number->string counter)))
>
> \markup #(nextcount)
> \markup #(nextcount)
>
>
> I would like to know if it is possible to write
Periodically I spend some time on lilypond/scheme hoping to understand a
bit more how use them together. This is what I these days.
I tried to write in different way the function nextcount that return a
number, as a string, increased by one each time you call it.
%standard version
\version
Folks,
this is mostly to give a reference to those who might hit the same
problems that I had:
I decided to switch from my ancient Linux Mint 17.3 to Linux Mint 19.1
yesterday. In order to set up a working build environment, I had to
provide a working Guile 1.8 which seems not to be in the
>
> []
>
> For me these are not enough clear to understand the problem. Is there any
> way to get a more precise indication of the error I did?
>
> Yes, by reading the whole output ;-) Sorry for sounding harsh, I agree
> that it is non-intuitive. But often the messages for "GUILE signaled an
>
Am 20.12.18 um 10:52 schrieb Gianmaria Lari:
This program does not compile because myvar is not defined.
\version "2.19.82"
test = #(cond
((= myvar 0) "zero")
((= myvar 1) "one")
)
\markup \test
And this is the fixed version
\version
This program does not compile because myvar is not defined.
\version "2.19.82"
test = #(cond
((= myvar 0) "zero")
((= myvar 1) "one")
)
\markup \test
And this is the fixed version
\version "2.19.82"
myvar = 1
test = #(cond
((= myvar 0) "zero")
((=
17 matches
Mail list logo
