On 08/23, Kieren MacMillan wrote:
> You can always use \fixed. =)
I didn't know about \fixed until just now. My first thought was to use
this to make the "default" pitches begin on the bottom space of the
staff, i.e., for treble clef
\fixed f' {f g a b c d e}
is equivalent to
{f' g' a' b'
Hi Mason,
> I thought of that, but my worry is that I'll still make octave errors,
> but each will result in one transposed note instead of a transposed
> phrase, which might be even less apparent than proofreading.
That is a concern…
> I also find relative note entry to be more intuitive and
Thanks Kieren,
On 08/23, Kieren MacMillan wrote:
> My primary suggestion: use absolute instead of relative note entry, and you
> will never have incorrect octavation again. :)
I thought of that, but my worry is that I'll still make octave errors,
but each will result in one transposed note
Hi Mason,
> placing a note in the wrong octave
My primary suggestion: use absolute instead of relative note entry, and you
will never have incorrect octavation again. :)
My secondary suggestion: to make entry fast and super-accurate, use MIDI entry
if possible.
If you stick with relative
Sent: Friday, August 23, 2019 1:41 PM
To: lilypond-user@gnu.org
Subject: workflow advice: avoiding wrong octave errors?
I typically make few errors while inputting music. The two most common
exceptions are incorrect note durations and placing a note in the wrong
octave. The former generally
"Octave checks" occurred to me while I was writing. I should have
thought to RTFM before sending...
http://lilypond.org/doc/v2.18/Documentation/notation/changing-multiple-pitches#octave-checks
Mason
On 08/23, ma...@masonhock.com wrote:
> I typically make few errors while inputting music. The
I typically make few errors while inputting music. The two most common
exceptions are incorrect note durations and placing a note in the wrong
octave. The former generally is not a problem, because bar checks catch
the error and tell me where to look. However, the latter slips by more
easily.
If
