Re: Unconventional score and unwanted stray staff lines

[David Bellows]

Hi Karim,

> My workaround was to put at each end of a part where this occurs, this

That does work! Thank you very much for this!

If you can search my emails to the list today about the issue, I
include more information about when this issue occurs in my scores.
The only staves that continue to be created are the ones where the
final note is an actual printed note. If the final note of a staff is
a rest or space then the extra staves are not printed. Also, it
appears that the problem only occurs if the final note is less than a
quarter note, but I haven't tested that thoroughly.

In other words, at least in my case, this appears to be a bug?

Thanks again for your help on this. If this is a bug that isn't going
to be fixed anytime soon then your solution does the trick.

On Sun, May 19, 2019 at 7:47 AM Karim Haddad <address@hidden> wrote:
>
> Dear David,
>
> Lately I had a similar issue with a multi-tempi and multi-metered ensemble 
> score.
> However the strayed clefs and staves where not on all instruments. I suspect 
> it does have to do with internal timing lilypond calculations.
> My workaround was to put at each end of a part where this occurs, this :
>
> %here is the closing bar :
> \once \set Staff.whichBar = "|."
> % these are to stop the running staff and "phantom" clef and instrument name 
> going on .... :
>
> \override Staff.Clef.stencil=##f
> \set Staff.shortInstrumentName = #""
> \stopStaff
>
> Hope this helps.
>
> Best
> Karim
>
> On Sun, May 19, 2019 at 09:04:47AM -0400, address@hidden wrote:
> >
> > Message: 2
> > Date: Sat, 18 May 2019 20:09:10 -0700
> > From: David Bellows <address@hidden>
> > To: Andrew Bernard <address@hidden>
> > Cc: lilypond-user Mailinglist <address@hidden>
> > Subject: Re: Unconventional score and unwanted stray staff lines
> > Message-ID:
> >       <address@hidden>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Hi Andrew,
> >
> > > adding \stopStaff at the end of the sections - does this do what you want?
> >
> > That gets me really close except ...
> >
> > > There seems to be some stray clefs in this, but I am sure you can tidy 
> > > this up.
> >
> > I have no idea where those stray clefs are coming from. In the first
> > pdfs I sent they didn't show up. However, the one bass clef I see in
> > these new versions does correspond to where a bass clef was in the
> > original pdfs I sent. As in the stray bass clef is where a stray empty
> > staff was originally. I'm guessing it's related.
> >
> > > I can't quite grasp what your score is. Is it for five pianos, as all the 
> > > piano staves are grouped into one system? ... I assume this is 
> > > algorithmically generated music?
> >
> > The piece is really for any number of instruments but all of one kind.
> > Like 20 violins or, as in this example, 5 pianos. And yes, the music
> > is generated algorithmically. This particular example just uses the
> > most basic function for generating pitches, durations and dynamics
> > without trying to make it sound good.
> >
> > So what you have here are five different "melodies" generated for five
> > different pianos that all get played at the same time. I think the way
> > I have it grouped makes the most sense but I'm always open to
> > suggestions. I haven't put in the instrument labels yet and I left off
> > the title stuff.
> >
> > On Sat, May 18, 2019 at 7:36 PM Andrew Bernard <address@hidden> wrote:
> > >
> > > Hi David,
> > >
> > > I can't quite grasp what your score is. Is it for five pianos, as all the 
> > > piano staves are grouped into one system?
> > >
> > > Anyway, adding \stopStaff at the end of the sections - does this do what 
> > > you want? There seems to be some stray clefs in this, but I am sure you 
> > > can tidy this up. I assume this is algorithmically generated music?
> > >
> > > Andrew
> > >
> >
> >
> >
> webpage : http://karim.haddad.free.fr