Re: GDP: LM 3-4

[Graham Percival]

On Fri, 8 Feb 2008 19:44:02 -0500
"calvin mitcham" <address@hidden> wrote:

> now that i'm
> trying to help, i'll ramble out loud here a little... to just read
> these sections is confusing and boring. the tweaking is especially
> hard to read. i mean i hardly ever have an issue about how lilypond
> engraves, and when it is different than what i'm transcribing, i
> usually don't care.

I'm generally the same way.  :)

But let's try to un-ramble a bit:
- is the tutorial clear?  (I don't think anybody has complained
  about this, but I can never be certain -- if you haven't done so
  recently, please read the tutorial and try to remember what
  things confused you in the beginning.)
- is LM 3 Fundamental clear?

Given your stated interest, I suggest you just focus on that for
now.  If you're happy with lilypond output, then LM 4 Tweaks is
almost completely pointless... and I know from great experience
that it's really difficult to read *any* documentation (or,
*cough*, textbook :)  if you're not interested in the subject
and/or don't see an application of that knowledge.

> i was proud/relieved recently, when after ~10 minutes of targetted
> study, i got a
> 
> \once \override Score.MetronomeMark #'padding = #4
> \tempo 4=88
> \set Score.skipBars = ##t R1*3

As a historical sidenote, try looking at the mailist archives from
5 or more years ago.  Having a relatively new user being able to
figure this out in 10 minutes is a *huge* improvement in the docs.

> to move the tempo marking above the "3" for the multi-measure rest.
> when given a specific problem to solve like this, the lm and nr docs
> are quite helpful. i had to get the naming convention, which
> engraver, and the property, and it worked out pretty quickly. but to
> just peruse the list of objects and properties is painful.

With doc sections like LM 4.5.2, we've tried to make it so that
you don't need to peruse the list of objects in the IR.  It'll
never be perfect, of course.

>  now file structure is another confusing subject where again i have no
> sugesstion, but i do wish it were easier for the newbie. i worked on a
> couple of pieces for hours trying to use includes etc to completely
> minimize the amount of repeating any typing, such as putting music
> notes for violin, pianoright and pianoleft in separate files, the
> combining to print a score, a piano part with reduced violin above,
> and a violin by itself. i got something passable, but never nailed
> where some things. for example, i could not get a piano with smaller
> violin staff without repeating the violin music with a smaller staff,
> or having the violin part not show fingerings in the piano printout.

Again, please read LM 3 in detail, and let us know exactly which
section was confusing.  ie
LM 3.1.1: understandable?
LM 3.1.2: understandable?

... etc.  Don't try to jump ahead and read 3.1.3 if 3.1.2 isn't
clear!

This will be very helpful for us.  I know that this kind of job is
harder on the first few readers, but the agony you go through will
indicate exactly what/how to improve the docs, which will benefit
all future readers.

Cheers,
- Graham