[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Denemo-devel] trouble creating parts
From: |
Richard Shann |
Subject: |
Re: [Denemo-devel] trouble creating parts |
Date: |
Sat, 12 Nov 2016 12:30:07 +0000 |
Sorry! There *is* a serious-looking error in the file as you originally
posted it; near the top there is:
#(define denemo-top-margin ...for they shall...)
where the red-highlighting starts.
it seems that in setting the top margin you inserted the text "... for
they shall ..." instead of a number (such as 20). I deleted this and
then ran typeset and got the sort of warning messages I wrote about
below (they refer to another copy of your file that I extracted by
tortuous means earlier...)
It would be good for those margin setting commands to test out the
syntax for validity before letting you insert things like that, I've put
a bug report in for this.
You would normally expect to be able to fix this by re-running the
margin command, but in this case the bad value persists. To fix your
score open up Score->Score Properties Editor and delete the TopMargin
directive. There is a second TopMargin directive, which is (I guess) the
one where you re-edited the top margin.
Let me know when if you have a problem deleting this bad directive.
Richard
On Sat, 2016-11-12 at 11:53 +0000, Richard Shann wrote:
> On Sat, 2016-11-12 at 10:14 +0000, Richard Shann wrote:
> > On Sat, 2016-11-12 at 09:46 +0000, Richard Shann wrote:
> > > On Sat, 2016-11-12 at 01:11 -0800, Donald J. Stewart wrote:
> > > > I've attached the file.
> > >
> > > you have to compress the file before attaching it to the email.
> >
> > I've used the list-moderator interface to allow this email through so
> > there should be no need to re-send it compressed on this occasion.
>
> The file has now arrived on the mailing list.
> I've tested out the .denemo file attached to it.
> The full score typesets with error messages in the LilyPond window:
> ================================================================================
> Typesetting ...Done/tmp/Denemo_UHBTQY/denemoprintB.ly:685:346: warning:
> unterminated hyphen; removing
> Bless -- ed __ are __ the poor __ in spi -- rit... Bless -- ed __ are __
> the meek... __ Bless -- ed __ are they __ that mourn... Bless -- ed are
> they __ that hun -- ger and thirst __ af -- ter jus -- tice..=2E __
> Bless -- ed, __ bless -- ed are __ the mer -- ci -- ful... __ Bless --
> ed __ are __ the __ peace -- mak -- ers, __ the peace -- mak
>
> -- ers. __ jus -- tice... __ __ af -- __ Bless-
> /tmp/Denemo_UHBTQY/denemoprintB.ly:1081:21: warning: unterminated
> decrescendo
> f-\fermata
> \decr \AutoEndMovementBarline
> /tmp/Denemo_UHBTQY/denemoprintB.ly:81:79: warning: decrescendo too small
> f'' f'' \cr g'' g'' f'' f'' g'' g'' f'' f'' g'' g''<> \ff
> bes''4:32
>
> \decr~ \!\AutoBarline
> /tmp/Denemo_UHBTQY/denemoprintB.ly:690:23: warning: cannot resolve rest
> collision: rest direction not set
> \tempo 4=84
> r1\AutoBarline
> ...
> ================================================================================
>
> The first message is about your lyrics - I'm not an expert on LilyPond
> lyric syntax - you have doubled hyphens and doubled underscores - should
> these be doubled? Should not the hyphens be attached to the previous
> syllable (i.e. no space)?
>
> The second message says you have a decr start with no decr end later.
>
> The last message is for part writing, where you have more than one rest
> at one moment and have not specified which voice they are in, or if they
> are to be combined (see Staffs/Voices->Voices menu).
>
> However, these are all just Warning messages, and so you *do* get a
> typeset score.
>
> Putting the cursor in the top staff in the Denemo Display and clicking
> Part in the Print View also typesets with warning, attached is the PDF
> created by clicking the PDF button. The LilyPond window shows the
> following warnings in the lower pane in this case:
>
> ================================================================================
> Typesetting ...Done/tmp/Denemo_UHBTQY/denemoprintA.ly:36:50: warning:
> crescendo too small
> g'?2.-\tenuto \decr<> \p d'4\glissando
> \cr( \!\AutoBarline
> /tmp/Denemo_UHBTQY/denemoprintA.ly:81:79: warning: decrescendo too small
> f'' f'' \cr g'' g'' f'' f'' g'' g'' f'' f'' g'' g''<> \ff
> bes''4:32
>
> \decr~ \!\AutoBarline
> /tmp/Denemo_UHBTQY/denemoprintA.ly:163:77: warning: decrescendo too
> small
> bes'4-\tenuto<> \f a'4-\tenuto aes'4-\tenuto<> \mf
> ges'4-\tenuto
>
> \decr\AutoBarline
> /tmp/Denemo_UHBTQY/denemoprintA.ly:189:139: warning: decrescendo too
> small
> <> \f<> ^\markup \italic {"con sord." } cis''16 \cr dis'' e''
> fis'' cis'' dis'' e'' fis'' cis'' dis'' e'' fis''<> \ff gis''4:32
>
> \decr~ \!\AutoBarli...
> ================================================================================
>
> the cursor does indeed move to the first of these warnings at Staff 1,
> bar 15 on the last note. And indeed the crescendo between the d'4 (which
> is a d 1/4) note and the following ees''8 (an e-flat 1/8th) note is
> rendered as a squashed up line. LilyPond is not clever enough to fix
> this for you by giving extra space.
> Searching in the View->Command Center for "cres" I came to
>
> Command: Lengthen Hairpin
> Inserts a directive to lengthen the following cresc or dim hairpin.
> Location: ObjectMenu->NotesRests->Markings->Dynamics
> Internal Name: LengthenHairpin
>
> which may help in this situation.
>
> I also put the cursor in the Soprano staff and clicked Part in the Print
> View - this typeset without warning messages - as it involves those __
> and -- in the lyrics I guess they are all right - the "warning:
> unterminated hyphen; removing" message above must refer to some other
> verse.
>
> HTH
>
> Richard
>
>
>
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/denemo-devel
- [Denemo-devel] trouble creating parts, Donald J. Stewart, 2016/11/09
- Re: [Denemo-devel] trouble creating parts, Richard Shann, 2016/11/09
- Re: [Denemo-devel] trouble creating parts, Donald J. Stewart, 2016/11/12
- Re: [Denemo-devel] trouble creating parts, Donald J. Stewart, 2016/11/12
- Re: [Denemo-devel] trouble creating parts, Richard Shann, 2016/11/12
- Re: [Denemo-devel] trouble creating parts, Richard Shann, 2016/11/12
- Re: [Denemo-devel] trouble creating parts, Richard Shann, 2016/11/12
- Re: [Denemo-devel] trouble creating parts,
Richard Shann <=
- Re: [Denemo-devel] trouble creating parts, Richard Shann, 2016/11/12
- Re: [Denemo-devel] trouble creating parts, Donald J. Stewart, 2016/11/14
- Re: [Denemo-devel] trouble creating parts, Richard Shann, 2016/11/15
- Re: [Denemo-devel] trouble creating parts, Andreas Schneider, 2016/11/15
- Re: [Denemo-devel] trouble creating parts, Jeremiah Benham, 2016/11/15
- Re: [Denemo-devel] trouble creating parts, Donald J. Stewart, 2016/11/15
- Re: [Denemo-devel] trouble creating parts, Andreas Schneider, 2016/11/15
- Re: [Denemo-devel] trouble creating parts, Andreas Schneider, 2016/11/15
- Re: [Denemo-devel] trouble creating parts, Donald J. Stewart, 2016/11/15
- Re: [Denemo-devel] trouble creating parts, Richard Shann, 2016/11/15