Re-use \chordmode for strumming patterns

2015-08-25 Thread Joel Ebel
Hi. I'm curious if there's a way to re-use a variable containing chords entered in \chordmode to create strumming patterns with Pitch_squash_engraver and \improvisationOn. I like only having to enter the chords once, so if I change something, I only need to do it in one place, and I also would

Re: Re-use \chordmode for strumming patterns

2015-08-25 Thread Joel Ebel
chordRoot = #(define-music-function (m) (ly:music?) (event-chord-reduce m)) That works perfectly! I don't like the name. Once we come up with a nice bike shed color, we probably should provide that function in LilyPond proper and document it along with Pitch_squash_engraver. I agree that

Re: Make a new staff occupy the same vertical space as a previous staff

2015-08-27 Thread Joel Ebel
On Thu, Aug 27, 2015 at 2:53 AM, David Kastrup d...@gnu.org wrote: Oh wow. This one is seriously annoying. If you take out all \stopStaff, it is apparent that the TabStaff is alive through the whole piece. This is also the case when replacing \new Line with \new StaffGroup. This is

Re: Re-use \chordmode for strumming patterns

2015-08-27 Thread Joel Ebel
ChordNames { c1 c c c } \relative c'' { c1 c c c} } On Tue, Aug 25, 2015 at 11:31 AM, Joel Ebel jbe...@mybox.org wrote: chordRoot = #(define-music-function (m) (ly:music?) (event-chord-reduce m)) That works perfectly! I don't like the name. Once we come up with a nice bike shed color

Re: Make a new staff occupy the same vertical space as a previous staff

2015-08-25 Thread Joel Ebel
On Tue, Aug 25, 2015 at 9:53 PM, David Kastrup d...@gnu.org wrote: The following appears to work here. Of course it begs the question whether we should provide a context definition like that, possibly with a better name, in LilyPond by default. Excellent! That does work, which is good because

Re: Make a new staff occupy the same vertical space as a previous staff

2015-08-29 Thread Joel Ebel
} } } \layout { \context { \name Line \type Engraver_group \consists Axis_group_engraver \accepts TabStaff \accepts RhythmicStaff } \context { \Score \accepts Line } } On Fri, Aug 28, 2015 at 11:48 AM, David Kastrup d...@gnu.org wrote: Joel Ebel jbe

Make a new staff occupy the same vertical space as a previous staff

2015-08-25 Thread Joel Ebel
I'm sure this is documented somewhere and I just can't seem to find it. How do I get a new staff to immediately follow a previous staff in the same vertical space. In this simple example, I'd like the TabStaff to end, and the RhythmicStaff to immediately follow in the same vertical space, rather

Re: Make a new staff occupy the same vertical space as a previous staff

2015-08-26 Thread Joel Ebel
On Tue, Aug 25, 2015 at 10:26 PM, Joel Ebel jbe...@mybox.org wrote: On Tue, Aug 25, 2015 at 9:53 PM, David Kastrup d...@gnu.org wrote: The following appears to work here. Of course it begs the question whether we should provide a context definition like that, possibly with a better name

Re: Make a new staff occupy the same vertical space as a previous staff

2015-08-25 Thread Joel Ebel
The closest I've been able to get so far is to instantiate the TabStaff and the RhythmicStaff inside the ChordNames in parallel with the chords I want to make. I still don't get the TabStaff and the RhythmicStaff on the same line, but if I insert a \break (commented out below) in between them,

Re: How to correctly compile the Messiah from Neuvar's Site.

2015-09-22 Thread Joel Ebel
I filed a bug last October that some of the parts wouldn't compile with 2.18. I think I wound up building those parts with 2.13, and the rest with 2.18. https://github.com/nsceaux/nenuvar/issues/9 ___ lilypond-user mailing list lilypond-user@gnu.org