Thanks for all the help. As per Simon's advice, I'm now doing this to
get rid of the TAB clef on the first line of RhythmicStaff, and I like
the removal of the DevNull. It's perhaps a toss-up whether the source
is easier to read with around the TabStaff it vs putting a
\stopStaff after it, but
Joel Ebel jbe...@mybox.org writes:
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
Am 27.08.2015 um 15:50 schrieb 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
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
Joel Ebel jbe...@mybox.org writes:
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
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, in
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
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
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,
Joel Ebel jbe...@mybox.org writes:
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
10 matches
Mail list logo
