On Tue, 2024-09-10 at 11:06 -0400, Bric wrote: > Sorry about top-posting (is it okay?)
In this case a new message and subject would be preferred - you don't appear to be following up anything in the message you are replying to. > > So, some of the error messages can only be read if you launch denemo > from the command line (showing at the command line) There is stuff emitted to the terminal (if any) but it is not intended for the end user. > > experiencing a new typesetting error, where the rendering window is > showing a minimal staff fragment with the clef and the message > "INVALID! try Score->Check Score command" This usually indicates that the LilyPond syntax being emitted has some error that makes it unreadable beyond a certain point. If you know what your last change was it would pay to look closely at it, undo it, redo it etc. You can also look at the error message in the LilyPond View (and possibly post it here as they are frequently obscure for those not familiar with LilyPond syntax). Beyond that you can resort to chopping out portions of your score until it starts typesetting again and isolating by that means the place where the error has been introduced. > > I go to "Score -> Check Score" and get "No problem detected in this > score" This command has a set of checks that it runs through, common errors such as not terminating a tuplet or slur or ... However the set of errors that you can create is infinitely larger. > > (Also, sometimes you get "cursor may have moved to the error" - you > look at the cursor and see no problem.) Often LilyPond only detects the problem when it gets to the end and so no location information is available, but often it is and the cursor does move to the position. > > Running denemo in verbose mode ( -V ) i see: > > denemo - CRITICAL: Call to find_xes_in_measure for bad measure number > 35 > > there is no measure 35; the editor shows 34 as the last measure. These messages to the console are unlikely to help you > > I'm stuck. see my suggestions above. If you can't backtrack on your work try posting the LilyPond error message or chopping the score down in size and posting the smallest bit that has the error. Richard > > > > On 09/10/2024 5:36 AM EDT Richard Shann <rich...@rshann.plus.com> > > wrote: > > > > > > On Mon, 2024-09-09 at 16:52 -0400, Bric wrote: > > > > > > > On 09/09/2024 2:23 PM EDT Richard Shann > > > > <rich...@rshann.plus.com> > > > > wrote: > > > > > > > > 'Screenshot from 2024-09-09 16-44-42.png' > > > > On Mon, 2024-09-09 at 12:28 -0400, Bric wrote: > > > > > Experiencing complete failure with voices. > > > > > > > > > > Is there comprehensive documentation on how to use voices? > > > > > > > > > > At the moment I am thinking I need multiple voices per staff > > > > > because > > > > > ordinary chords do not allow notes with different durations > > > > > on > > > > > the > > > > > same (shared) staff, aligned vertically (where, in spite of > > > > > the > > > > > different duration they all START simultaneously). > > > > > > > > correct, that is what they are for > > > > > > > > > Example: > > > > > > > > > > > > > > > > > > > > I added a staff with a designated new voice... I can't even > > > > > get > > > > > past > > > > > the rendering error -- "Typeset" leads to "Check Score. > > > > > Cursor > > > > > may > > > > > have been moved..." when I populate the extra voice with any > > > > > notes > > > > > > > > can you post an example of such a thing? > > > > > > > > > > > > > I guess this mailing list defaults to text-only formatting? > > > > > > (had HTML for my previous message) > > > > > > attaching images in that case > > > > > > The rendering error screenshot shows the top two voice notes > > > _next_ > > > to each other rather than aligned one above the other. > > > > > > by the way - typically the render errors are non-descriptive > > > (error > > > specifics do not surface) > > > > To see the exact error messages that LilyPond is emitting typeset > > in > > the LilyPond View. In the case of your file it is just a warning > > that > > you have your two voices clashing - the warning message is: > > > > Typesetting ...Done > > /tmp/Denemo_7RIET2/denemoprintA.ly:50:10: warning: this Voice needs > > a > > \voiceXx or \shiftXx setting > > > > e''4 d'' c''\AutoBarline > > /tmp/Denemo_7RIET2/denemoprintA.ly:50:15: warning: this Voice needs > > a > > \voiceXx or \shiftXx setting > > e''4 > > d'' c''\AutoBarline > > /tmp/Denemo_7RIET2/denemoprintA.ly:50:19: warning: this Voice needs > > a > > \voiceXx or \shiftXx setting > > e''4 d'' > > c''\AutoBarline > > /tmp/Denemo_7RIET2/denemoprintA.ly:51:10: warning: this Voice needs > > a > > \voiceXx or \shiftXx setting > > > > c'' d'' c''8 d''} > > /tmp/Denemo_7RIET2/denemoprintA.ly:51:18: warning: this Voice needs > > a > > \voiceXx or \shiftXx setting > > c'' d'' > > c''8 d'... > > > > The reason for the error is that while you have set the top staff > > to be > > Voice 2 you have not set the direction of the second staff, so it > > is > > defaulting to automatic voice (up or down stems depend on > > above/below > > mid line of staff). > > You can use the command > > > > Command: Choose Voice > > The Voice 1,2,3,4 commands set up the voices so that first and > > third > > voices get stems up, second and fourth voices get stems down, third > > and > > fourth voice note heads are horizontally shifted, and rests in the > > respective voices are automatically moved to avoid collisions. The > > Automatic Voice command returns all the voice settings to the > > neutral > > default directions. The Denemo display shows automatic stem > > directions, > > use StemDown and StemUp commands if you wish to affect the display. > > Location: Object Menu ▶ Directives ▶ Typesetter ▶ Voices > > > > to set the voice (and to change it mid-music if needed) > > > > HTH > > > > Richard > > > > > > > > > > > > > > > > > > > > > > > > > > I apparently don't know the basics of voices > > > > > > > > > > So my questions are: > > > > > > > > > > 1. How do I make voices work? > > > > > 2. How do I make the notes of different voices vertically > > > > > align > > > > > perfectly ? > > > > > > > > That happens automatically > > > > > > > > > 3. (#2 with different durations vertically aligned in spite > > > > > of > > > > > that > > > > > difference) > > > > > > > > also automatic > > > > > > > > > > > > > > 4. (I am assuming I can figure out stem direction on my own, > > > > > although it would be nice if there is a smart algorithm that > > > > > automatically assigns stem direction, as shown in the > > > > > embedded > > > > > image > > > > > here) > > > > You use the > > > > Command: Choose Initial Voice > > > > Choose which voice this staff will initially be set to. To > > > > change > > > > voice > > > > during music see the Directives->Voices menu. > > > > Location: Object Menu ▶ Staffs/Voices ▶ Voices > > > > Internal Name: InitialVoice > > > > > > > > and then commands like > > > > > > > > Command: Voice Preset 1 (Stems Up) > > > > Preset for first voice. Stems up > > > > Location: Object Menu ▶ Directives ▶ Typesetter ▶ Voices > > > > Internal Name: VoicePreset1 > > > > > > > > and friends if you need to switch stem direction mid music. > > > > > > > > HTH > > > > > > > > Richard Shann > > > > > > > > > > > > > >
