nine.fierce.ballads | 31 Oct 23:50 2014
Picon

Re: Add chord range to make-part-combine-music (issue 144170043 by nine.fierce.ballads <at> gmail.com)

On 2014/10/31 13:36:31, dak wrote:
> Do you have a good suggestion how we could separate out the part
engraving
> forced decision into settings that operate per-voice rather than
> per-part-engraver?

> Maybe something like \forceAutomatic \forceChord \forceApart
\forceSolo with
> increasing priority (Solo in one voice beats Chord in the other)?

Rock crushes scissors, jazz beats rock.  I'll think about it when I get
into solo inhibition, but first I'll redo the chord-range option
properly.

One thing just occurred to me.  If this option is going into the UI, do
you think the numbers should be 1-based for easier comprehension by
musicians?  For example, use '(1 . 9) to allow chording unisons to
ninths, rather than '(0 . 8)?

https://codereview.appspot.com/144170043/
James Lowe | 30 Oct 22:40 2014
Picon

PATCHES: Countdown for November 2nd 2014

Hello,

Here is the current patch countdown list. The next countdown will be on
November 2nd.

You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch

____________________

PUSH:

Trevor Daniels: Incorrect vector form of break-visibility
http://code.google.com/p/lilypond/issues/detail?id=4175

David Nalesnik: Patch: Use number-pair-list? with 'control-points
http://code.google.com/p/lilypond/issues/detail?id=4174

David Kastrup: Patch: tie-formatting:
s/Stem::note_head_positions/Stem::head_positions/
http://code.google.com/p/lilypond/issues/detail?id=4170

Trevor Daniels: Add description of "dimension" to Technical Glossary
http://code.google.com/p/lilypond/issues/detail?id=4168

James Lowe: Patch: Added recorder diagram
http://code.google.com/p/lilypond/issues/detail?id=4163

David Kastrup: Patch: Implement -dtags-to-keep and -dtags-to-remove
commandline options
(Continue reading)

lemzwerg | 29 Oct 06:53 2014

Issue 4151: implicitTimeSignatureVisibility->initialTimeSignatureVisibility (issue 163520043 by tdanielsmusic <at> googlemail.com)

LGTM

https://codereview.appspot.com/163520043/
k-ohara5a5a | 29 Oct 06:06 2014
Picon

Re: Add chord range to make-part-combine-music (issue 144170043 by nine.fierce.ballads <at> gmail.com)

This seems to allow the style of partcombine where unisons are
double-stemmed which would be very nice.
You can, if you like, put a small image (like a 2kB png) on the lilypond
issue tracker showing the desired output; then people can understand the
purpose of the patch.

