cross staff beams in choir staff

2008-03-14 Thread Orm Finnendahl
Hi, I'm trying to typeset cross staff notes on a 12-staff percussion system. Defining the staff systems as Staff and the StaffGroup as PianoStaff works well. Trying the same with ChoirStaff and the individual Staff systems as DrumStaff results in lots of errors and the beams and staff lines not

Re: cross staff beams in choir staff

2008-03-14 Thread Neil Puttock
Hi Orm, Would you mind posting a minimal example which demonstrates the problems you're having? Here's a quick snippet I've knocked up using ChoirStaff and DrumStaff which seems to be working fine: \version 2.11.42 \paper { ragged-right = ##t } \score { \new ChoirStaff {

Re: cross staff beams in choir staff

2008-03-14 Thread Trevor Bača
On Fri, Mar 14, 2008 at 11:42 AM, Orm Finnendahl [EMAIL PROTECTED] wrote: Hi, I'm trying to typeset cross staff notes on a 12-staff percussion system. Defining the staff systems as Staff and the StaffGroup as PianoStaff works well. Trying the same with ChoirStaff and the individual Staff

Re: cross staff beams in choir staff

2008-03-14 Thread Orm Finnendahl
Hi Neil, Am 14 Mär schrieb Neil Puttock: Hi Orm, Would you mind posting a minimal example which demonstrates the problems you're having? Sure. The first attached file works, the second doesn't (and neither works with DrumStaff instead of Staff). Please try it out. Maybe my lilypond version

Re: cross staff beams in choir staff

2008-03-14 Thread Reinhold Kainhofer
Am Samstag, 15. März 2008 schrieb Trevor Bača: I don't know the real (ie, structual) answer. But here's the workaround for setting the system start brace to transparent: Alternatively, simply set the systemStartDelimiter for your PianoStaff to SystemStartBracket instead of the default brace,

Re: cross staff beams in choir staff

2008-03-14 Thread Neil Puttock
On Fri, Mar 14, 2008 at 11:47 PM, Orm Finnendahl wrote: Sure. The first attached file works, the second doesn't (and neither works with DrumStaff instead of Staff). Please try it out. Maybe my lilypond version is too dated (2.11.7) Thanks. There may well be an issue with version 2.11.7,