denemo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] trouble creating parts


From: Donald J. Stewart
Subject: Re: [Denemo-devel] trouble creating parts
Date: Wed, 30 Nov 2016 23:30:55 -0800
User-agent: KMail/5.1.3 (Linux/4.4.0-51-generic; KDE/5.18.0; x86_64; ; )

On Tuesday, November 22, 2016 8:50:16 AM PST Richard Shann wrote:
> On Mon, 2016-11-21 at 22:02 +0000, Richard Shann wrote:
> > On Mon, 2016-11-21 at 13:23 -0800, Donald J. Stewart wrote:
> > > rats...I turned on 'typeset barlines literally' and now Denemp Print
> > > View
> > > shows that Lilypond can't typeset score...
> > > 
> > > I took out the 'offending' repeats and still get the message...
> > 
> > ... so what is the offending syntax & LilyPond's message about it (i.e.
> > right-click->Typeset in the LilyPond window and look in the pane 
below).
> > 
> > IIRC "Typeset barlines literally" just means issuing \bar "|" at each
> > point in the music where Denemo has a barline in the Denemo 
Display.
> 
> Well, as usual IIRC is not good enough :)
> In fact this command adds *two* directives, one, "DenemoBar", does 
issue
> a \bar command, but with extra fancy stuff to get bar numbering 
working.
> The other is a directive tagged "ScoreTiming" which issues the syntax
> 
> \set Score.timing = ##f
> 

This may be the case, as I can toggle 'Typeset Barlines Literally', thereby 
turning the command on or off, and allow Denemo Print View to actually 
print the score (when it's toggled on, Denemo Print View gives the error 
code, when it's toggled off, it prints)

> which I suspect is what you want - I think that is just turning off
> automatic barlines. So you could delete the "DenemoBar" directive and
> that would stop warnings about clashes between \bar commands you 
insert
> manually and the ones inserted for each Denemo "barline" in the score.
> 
> Richard
> 
> > This would cause warnings where you have other \bar xxx commands 
at the
> > same places ... but I can't imagine that it would cause an actual
> > LilyPond error.
> > 
> > 
> > Richard
> > 
> > 
> > 
> > _______________________________________________
> > Denemo-devel mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/denemo-devel





reply via email to

[Prev in Thread] Current Thread [Next in Thread]