Re: Attaching markup to high-level objects

[Peekay Ex]

Jim,

On Sun, Nov 13, 2011 at 9:57 AM, Jim Long <address@hidden> wrote:
> Thank you very much, James.

No problem - don't forget to cc the list so others see the reply that
may contain more information for them to assist.

>

> I'll take an earnest look at your suggestion in the morning.  I
> do recall hitting a wall once when I discovered that Lily won't
> accept two consecutive 'mark' directives, like for a
>
> \mark default
> \mark \markup \musicglyph #"scripts.segno"
>
> when you want to have rehearsal letter A and a Segno at the same
> location.  I have noticed the \concat and \column operators, so
> maybe using \column like
>
> \mark \markup \column { { \musicglyph #"scripts.segno" } { \mark default } }
>
> is the way to put a Segno vertically aligned over a rehearsal letter?

See:

http://lsr.dsi.unimi.it/LSR/Item?id=735

and

http://lsr.dsi.unimi.it/LSR/Item?id=736

another example

http://lsr.dsi.unimi.it/LSR/Item?id=575

more complex

http://lsr.dsi.unimi.it/LSR/Item?id=202

I'll leave the rest of this email intact for others to read.

>
> I'm attaching my latest project as a thank-you and an example of
> my learning curve.  It's not real clean inside, but it shows
> where I am presently with figuring out how to have clean, modular
> arrangements with pertinent markup in the right places.  My
> current method is to use a lot of extra-offset overrides.  The
> example is all the more cluttered because I discovered I didn't
> have quite the right repeat pattern, and had to shuffle the last
> note (high G) and a Cmaj7 chord out of the 'head' and into each
> of the four endings.  The second ending is ONLY that bar, so that
> pretty much dictates that they all have to have that bar plus 0
> or more bars.  Listen to the MP3 and follow the chart and you'll
> see what I mean.  I could have 'unrolled' the repeats and D.S.,
> but a) that would probably put it beyond two pages, and b) some
> players I know definitely like seeing the percent repeats and
> bar-and-dot repeats, because it tells them that the music is
> exactly the same the next time, whereas having it all written out
> again makes them have to read it again.  They like the
> confirmation of repetition versus a written out variation of the
> previous themes.
>
> Joe Sample's 1978 recording of this tune is at:
>
> http://umpquanet.com/james/01-Rainbow_Seeker.mp3
>
> My intent is just to say thank you and to show how I'm coping
> with text placement currently.  The obvious problem is, that as
> soon as I change the staff size a little to make the score fill
> more space or less space or just adjust a line break or two, then
> all my 'extra-offset' values are wrong and I have to re-position
> several text strings by trial and error.  When I express a
> section of music as music expression that may be 8 or 16 bars
> long, like:
>
> \head
> \bar "|."
>
> then my options for placing markup are either before the head or
> after it.  So if "head" occurs in one place with one sort of
> markup and another place with a softer or slower expression
> direction, and a third place with a piu mosso at the beginning
> and a rallantando at the end, it becomes hard to keep the 'head'
> definition clean and place different markup on the three or more
> places where it occurs.  Also, you can see that the extra-offset
> method seems to stretch staff spacing around volte and such.
>
> The intro motif on "Rainbow Seeker" occurs once as the intro, in
> a 3x repeat, and again between the head and the solo, but with
> only a 1x repeat.  Then largely the same rhythm appears again
> after the solo and before the restatement of the head, and once
> again at the coda/fourth ending.
>
> BTW, is there any hope for my suggestion of being able to use a
> 'chordmode' section as a RhythmicStaff music expression without
> getting the funny doubled note heads from the pitch-collapse
> engraver?
>
> Anyway, cheers, and thanks for the new arrows in my quiver.
>
> Regards from Portland,
>
> Jim
>
>
> On Sun, Nov 13, 2011 at 08:20:09AM +0000, Peekay Ex wrote:
>> Hello,
>>
>> On Sun, Nov 13, 2011 at 2:35 AM,  <address@hidden> wrote:
>>
>>
>> > Failing that, if there were a way to attach markup to a bar line,
>> > that (plus perhaps an 'extra-offset') would suffice in the majority
>> > of situations I can think of.
>> >
>> > Is there such a way to attach markup to a high-level music
>> > expression or a bar line, rather than just a low-level simple
>> > music element, like a note or rest?
>>
>> \version "2.14.2"
>>
>> \relative c' {
>>   \once \override Staff.Clef #'break-align-symbols = #'(clef)
>>   \mark "Clef"
>>   a'4 b c d |
>>   \key ees \major
>>   \once \override Staff.KeySignature #'break-align-symbols = 
>> #'(key-signature)
>>   \mark "Key Sig"
>>   e f g a |
>>   \once \override Staff.BarLine #'break-align-symbols = #'(bar)
>>   \mark "Barline"
>>   g f e d |
>> }
>>
>> See:
>>
>> http://lilypond.org/doc/v2.14/Documentation/notation/writing-text#text-marks
>>
>> Specifically the snippet
>>
>> 'Aligning marks with various notation objects' down the page
>>
>>
>>
>> --
>> --
>> James
>



-- 
--
James