Re: How to proofread?
Am 30.11.19 um 16:35 schrieb Jinsong Zhao:
Hi there,
It's may be some off topic. After a long struggle, I have nearly done
the input of a sheet music. Then, I need to proofread it.
Generally, I split the screen into left and right frames, and put the
score that Lilypond output and the original one into each frame, and
read/compare notes one by one.
Is there any other ways you prefer to do proofread?
Best,
Jinsong
One tool available for proof-reading is Frescobaldi's Manuscript Viewer
that lets you place the engraver's copy and the engraved LilyPond score
next to each other withing one environment - and you have access to the
text editor in that same environment through point-and-click.
What I often do is force the engraving to use the original line/page
breaking during editing. This can be done by inserting a custom command
like \originalLineBreak that is defined as
originalLineBreak = \break
etc. for page breaks and page turns.
For publication this can be changed to
originalLineBreak = {}
Alternatively you can use the more convenient openLilyLib package
page-layout (https://github.com/openlilylib/page-layout) (needs the
breaks package and oll-core too).
Urs
Line by line! Re: How to proofread?
Hello, for me proofreading line by line as Wol described is the most helpfull method, and I use it as the top method beside reading the original in combination with hearing the midi-output. Best Regards Roland
Re: How to proofread?
On 30/11/2019 15:35, Jinsong Zhao wrote:
Hi there,
It's may be some off topic. After a long struggle, I have nearly done
the input of a sheet music. Then, I need to proofread it.
Generally, I split the screen into left and right frames, and put the
score that Lilypond output and the original one into each frame, and
read/compare notes one by one.
Is there any other ways you prefer to do proofread?
I proof-read as I go. I can't remember where it came from, but someone
on the list said "create a variable mbreak, and use it everywhere the
original manuscript has a line break. Set it to { \break } while you're
entering the music, then set it to {} when you're done."
Like you, I have one window with the original scan, and obviously
another with lilypond output, and a third with the lilypond source. But
I always proof-read the score line by line - I enter a line, compile,
proof-read, and move on to the next. Once I'm done, I null out mbreak
and let lilypond format the score as it will.
I mostly do this to transpose parts seeing as I play the trombone, so
the part may be in Bb treble clef, tenor clef, or bass clef, and I want
to print it out in treble or bass.
I also separate out the notes from the layout, so once I've
done/proofread my first part, when I do a second part I know the layout
is correct so (and I've found the parts were wrong once) if the notes
and repeats and double bars etc don't match up, I know that normally
I've messed up the notes. (On that occasion, a previous copyist had
messed up the bars ... :-)
Cheers,
Wol
Re: How to proofread?
Hi Jinsong, I found that proofreading visually does not really work for me, I just overlook too many errors. But I can recommend listening to MIDI output. I usually take single voices (or sometimes one voice for checking and e.g. bass for reference) while reading the original. Listening to all voices at once can be too much, especially if there's a lot going on. Hope this works for you! Nora On 30.11.19 16:46, David Nalesnik wrote: Hi Jinsong, On Sat, Nov 30, 2019 at 9:36 AM Jinsong Zhao wrote: Hi there, It's may be some off topic. After a long struggle, I have nearly done the input of a sheet music. Then, I need to proofread it. Generally, I split the screen into left and right frames, and put the score that Lilypond output and the original one into each frame, and read/compare notes one by one. Is there any other ways you prefer to do proofread? Best, Jinsong You could try proofreading by going through the music backwards. That way you are less likely to "see what you want to see." MIDI output is also useful for proofreading. Hope this helps! David
RE: How to proofread?
David, Insigtful! I shall change my proofing. Mark -Original Message- From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of David Nalesnik Sent: Saturday, November 30, 2019 7:46 AM To: Jinsong Zhao Cc: lilypond-user Subject: Re: How to proofread? Hi Jinsong, On Sat, Nov 30, 2019 at 9:36 AM Jinsong Zhao wrote: > > Hi there, > > It's may be some off topic. After a long struggle, I have nearly done > the input of a sheet music. Then, I need to proofread it. > > Generally, I split the screen into left and right frames, and put the > score that Lilypond output and the original one into each frame, and > read/compare notes one by one. > > Is there any other ways you prefer to do proofread? > > Best, > Jinsong > You could try proofreading by going through the music backwards. That way you are less likely to "see what you want to see." MIDI output is also useful for proofreading. Hope this helps! David
Re: How to proofread?
On 11/30, Jinsong Zhao wrote: > Hi there, > > It's may be some off topic. After a long struggle, I have nearly done > the input of a sheet music. Then, I need to proofread it. > > Generally, I split the screen into left and right frames, and put the > score that Lilypond output and the original one into each frame, and > read/compare notes one by one. > > Is there any other ways you prefer to do proofread? > > Best, Jinsong After note entry, for my first round of proofreading I import Lilypond's midi output into Musescore and play it back. This * changes the layout * has per-track muting/soloing * automatically scrubs though the score to follow playback * strips out some things like dynamics all of which I find useful for hearing errors and visually spotting things that I missed while working with Lilypond's output. I try to use Musescore to make sure all of the pitches and rhythms are solid, and then return to Lilypond's output for proofreading other score objects. I also find that when I print the score and read through it on paper I spot more errors than when viewing it on a computer screen. I don't like to waste paper, so I try to catch as many errors as possible at the computer, but after that at least one or two rounds of printing out and proofreading is necessary. For scores with multiple staves, I find also that I notice different errors while looking at the whole score from when I look at a part containing just one staff, so I read it both ways. If you have a fairly large monitor that can rotate 90 degrees vertically, a vertical screen orientation can allow you to fit an entire page to the screen, which I sometimes find preferable to scrolling around. I also have learned what kinds of errors I am most likely to make and to miss while proofreading, such as octave displacement, and I look specifically for errors like those. Mason signature.asc Description: PGP signature
Re: How to proofread?
On Sat, Nov 30, 2019 at 7:36 AM Jinsong Zhao wrote: > > Hi there, > > It's may be some off topic. After a long struggle, I have nearly done > the input of a sheet music. Then, I need to proofread it. > > Generally, I split the screen into left and right frames, and put the > score that Lilypond output and the original one into each frame, and > read/compare notes one by one. > > Is there any other ways you prefer to do proofread? One of the ways I "proofread" a LilyPond piece is to listen to the MIDI playback, especially while looking at the original score. If you're a good sight reader, or you know the piece, this can help you spot bugs. --- Knute Snortum (via Gmail)
Re: How to proofread?
"Jinsong Zhao" wrote 30/11/2019 15:35:23 It's may be some off topic. After a long struggle, I have nearly done the input of a sheet music. Then, I need to proofread it. Generally, I split the screen into left and right frames, and put the score that Lilypond output and the original one into each frame, and read/compare notes one by one. Is there any other ways you prefer to do proofread? I usually check the entry with the original after completing each part on each system (I usually work with SATB four-part harmony using Frescobaldi for note entry). Then, at the end, I listen to the Midi and finally I print it and play it through carefully on a piano. HTH, Trevor
Re: How to proofread?
Hi Jinsong, On Sat, Nov 30, 2019 at 9:36 AM Jinsong Zhao wrote: > > Hi there, > > It's may be some off topic. After a long struggle, I have nearly done > the input of a sheet music. Then, I need to proofread it. > > Generally, I split the screen into left and right frames, and put the > score that Lilypond output and the original one into each frame, and > read/compare notes one by one. > > Is there any other ways you prefer to do proofread? > > Best, > Jinsong > You could try proofreading by going through the music backwards. That way you are less likely to "see what you want to see." MIDI output is also useful for proofreading. Hope this helps! David
