Steven Weber wrote
> [...]
> which works great for everything except the multi-measure case. Your
> brilliant override below fixes the multi-measure case as well. Thanks!
better praise the developers who provide functions for even such rare cases!
Eluze
--
View this message in context:
htt
Keith OHara writes:
> Mario Bolognani fastwebnet.it> writes:
>
>>
>> staffs are are not separated as specified.
>
> When you ask LilyPond to make the tuplet number transparent
> terzinesenza = \override TupletNumber #'transparent = ##t
> she gives the number the usual space.
Pffft. The Tupl
Turns out it's not the time signature that's causing the problem, it's the
clef of the second staff.
\once \override Score.TimeSignature.stencil = ##f
\once \set Staff.explicitKeySignatureVisibility = #end-of-line-invisible
\once \set Score.explicitClefVisibility = #end-of-line-invisible
And the
Mario Bolognani fastwebnet.it> writes:
>
> staffs are are not separated as specified.
When you ask LilyPond to make the tuplet number transparent
terzinesenza = \override TupletNumber #'transparent = ##t
she gives the number the usual space.
To understand the space between the staves you can
Colin Campbell writes:
> In looking over your files, I see you are making a lot of changes to
> spacing, particularly system-system values, and perhaps this is the
> cause of your problems starting around measure 89. Because there has
> been a lot of work done in the spacing mechanisms of LilyPon
On 11/05/2013 12:34 AM, Mario Bolognani wrote:
Version 2.16.2 and 2.17.95 do not compile correctly
staffs are are not separated as specified.
Sorry for the long annex, but it’s difficult for me to isolate the bug. Suspect
it is in the type of fractions used with the feature “times”.
In orde
I'm currently using:
\once \set Staff.explicitKeySignatureVisibility = #end-of-line-invisible
\once \override Staff.TimeSignature.stencil = ##f
which works great for everything except the multi-measure case. Your
brilliant override below fixes the multi-measure case as well. Thanks!
I'm still
Steven Weber wrote
you can add
\override MultiMeasureRest.#'spacing-pair = #'(staff-bar . staff-bar)
to have the mmrest ignore the space taken by the TimeSignature
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Multi-measure-rests-before-a-new-temporary-staff-is
Werner LEMBERG writes:
>> All previous versions didn’t work. See annexes.. Please, try to
>> compile rebel_elemens_score.ly and see what happens...
>
> Which annexes? There is not a single attachment. In case you have
> difficulties with attachments, can you post it somewhere, providing a
> lin
Here is the link: https://www.dropbox.com/sh/gn7h2tfvkaeqmju/wIR7yRWaLr
Mario Bolognani
Via Celimontana, 15
I-00184 Roma
tel. studio: 06-77200380
cell: 348-3363833
fax: 06-233211272
email: mario.bologn...@unito.it
ma...@fastwebnet.it
www.baroquemusic.it
Il giorno 05/nov/2013, a
> All previous versions didn’t work. See annexes.. Please, try to
> compile rebel_elemens_score.ly and see what happens...
Which annexes? There is not a single attachment. In case you have
difficulties with attachments, can you post it somewhere, providing a
link?
Werner
__
All previous versions didn’t work. See annexes.. Please, try to compile
rebel_elemens_score.ly and see what happens...
Thank you for collaboration
Mario Bolognani
Mario Bolognani
Via Celimontana, 15
I-00184 Roma
tel. studio: 06-77200380
cell: 348-3363833
fax: 06-233211272
email: mario.b
Mario Bolognani writes:
> Version 2.16.2 and 2.17.95 do not compile correctly
> staffs are are not separated as specified.
>
> Sorry for the long annex, but it’s difficult for me to isolate the
> bug. Suspect it is in the type of fractions used with the feature
> “times”.
There is no attachment
On Nov 5, 2013, at 3:01 AM, Steven Weber wrote:
> Laziness. The movement I'm typesetting is 600+ measures long with tons of
> time changes, and only 15 measures of that are split. That's why LP allows
> this kind of construct in the first place, no? Because we still don't have
> a good way to
Steven Weber wrote
> Laziness. The movement I'm typesetting is 600+ measures long with tons of
> time changes, and only 15 measures of that are split. That's why LP
> allows
> this kind of construct in the first place, no? Because we still don't
> have
> a good way to say "skip the next 500 meas
15 matches
Mail list logo