On Fri, 23 Sep 2011 00:07:39 -0700, m...@apollinemike.com
m...@apollinemike.com wrote:
On Sep 23, 2011, at 8:56 AM, Keith OHara wrote:
On Thu, 22 Sep 2011 23:11:08 -0700, m...@apollinemike.com
m...@apollinemike.com wrote:
On Sep 23, 2011, at 6:38 AM, Keith OHara wrote:
Phil Holmes email
Phil Holmes email at philholmes.net writes:
There are 2 significant problems I've found with 2.15.12. The first is
shown in the Les Nereides regtest - a fingering indication goes missing.
Confirming. The missing fingering indication is hidden under a note head
in the other voice. The
Phil Holmes email at philholmes.net writes:
I've not been able to check much more, because of subtle differences between
the treble clef in 15.12 and 15.10, but that's a starter.
But the G clef changed between .8 and .9
___
lilypond-devel mailing
David Kastrup dak at gnu.org writes:
The reason is that Rietveld just supports discussing and
improving a single patch/commit.
A counterexample http://codereview.appspot.com/4830064/
More complicated sets can benefit from Reitveld's ability
to load patch sets relative to different
Graham Percival graham at percival-music.ca writes:
If that makes you pause and wonder if
you should really push a particular patch (because it would leave
something hanging or unfinished), then put that on a separate
branch and/or upload to rietveld instead of pushing to master.
I like the
Phil Holmes email at philholmes.net writes:
Same problem as 2.15.9 - I think the change of spacing from the clef to the
first note means that almost every regtest is different.
I looked through the 2.15.10 vs .9 comparison and recognized the cause of most
changes Those I didn't
On Sat, 03 Sep 2011 00:13:56 -0700, Trevor Daniels t.dani...@treda.co.uk
wrote:
although the grace
note in lyric-hyphen-grace.ly seems closer to the
time signature than normal notes. Any idea why this
is, Keith?
That is how grace notes were spaced in the last two stable versions.
Grace
Graham Percival graham at percival-music.ca writes:
please add a new Critical issue for [profiles]. We can always mark it
invalid later.
now issue 1858
song-melisma.ly
The former extra space was issue 1779
beam-feather-breaking.ly : lots of changes system spacing. Mike,
IIRC feathered
Keith OHara k-ohara5a5a at oco.net writes:
beam-feather-breaking.ly : lots of changes system spacing.
Oops. Instead of the above, I meant to reference
dynamics-alignment-breaker-linebreak.ly : lots of extra space at
the beginning of the first bar.
when I said
My fix to issue 1785
On Wed, 31 Aug 2011 00:56:53 -0700, Trevor Daniels t.dani...@treda.co.uk
wrote:
The horizontal spacing of fret diagrams is much tighter in 2.15.9;
too tight I would say. Is this an expected change?
From the patch for issue 1779.
Fret boards were, sometimes, getting the spacing intended
Phil Holmes email at philholmes.net writes:
the other
is a slight spacing change - it looks like, as a general rule, 2.15.9 is
slightly more compact on ragged-right versus 2.15.7 (which is my local
baseline).
Due to the fix for issue 1779.
I'll attach one difference file which I don't
Mike Solomon mikesol at ufl.edu writes:
As I stated in a previous mail, it is easy to re-instate
a length property in the stem-interface and then
build it into either Stem::internal_height or Stem::print.
I have no problem with this.
The KEEP LENGTH option is the best,
because 'length
Phil Holmes email at philholmes.net writes:
Or we could take shifts in checking images.
I've looked closely at the changes with distance 5.0 or above, and
looked quickly at the others. If one more person takes a shift
starting at the small 'distances' that would be great.
One concern: Cell
Keith OHara k-ohara5a5a at oco.net writes:
Two unexpected spacing changes that I will investigate:
beam-extreme.ly spacing-correction-accidentals.ly
The /new/ behavior is correct in these two tests.
(That is, the output matches the intent of the code)
I forgot to mention, tuplet brackets
On Thu, 18 Aug 2011 23:25:40 -0700, Mike Solomon mike...@ufl.edu wrote:
On Aug 19, 2011, at 5:01 AM, k-ohara5...@oco.net wrote:
A swing and a miss, I'm afraid.
See input/regression/pedal-bracket for what the original alignment goals
were. (You could expand that reg-test to cover issue 723)
Mike Solomon mikesol at ufl.edu writes:
I maintain that the best solution is:
\override Staff.Accidental #'layer = #-100
\override Staff.LedgerLineSpanner #'layer = #-101
\override Staff.Accidental #'whiteout = ##t
Which is a trivial change to engravers-init.ly. I'll post a patch later
Janek Warchoł janek.lilypond at gmail.com writes:
As a nice inauguration of me having git push ability, i broke my
repository :) git pull seems not to work properly.
Your commit looks fine on the repository, so nothing to worry about there.
I would expect another line in your
I pushed the patches for issues 1779 and 1785, the ones that made small changes
to *lots* of regression tests.
Probably you want to absorb these changes in new `make test-baseline`
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Janek Warchoł janek.lilypond at gmail.com writes:
I would expect another line in your configuration, added below:
[remote origin]
url = ssh://janekw at git.sv.gnu.org/srv/git/lilypond.git
fetch = +refs/heads/master:refs/remotes/origin/master
Probably you want to go
Graham Percival graham at percival-music.ca writes:
I know there's a lot of big things in here to review,
I should make it two issues fewer.
These two were on the list finished Friday, I've just not been on linux to push.
% (single patch does both issues)
accidentaled notes too far from
On Thu, 18 Aug 2011 23:25:40 -0700, Mike Solomon mike...@ufl.edu wrote:
On Aug 19, 2011, at 5:01 AM, k-ohara5...@oco.net wrote:
I think the correct fix is merely to ignore suspended heads, which could
be implemented as aligning to the stem for down-stems. I find good
evidence to back that up
On Fri, 19 Aug 2011 01:33:56 -0700, Phil Holmes m...@philholmes.net wrote:
- Original Message -
From: Keith OHara
I don't know until next time I look at Ted Ross' book in the library.
Mostly I was being rhetorical, calling to attention the vastly different
time-scales that Mike
Graham Percival graham at percival-music.ca writes:
We will make a “Type-Critical”; a new stable release will only
occur if there are 0 type-Critical issues.
[...]
it also attracts the attention of potential
contributors, so we should avoid having any glaring problems which
would stop
On Wed, 10 Aug 2011 22:06:16 -0700, Graham Percival gra...@percival-music.ca
wrote:
On Thu, Aug 11, 2011 at 04:59:02AM +, Keith OHara wrote:
Graham Percival graham at percival-music.ca writes:
Type-critical:
You might want to split this into two:
regressions to the output of Lilypond
Graham Percival graham at percival-music.ca writes:
Type-critical:
You might want to split this into two:
regressions to the output of Lilypond, and
critical impediments to development
* Type-ignorance: (fixme name?) it is not clear what the
correct output should look like.
In
Graham Percival graham at percival-music.ca writes:
That proposal failed to achieve clarity and consensus
within a month, mostly due to the proposal being too broad.
By to broad I guess you mean that the old proposal affected `make bin`,
which doesn't suffer the sea-of-output problem.
The
On Sat, 06 Aug 2011 03:13:33 -0700, Phil Holmes m...@philholmes.net wrote:
From: Keith OHara k-ohara5...@oco.net
I agree, and want `make bin` to show me warnings. I might have been
taking the proposal too literally.
I know no reason why it shouldn't. Have you tried putting code
On Sat, 06 Aug 2011 00:13:49 -0700, Jan Warchoł
lemniskata.bernoulli...@gmail.com wrote:
2011/8/6 Keith OHara k-ohara5...@oco.net:
order in which the project encourages
contributors to attack issues.
Sounds good to me. Still, decision depends on our views about
relative importance of user
On Sat, 06 Aug 2011 01:52:27 -0700, m...@apollinemike.com
m...@apollinemike.com wrote:
Do you know where these reference points are specified?
No, but the extents of each glyph are calculated relative to the reference
points,
so from the extents we can figure how long to make the rods to
Phil Holmes mail at philholmes.net writes:
Phil Holmes mail at philholmes.net writes:
One major change from 2.15.7 - in nested-property-revert.ly. I'm
assuming this is down to David's reversion of an earlier commit.
I think this needs to be added to the tracker, and would normally
David Kastrup dak at gnu.org writes:
Keith OHara k-ohara5a5a at oco.net writes:
Unless somebody objects, I will remove 'nested-property-revert.ly' from
the test suite; The test code still exists in the open issue 1063.
I'd like to keep this test as I am working on the full
mike at apollinemike.com mike at apollinemike.com writes:
I'm getting a lot of circular dependencies for
input/regression/beam-skip.ly from the current master.
I don't have time to do a full git bisect, but is this
standard behavior?
You should have a word with the gentleman who pushed
David Kastrup dak at gnu.org writes:
Looks like we associate differing meanings with one or several of the
words unless, somebody or objects.
Oops. I'm delaying pushing.
The troublesome word was the verb keep, from I'd like to keep.
Of course you can keep it, on your branch.
If the test
Graham Percival graham at percival-music.ca writes:
** Proposal details
When you run make or make doc,
* All output will be saved to various log files, with the
exception of output directly from make(1).
* By default, no other output will be displayed on the
Janek Warchoł lemniskata.bernoullego at gmail.com writes:
Good example! It reminded me that usually there are less suspended
notes in a chord than normal ones (i.e. in your example the third pair
consists of chords with two normal notes and one suspended). Because
of that it is indeed
mtsolo at gmail.com writes:
I was assuming that a rod
attaches to the right of the left `between-columns' and the left of the
right one? Is this not the case?
I haven't tried the patch yet, but the rods of rods-and-springs measure from
the
reference points of the objects.
The left-
Reinhold Kainhofer reinhold at kainhofer.com writes:
We shouldn't need to type anything to see the warnings/errors of a compile
run.
I agree, and want `make bin` to show me warnings. I might have been taking
the proposal too literally.
* There will be no additional “progress messages”
On Wed, 03 Aug 2011 15:42:55 -0700, Graham Percival gra...@percival-music.ca
wrote:
On Tue, Aug 02, 2011 at 07:48:12AM +, Keith OHara wrote:
I'm curious first what we want the priority field to mean.
[...]
The more that I think about it, the more I like this
interpretation
Graham Percival graham at percival-music.ca writes:
** Rationale
Bug squad members are confused, users are confused, and (to a
certain extent) Graham just makes up the rules for “Critical” as
he goes along. Let’s get some clarity here.
Giving priority to issues which hinder development
Graham Percival graham at percival-music.ca writes:
I will be running fixcc.py on the git repo
Tabs-to-spaces and trailing-spaces-strip are now done by the Python script, so
you don't need to do these steps by hand.
Apologies for the inconvenience; this should be a one-time painful
Carl Sorensen c_sorensen at byu.edu writes:
error: failed files: 6e/lily-5d49e0f2.ly 85/lily-8f5bb797.ly
73/lily-b2bdecac.ly 1f/lily-78f1d22c.ly cf/lily-a34c4419.ly
c0/lily-66f81f54.ly f5/lily-67985894.ly 5d/lily-a5120b71.ly
32/lily-8af6d1a5.ly 88/lily-a8992af6.ly cb/lily-55c6c8df.ly
Colin Campbell cpkc at shaw.ca writes:
New today, for Friday:
Issue 621:
Dynamics should avoid cross-staff BarLines (e.g.
GrandStaff, PianoStaff etc) - Rietveld
I should advertise that the patch on this issue includes a Docs change.
After the patch we no longer need to
On Fri, 29 Jul 2011 14:51:35 -0700, Neil Puttock n.putt...@gmail.com wrote:
The automatic behaviour is undesirable, since it introduces extra
space before the dynamic to prevent the collision.
Let's put that concept on the tracker for item 621.
You're unlikely to see this in engraved music.
On Thu, 28 Jul 2011 05:46:29 -0700, reinhold.kainho...@gmail.com wrote:
Message:
On 2011/07/26 02:17:28, Keith wrote:
I like it, although I can still get the error if I put a new voice in
the quoted
expression like this:
quoteMe = \relative c' \new Voice {
Yeah, but then we have a
midi-volume-equaliser.log (and other midi regtests): warnings removed (I've
lost track of whether these are supposed to be there)
-warning: MIDI channel wrapped around
They are not, and their appearances in regression test comparisons will
disappear soon, as the patch spreads through
mike at apollinemike.com writes:
On Jul 24, 2011, at 11:29 PM, Neil Puttock wrote:
On 23 July 2011 15:48, mtsolo at gmail.com wrote:
In the
example given in Issue 36, I would personally rotate the stencil
downwards, and this patch would give me all the data necessary
to
mike at apollinemike.com writes:
I get the following error during make check:
[...]
Failed files: (1c/lily-e69a97ad.ly
[...]
Child returned 1
make[2]: *** [out-test/collated-files.texi] Error 1
rm out-test/rest-dynamic.midi out-test/quantize-duration-2.midi [...]
make[1]: ***
mtsolo at gmail.com writes:
This fixes issue 163. The only downside is that it adds another entry
to an already-crowded details list.
Mike, it seems that the existing properties 'height-limit and 'ratio *should*
control the situations in issue 163.
In fact, making 'height-limit larger
On Sat, 16 Jul 2011 08:11:02 -0700, pkx1...@gmail.com wrote:
Passes Make tests - I still get:
--snip--
Interpreting music...
-warning: MIDI channel wrapped around
-warning: remapping modulo 16
MIDI output to
The test output shows the change from the old behavior. Lines with '-' in
Graham Percival graham at percival-music.ca writes:
NB: if anybody wants to start looking at various command-line
scheme indenters (whether that's extracting the elisp
scheme-indent and making it work with guile,
Ooh, that would be very nice if it is possible !
Standalone programs that did
On Thu, 14 Jul 2011 00:47:58 -0700, Trevor Daniels t.dani...@treda.co.uk
wrote:
I was hoping to recommend going with this, so we could
wrap up this issue, but then I found
- new_context-event_source ()-
- add_listener (GET_LISTENER
(new_context-create_context_from_event),
+
Karl Hammar karl at aspodata.se writes:
Graham:
...
I'm going to make the bold step of assuming that we will eliminate
tabs in all C++ files.
That implies that tabs in strings should be replaced with \t, is that
what you want?
I think we want this very much, because a literal tab in
On Tue, 05 Jul 2011 00:18:21 -0700, Trevor Daniels t.dani...@treda.co.uk
wrote:
Carl Sorensen wrote Tuesday, July 05, 2011 7:12 AM
long_variable_name = (first_term
+ second_term);
I prefer this indentation too. If Emacs users forget
the brackets Astyle will indent
On Wed, 06 Jul 2011 12:55:31 -0700, Graham Percival gra...@percival-music.ca
wrote:
On Wed, Jul 06, 2011 at 07:04:11PM +, jan.nieuwenhui...@gmail.com wrote:
I do think that it's important that the suggestion that
Emacs would not indent GNU code correctly has been withdrawn.
I agree; I'm
Original Message
From: Graham Percival gra...@percival-music.ca
Sent: Wednesday, July 06, 2011 1:03 PM
To: k-ohara5...@oco.net, carl.d.soren...@gmail.com,
percival.music...@gmail.com, t.dani...@treda.co.uk, jann...@gnu.org,
c_soren...@byu.edu, jan.nieuwenhui...@gmail.com,
On Mon, 04 Jul 2011 09:32:21 -0700, Trevor Daniels t.dani...@treda.co.uk
wrote:
Jan Nieuwenhuizen wrote Monday, July 04, 2011 10:28 AM
It seems
to me that someone is spending a lot of effort `just' to
accommodate
people who haven't found how awesome Emacs is to edit code and
thus introduce
On Sun, 03 Jul 2011 01:15:04 -0700, k-ohara5...@oco.net wrote:
On 2011/07/03 07:22:07, Graham Percival wrote:
2. some multi-line comments are still modified:
Astyle preserved the alignment, relative to the /*, in the original.
That is to say, I think you were comparing against the output
On Sun, 03 Jul 2011 05:18:32 -0700, Carl Sorensen c_soren...@byu.edu wrote:
if (Score *newscore = unsmob_score (entry))
-*t = scm_cons (newscore-clone ()-unprotect (), SCM_EOL);
+* t = scm_cons (newscore-clone ()-unprotect (), SCM_EOL);
else if (Page_marker *marker
On Sat, 02 Jul 2011 13:19:23 -0700, Graham Percival gra...@percival-music.ca
wrote:
On Thu, Jun 30, 2011 at 12:04:11AM -0700, Keith OHara wrote:
We could use a regexp pre-filter to add space where gnu-style wants it, and use
that as a model to support the request for a new option in astyle
On Sat, 02 Jul 2011 15:57:38 -0700, Graham Percival gra...@percival-music.ca
wrote:
On Sat, Jul 02, 2011 at 03:13:05PM -0700, Keith OHara wrote:
Why run an indenter over the entire repository?
1. newbies tend to trust that the existing material shows how they
should do things. 2. if we
On Wed, 29 Jun 2011 21:05:51 -0700, Carl Sorensen c_soren...@byu.edu wrote:
Do you have the ability to easily test a change that doesn't pad a
parenthesis if it's following the same character, ie. (( won't get an extra
space?
It turns out to be very easy to modify astyle so as to skip the
Graham Percival graham at percival-music.ca writes:
At the moment I'm leaning towards using astyle+postprocessing.
The script in question is here:
Don't post-process, or you mis-align the indentation that astyle did.
Pre-filtering works well, assuming we drop the corresponding astyle
On Wed, 29 Jun 2011 21:05:51 -0700, Carl Sorensen c_soren...@byu.edu wrote:
On 6/29/11 6:01 PM, Keith OHara k-ohara5...@oco.net wrote:
Graham Percival graham at percival-music.ca writes:
At the moment I'm leaning towards using astyle+postprocessing.
padding that can be helpful
On Mon, 27 Jun 2011 05:45:54 -0700, Graham Percival gra...@percival-music.ca
wrote:
On Sun, Jun 26, 2011 at 06:12:07PM -0700, Keith OHara wrote:
On Sun, 26 Jun 2011 10:48:36 -0700, Graham Percival gra...@percival-music.ca
wrote:
A few specific problems with astyle:
* it doesn’t indent
On Mon, 27 Jun 2011 10:37:10 -0700, Graham Percival gra...@percival-music.ca
wrote:
When I look at
git diff origin/dev/gperciva-fixcc origin/dev/gperciva-astyle
I'm still leery about some changes.
Some indentation is off because fix-astyle-fiddle removes spaces after
indentation.
Graham Percival graham at percival-music.ca writes:
No. fixcc.py will [need] emacs 23.1.1 to be installed.
If the version of emacs matters, then
1) we might have more work when people move to 24
2) it hints that emacs formatting is not stable enough for our purpose
astyle 2.02 is the
On Sun, 26 Jun 2011 10:48:36 -0700, Graham Percival gra...@percival-music.ca
wrote:
indent(1) can't handle C++ code.
That's surprising. Bummer.
From earlier,
A few specific problems with astyle:
* it doesn’t indent enum in gnu style
I can't find gnu instructions for indenting enums,
Graham Percival graham at percival-music.ca writes:
Stdout is used for valuable program output, stderr for any kind of
message, including progress. The name stdERR is possibly somewhat
unfortunate and comes from the days that unix commands would only
print something (to stdERR) if
On Sat, 25 Jun 2011 03:53:40 -0700, mts...@gmail.com wrote:
Keith: are you still interested in tackling this problem? I know there
have been some changes in note-collision.cc, so I'll likely scrap this
patch and start from scratch,
I purposely put it off until 2.14 was out.
Looking at it
On Sat, 25 Jun 2011 13:24:28 -0700, Jan Warchoł
lemniskata.bernoulli...@gmail.com wrote:
have you considered fixing issue 39 by shortening the flag (as we're
going to have plenty of shortened flags available)? Or maybe
shortening a flag a bit and lenghtening the stem a bit would be the
best
James Lowe James.Lowe at datacore.com writes:
I made the patch and then aborted my changes.
I noticed however that the mod dates were still the same as the time
I made the patch, even though the files themselves are the original files
That is normal.
The file system reports the last time
Graham Percival graham at percival-music.ca writes:
This one will be contentious.
Maybe the various opinions will share a small overlapping area of consensus;
applying even a small improvement might be enough to make life easier.
** Eliminate tabs
That helps (even though editors should
James Lowe James.Lowe at datacore.com writes:
I think we have some duplication in this section but would like a second
opinion
I agree. The two snippets do not need to be quoted in the documentation
because
you cover all the concepts earlier.
Janek Warchoł lemniskata.bernoullego at gmail.com writes:
The change is almost certainly due to new beam collision algorithm.
I'm forwarding this message to the development team so that they will
know about this issue.
I'm not sure if it's a bug, though
I think it is a documentation issue.
Keith OHara k-ohara5a5a at oco.net writes:
On Fri, May 27, 2011 at 10:44 PM, Keith OHara k-ohara5a5a at oco.net
wrote:
If the flexible-vertical-spacing variable 'stretchability is defined, but
has value 0.0, then
a) the staves will not stretch to fill extra space
b) the staves
On Tue, 31 May 2011 01:14:45 -0700, Joe Neeman joenee...@gmail.com wrote:
On Fri, May 27, 2011 at 10:44 PM, Keith OHara k-ohara5...@oco.net wrote:
If the flexible-vertical-spacing variable 'stretchability is defined, but
has value 0.0, then
a) the staves will not stretch to fill extra space
b
Phil Holmes mail at philholmes.net writes:
Phil Holmes mail at philholmes.net wrote in message
news:is2ucp$h53$1 at dough.gmane.org...
Official site looks good - some slight changes in where lyrics are placed,
Formerly, the padding=0.2 and minimum-distance=2.8 were erroneously added
percival.music.ca at gmail.com writes:
The regtest comparison shows some warnings in rest-polyphonic2.ly in a
different place. I don't know if that's significant.
It is not.
This is the regtest that proves too-many colliding rests will be placed
consistently, even though the array holding
One of the special-cases in the LilyPond code is confusing me.
( This special-case code is in Page_layout_Problem::get_fixed_spacing(). )
If the flexible-vertical-spacing variable 'stretchability is defined, but has
value 0.0, such as:
*-*-spacing = #'((basic-distance . 16)
Carl Sorensen c_sorensen at byu.edu writes:
Pushed, along with some other patches I wanted to cherry-pick.
Should be ready for a release now, I think.
Not quite.
The commit Fix determine-frets so that it preserves note order
causes regression test tablature-negative-fret.ly
to fails with
mike at apollinemike.com mike at apollinemike.com writes:
Just a question - are we comfortable making a release even though issue 1648
isn't resolved?
I think it would be fine to leave issue 1648 open for version 2.13.62. I am
rather expecting someone to argue that issue 1648 is not
James Lowe James.Lowe at datacore.com writes:
I have just pushed a change to the CG but forgot to commit some additional
changes so they didn't get pushed.
So the CG won't compile now.
My guess is that you collected the changes into an 'amended' commit,
which would replace the first
Graham Percival graham at percival-music.ca writes:
On Thu, Apr 28, 2011 at 02:45:07PM +0100, Graham Percival wrote:
We can't just change VERSION in git master, because that's used to
generate the website,
oh wait, I just remembered that we have a separate MINOR_VERSION
from
Phil Holmes mail at philholmes.net writes:
Les Nereides has lost a
hairpin in the 4th bar. I don't believe the regtest has been changed, so
this seems critical.
I'll try to make a tiny bug report today; it looks like dynamic spanners
with grace note timing get lost. (Phil if you want to
On Mon, 21 Mar 2011 23:06:12 -0700, Joe Neeman joenee...@gmail.com wrote:
Unfortunately, if I protect the assignment to the property with an if
(!pure), I am letting the page-breaking planning rely on the user-requested
affinities, and then changing them for the page-layout phase. The
On Sat, 19 Mar 2011 22:46:51 -0700, Joe Neeman joenee...@gmail.com wrote:
It might cause problems if pure is true. When the method is called with
pure, it shouldn't cause any side effects. For a concrete example, this
will mess up if you have
Staff
Lyrics with affinity down
Staff that
On Mar 15, 2011, at 6:51 PM, Carl Sorensen wrote:
address@hidden wrote Tuesday, March 15, 2011 5:00 PM
\relative c' { \time 3/4 { cis a'4 b fis'2 } \\ { d2. } }
Produces the attached output. Is there a way to get it so that the dot
does not collide with the notehead (w/o resorting to extra
On Wed, 16 Mar 2011 06:39:26 -0700, Jan Nieuwenhuizen jann...@gnu.org wrote:
Keith OHara schreef op di 15-03-2011 om 23:09 [-0700]:
I tried to summarize what the relevant classes do, and indicated the
desired extensions in [[ ]] below :
Not really:
* midiChannelMapping = #'instrument
On Tue, 15 Mar 2011 13:53:41 -0700, Jan Nieuwenhuizen jann...@gnu.org wrote:
To create a new track for each voice as we do now,
still seems a bit like a kludge to fix MIDI's brokenness.
It is, at least, the same kludge others (classicalmidiconnection.com) use when
they have more than 16
On Tue, 15 Mar 2011 01:50:32 -0700, Jan Nieuwenhuizen jann...@gnu.org wrote:
1) re-balancing the instruments
Do you have a test file for that?
We have input\regression\midi-volume-equaliser.ly; the equalizer is still
effective, but the values will probably need re-balancing if you implemnt
On Mon, 14 Mar 2011 02:14:14 -0700, Jan Nieuwenhuizen jann...@gnu.org wrote:
Keith OHara schreef op zo 13-03-2011 om 17:05 [-0700]:
Sensible, but this leaves a partially-finished major change in the
branch that Graham just tagged as 2.14 release candidate.
What's partial about the change
Neil Puttock n.puttock at gmail.com writes:
Interesting. I was on the right track, but it appears to be deleting
something which has already been deleted:
Audio_staff*
Staff_performer::new_audio_staff (string voice)
[..]
In baerenreiter-sarabande.ly, there's an unnamed voice (I'm not
On Mon, 14 Mar 2011 14:19:46 -0700, Jan Nieuwenhuizen jann...@gnu.org wrote:
Keith OHara schreef op ma 14-03-2011 om 13:50 [-0700]:
Dynamics are newly implemented as note-on-velocity,
but the old implementation as channel-volume is still there,
What would the correct fix be?
Well, MIDI
On Sat, 12 Mar 2011 12:35:16 -0800, Jan Nieuwenhuizen jann...@gnu.org wrote:
Ok, pushed. Something much like the previous output can still
be selected, just like the voice-channel mapping for reproducing
voice and staff mapping with the current midi2ly.
It generally works.
The MIDI port
Keith OHara k-ohara5a5a at oco.net writes:
I see you encode dynamics as MIDI note-on-velocity. (This is much better
than
the old way of encoding dynamics as MIDI volume!)
Except that using MIDI volume for dynamics lets LilyPond perform (de)crescendos
on a held note. Somebody might
On Sun, 13 Mar 2011 03:20:51 -0700, Jan Nieuwenhuizen jann...@gnu.org wrote:
I'm not removing anything just yet until we find a good way to
test these things or get some more info.
Sensible, but this leaves a partially-finished major change in the branch that
Graham just tagged as 2.14
On Sun, 13 Mar 2011 17:10:48 -0700, Graham Percival gra...@percival-music.ca
wrote:
If there is a critical regression, then go ahead and add an issue
I don't know of any yet, and I will not be looking for any.
The changes within the past week were significant enough that I expect
complaints
On Sat, 12 Mar 2011 05:48:08 -0800, Jan Nieuwenhuizen jann...@gnu.org wrote:
Ugh. I have just pushed fixes for setting the instrument and assigning
each track to a new port. It would be nice if you could test it, but
afaics it does not work with timidity, alas.
I see (with hexedit) the new
On Fri, 11 Mar 2011 01:32:39 -0800, Jan Nieuwenhuizen jan...@gnu.org wrote:
Neil Puttock schreef op do 10-03-2011 om 21:41 [+]:
both voices will still be allocated the same channel
Why would that be a problem? They're in different tracks.
Are you saying that the instrument of
On Fri, 11 Mar 2011 10:12:59 -0800, Jan Nieuwenhuizen jann...@gnu.org wrote:
Technical correctness probably has little merit if no player
supports it, but it is worth a try. Setting ports should be
quite easy and if major players support this, we're safe.
I know nothing about this, but some
401 - 500 of 552 matches
Mail list logo
