Hi,
Great! This is the perfect solution. I had to adjust the
(define-scheme-function) call a bit to run also under 2.18:
setStructuralVoice = #(define-scheme-function (parser location num) (integer?)
(make-apply-context
(lambda (context)
(ly:context-set-property! context 'structur
Maurits Lamers writes:
> Hi,
>
> Great! This is the perfect solution. I had to adjust the
> (define-scheme-function) call a bit to run also under 2.18:
>
> setStructuralVoice = #(define-scheme-function (parser location num) (integer?)
> (make-apply-context
> (lambda (context)
> (ly:
Hi Maurits,
Am 20.08.20 um 11:10 schrieb Maurits Lamers:
Hi,
Great! This is the perfect solution. I had to adjust the
(define-scheme-function) call a bit to run also under 2.18:
setStructuralVoice = #(define-scheme-function (parser location num) (integer?)
(make-apply-context
(lambda
Would someone please explain \accidentalStyle dodecaphonic in the following:
\score {
\new Staff { \treble }
\layout {
\context {
\Score
\accidentalStyle dodecaphonic
}
}
}
This is what found in the manuals, "A predefined command such as
\dynamicUp or a music ex
Lukas-Fabian Moser writes:
> Hi Maurits,
>
> Am 20.08.20 um 11:10 schrieb Maurits Lamers:
>> Hi,
>>
>> Great! This is the perfect solution. I had to adjust the
>> (define-scheme-function) call a bit to run also under 2.18:
>>
>> setStructuralVoice = #(define-scheme-function (parser location num)
See
http://lilypond.org/doc/v2.21/Documentation/notation-big-page.html#automatic-accidentals
--
Phil Holmes
- Original Message -
From: "Freeman Gilmore"
To: "Lilypond-User Mailing List"
Sent: Thursday, August 20, 2020 1:55 PM
Subject: \accidentalStyle dodecaphonic
Would someone p
Hi,
Nevertheless, I'd urge you to try and make sure that everything you
develop will work with current LilyPond versions. Not only in order to
lower the barrier for developers to help you (or others to make use of
your additions), but also because LilyPond simply has evolved a great
deal in the
Hi all,
@David: No, I haven't attempted to run convert-ly and I am very hesitant to do
so because I have no clue exactly where to start. That is because it is a
songbook with over 1000 songs, with choir arrangments and organ parts for each
of those songs, with many complex includes and external
Maurits Lamers writes:
> Hi all,
>
> @David: No, I haven't attempted to run convert-ly and I am very
> hesitant to do so because I have no clue exactly where to start. That
> is because it is a songbook with over 1000 songs, with choir
> arrangments and organ parts for each of those songs, with m
Hi everyone.
In typesetting chamber music with accompaniment, I would like to print
the tempo marks on the bottom staff.
Unfortunately, a tempo change produces a lot of space upon the bottom
staff, until the last tempo mark.
I think that a similar issue has already been discussed two years ago
Hey,
>
> Computers have this wonderful facility called a "copy".
I know, and also version systems like git :)
>
>> I would definitely love to bring the entire system to the most recent
>> version of Lilypond, or at least 2.18.2 (which is the version
>> installed by default under Ubuntu 18.04LTS
Hi Francesco,
> Unfortunately, a tempo change produces a lot of space upon the bottom
> staff, until the last tempo mark.
Try
> \layout {
> \context {
>\name "MarkLine"
>\type "Engraver_group"
\RemoveAllEmptyStaves
...
That seems to work for me.
Hope that helps!
Kieren.
_
I have just spent half a day trying to work out why one staff in my
orchestral score extends beyond the final barline.
Eventually I found out that it is because \partCombine seems only
partially to understand tags.
The following example illustrates this:
%
\version "2
David Sumbler writes:
> I have just spent half a day trying to work out why one staff in my
> orchestral score extends beyond the final barline.
>
> Eventually I found out that it is because \partCombine seems only
> partially to understand tags.
That is a misstatement. \partCombine does not us
Thanks for the reply.
It removes the blank space, but, unfortunately, the tempo marks too!
Il giorno gio 20 ago 2020 alle ore 19:13 Kieren MacMillan
ha scritto:
>
> Hi Francesco,
>
> > Unfortunately, a tempo change produces a lot of space upon the bottom
> > staff, until the last tempo mark.
>
>
Hi,
> Thanks for the reply.
> It removes the blank space, but, unfortunately, the tempo marks too!
Oops!
\RemoveAllEmptyStaves
keepAliveInterfaces = #'( metronome-mark-interface )
That should do it. =)
Cheers,
Kieren.
Kieren MacMillan, composer (he/him/
On Thu, 2020-08-20 at 20:06 +0200, David Kastrup wrote:
> David Sumbler writes:
>
> > I have just spent half a day trying to work out why one staff in my
> > orchestral score extends beyond the final barline.
> >
> > Eventually I found out that it is because \partCombine seems only
> > partial
It works perfectly on the test file.
On the real score it prints just the tempo marks in the first system,
I don't understand why...
Anyway, I will write the second tempo as a markup.
Thanks a lot!
F.
Il giorno gio 20 ago 2020 alle ore 20:31 Kieren MacMillan
ha scritto:
>
> Hi,
>
> > Thanks for t
> "David" == David Sumbler writes:
David> What I should like to know is 1) how can I use drum and other
David> untuned percussion sounds? 2) I notice that fluidr3_gm has
David> dozens - probably hundreds - of extra sounds and instruments
David> beyond the standard 128. How can I access the
-- Forwarded message -
From: Freeman Gilmore
Date: Thu, Aug 20, 2020 at 4:14 PM
Subject: Re: \accidentalStyle dodecaphonic
To: Phil Holmes
On Thu, Aug 20, 2020 at 9:21 AM Phil Holmes wrote:
>
> See
> http://lilypond.org/doc/v2.21/Documentation/notation-big-page.html#automatic-a
Sets the accidental style to dodecaphonic - every single note displays
an accidental. Used by early Serialists, and a good number of modernist
composers. All my scores use it exclusively.
From the NR under Accidentals:
This rule reflects a practice introduced by composers at the beginning
of
21 matches
Mail list logo