Midi2ly: handle staves with more than four voices. Fixes #1580.
The correct \voiceOne, \voiceTwo,.. etc. mapping is probably lost in
such cases. We need a good test file that shows how the mapping
should be handled.
Mike Solomon [Mon, 28 Mar 2011 14:58:29 +0000 (10:58 -0400)]
Assures smooth transitions at glissando line breaks.
When a glissando breaks over lines, the left point of the beginning-of-line
glissando picks up on the y-axis where the right point of the end-of-line
glissando ends.
Janek Warchoł [Fri, 18 Mar 2011 11:19:56 +0000 (12:19 +0100)]
downstem 64th and 128th flag touchup
64th and 128th flags are made less trianglish (squeezed at the bottom),
also the gap between flag and notehead is reduced.
The flags look now more consistent with 16th and 32nd flags,
as well as with upstem flags.
Janek Warchoł [Fri, 18 Mar 2011 10:38:37 +0000 (11:38 +0100)]
shortening of downstem 8th flag
This was discussed here:
http://lists.gnu.org/archive/html/lilypond-devel/2011-03/msg00128.html
Not many people gave their opinions;
Carl prefers not changing this, but he doesn't feel strongly about it,
Werner is not sure, but feels a bit more like shortening the flag,
Mike agrees to make the change.
My opinion is that it should be changed.
Janek Warchoł [Fri, 18 Mar 2011 10:33:55 +0000 (11:33 +0100)]
including blot_diameter in calculating upstem flag lengths
Doing so is needed in case of 32nd flag,
because after changing 32nd stem length it touches staff line.
In case of 64th and 128th this isn't really needed,
but i added it for consistency's sake.
James Lowe [Tue, 22 Mar 2011 17:55:18 +0000 (17:55 +0000)]
Doc: NR addition to existsing @knownissue
As per Mike Solomon's suggestion, added additiona additional sentence
to exitsing @knownissue for collisions with automatic beaming.
Included a simple @lilypond to illustrate the issue (thanks Mike!)
Also took opportunity to tidy up the cindex for beams (make them more
consistent - beam vs beams vs beaming etc.) added a few more and removed
some repeated ones.
removed some unnecessary line spaces in the itely file itself
Trevor Daniels [Tue, 22 Mar 2011 17:09:39 +0000 (17:09 +0000)]
Docs: LM: New behaviour of 'outside-staff-priority
- certain score-level objects are now moved to the top
staff just after line breaking so they are now positioned
correctly in the outside-staff-priority hierarchy.
(It's been this way since 2.13.4)
James Lowe [Tue, 15 Mar 2011 18:15:24 +0000 (18:15 +0000)]
Doc: Added @knownissue to NR for fingering
By default double-diogit fingering (i.e. >9) is no possible using
standard fingering markups. There is an LSR that has been posted for
approval and can be included as necessary.
Tidied up some grammar and minor punctuation changes.
Mike Solomon [Tue, 15 Mar 2011 10:57:49 +0000 (06:57 -0400)]
Changes the spanner-placement property of FootnoteSpanner to ly:dir
Now, the annotation on a spanner will always fall on the first (LEFT
or CENTER) or last (RIGHT) broken spanner if the spanner is broken.
Defaults to LEFT.
Midi: only output PORT if midiChannelMapping == #'voice.
This reduces the risk of creating trouble for the default
#'instrument-mode output and the old #'staff-mode output,
while leaving the option open for MIDI-players to do the
right thing with ports in the #'voice-mode: in each track,
each channel 0 should be able to play another instrument.
Midi2ly: refactoring: initial support for instrument<->channel mapping.
Files using instrument<->channel mapping [and thus obviously] combined
with voice<->track mapping (the new LilyPond default) are now handled
by midi2ly.
Nicolas Sceaux [Wed, 16 Feb 2011 21:42:36 +0000 (22:42 +0100)]
Fret diagram fixes
- fix padding and size of mute/open signs when size is overridden
- fix first fret label position
- allow fully customizable first fret label
- allow per-finger dot color change
- add reg test for fret diagram magnification
- add a test case for first fret custom label
- add a test case for dot color inversion
Midi: allow alternate channel mappings: per instrument, staff, voice.
The property midiChannelMapping specifies the mapping of MIDI channels:
per instrument (default), staff or voice.
The default mapping, per instrument, makes for optimal re-using of
channels. Per voice mapping allows re-creating of voices and
arranging them on staffs with the current midi2ly. Per staff mapping
closely matches the old default.
With voices mapped to tracks, midi2ly can neatly recreate voices
without needing to do tricky guessing. Some extra trickery will
be needed to re-assign the voices to the correct staves.
Also, midi channels are optimally re-used: identical midi instruments
accross different staves share the same channel. This can fix
running out of channels in some cases, where similar instruments
are notated on different staves.
projects / lilypond.git / log