9 Aug 23:14 2014

### Documentation for issues 3601 (based on 3581), 4042 (NR: "MIDI output", Section 3.5)

Hi,

In response to
<http://lists.gnu.org/archive/html/lilypond-devel/2014-08/msg00060.html>,
here's some new documentation for Section 3.5 ("MIDI output") of the
Notation Reference (v2.19.11).  The main goal of the proposed additions
is to describe the MIDI context properties implemented in issues 3581
(with issue 3601 about the missing documentation) and 4042.  (I'm the
author of the code patches in those issues.)

To support this goal, I'll also propose changes to some existing
sections of the documentation: these changes include an attempt to (at
least partially) document the Score.midiChannelMapping context property,
and an expanded description of MIDI channels.

The changes proposed (in plain text) to the documentation are
interleaved with my comments and questions.  If it'd be more useful to
format the actual changes in some other way, please tell me what I need
contributions" mentioned in the Contributor's guide, however from the
previous discussion I understood that it would still be OK to just send
these suggestions to the bug list.  This is the first time I've ever
proposed any changes to the documentation...)

Best regards,
Heikki Tauriainen

======================================================



8 Aug 16:53 2014

### barcheck failure with partial in middle of piece

I'm getting an unexpected barcheck failure when using partial in the middle
of a piece.  In the minimal example below, if you comment out the chords the
first barcheck succeeds, but with the chords included it fails.  (Also the
beaming in that first measure is off.)

Not sure if this is a bug or if I'm expecting too much from \partial.  In
2.18 there was a warning for using \partial after the start of a piece, but
not in 2.19.

(Actual use case: in fiddle tunes where the A and B parts are each repeated,
and there's a line \break before the start of the B part...  the pickup
notes for the B part should be notated at the beginning of the B part,
rather than at the end of the A part, to easily see them when repeating back
to the start of the B part.  Hence the use of partial in the middle of a
piece.)

Cheers,
-Paul

\version "2.19.11"

melodyOne = \relative {
\time 6/8
a'8 a a a a a | % this barcheck fails when chords are present
\partial 8
d8 |
c8 c c c c c |
}

chordsOne = \chordmode {


8 Aug 10:20 2014

### Issue 1129: Font styles return to default when font size changed

Is this likely to be resolved? Perhaps a more fully-functioning workaround?

I'm not nearly clever enough to do either myself, and it looks as though
I must generate a series of scores with manually-set page numbers (and
blank pages) and combine them with pdftk.

--

--
Hilary

7 Aug 14:27 2014

### Documentation of self-alignment-X


the docs (
http://www.lilypond.org/doc/v2.18/Documentation/internals/self_002dalignment_002dinterface
) say:
"
self-alignment-X (number)

Specify alignment of an object. The value -1 means left aligned, 0
centered, and 1 right-aligned in X direction. Other numerical values may
also be specified.
"
I think it would be well worth adding to the last sentence:

The unit is half the object width.

Richard Shann

6 Aug 21:34 2014

### spacing.itely sectioning does not match menu

Hi all,

Building docs from scratch, I get an error in French (I'm on it) but also

"Please check the logfile notation.bigtexi.log for errors

make[3]: *** [out-www/notation-big-page.html] Error 255
make[3]: *** Waiting for unfinished jobs....

Please check the logfile notation.splittexi.log for errors
"

and in notation.splittexi.log:

"
** Node following Optimal page breaking' in menu Optimal page turning'
and in sectionning Minimal page breaking' differ
** No node following One-line page breaking' in menu, but Optimal page
turning' follows in sectionning
"

* Manual page breaking::
* Optimal page breaking::
* Optimal page turning::
* Minimal page breaking::
* One-line page breaking::

But sectioning is:
1488:	 <at> subsection Page breaking


3 Aug 17:17 2014

### LSR 405 (Changing the tuplet number)

One remaining occurrence of \times in texidoc:

- the denominator of the argument to the  <at> code{\\times} command.
+ the denominator of the argument to the  <at> code{\\tuplet} command.

Cheers,
Jean-Charles

2 Aug 19:36 2014

### Ambiguous (de)crescendo in MIDI error

Something that is seen a lot in 19th and 20th century music is a crescendo
or decrescendo without going to a specific dynamic.  The performer is given
the freedom to decide how much to change the dynamics.  This causes an
error message: "programming error: Impossible or ambiguous (de)crescendo in
MIDI."

%%% BEGIN
\version "2.19.10"

\score {
\relative c' {
c1 \p | c4 \< d e f | g \> f e d | c1 \p
}
\layout {}
\midi {}
}
%%% END

This error message should be a warning and give some line number to the
offending code.

Knute Snortum
(via Gmail)

1 Aug 16:19 2014

### version 2.18 discrapency

> I'm not top posting.
wellcome test file of version 2.18 mentions:
\version "2.16.0"

31 Jul 19:35 2014

### Custom contexts: \accepts behaves weirdly for grouping contexts

Hi,

i have noticed something strange wrt/ \accepts behaviour.

\layout {
\context {
\Staff
\name "Foo"
}
}

\new Foo { c'1 }

of a Foo a Staff is created), because no context accepts Foo.  So i do

\layout {
\context {
\Score
\accepts "Foo"
}
\context {
\Staff
\name "Foo"
}


30 Jul 12:41 2014

### leave all August

Dear Bug Squad

I'll be away from my computer all the month of August.
I'll still read the emails on mobile but I won't be able to reply to bug
reports or verify the issues.
See you in September!

Ciao
Federico

29 Jul 00:58 2014

### Re: self-alignment-X has negligible effects on dynamics

Well, the output while using 'self-alignment-X with DynamicText _has_ changed.
This needs thoroughly documentation.
And it will likely break some of my custom-functions.
This will not be a big problem for me, I assume, though maybe others
rely on the old behaviour as well.

I uploaded two images for better comparing, with ref-points and
testing TextScript, too:
2.18.0
http://imgur.com/2vcBG3n.png

2.19.11
http://imgur.com/vE8HaSg.png

(The source-code uses my most recent code for ref-points, which may
not be the same as in openlilylib, is attached.)

All in all I'd vote for the new behaviour, because it seems to be more
logical and consistent to how TextScript is aligned.

Cheers,
Harm

_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
`