/lilypond.git/'
What the heck?
Try logging in manually first. You may need to approve the host SHA1
once.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug
Valentin Villenave [EMAIL PROTECTED] writes:
2008/1/7, David Kastrup [EMAIL PROTECTED]:
Try logging in manually first. You may need to approve the host SHA1
once.
Thank you David. I have no idea how to manually log in, and neither
do I know how to approve the SHA1 sum (where do I find
used favorably? I would be willing considering to sponsor some
development here but one should flesh out what is sensible here in
advance, and how much work would need to get put in what area.
Thanks,
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Ping? Anybody out here?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
|
would be wrong, for example.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
|
:|:
4 |
would be wrong, for example.
Here an example from Brahms Gesamtausgabe, Haydn Variations, which
demonstrates what I mean.
Hm, at the ultimate beginning. Isn't it customary not to set a repeat
sign at all in that case?
--
David Kastrup
with a picture)?
Meter changes should occur before an opening repeat sign. If there is a
closing one immediately adjacently, opening and closing one are placed
apart, and the meter change in between.
--
David Kastrup
___
bug-lilypond mailing list
bug
. Short of that, Lilypond should pick the
way that best reflects the art of typesetting, as recognized by the
developers. It is ok if there are manual overrides (and style overrides
for a whole document), but the defaults should not require music
typesetting taste and choices.
--
David Kastrup
?
For the purposes of typesetting, I think they are. Except that in the
order of accents, they are usually placed outermost IIRC.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
of that (which caused me to look for the wrong bug in an input
file of mine).
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi,
neither on gmane nor on mail-archive.org can I find a copy of my report
URL:http://lists.gnu.org/archive/html/bug-lilypond/2009-10/msg00049.html.
So what happened? Did the recent gmail outage lose reports for good on
most channels that people actually use?
--
David Kastrup
: bug.png
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
, the error column is being tracked by counting characters,
but is displayed by counting bytes. The indicator appears too early
because of that (which caused me to look for the wrong bug in an input
file of mine).
--
David Kastrup
___
bug-lilypond mailing
-Eluze elu...@gmail.com writes:
David Kastrup wrote:
The following input file:
… which is a .bin file and should be a .ly file - but downloaded its content
looks like
\markup{
Määä A♯ B♭ \break
}
now, if i comment the \break (or omit it), the file compiles quite well -
did i
-Eluze elu...@gmail.com writes:
David Kastrup wrote:
-Eluze elu...@gmail.com writes:
now, if i comment the \break (or omit it), the file compiles quite well -
did i miss something?
The subject line and the problem description?
ahhh! i see now - i thought you were looking
Patrick McCarty pnor...@gmail.com writes:
On 2009-10-18, David Kastrup wrote:
GNU LilyPond 2.13.4
Processing `bad.ly'
Parsing...
bad.ly:4:16: error: syntax error, unexpected MUSIC_IDENTIFIER
MÃÃÃ A\342\231
\257 Bâ \break
error: failed files: bad.ly
Apparently
Patrick McCarty pnor...@gmail.com writes:
On 2009-10-18, David Kastrup wrote:
GNU LilyPond 2.13.4
Processing `bad.ly'
Parsing...
bad.ly:4:16: error: syntax error, unexpected MUSIC_IDENTIFIER
MÃÃÃ A\342\231
\257 Bâ \break
error: failed files: bad.ly
Apparently
Graham Percival gra...@percival-music.ca writes:
On Sun, Oct 25, 2009 at 02:16:27PM +0100, David Kastrup wrote:
Valentin Villenave v.villen...@gmail.com writes:
2009/10/24 Frédéric Bron frederic.b...@m4x.org:
1. can somebody feed the bug tracker with this bug?
Sorry, I got lost
Graham Percival gra...@percival-music.ca writes:
On Mon, Oct 26, 2009 at 01:43:59PM +0100, David Kastrup wrote:
A response time of a week is a sign that the mechanism is not working
out.
We *don't* have a response time of a week. Currently the only
person who has shown the slightest bit
: if there are different accidentals in xxx and
yyy for a note, a recurrence of the note after the split needs a
cautionary accidental.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Valentin Villenave v.villen...@gmail.com writes:
On Sun, Oct 18, 2009 at 2:34 PM, David Kastrup d...@gnu.org wrote:
% \bracket appears to correctly bracket an entire construct, but
% calculate its overall dimension just from its last part
Thanks, but the actual bug doesn't even need
their sample code.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Graham Percival gra...@percival-music.ca writes:
On Fri, Oct 30, 2009 at 11:15:45AM +0100, David Kastrup wrote:
Valentin Villenave v.villen...@gmail.com writes:
On Thu, Oct 29, 2009 at 11:08 PM, Neil Puttock n.putt...@gmail.com wrote:
This bug looks like #807, which has a patch pending
be nice. But one can probably guess somewhat reliably by checking
the width of the result.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
of the
contributor's guide would appear to be a task at frog level once a
decision about the scope of code changes has been made.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Valentin Villenave v.villen...@gmail.com writes:
On Sun, Dec 20, 2009 at 11:01 AM, David Kastrup d...@gnu.org wrote:
The current state of make-markup-command is less than satisfactory since
make-markup-command and make-builtin-markup-command have different
syntaxes and semantics, making
David Kastrup d...@gnu.org writes:
lilyp...@googlecode.com writes:
Comment #4 on issue 898 by v.villenave: Enhancement: rests should be
taken into account when determining beaming intervals
http://code.google.com/p/lilypond/issues/detail?id=898
David, could you elaborate on that (and send
with is the generic Bug
Team. Suggestions appreciated.
Bug squad.
URL:http://www.girlgeniusonline.com/comic.php?date=20060315 shows one
of them in action.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman
Francisco Vila paconet@gmail.com writes:
2010/2/1 Graham Percival gra...@percival-music.ca:
At the moment, the best I can come up with is the generic Bug
Team. Suggestions appreciated.
Flysprayers :-)
You would not want to poison the frogs.
--
David Kastrup
would
be _debuggers_. However, that name happens to be already a _proper_
computing related name for the task within Lilypond, and thus is no
longer suitable as an informal one.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
, having proposed it, and I have been appalled
by buggers. However, I have not seen that I could have added anything
to the discussion that had not already been said and considered.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
this
snippet will avert the abort.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
think otherwise)
Whole-measure rests are centered in the _bar_, not with other noteheads.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
' (perhaps incorrect
sectioning?).
[...]
And so forth and so on.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Neil Puttock n.putt...@gmail.com writes:
On 8 April 2010 19:24, David Kastrup d...@gnu.org wrote:
And so forth and so on.
I've pushed a compile fix which should sort this out for you.
Thanks. Appears to work here.
--
David Kastrup
___
bug
Phil Holmes m...@philholmes.net writes:
At the end of a piece of music, a text Pedal down marking (from
\sustainOn) should automatically be marked with a Pedal up marking,
Why?
but isn't.
--
David Kastrup
___
bug-lilypond mailing list
bug
not require
the full focus of the musicians.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
into play only once line breaking is already completed. With a
rigid layout, there is nothing you can do to fix the previous bad
decision. You can only call it foul and have TeX emit a warning.
I think we need to be better than that.
--
David Kastrup
it into a shape acceptable for committing,
and the original contributor has lost interest.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
} }
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
chord names for the chord buttons in the
lower staff.
It would not do to just use textual markup here since textual markup is
not transposable.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug
.
Anyway, I should think that this bug description including a list of
relevant examples should warrant being recorded by the bug squad.
All the best.
David Kastrup d...@gnu.org writes:
David Kastrup d...@gnu.org writes:
I get the following two programming errors. What's up?
A simpler test case
Dmytro O. Redchuk brownian@gmail.com writes:
On Wed 09 Jun 2010, 16:52 David Kastrup wrote:
Anyway, I should think that this bug description including a list of
relevant examples should warrant being recorded by the bug squad.
i simply can not understand (tm) what's the problem (tm
phrase Small example, and error symptom still missing might
well be a safe choice in any case.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
the voice explicitly, as implicit voice generation
does not work with things like quotes (or tempo marks inside
triplets):
\new Voice {
\relative c'' {
\quoteDuring #part { s4 }
}
}
Is there a good reason to have implicit voice generation not work in
such circumstances?
--
David
Reinhold Kainhofer reinh...@kainhofer.com writes:
Am Montag, 14. Juni 2010, um 12:28:48 schrieb David Kastrup:
Reinhold Kainhofer reinh...@kainhofer.com writes:
You need to create the voice explicitly, as implicit voice generation
does not work with things like quotes (or tempo marks inside
it is implemented
inside of Lilypond.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
-crescendo-hairpin
inline: lily-74fc53ae.png
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
text can be amended so that the intent becomes clearer?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
of why I need (begin ) blocks and what they do..
They execute all inner forms in sequence, and are just a single form on
the outside. The Lisp equivalent would be (progn ...).
4. A REPL for testing out scheme stuff
lilypond -e '(top-repl)'
--
David Kastrup
there because of being in the inside
of \repeat unfold?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
cleverness than a straight approach to the problem, I
don't see how it could not be an issue. Lilypond is supposed to be a
tool for typesetting music, not some contraption which we can cleverly
trick into typesetting music.
If we wanted that, we would still be using TeX.
--
David Kastrup
documentation that need to get
installed separately as lilypond-doc and will likely unpack into
/usr/share/doc/lilypond-doc where you can browse through them with your
browser.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
to voices rather than merely to current
time.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
(and the Midi) by default.
If all other dynamic specifitions end up below the staff, you'll be
surprised at this one.
I consider it bad style to write like this, but there have not been
convincing alternatives yet, have they?
--
David Kastrup
___
bug
) An automatic beam ending just before a staff change fails to expand
skylines, resulting in similar collisions. Explicit [ ] beams are a
workaround. First described in this issue, comments 2 and following.
That sounds like something that could be addressed without something
else caving in.
--
David
of doing C-c C-t after F . The followup will
then be both sent to the nntp server as well as to the poster, marked as
a courtesy copy.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
}
} }
Hm. Initial skyline estimate does not take into account the systems
themselves and/or the clef?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
of too tight or too loose. It
is a matter of too unpredictable.
And if you really want to see some hot action, just write
\score { c }
as often as you want. Regardless of how much of those you put into the
file, the outcome will be just a single page.
All this is rather erratic.
--
David
Phil Holmes m...@philholmes.net writes:
David Kastrup d...@gnu.org wrote in message
news:87vd5nny58@lola.goethe.zz...
Phil Holmes m...@philholmes.net writes:
[Please don't write anything important below your signature, as mail
clients will cut this away on reply].
Apologies. I have
David Kastrup d...@gnu.org writes:
David Kastrup d...@gnu.org writes:
I have to disagree with your assessment: the behavior of 12.3 made sense
under the constraints the code worked with. It was a result of its
design decisions. The result of 13.35 does not make sense. As you can
easily
David Kastrup d...@gnu.org writes:
I have to disagree with your assessment: the behavior of 12.3 made sense
under the constraints the code worked with. It was a result of its
design decisions. The result of 13.35 does not make sense. As you can
easily see by removing the markup
then it
breaks just fine).
Oh. Wow.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Check the first two systems on the second page of the following score:
\repeat unfold 80 { c'''-1 e'''-3 g'''-5 c' c,-1 e,-3 g,-5 c' }
Perhaps skylines should not be taken as literally as that, but padded
out somewhat.
--
David Kastrup
___
bug
{ R2 }
results in a (correct) barcheck failed warning, but also in an I am not
spanned! error:
R2 does not fill the measure that's why the MultiMeasureRest complains.
No LilyPond bugs as far as I can tell.
Incomprehensible error messages count as bugs.
--
David Kastrup
consistent with the layout of
the previous pages.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Phil Holmes m...@philholmes.net writes:
David Kastrup d...@gnu.org wrote in message
news:87mxqvcsvr@lola.goethe.zz...
Check the output of the following:
test = { c-1-^ r f-2-^ r c-3-^ r f-4-^ r c-1-^ r f-2-^ r c-3-^ r }
\score {
\repeat unfold 8 { \test \test r
\transpose c c
Phil Holmes m...@philholmes.net writes:
David Kastrup d...@gnu.org wrote in message
news:8762xjcltg@lola.goethe.zz...
What is wrong with the above?
Nothing. It's just that it's one of many you've posted, and I wanted
to know which you felt best illustrated the issue.
There is more
Dmytro O. Redchuk brownian@gmail.com writes:
On Sun 03 Oct 2010, 03:12 David Kastrup wrote:
Wilbert Berendsen lily...@xs4all.nl writes:
Op donderdag 30 september 2010 schreef Marnix:
L.S.,
For the following file
\version 2.12.4
{ R\breve\fermata }
use R\breve
threshold, completely unlock the teeth. A smoother transition from
locked to unlocked would appear to make sense, hence the suggestion to
pad diagonally, where the sum of adjacent horizontal and vertical
distances should not fall below a given limit.
Another option would be Euclidian.
--
David
that they will need to turn off
autobeaming manually after the cadenza, as does the notation reference.
I think this is the right thing to do.
I think a revert would be more appropriate.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
Dmytro O. Redchuk brownian@gmail.com writes:
On Wed 06 Oct 2010, 07:44 David Kastrup wrote:
Carl Sorensen c_soren...@byu.edu writes:
On 10/5/10 5:50 PM, Keith E OHara k-ohara5...@oco.net wrote:
If \cadenzaOff turns autobeaming on, then what about scores that turn off
autobeaming
on two different runs even.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
expression returning parallel music.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
/Item?id=720
I have some problems reconciling Fixed with workaround.
workaround corresponds to categories Wontfix or Postponed or a
priority Low. But Fixed and workaround seem like an odd match.
--
David Kastrup
___
bug-lilypond mailing list
bug
for anything.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
by tweaking
existing knobs. The existing knobs are no use for a reasonable
automatic resolution of the problem.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Valentin Villenave valen...@villenave.net writes:
On Fri, Oct 29, 2010 at 9:56 AM, David Kastrup d...@gnu.org wrote:
Greetings David,
Oh, by the way: it would be nice to have an option to let Lilypond use
the same space stretching on the last page (in case it fits) than on the
last non
output that is not in
any manner a sensible representation of the input.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
really help if
this could be solved.
The above would not solve it. Some things would work, some things would
not. Depending on the voice they happen in.
So don't get your expectations too high about what gains can be expected
from implementing that proposal.
--
David Kastrup
(namely sources
that don't fiddle with non-working properties in the wrong context).
And we _have_ snippets fiddling with typesetting stuff two times, using
transparent parts for each pass, that would work much more elegant with
the equivalent of subvoices.
--
David Kastrup
versions pasted over each other using transparency and disabling
collision detection. I mean, ugh.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
at the voice level, and
\\ introduces subvoices/threads/whatever (presumably one level above
chord level which would be responsible for the stemming), then we
would not be losing our voice when entering a { \\ } construct.
--
David Kastrup
___
bug
the feeling that they might. But
without any prospective code, I can't judge that aspect.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
death. With free
software, stagnation mostly means stagnation.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
behaviour.
I hope this would require a
\set slashedBeamedAcciaccatura = ##t % default is ##f
or something like that to be activated.
Why? There is no sense to use the same notation as an appoggiatura by
default since both duration and onset of the two are different.
--
David Kastrup
executable called gsnd or so (Ghostscript no
display), but you should not really need it if the devices are already
set on the command line. For Windows, something like gswin32c is needed
(the c is important).
--
David Kastrup
___
bug-lilypond mailing
Phil Holmes m...@philholmes.net writes:
David Kastrup d...@gnu.org wrote in message
news:87y68dmy2e@lola.goethe.zz...
Phil Holmes m...@philholmes.net writes:
The PC is unusable when it's running - all the Ghostscript command
line interfaces get in the way.
Huh? If you see Ghostscript
to the last stable version.
inline: junk.preview.png
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
David Kastrup d...@gnu.org writes:
Take a look at the following:
\markup { \concat { \center-column { Ooh ah }
\center-column { Ah oooh }
\center-column { Ooh ah }
} }
It would appear that the middle column has no horizontal size at all.
I think that's
Reinhold Kainhofer reinh...@kainhofer.com writes:
Am Mittwoch, 15. Dezember 2010, um 15:43:42 schrieb David Kastrup:
Take a look at the following:
\markup { \concat { \center-column { Ooh ah }
\center-column { Ah oooh }
\center-column { Ooh ah
.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
or logical reason to assume accidentals
are reset. If that was the underlying assumption for a clef change,
the key signature would be repeated.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug
Phil Holmes m...@philholmes.net writes:
David Kastrup d...@gnu.org wrote in message
news:87ei92oxo3@lola.goethe.zz...
Phil Holmes m...@philholmes.net writes:
\relative c' {
\clef bass cis2 c
\clef tenor cis2 \clef bass c % natural is not printed!!
\clef bass cis2 \clef tenor c
Reinhold Kainhofer reinh...@kainhofer.com writes:
Am Dienstag, 28. Dezember 2010, um 14:23:14 schrieb Phil Holmes:
David Kastrup d...@gnu.org wrote in message
I don't think it is correct. If you set the above with \key g\major,
you will notice that the key signature is _not_ repeated
Phil Holmes m...@philholmes.net writes:
David Kastrup d...@gnu.org wrote in message
news:87aajqowbn@lola.goethe.zz...
Phil Holmes m...@philholmes.net writes:
Apologies. As you're probably aware, I'm a Windows man, and some
postings don't quote properly using my mailreader.
I am sure
. And that even though I am testing Mike's patch right now.
vi = \relative c'' { cis16 e g4 b,8 a e'16 fis32 g ~ g16 fis8 e16 }
vii = \relative c'' { g8 b e4 ~ e16 d cis b a8 b }
{ \key d\major
\partcombine \vi \vii |
\vi \\ \vii }
inline: bug.preview.png
--
David Kastrup
Reinhold Kainhofer reinh...@kainhofer.com writes:
Am Samstag, 8. Januar 2011, um 22:25:51 schrieb David Kastrup:
So what do we get? The part combiner messes with the beaming in a
manner that does not look like an improvement (arguably by design),
The problem with beaming is that the chord
Reinhold Kainhofer reinh...@kainhofer.com writes:
Am Samstag, 8. Januar 2011, um 23:30:21 schrieb David Kastrup:
Reinhold Kainhofer reinh...@kainhofer.com writes:
Am Samstag, 8. Januar 2011, um 22:25:51 schrieb David Kastrup:
So what do we get? The part combiner messes with the beaming
Reinhold Kainhofer reinh...@kainhofer.com writes:
Because the part-combiner does not check how long notes are... It just
checks onsets of notes.
That can't be the whole story since the spurious solo does not occur
throughout when one voice is syncopated, just at its end.
--
David Kastrup
1 - 100 of 1473 matches
Mail list logo
