Activity for Simon Albrecht
-
Simon Albrecht posted a comment on ticket #5638
And here’s the main example from that introduction—compiled with v2.19.83: \include "oll-core/package.ily" \loadModules snippets #'((notation-snippets shaping-bezier-curves shapeII)) \paper { ragged-right = ##t indent = 0 } SUp = \change Staff = "up" SDn = \change Staff = "down" \new PianoStaff << \new Staff = up \relative d { \clef G \key e \major \time 3/16 \voiceTwo \slurUp \SDn \times 2/3 { b32( g' b } \SUp \times 2/3 { d g e' } \times 2/3 { d b g') } | \SDn \times 2/3 { b,,,32( g' b } \SUp \times...
-
Though I would argue that in this case the left endpoint should be slightly further up.
-
There are some examples in the documentation for shapeII in openlilylib:
-
A very valiant undertaking—it would certainly be great to see improvement there! I don’t think many people have taken notice yet—you should certainly post to the user and/or devel list to ask for input. I haven’t done many projects myself that required extensive slur tweaking.
-
Improve Lilypond Automatic Slurs
-
Make build output terse by default
-
Another example: \version "2.19.83" #(set-global-staff-size 16) \paper { #(set-paper-size "a9") indent = 0 } \header { tagline = ##f } partA = \relative c'' { R1 | \partcombineApart b1 | } partB = \relative c' { R1*2 | } \markup \justify { The second half of the rest in \typewriter "\partB" is ignored: } \partcombine \partA \partB
-
Mark’s initial example does trigger the bug with 2.19.83 (Ubuntu 16, 64-bit), while my smaller example does not… A couple similar issues were found to be caused by rounding issues. Maybe this one too?
-
mid-bar \newSpacingSection leads to collisions
-
The two examples added by Alexander work perfectly fine with 2.19.83. The original example still shows the bug: \version "2.19.83" \relative c' { \override Score.SpacingSpanner.packed-spacing = ##t \repeat unfold 20 { c2. \newSpacingSection e4 } } (see original.png) But as this example shows, packed-spacing isn’t at the core of the problem, but any mid-bar use of \newSpacingSection will disable some collision control: \version "2.19.83" \relative { \accidentalStyle forget <cis' eis gis cis>2 \newSpacingSection...
-
Doc: Document new function for css-color (accompanying x11-color)
-
bendAfter broken by chords
-
TextSpanner: left text incorrectly influences dashes
-
clash between staves
-
setting direction of instrumentName makes lilypond crash
-
cross-staff slur hides text in eps backend
-
staffgroup-staff-spacing may be applied multiple times per StaffGroup
-
The considerations on beam subdivision in [#5547] are possibly pertinent.
-
The considerations on beam subdivision in [#5547] are probably pertinent.
-
Beams with multiple subdivisions
-
We should regard this as superseded by [#5547].
-
Related issues: [#1515] [#2361] [#2474] [#4738] [#4739] [#4740] [#4919]
-
This is related to [#5547].
-
Wrong beam subdivision when duration == baseMoment
-
This is superseded by [#5547].
-
Wrong beaming with rest before subdivision
-
Like [#4738], this is also superseded by [#5547].
-
Clean up Beaming_pattern::beamify
-
This is superseded by [#5547].
-
Grand Comprehensive Subdivided Beams Issue
-
Similar issues: https://sourceforge.net/p/testlilyissues/issues/472/ https://sourceforge.net/p/testlilyissues/issues/1152/
-
Almost-synchronous accidental makes the first one collide
-
Rafael Fontenelle adds: Indeed, Pango 1.44 dropped support to FreeType font, as posted in https://blogs.gnome.org/mclasen/2019/05/25/pango-future-directions/.
-
Compatibility with pango 1.44
-
magnifyStaff breaks noteHead offset in some chords with a 2nd in them and ledger line(s)
-
One possible solution would be a markup command that returns the current bar number for use in instrumentName/vocalName.
-
The two issues are unrelated, since 3038 talks about \repeat unfold.
-
This issue talks about \repeat unfold, while #5031 talks about \repeat volta. I don’t think there’s any relation between the two.
-
merge-differently-headed and merge-differently-dotted merge incorrectly with NoteColumn.force-hshift overridden
-
LyricExtender unduly shortened for end-of-line clef change
-
X-aligning problem with chords containing unisons
-
modern-straight-flag and flat-flag should correspond to beams in thickness and gap
-
The problem with putting the whiteout itself 0.5 or 1 layers below is that it may well mess with use cases that already use that layer for other grobs, so I think it would rather be a matter of the drawing process intelligently handling grobs and whiteout on one layer without changing layer values. That might be somewhat difficult…
-
Improve whiteout behaviour with indifferent layering
-
Doc: NR - Measure_grouping_engraver needs beatStructure and baseMoment set as well to work as expected
-
Another fingering vs. accidental problem
-
LigatureBracket shouldn’t avoid invisible stems
-
Issue [#3037] fixed the problem with line breaks, so is there any remaining reason why this would be considered necessary? It doesn’t seem like the functionality of tuplet brackets is serving ligature brackets badly, and why reinvent the wheel?
-
improvisationOn doesn’t work in DrumStaff with altered drumStyleTable
-
Clefs at line break shorten slurs unduly
-
Overlap of key signature and first note
-
Crash with specific combination of pitch and omitted note head
-
Crash with specific combination of pitch and omitted note head
-
tied-over accidentals take space if another accidental is added
-
Reported here: https://lists.gnu.org/archive/html/bug-lilypond/2018-05/msg00046.html
-
Possibly related, but closed, issue: [#367]
-
layout-set-staff-space confuses chord note head placement in a certain situation
-
layout-set-staff-size doesn't work properly
-
layout-set-staff-size doesn't work properly
-
Enhancement: easier support for alternative music fonts
-
Redundancy in the LM regarding `\omit` and `\hide`
-
Stop assuming the reader knew about gmane. http://codereview.appspot.com/331660043
-
Originally posted by: simon.al...@mail.de LSR snippet 1010 has an updated snippet for Shevek’s MarkLine context workaround, linked to above in comment #5.
-
LM: incorrect staff-staff-spacing example (regression)
-
I meant manually omitting the accidental – which works fine but is not at all resistant to layout changes.
-
Segfault with midi and \new StaffGroup
-
Fails make check .. for example: \sourcefilename "/tmp/lilypond-autobuild/input/regression/metronome-mark-broken- bound.ly" \sourcefileline 0 \version "2.17.11" \header { texidoc = "A @code{MetronomeMark}, @code{RehearsalMark} and @code{BarNumber} should not effect the starting point of spanners. " } << \new Staff { e'1 \time 4/4 \break | \tempo \markup { "fooooo" } 4 = 90 e'1 | e'1 | } \new Staff { \override Score.MetronomeMark.break-visibility = #all-visible \override TupletBracket.breakable =...
-
A more condensed example by Kieren MacMillan: \version "2.19.61" musicA = { g'1\> R1\! } musicB = { b'1\> R1\! } \new Staff \partcombine \musicA \musicB
-
[partcombine] partcombine can't handle simultaneous hairpins
-
I agree.
-
Version ‘fuzzy-7’ looks great!
-
I second that.
-
whole note angled tremolo
-
Homepage pop-ups are annoying
-
Create italic numbers for Feta
-
Create italic numbers for Feta
-
Apparently they didn’t. Thanks for spotting the mistake!
-
\reduceChord seems good to me. However, it would still be good to have this enabled...
-
Rough sketch at user interface: \set Score.voltaBarNumbering = #'() \set Score.voltaBarNumbering...
-
Bar numbering in volta repeats: add option to count once or as often as played
-
Bar numbering in volta repeats: add option to count once or as often as played
-
Bar numbering of alternatives
-
Since I don’t have access to my Google account right now, I can’t upload the patch...
-
NR 1.2.1.d: Split note correctly
-
Issue 5026: \crossStaff mangles all grace note flags.
-
\crossStaff mangles all grace note flags
-
Web: minor improvements to the ‘Bug reports’ page
-
Point to `\resetRelativeOctave` in NR 1.1.1.b
-
Allow users to use file names also present in `ly/`
-
Allow users to use file names also present in `ly/`
-
Forwarded from Alexander Kobel, out of the duplicate issue 5018: Automatic LyricExtenders...
-
Enhancement: automatically engrave lyric extenders
-
Forwarded from Alexander Kobel, out of the duplicate issue 5018: Automatic LyricExtenders...
-
Automatic LyricExtenders
-
In my authority as member of the Right Honourable Bug Squad :-) I dare to redirect...
-
New patchset with changed wording according to Graham’s comments, and reverting the...
-
Feature request: auto-hyphenation in markup
-
Patch set 3 uploaded. I attach the current state as a single patch.
-
Web: minor improvements to the ‘Bug reports’ page
-
Point to `\resetRelativeOctave` in NR 1.1.1.b
1 >