While pondering how an “nth time only” feature might work, I considered what it
might take to generalize the way the Mark engraver handles updating the
rehearsal mark number and make it expressible in ly code instead.
I have a working prototype that uses all the following features and I’m lookin
On Sa., 10. Dez. 2011 00:32:48 CET, Xavier Scheuer wrote:
> On 12 September 2011 21:03, Reinhold Kainhofer
> wrote:
> > I'm currently investigating how to implement measure counters (Bug
> > 146): http://code.google.com/p/lilypond/issues/detail?id=146
>
> Plop, I n
On 12/9/11 4:32 PM, "Xavier Scheuer" wrote:
>On 12 September 2011 21:03, Reinhold Kainhofer
>wrote:
>> I'm currently investigating how to implement measure counters (Bug 146):
>> http://code.google.com/p/lilypond/issues/detail?id=146
>>
>> Compared
On 12 September 2011 21:03, Reinhold Kainhofer wrote:
> I'm currently investigating how to implement measure counters (Bug 146):
> http://code.google.com/p/lilypond/issues/detail?id=146
>
> Compared to multi-measure rest numbers and to percent repeat numbers, there is
> a
nga or breve)...
Can't you just use the same timing information the
Multi_measure_rest_engraver uses? It knows the current moment and the
length of each bar, so you only have to store columns (via
currentCommandColumn) and create a new counter grob for each bar. You
just need to set the bounds
Am Monday, 12. September 2011, 21:14:11 schrieb Neil Puttock:
> On 12 September 2011 20:03, Reinhold Kainhofer
wrote:
> > Any idea how to implement this?
>
> Shouldn't it just be a spanner whose bounds are the left column and
> right column for each bar? Similar to a full-bar rest or percent
>
On 12 September 2011 20:03, Reinhold Kainhofer wrote:
> Any idea how to implement this?
Shouldn't it just be a spanner whose bounds are the left column and
right column for each bar? Similar to a full-bar rest or percent
repeat.
Cheers,
Neil
___
lil
I'm currently investigating how to implement measure counters (Bug 146):
http://code.google.com/p/lilypond/issues/detail?id=146
Compared to multi-measure rest numbers and to percent repeat numbers, there is
a little complication: There is no grob to attach the numbers to (the percent
r
LGTM.
http://codereview.appspot.com/4757043/diff/1/lily/staff-performer.cc
File lily/staff-performer.cc (right):
http://codereview.appspot.com/4757043/diff/1/lily/staff-performer.cc#newcode69
lily/staff-performer.cc:69: // For now, ask the last Staff_performer
clean up during its finalize()
fin
On Sat, 16 Jul 2011 08:11:02 -0700, wrote:
Passes Make tests - I still get:
--snip--
Interpreting music...
-warning: MIDI channel wrapped around
-warning: remapping modulo 16
MIDI output to
The test output shows the change from the old behavior. Lines with '-' in
front were present in
Passes Make tests - I still get:
--snip--
@ -1,8 +1,6 @@
Parsing...
Renaming input to:
`/home/jlowe/lilypond-git/input/regression/midi-volume-equaliser.ly'
Interpreting music...
-warning: MIDI channel wrapped around
-warning: remapping modulo 16
MIDI output to
`/home/jlowe/lilypond-git/build/
's request is the possibility to
typeset bar numbers centered over each measure. The obvious syntax for
such an option would be a normal property setting, right?
I don't mean to be rude, but are you understanding what we're
understanding? We're not discussing bar *numbers*, we'
As you know, it's already possible to get bar numbers on every single
measure
(or every 5th or whatever) but they will be printed on top of the bar
lines.
The only new feature I can see in Werner's request is the possibility to
typeset bar numbers centered over each measure. The obvious syntax f
> > \tag #'tuba \barCounterOn
> > c r g\< r |
> > c r g r |
> > c r g r |
> > c\f r g r |
> > \tag #'tuba \barCounterOff
>
> Please also add a feature to make the number visible/invisible. A
> lot of the music I see starts counting on the first bar, but only
> starts
In message <[EMAIL PROTECTED]>, Werner LEMBERG
<[EMAIL PROTECTED]> writes
In orchestral parts it is quite common to have bar counters like this:
Very late response, I know :-)
1 2 3 4
c r g r | c r g r | c r g r | c r g r |
In orchestral parts it is quite common to have bar counters like this:
1 2 3 4
c r g r | c r g r | c r g r | c r g r |
cresc. - - - - - f
Currently, lilypond provides automatic bar counting for repeats only.
It would be great if
16 matches
Mail list logo