lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multi-measure rests and mark collisions ...


From: Wols Lists
Subject: Re: Multi-measure rests and mark collisions ...
Date: Sat, 23 Apr 2016 11:25:05 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0

On 22/04/16 19:36, David Wright wrote:
> On Fri 22 Apr 2016 at 15:47:59 (+0100), Anthonys Lists wrote:
>> On 22/04/2016 14:31, Kieren MacMillan wrote:
>>> David K wrote:
>>>>> Hm?  How could you even have a compressed multi-measure rest when there
>>>>> is anything like an "8-bar phrase" in parallel?
>>>>> That sounds like a problem that cannot occur.
>>> I assume Wol (like me) has the problem where the compressed rest happens in 
>>> the part, not in the full score — but one wants not to have to use multiple 
>>> \tag constructs just to handle this issue.
>> Exactly... I write my music with "voiceStaff" to contain all the
>> score-level stuff eg tempi, tune names, rehearsal marks etc, and
>> "voiceInstrument" to contain the stuff that varies by instrument, eg
>> notes, dynamics, anything else like that ...
>>
>> In the case example, the phrase is eight bars long, commencing with
>> a two-bar rest. For another instrument, it won't have a rest. And I
>> don't want the output to change dramatically depending on what's in
>> the part.
>>
>> So of course, because voiceStaff is not meant to contain notes, it
>> uses "s" all the time. And I very rarely produce scores, this case
>> is absolutely typical for me in that we only have a bass-clef part,
>> and because while some players in our section can read both, we have
>> some players who can only read bass or treble clef so transposing is
>> a regular requirement. So I'll have three parts to do, 1st, 2nd and
>> bass.
> 
> I haven't followed all that. Is this the sort of thing you want?
> 
Pretty much. In your example it's exactly okay - the "poco allegretto"
is to the right of the rehearsal mark, so the four marks take three
lines to display. (Note I tend to use box-barnumber, so my rehearsal
marks can get quite wide :-)

Now, imagine the "poco allegretto" and "This is the army mr jones" were
the other way round - the "This" would collide with the rehearsal mark,
and it would take four lines.

I want some semi-automatic way so I can push the other markup to the
right of the rehearsal mark and make sure I only use three lines. Oh -
and if I use "extra-spacing-width" (which iirc works fine with
multi-measure-rests), as soon as I have another part which actually has
some notes in the first bar of the MMR, that first bar will be the same
width as the markup so that then looks awful :-(

The problem really is, all I want to do is stick multiple marks on a
barline (which doesn't work, lily doesn't do multiple \mark's :-(, and I
want to be able to move those markups to the right so they don't collide
with the rehearsal mark. \tempo *partly* solves my problem. The trouble
is, all the tweaks I've come up with (like for example "s1 s1*11") all
have side effects that don't matter in certain cases, and matter
enormously in others.

As Kieren said, this stuff is generic across all parts, so he and I want
to store it in a generic variable that then gets merged with the notes.
But there doesn't appear to be a syntax that isn't crucially dependent
on the notes being merged, other than filling the generic variable with
a whole bunch of special-case formatting tags, which totally misses the
point of having a generic variable :-( (plus I haven't used tags yet,
another learning curve ...)

Cheers,
Wol




reply via email to

[Prev in Thread] Current Thread [Next in Thread]