| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | Issue 2245: always align dynamics and lyrics on "main" notehead...Until now, LyricTexts and DynamicTexts had their X-parents set to
the first NoteHead in the NoteColumn. This resulted in inconsistent
alignment - placement of lyrics and dynamics depended on the order
of notes in the input:
% this was aligned differently
{ <f' g'>1\p <g' f'>\p }
\addlyrics { la la }
By using NoteColumns themselves as the X-parents, we make sure that
the input order won't matter. Since the NoteColumn contains all NoteHeads
(including suspended ones, which usually should be ignored when aligning),
as well as Flags and some other objects, we cannot use its X-extent directly -
instead, we add a function for calculating X-extent of the "main" part of the
NoteColumn, i.e. X-extent of the non-suspended NoteHeads (represented by the
NoteHead furthest away from the stem).
| Janek Warchoł | 2014-07-08 | 1 | -0/+25 |
| * | Issue 3942: Scale slurs and ties when using \magnifyMusic. | Mark Polesky | 2014-07-06 | 7 | -16/+237 |
| * | TextScript, CombineTextScript: use aligned_on_parent...I think this makes more sense than just using "self-alignment".
It makes these grobs consistent with Lyrics and Dynamics, and
allows users to override their alignment more predictably.
Expected changes in output: TextScripts and CombineTextScripts
will be aligned slightly different when the user sets self-alignment-X
explicitly (parent notehead will be included in alignment, as in Lyrics).
Default placement should remain the same.
I'm also changing one regtest, just to make sure that despite slightly
changed alignment the markups will stick out far enough to the left.
| Janek Warchoł | 2014-07-05 | 1 | -12/+10 |
| * | Reg Tests: XML 02a fix incorrect last note duration...Issue 3974
Unofficial MusicXML test suite shows incorrect last not duration
the last note was duration 2 (undotted 64th) but shows dotted 128th
Added some missing <type> elements
Corrected the durations of the last measure
Fixes provided by Patrick Schmidt
| Patrick Schmidt | 2014-07-05 | 1 | -20/+35 |
| * | Reg Tests: XML 01b has an incorrect number of measures...Issue 3973
01b-Pitches-Intervals.xml from the Unofficial MusicXML
test suite contains only a single measure in MusicXML,
but there should be 41.
musicxml2ly is very tolerant here so the error doesn’t
show in the pdf.
Added missing <measure> elements
Fixed a typo in the title
Added missing <accidental> elements (They represent
the actual notated accidentals. Without these elements
there shouldn’t be any visible accidentals. So this is
actually a bug in musicxml2ly. The bug doesn’t show here
because musicxml2ly interprets the <alter> element which
represents the sounding pitch of a note.)
Fixes provided by Patrick Schmidt
| Patrick Schmidt | 2014-07-05 | 1 | -1/+135 |
| * | Issue 3968: Improve output of scheme-engraver.ly regtest. | Mark Polesky | 2014-07-02 | 1 | -39/+36 |
| * | Issue 3966/2: Allows the user to override the text property of ChordName...This is a reimplementation of issue 2813.
| David Kastrup | 2014-06-30 | 1 | -0/+13 |
| * | Issue 3966: Revert "Allows the user to override the text property of ChordName"...This reverts commit 0d4c79ec0f5d728ac7fe58b87ccf51079ec33766.
Conflicts:
input/regression/chord-name-override-text.ly
lily/chord-name-engraver.cc
Reverts patch of issue 2813.
| David Kastrup | 2014-06-30 | 1 | -13/+0 |
| * | Issue 3254: align unassociated lyrics using NoteColumn extent....This makes unassociated lyrics behave consistently with
associated lyrics. Until now, "standalone" lyrics
were left-aligned (more precisely: their X-offset was 0);
changing self-alignment-X didn't have any effect on them.
Now it's possible to specify their alignment, like with
associated lyrics.
Also, this changes how issue 104 was resolved (see 0b14e8b2e122d) -
alignment of syllables that are associated to a context without
noteheads is no longer aborted - and solves issue 247.
Later on, these changes should allow using aligned_on_parent for
other grobs (such as DynamicTexts).
Expected changes in output: all lyrics should be centered by default.
| Janek Warchoł | 2014-06-26 | 2 | -4/+47 |
| * | Color and/or parenthesize single dots in fret-diagrams...Issue 2752
Makes it possible to color and/or parenthesize single dots in
fret-diagram-verbose
Introducing two properties for use in fret-diagram-details
- fret-label-horizontal-offset
affecting the fret-label-indication, like the existing
`fret-label-vertical-offset'
- paren-padding
affecting the padding of the parenthesis
Extending relevant reg-tests.
Documenting it in NR, fretted-strings.itely
| Thomas Morley | 2014-06-20 | 3 | -15/+61 |
| * | Issue 3926: Add \magnifyMusic; clarify fontSize in docs. | Mark Polesky | 2014-06-05 | 1 | -0/+22 |
| * | Add regtest for \once \unset | David Kastrup | 2014-06-05 | 1 | -0/+37 |
| * | makelsr and update-with-convert-ly | Keith OHara | 2014-05-20 | 4 | -11/+11 |
| * | Tuplet brackets should reliably not follow kneed beams, regardless of whether......This affects input/regression/tuplet-number-kneed-beam-horizontal-fit,
and the following:
{
\override TupletBracket.bracket-visibility = ##t
\times 1/2 { c8 c''' c c''' }
}
Is it safe to call Beam::is_knee in Tuplet_bracket::calc_position_and_height?
| Devon Schudy | 2014-04-14 | 1 | -1/+4 |
| * | Bad positioning of tuplet numbers on kneed beams with Beam.positions override....Previously, when Beam.positions was overridden, tuplet numbers on kneed beams
would automatically be placed according to the bracket instead of against
the beam. This happened because the check for whether the beam was kneed
or not returned false in such cases. This patch replaces that check.
It also:
--adds a regtest demonstrating behavior with Beam.position overrides
--removes some redundant code
| David Nalesnik | 2014-04-05 | 1 | -0/+39 |
| * | Warn when \time is used in mid-measure, and reset measurePosition....This makes issues 3696 and 3888 less mysterious.
| Devon Schudy | 2014-04-05 | 1 | -0/+28 |
| * | Improve positioning of tuplet numbers for kneed beams....In the past LilyPond always placed tuplet numbers according to the
position of a bracket, though this bracket may or may not have actually
been drawn. This system led at times to tuplet numbers which appeared
stranded when there was a kneed beam and no visible bracket.
This patch positions the tuplet number independently of brackets and
close to the beam when the the bracket is not drawn, the beam is kneed, and
there is an appropriate beam segment to place the number against.
The side of the beam on which the number is placed is chosen by principles
derived from Gould. The number is centered horizontally on the beam.
Collision detection is also introduced. The number will be offset
horizontally if it is too close to an adjoining note column. All shifts
preserve the number's vertical distance from the beam. If the number is
too large to fit in the available horizontal space (between note columns
to either side), we use the old bracket-based positioning system. In the
event of a collision with an accidental, the tuplet number is moved
vertically, away from the beam.
The older behavior is always available through an override of the property
`knee-to-beam' which is introduced by this patch, and set by default to true.
This patch also adds a header file, `tuplet-number.hh', and provides
a number of regression tests illustrating various features.
| David Nalesnik | 2014-02-14 | 7 | -0/+228 |
| * | Issue 3835: Chord change detection in repeat alternatives...Let chord change detection in repeat alternatives happen in relation
to the chord active at the beginning of the first alternative.
| David Kastrup | 2014-02-08 | 1 | -0/+22 |
| * | Rerun scripts/auxiliar/update-with-convert-ly.sh | David Kastrup | 2014-02-02 | 35 | -113/+113 |
| * | Double G clef, tenor G clef, varpercussion clef and varC clef...This patch covers the clefs requested in:
http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00029.html
(double G clef and varpercussion clef)
http://lists.gnu.org/archive/html/lilypond-user/2013-11/msg00661.html
(tenor G clef)
http://code.google.com/p/lilypond/issues/detail?id=693
(varC clef)
| Marc Hohl | 2014-01-24 | 1 | -13/+30 |
| * | Run scripts/auxiliar/update-with-convert-ly.sh | David Kastrup | 2014-01-21 | 17 | -45/+45 |
| * | Simplify tremolo display (issue 3783) | David Kastrup | 2014-01-15 | 1 | -1/+1 |
| * | Issue 3751: Doc: Augment documentation for \inStaffSegno... Slightly expand referring text in NR 1.2.5
Expand NR 1.4.1 with additional text and examples
Add regression test
| Trevor Daniels | 2014-01-11 | 1 | -0/+33 |
| * | Add version to make-relative-copies regtest for GUB build | Phil Holmes | 2014-01-05 | 1 | -0/+2 |
| * | Revert "Prevents dynamics from colliding with cross-staff stems."...This reverts commit 3bcfd69d91f52f70598f73719fbed7aa6eea8ad3.
Conflicts:
input/regression/dynamics-avoid-cross-staff-stem.ly
lily/include/interval-minefield.hh
lily/include/self-alignment-interface.hh
lily/interval-minefield.cc
lily/new-dynamic-engraver.cc
lily/self-alignment-interface.cc
scm/define-grob-properties.scm
scm/define-grobs.scm
scm/output-lib.scm
| Keith OHara | 2014-01-03 | 1 | -19/+0 |
| * | note-spacing: let compressibility be uniform; issue 3304...Comments implied that half the width of accidentals, etc., was added
to the ideal spacing between notes, but in fact only compressibility
was affected. The non-uniform compressibility caused note-spacing
to become non-uniform when the lines were compressed. For example
A sequence {\stemUp a a d a] would have the head of the D tuck under
the preceding A.
This commit keeps spacing uniform on compressed lines until objects
come within padding of each other.
| Keith OHara | 2014-01-03 | 2 | -5/+4 |
| * | note-spacing: stretch somewhat uniformly...Start with a basic spring based on the note duration, and apply optical
corrections to that. This results in more consistent springs thus more
uniform stretching in polyphonic situations.
| Keith OHara | 2014-01-03 | 1 | -14/+4 |
| * | Adds outside-staff-interface and outside-staff-axis-group-interface...When a property exists in an interface, the property should make sense for
a sensible of grobs that implement that interface. Otherwise, the property
should be part of a separate interface that applies to a sensibly-sized
group of grobs.
Various properties having to do with outside-staff calculations belong to
grob-interface. This does not make sense for many grobs (StaffSpacing,
NoteSpacing, SpacingSpanner, StaffSymbol just to name a few). There is a
limited collection of grobs for which outside-staff properties make sense.
The outside-staff-interface provides a separate interface to be implemented
by these grobs.
The same is true for axis groups that place outside-staff grobs, which form
a limited subset of grobs implementing the axis-group-interface. Rather than
putting the relevant properties in the axis-group-interface, we move
them to an outside-staff-axis-group-interface.
| Mike Solomon | 2013-12-31 | 1 | -0/+1 |
| * | Issue 3727: Allow header blocks and output definitions in \score to precede m......This addresses a frequent complaint of users.
| David Kastrup | 2013-12-19 | 1 | -0/+22 |
| * | Completion_*_engraver: add means to preserve scale factor; issue 3650 | Keith OHara | 2013-12-06 | 2 | -10/+20 |
| * | Issue 3682/2: Change documentation and regtests for \beamExceptions | David Kastrup | 2013-12-04 | 3 | -34/+16 |
| * | Add regtest for copy/modify semantics of make-relative macro | David Kastrup | 2013-12-01 | 1 | -0/+29 |
| * | Add regtest for music argument semantics of make-relative macro | David Kastrup | 2013-12-01 | 1 | -0/+32 |
| * | Run scripts/auxiliar/update-with-convert-ly.sh | David Kastrup | 2013-12-01 | 1 | -2/+2 |
| * | Grace notes: only shorten previous note if overlapping...Previously a grace note after a rest shortened the last note before the
rest.
This patch shortens the previous note to the start of the grace note
rather than by the length of the grace note, so notes before rests
aren't affected unless the grace notes are longer than the rest.
| Devon Schudy | 2013-11-29 | 1 | -0/+14 |
| * | Issue 3648/6: Regtest for rhythmic sequences. | David Kastrup | 2013-11-19 | 1 | -0/+11 |
| * | Issue 3648/4: Let \displayLilyMusic deal with pure rhythms | David Kastrup | 2013-11-19 | 1 | -0/+3 |
| * | Use #{ 4 #} and #{ c #} for duration/pitch in optional-args regtest | David Kastrup | 2013-11-19 | 1 | -9/+4 |
| * | Issue 3644: A \score-lines markup list command for multi-lines embedded scores...Originally requested as issue 1334.
Like the \score markup, \score-lines is not called through the normal
markup list command mechanisms as it would require something awkward
along the lines of
\score-lines ##{ \score { ... } #}
to get this through. Instead, a reserved word \score-lines in the
parser will manually call the command with an embedded score, leading
to just
\score-lines { ... }
This is somewhat clumsy in several ways: it requires an additional
reserved identifier (no other reserved identifier contains a dash),
and it means that a score may occur in a file without an explicit
enclosing \score command.
Nevertheless, the previous semantics implemented as issue 1334 were
not tenable: particularly after issue 3270 had been passed, it was
close to impossible for the average user to come up with a way of
getting an actual markup list from a score.
Note that there are as of yet no user-level commands spacing a markup
list in a way similar to the spacing inside of a \score markup.
| David Kastrup | 2013-11-13 | 1 | -0/+40 |
| * | Remove dots that overflow chords; issue 3179 | Keith OHara | 2013-11-06 | 1 | -0/+17 |
| * | page-layout: nonstaff lines, follow-up commit 7a60a342 | Keith OHara | 2013-11-02 | 1 | -1/+7 |
| * | Issue 2379: resetting autoBeaming after a cadenza...Letting measurePosition track the grace state of current_moment
unconditionally keeps it from moving into uncharted territory when
Timing.timing gets switched on or off during grace times.
| David Kastrup | 2013-11-02 | 1 | -0/+21 |
| * | Improvements to \offset...Property can be specified with or without #' prefix.
Directed tweaks are possible.
Music is returned in case of a failed tweak on that music. This eliminates
cryptic "post-event expected" error.
Regtest:
--remove #' prefix before property names
--remove unnecessary # before numbers
--add example showing directed tweaks
--faulty tweak converted to an override of correct property
Revise docstring of find-value-to-offset in `scm/music-functions.scm.'
| David Nalesnik | 2013-10-31 | 1 | -13/+22 |
| * | Adds ly:generic-bound-extent function....This allows for spanner functions written in Scheme to use bound
extents instead of the full extents of their bounds.
Adds a regtest to show this at work with BendAfter.
Note that this can likely be replaced in the future with horizontal
skylines.
| Mike Solomon | 2013-10-31 | 1 | -0/+23 |
| * | format-metronome-mark and metronome-markup don't support styles other than de......issue 3096
- introducing 'styled-metronome-markup' with the (currently quite
theoretical) possibility to use another font here. For now
the font-argument is used only to make
\override MetronomeMark #'font-name = ...
possible.
- adding 'flag-style to define-grob-properties.scm, the
MetronomeMark-properties in define-grobs.scm and in text-interface.cc
- adding a regtest for different 'metronomeMarkFormatter'.
It's now possible to override MetronomeMark with 'style, 'flag-style and
'font-name to customize the appearance.
| Thomas Morley | 2013-10-29 | 1 | -0/+108 |
| * | Run scripts/auxiliar/update-with-convert-ly.sh...Actually, this is an understatement. This is the result of
scripts/auxiliar/update-with-convert-ly.sh
git checkout HEAD ly/{engraver,music-functions,property}-init.ly input/regression/display-lily-tests.ly Documentation/{,*/}learning/*.itely
and then committing.
| David Kastrup | 2013-10-25 | 10 | -39/+39 |
| * | Issue 3313: Add the command \offset...The ability to offset values of various properties would be a useful
enhancement of LilyPond. Currently, this is possible for default values
of the property 'control-points using the \shape command. The following
patch seeks to generalize the application of offsets to grob properties.
Both overrides and tweaks are supported, on the model of \shape and
\alterBroken.
Offsets are currently limited to three data types: number, number-pair,
and number-pair-list (this last is defined by this patch and represents
the type used, for example, by 'control-points). Offsets are limited to
the properties listed in the grob descriptions contained in
`scm/define-grobs.scm'. Offsets will be reckoned against an override
currently in effect; otherwise, the default setting from the grob
description will be used.
| David Nalesnik | 2013-10-13 | 1 | -0/+73 |
| * | Making flat flags available...Issue 3591
The markup-command 'note-ny-number' and the relvant regression-
tests are extended, too.
The sippet 'using-alternative-flag-styles.ly' from
Documentation/snippets/new/ isn't changed for now, will be tackled
in a follow up.
| Thomas Morley | 2013-10-11 | 3 | -2/+16 |
| * | Add regtest for quoted identifiers | David Kastrup | 2013-10-04 | 1 | -0/+26 |
| * | Add regtest for Grace_auto_beam_engraver | David Kastrup | 2013-10-04 | 1 | -0/+40 |