> I see that recording-group-emulate calls (ly:context-property child
> 'instrumentTransposition)).  Should I look to that as an example?

No.  We could not find any way in which this was functioning.
  (http://code.google.com/p/lilypond/issues/detail?id=645#c11)
recording-group-emulate works before the Property_engraver gets a chance
to set instrumentTransposition on the output Staff.

It would be nice to be able to change the chord-range in the middle of
the music, but in general, context properties seem a poor choice,
because the output contexts are not even determined when \partcombine
executes.

If you used a context, the way David is trying for partCombineChords,
etc., you could say
   combined = \displayMusic \transpose c c' \partcombineUp
     {c4 c c c  \set partcombineChordRange = #'(2 . 8)
        | c c c c}
     {c4 c c e | c c c c }
but then user would be understandably confused when
   \new Staff \with { partcombineChordRange = #'(4 . 5) } \combined
has no effect.

You see what Reinhold did when he created \partCombineChords and so on;
(Continue reading)

k-ohara5a5a | 28 Oct 08:00 2014
Picon

Re: Reimplement forced partcombine decisions via context properties (issue 144600043 by dak <at> gnu.org)

Now I see the problem.  The properties you are using are those created
in a pre-engraving step, done separately on each of the inputs to
\partcombine.  Using properties of those separate contexts for the
force-part-combine state is a bad idea.

Right now, \partCombineApartOnce, etc., affects the split-list output of
the music function \partcombine
  \displayMusic \partcombine
   {\partcombineApart
    e4 e e \partcombineApartOnce e | e e e e}
   {c4 c \partcombineChords c c     | c c c c } }
so it makes sense to store the state in a variable in the scheme that
implements \partcombine as it is done now.

In order to make a \once\partcombineApart work like most other
\once\override commands, you would have to do something like delay the
forced part-combine decisions until the real engraving, write a real
Part_combine_engraver that lives in the Staff, and store the forced
state in properties in that Staff (maybe renaming what is currently
called Part_combine_engraver to Part_combine_text_engraver).

https://codereview.appspot.com/144600043/diff/40001/scm/part-combiner.scm
File scm/part-combiner.scm (right):

https://codereview.appspot.com/144600043/diff/40001/scm/part-combiner.scm#newcode262
scm/part-combiner.scm:262: (evs1 (recording-group-emulate m1 listener)))
So each of the two music expressions going into \partcombine is sent
through a scheme engraver, with an output definition 'partCombineLister'
that turns of graphical layout, to generate events for \partcombine to
analyze and turn into a music expression to go into the usual engravers.
(Continue reading)

James Lowe | 27 Oct 22:31 2014
Picon

PATCHES: Countdown for October 30th 2014

Hello,

Here is the current patch countdown list. The next countdown will be on
October 30th.

You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch

____________________

PUSH:

David Kastrup: Patch: tie-formatting:
s/Stem::note_head_positions/Stem::head_positions/
http://code.google.com/p/lilypond/issues/detail?id=4170

Trevor Daniels: Breaking syntactic sugar
http://code.google.com/p/lilypond/issues/detail?id=4169

James Lowe: Patch: Added recorder diagram
http://code.google.com/p/lilypond/issues/detail?id=4163

David Kastrup: Patch: Implement -dtags-to-keep and -dtags-to-remove
commandline options
http://code.google.com/p/lilypond/issues/detail?id=4160

Trevor Daniels: Slur and Tie subproperties for 'details should be documented
http://code.google.com/p/lilypond/issues/detail?id=1154

David Kastrup: LilyPond should accept a tie between notes which are
(Continue reading)

nine.fierce.ballads | 27 Oct 03:30 2014
Picon

Issue 4176: Add regtests for numbered and single-digit time signature styles (issue 162300043 by nine.fierce.ballads <at> gmail.com)

Reviewers: ,

Description:
Add regtests for numbered and single-digit time signature styles
https://code.google.com/p/lilypond/issues/detail?id=4176

Please review this at https://codereview.appspot.com/162300043/

Affected files (+38, -0 lines):
   A input/regression/time-signature-numbered.ly
   A input/regression/time-signature-single-digit.ly

Index: input/regression/time-signature-numbered.ly
diff --git a/input/regression/time-signature-numbered.ly  
b/input/regression/time-signature-numbered.ly
new file mode 100644
index  
0000000000000000000000000000000000000000..81cc81b4d279e2d434999c84df8dc12596fc6595
--- /dev/null
+++ b/input/regression/time-signature-numbered.ly
 <at>  <at>  -0,0 +1,22  <at>  <at> 
+\version "2.19.16"
+
+\header {
+  texidoc = "The numbered time signature style prints a fraction."
+}
+
+#(ly:expect-warning "strange time signature found: 1/99999")
+#(ly:expect-warning "strange time signature found: 10/6")
+#(ly:expect-warning "strange time signature found: 8/20")
(Continue reading)

nine.fierce.ballads | 26 Oct 04:27 2014
Picon

Issue 3286: add single-C time signature style (issue 164830043 by nine.fierce.ballads <at> gmail.com)

Reviewers: ,

Description:
Issue 3286: add single-C time signature style

This style is identical to single-digit except that C is printed
instead of 4 and cut-C is printed instead of 2.

Please review this at https://codereview.appspot.com/164830043/

Affected files (+28, -0 lines):
   A input/regression/time-signature-single-c.ly
   M lily/time-signature.cc

Index: input/regression/time-signature-single-c.ly
diff --git a/input/regression/time-signature-single-c.ly  
b/input/regression/time-signature-single-c.ly
new file mode 100644
index  
0000000000000000000000000000000000000000..8921bcf98a5bd4b5e02742431d3d7677615ab12a
--- /dev/null
+++ b/input/regression/time-signature-single-c.ly
 <at>  <at>  -0,0 +1,20  <at>  <at> 
+\version "2.19.16"
+
+\header {
+  texidoc = "The single-C time signature style prints a C for any time  
signature fraction with 4 in the numerator and print a cut-C for any time  
signature with 2 in the numerator."
+}
(Continue reading)

Dan Eble | 26 Oct 03:49 2014
Picon

"Parsed object should be dead" with LilyDev 3

Does anyone else see a lot of “Parsed object should be dead” programming errors in the regression test logs?
— 
Dan

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Dan Eble | 26 Oct 02:34 2014
Picon

Time signature markups

time-signature.cc <http://time-signature.cc/> has a comment at the top saying, “This file should go;
the formatting can completely be done with markups.”  Can anyone point me to a good example of that, or is
it a unique idea?

Thanks,
— 
Dan

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Dan Eble | 25 Oct 20:15 2014
Picon

Non-numeric time signatures

Simon (and all),

Regarding the request to display 4/2 as cut-c by default, https://code.google.com/p/lilypond/issues/detail?id=3286

I think it would make sense to extend the default style to offer a simple way to get the doubled symbols:
    2/1 -> double cut-c (Schubert op. 90 no. 3)
    4/2 -> double c (my obscure hymnal)

You mentioned that you would be satisfied if there were a different style for your alla breve case.  Do you
really need a style or is the following good enough?

timeAllaBreve = {
  \once \override Staff.TimeSignature.stencil = 
  #(lambda (grob)
     (grob-interpret-markup grob
      #{ \markup \musicglyph #"timesig.C22" #}))
  \time 2/1
}

Another thing that occurs to me is a possible parallel with non-numeric tempo.  When the single cut-c symbol
is used to indicate 2/1, does it need to be annotated with text?  If so, would something like \time “alla
breve” 2/1 be any better than the way it has to be done now?

Another potential use for that is \time “swing” 4/4.

Regards,
— 
Dan

_______________________________________________
(Continue reading)


Gmane