Comment #2 on issue 984 by k-ohara5...@oco.net: Noteheads don't merge when
one of the voices contains a second
http://code.google.com/p/lilypond/issues/detail?id=984
There is a TODO comment in note-collision.cc check_meshing_chords()
indicating a plan to resolve this, by filtering out the h
mike apollinemike.com apollinemike.com> writes:
> 2.
> 2.
> merge-differently-headed works on the first chord but not the second.
>
> Is this a known issue?
>
http://code.google.com/p/lilypond/issues/detail?id=984
Noteheads don't merge when one of the voices contains a second
__
A revision to the snippet in section 3.5.1 of the Notation Reference is
awaiting
approval in the LSR.
Changing MIDI output to one channel per voice [corrected]
The only change is the text. The old text "there are only 16 MIDI channels
available per track" was wrong. Tracks are purely file or
Updates:
Labels: -Patch-new Patch-review
Comment #6 on issue 1618 by k-ohara5...@oco.net: unpredictable placement of
rests
http://code.google.com/p/lilypond/issues/detail?id=1618
I resolved my connection problem, and uploaded the patch and a regtest at
http://codereview.appspot.com/4
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical Regression
New issue 1636 by k-ohara5...@oco.net: midiVolume 0.0 not respected
http://code.google.com/p/lilypond/issues/detail?id=1636
Setting midi volume to 0.0 for some instruments is very useful for
proofreading (proof-liste
Updates:
Labels: fixed_2_15_0 backport
Comment #9 on issue 1620 by k-ohara5...@oco.net: Midi overflow with
instrument changes
http://code.google.com/p/lilypond/issues/detail?id=1620
So we need to mention midiChannelMapping in CHANGES.
I will try to add that soon.
midiVolume did work
Comment #5 on issue 1618 by percival.music.ca: unpredictable placement of
rests
http://code.google.com/p/lilypond/issues/detail?id=1618
Amazing work as always. I can confirm the clean regtests, and I've
uploaded the patch here:
http://codereview.appspot.com/4441066/
Updates:
Labels: Patch-new
Comment #4 on issue 1618 by k-ohara5...@oco.net: unpredictable placement of
rests
http://code.google.com/p/lilypond/issues/detail?id=1618
The problem is that rest-collision takes an array of rests, but handles
*only* the first rest in the array. The order
> It appears to me right now that chordGlissando is a sufficiently rough hack
> that it should probably be removed from the distribution and just be present
> in the LSR.
+1.
I will have time this weekend to work on an implementation that uses a context
property to control how glissandi are types
On 11-04-25 11:33 AM, Carl Sorensen wrote:
On 4/25/11 11:26 AM, "Federico Bruni" wrote:
Il giorno lun, 25/04/2011 alle 00.09 +0200, Federico Bruni ha scritto:
Or should I rather edit
Documentation/snippets/new/chord-glissando-in-tablature.ly?
I've changed my mind and I think that I should
On 4/25/11 11:26 AM, "Federico Bruni" wrote:
> Il giorno lun, 25/04/2011 alle 00.09 +0200, Federico Bruni ha scritto:
>> Or should I rather edit
>> Documentation/snippets/new/chord-glissando-in-tablature.ly?
>
> I've changed my mind and I think that I should edit this file instead of
> frette
Il giorno lun, 25/04/2011 alle 00.09 +0200, Federico Bruni ha scritto:
> Or should I rather edit
> Documentation/snippets/new/chord-glissando-in-tablature.ly?
I've changed my mind and I think that I should edit this file instead of
fretted-strings.itely.
In the meanwhile I've realized that relat
(This is MacOS X 10.5.8 on Intel.)
If I try to run midi2ly, I get a "version mismatch" for the midi library
imported by python.
I made sure to run python from the app bundle:
/Applications/LilyPond.app/Contents/MacOS/python
/Applications/LilyPond.app/Contents/Resources/bin/midi2ly
example.mid
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_0
Comment #3 on issue 1607 by percival.music.ca: patch for mandolin freboard
diagrams
http://code.google.com/p/lilypond/issues/detail?id=1607
pushed.
5becf12f5ada67346f70ad8cfe68589466619305
Status: Accepted
Owner:
CC: philehol...@googlemail.com, colinpkc...@gmail.com
Labels: Type-Build Priority-High Maintainability
New issue 1635 by percival.music.ca: clean up misleading warnings in
website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Start with "make webs
> I'm not top posting.
I have found an issue with the \partcombine tool, but I am not quite
sure whether it is a definite bug or one of the "various" limitations
it has. If one starts a tie, slur, crescendo hairpin or other such
while in one "mode" of \partcombine (\partcombineChords,
\partcombine
Comment #4 on issue 1633 by percival.music.ca: pdf utf-16be breaks doc
compile
http://code.google.com/p/lilypond/issues/detail?id=1633
Here's two bach schenkers. One is from a standalone compile with
out/bin/lilypond
and the other is from the docs. Both are from the same computer, same
Comment #3 on issue 1626 by percival.music.ca: Articulate produces faulty
barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
patch here:
http://codereview.appspot.com/4435069
___
bug-lilypond mailing list
bug-lilypond@gnu.or
Status: Fixed
Owner:
Labels: Type-Build Priority-Critical backport
New issue 1634 by percival.music.ca: make find(1) work on BSDs
http://code.google.com/p/lilypond/issues/detail?id=1634
8f4f11d08a43df534f9b720395f7e11a989e1664
should be backported.
Comment #5 on issue 1624 by percival.music.ca: Segfault with stabel and
development versions
http://code.google.com/p/lilypond/issues/detail?id=1624
2.15.0 is the lowest version of lilypond that we think it will work. Since
2.13.60 is lower than 2.15.0, you should not attempt to verify thi
On Apr 25, 2011, at 6:14 AM, David Kastrup wrote:
> "m...@apollinemike.com" writes:
>
>> From Damien Pallant:
>>
>> \new Staff {
>> \key ees \major
>> \clef treble
>> \override Staff.NoteCollision #'merge-differently-headed = ##t
>> \override Staff.NoteCollision #'merge-differently-dotted = ##t
"m...@apollinemike.com" writes:
> From Damien Pallant:
>
> \new Staff {
> \key ees \major
> \clef treble
> \override Staff.NoteCollision #'merge-differently-headed = ##t
> \override Staff.NoteCollision #'merge-differently-dotted = ##t
>
> \relative c' {
>
> << { r8 g ( bes d-3 ) f4-5 -- ees-4 --
Updates:
Status: Verified
Comment #2 on issue 1623 by brownian.box: Override Stem #'length-fraction
not applied to leger notes
http://code.google.com/p/lilypond/issues/detail?id=1623
(No comment was entered for this change.)
___
bug-lilypo
Comment #4 on issue 1624 by brownian.box: Segfault with stabel and
development versions
http://code.google.com/p/lilypond/issues/detail?id=1624
Sorry, what are "fixed_2_15_0" and "backport" ?
This code still segfaults with 2.13.60. Please, what's the version to
verify with?
>From Damien Pallant:
\new Staff {
\key ees \major
\clef treble
\override Staff.NoteCollision #'merge-differently-headed = ##t
\override Staff.NoteCollision #'merge-differently-dotted = ##t
\relative c' {
<< { r8 g ( bes d-3 ) f4-5 -- ees-4 -- } \\ { s8 g,~ 2. } >>
<< { r8 aes ( bes ees-4 ) f4-5
Il giorno dom, 24/04/2011 alle 19.43 -0600, Carl Sorensen ha scritto:
> I find it simpler to just do
> \new TabStaff \relative c' {
> \chordGlissando
> 8
> \chordGlissando
> 8
> }
>
> It still gets the warning, but I think it's easier than the
> \octaveCheck
> form.
>
I agree,
26 matches
Mail list logo
