Re: ossia staff without SystemStartBar / Bracket / Brace

[Simon Albrecht]

Hello Thomas,

Am 15.05.2015 um 21:00 schrieb Thomas Schuch:
> > Am 14.05.2015 um 23:46 schrieb Simon Albrecht:
> > > Hello,
> > >
> > > sometimes, if something is very difficult to achieve in Lilypond, 
> > > it’s just not a very good idea to do. This is one of those cases: 
> > > Lily has a knack of wanting to produce output complying to usual 
> > > notation standards, and it would be perfectly normal to have the 
> > > span bar
> > that should read: system start delimiter.
> > > span the ossia staff also. Not only that, it’s even necessary to 
> > > clarify that it does not belong to a separate system. So no, there 
> > > is no easier way, and for a good reason.
> > > See also 
> > > <http://lilypond.org/doc/v2.19/Documentation/notation/modifying-single-staves#ossia-staves>, 
> > > in case you shouldn’t have read it already.
> > >
> > > Yours, Simon
> > >
> > > Am 14.05.2015 um 20:54 schrieb musicus:
> > > > > I'm not top posting.
> > > > Is there an easier way to get an ossia Staff without SystemStart than
> > > > following code?
> > > > I'm thinking of something like SystemStartBar #'allow-span-bar = ##f
> > > >
> > > > \version "2.19.17"
> > > >
> > > > <<
> > > >    \new Staff = "ossia" \with {
> > > >          \remove "Time_signature_engraver"
> > > >          \hide Clef
> > > >          \hide KeySignature
> > > >          \magnifyStaff #2/3
> > > >    }{a a a a b b b}
> > > >    \new StaffGroup {
> > > >      <<
> > > >      \set StaffGroup.systemStartDelimiterHierarchy =
> > > >          #'(SystemStartBar (SystemStartBracket (SystemStartBrace a 
> > > > b)))
> > > >         \new Staff { a a a a b b b}
> > > >         \new Staff {a a a a a a a }
> > > >    >>
> > > > }
> > > > \layout {
> > > >    \context {
> > > >      \Score
> > > >      \omit SystemStartBar
> > > >      \override SystemStartBracket.style = #'bar-line
> > > >      \override SystemStartBracket.padding = #-0.1
> > > >      \override SystemStartBracket.thickness = #1.6
> > > >    }
> > > > }
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > lilypond-user mailing list
> > > > address@hidden
> > > > https://lists.gnu.org/mailman/listinfo/lilypond-user
> > >
> > >
> > > _______________________________________________
> > > lilypond-user mailing list
> > > address@hidden
> > > https://lists.gnu.org/mailman/listinfo/lilypond-user
> Dear Simon,
> this is my first visit of the mailing-list, so i hope that my answer 
> is right here.
You should always use ‘reply all’, that is, direct your answer to the 
list also. Others may be interested in the thread, now or later in the 
archives, and it’s good to make the information accessible to everyone. 
(The list interface can prevent receiving posts twice, if they are 
addressed both to somebody’s personal address and to the list.)
> I see your point about SystemStartBar and usual notation, but in my 
> case the ossia staff is not continuous but a on/off case for some 
> measures. I use the ossia staff to write variations of the original 
> score right above (or below) the concerning place. I find it way 
> easier to read the original score grouped with SystemStartBar/Brace 
> and let the ossia staff floating around.
So I did get you right there, nevertheless I don’t see a reason to not 
connect the ossia to the system at the beginning of lines. The (NBA) 
Bärenreiter vocal scores of Bach’s oratorios have ossia staves for 
appoggiaturas in recitatives, and I think they are connected to the 
system, and have clef and key signature at the beginning of the line. 
However, you’re free to do it as you like, of course, especially if the 
system-separator-markup makes it unambiguous in reading.
> Furthermore i use a horizontal line to recognize a new system.
> It's perfectly fine to use the workaround i posted, but i think an 
> ossia staff with a "annotating function" is not a too unusual use case 
> and maybe could be realized in a simple way.
> (I first tried to create a \new Staff directly in the original score 
> every time i need an ossia version as described in the documentation, 
> but i lost orientation in my code, so i switched to extra ossia staves)
> Can I add an image as example? I try to put one in the appendix, 
> otherwise the code below.
I didn’t receive any attachment.

Attached you’ll find an edited version of your code with inline 
comments, especially concerning coding style. If you’re interested in 
scheme, have a look at <http://community.schemewiki.org/?scheme-style>.
In general, lines shouldn’t exceed a lenghth of 80 characters at most.
Why not be a little more generous with spaces around { } \\? Even if not 
technically necessary, it will look less cramped then.

HTH, Simon

sarabande.ly
Description: Text Data