Janek Warchoł wrote Friday, March 04, 2011 11:42 PM
this is the next step of making stems and flags more beautiful:
i suggest making unbeamed 32nd stems a bit shorter than they are
now.
The main reason for doing so is to better match the stem length of
the
beamed notes.
As we know, the
Hey all,
After a bit of back and forth w/ Han Wen, I have drummed up a way to split this
up such that it can be part of LilyPond in two phases. It follows his
suggestion to push all of the non-balloon-related stuff first, and to push that
second. It will set the stencil property of
On Mar 4, 2011, at 9:47 PM, Keith OHara wrote:
Mike Solomon mikesol at ufl.edu writes:
http://codereview.appspot.com/4182071
I have no clue how convert-ly works: would anyone like to take on the task
of
implementing these conversions
in that script?
Cheers,
MS
Well,
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: Carl Sorensen c_soren...@byu.edu
Cc: Lily devel lilypond-devel@gnu.org
Sent: Friday, March 04, 2011 8:05 PM
Subject: Re: build system work
On Fri, Mar 04, 2011 at 11:38:19AM -0700, Carl Sorensen wrote:
On 3/4/11
Carl, Han-Wen, Werner, Trevor,
thanks for swift answers!
2011/3/5 Han-Wen Nienhuys hanw...@gmail.com
Therefore i call for shortening 32nd unbeamed notes by 0.25 ss. Do you
agree?
SGTM - I don't think we ever put this much thought or analysis into
the numbers we put there.
:) I'm going to
Neil Puttock schreef op vr 04-03-2011 om 23:08 [+]:
There were two bugs: missing snippets from the harmonics patch and an
undocumented translation property (restCompletionBusy).
Both fixed in master.
Thanks!
Jan
--
Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org
Hi,
while i'd love to improve beaming algorithm itself so that it would
produce perfect beams on its own, it's a task way beyond my current
skills. Still some wrong beams bother me very much, for example this
one
\relative c'' { b8[ a16 g] }
it's really too high, and the secondary beam doesn't
On Sat, Mar 5, 2011 at 10:18 PM, Mike Solomon mike...@ufl.edu wrote:
Hey all,
After a bit of back and forth w/ Han Wen, I have drummed up a way to split
this up such that it can be part of LilyPond in two phases. It follows his
suggestion to push all of the non-balloon-related stuff first,
2011/3/4 Graham Percival gra...@percival-music.ca:
PS I'm fairly certain that at the moment, all needs_work issues
do not have any more recent drafts that you need to look at.
Doesn't http://code.google.com/p/lilypond/issues/detail?id=1541
have a new draft? (with fixed indentation)
On 5 March 2011 12:57, Mike Solomon mike...@ufl.edu wrote:
Patch attached. The stuff that comes from your comments regarding
break-visibility is implemented in Balloon_interface::is_visible.
The patch currently represents about 85% of the original, omitting the 15%
that Han Wan had
- Original Message -
From: Francisco Vila paconet@gmail.com
To: Graham Percival gra...@percival-music.ca
Cc: Lily devel lilypond-devel@gnu.org; Phil Holmes
em...@philholmes.net
Sent: Friday, March 04, 2011 4:23 PM
Subject: Re: build system work
2011/3/4 Graham Percival
I try to run the script, but get the error Can't exec out-cov/midi2ly:
Permission denied at
/home/zxy/lilypond/2.13.24/scripts/build/out-cov/help2man line 193. I use *
root* to run it, and I don't know what does Permission denied mean. Anyone
who konw it?
2011/3/4 Carl Sorensen c_soren...@byu.edu
On Sat, Mar 5, 2011 at 11:57 PM, Mike Solomon mike...@ufl.edu wrote:
On Mar 5, 2011, at 7:19 AM, Joe Neeman wrote:
On Sat, Mar 5, 2011 at 10:18 PM, Mike Solomon mike...@ufl.edu wrote:
Hey all,
After a bit of back and forth w/ Han Wen, I have drummed up a way to split
this up such that it
Hello,
From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
[lilypond-devel-bounces+james.lowe=datacore@gnu.org] on behalf of Graham
Percival [gra...@percival-music.ca]
Sent: 04 March 2011 20:05
To: Carl Sorensen
Cc: Lily devel
Subject: Re:
On 5 March 2011 14:38, Mike Solomon mike...@ufl.edu wrote:
Done - thanks for bearing with me as I learn about break-visibility. It is a
corner of the code that I never had to deal with directly, so I'm still
getting my sea legs.
I suggest you remove the fallback value from
--
Phil Holmes
- Original Message -
From: Janek Warchoł lemniskata.bernoull...@gmail.com
To: lilypond-devel@gnu.org
Sent: Saturday, March 05, 2011 12:05 PM
Subject: a list of manually fine-tuned beaming exceptions?
Hi,
while i'd love to improve beaming algorithm itself so that
On Mar 5, 2011, at 11:08 AM, Phil Holmes wrote:
--
Phil Holmes
- Original Message - From: Janek Warchoł
lemniskata.bernoull...@gmail.com
To: lilypond-devel@gnu.org
Sent: Saturday, March 05, 2011 12:05 PM
Subject: a list of manually fine-tuned beaming exceptions?
Hi,
Janek Warchoł wrote Saturday, March 05, 2011 12:05 PM
while i'd love to improve beaming algorithm itself so that it
would
produce perfect beams on its own, it's a task way beyond my
current
skills. Still some wrong beams bother me very much, for example
this
one
\relative c'' { b8[ a16 g]
On Sat, Mar 05, 2011 at 01:37:04PM +0100, Jan Warchoł wrote:
2011/3/4 Graham Percival gra...@percival-music.ca:
PS I'm fairly certain that at the moment, all needs_work issues
do not have any more recent drafts that you need to look at.
Doesn't
From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
[lilypond-devel-bounces+james.lowe=datacore@gnu.org] on behalf of James
Lowe [james.l...@datacore.com]
Sent: 01 March 2011 20:16
To: Francisco Vila
Cc: lilypond-devel
Subject: Re: clarify a
2011/3/5 Graham Percival gra...@percival-music.ca:
On Sat, Mar 05, 2011 at 01:37:04PM +0100, Jan Warchoł wrote:
2011/3/4 Graham Percival gra...@percival-music.ca:
PS I'm fairly certain that at the moment, all needs_work issues
do not have any more recent drafts that you need to look at.
Hello all,
I think that commit a61ab84e86b209fe11d63ec488e02525b7481b5b
causes 'make all' to fail with
[snip]
LANG= makeinfo --enable-encoding -I
/home/marc/git/lilypond/Documentation -I. -I./out
--output=out/lilypond-changes.info out/changes.texi
out/changes.texi:88: Misplaced {.
On Sat, Mar 05, 2011 at 09:27:27PM +0100, Marc Hohl wrote:
I think that commit a61ab84e86b209fe11d63ec488e02525b7481b5b
causes 'make all' to fail with
Indeed. Fixed now, I believe.
Cheers,
- Graham
___
lilypond-devel mailing list
Pushed - 3930f57e6ccb6e7b1190d80055031733a45eae32
Closing this issue
http://codereview.appspot.com/4250044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
2011/3/5 Phil Holmes m...@philholmes.net:
I'm not qualified to comment, and it seems it would be hard work, but you
might be interested in this snippet in the music I'm setting now. To me,
the shorter beams look rather squashed, and I'm surprised they're not the
same height as the longer
On Mar 5, 2011, at 17:33, Janek Warchoł lemniskata.bernoull...@gmail.com
wrote:
2011/3/5 Phil Holmes m...@philholmes.net:
I'm not qualified to comment, and it seems it would be hard work, but you
might be interested in this snippet in the music I'm setting now. To me,
the shorter beams look
2011/3/6 m...@apollinemike.com m...@apollinemike.com:
On Mar 5, 2011, at 17:33, Janek Warchoł lemniskata.bernoull...@gmail.com
wrote:
Thanks for information! Yes, this should be investigated.
However, i'm afraid that when i change some well-established
parameters, it may cause unwanted
On 3/5/11 4:12 PM, Janek Warchoł lemniskata.bernoull...@gmail.com wrote:
Hi,
Short question: do you agree to make downstem 8th flag shorter, as in
single downstem proposed.png?
This way it won't blend into notehead. This would be consistent with
looks of other flags, see gaps.png.
I
Patch revised to remove the doc-section.sh bits which were pushed
separately. The remainder is just the partcombine explanation.
Ordinarily, I suppose this needn't go on reitveld, but wotthehell
archie, it started here so I'm putting the last bit up to close out the
process.
Short question: do you agree to make downstem 8th flag shorter, as
in single downstem proposed.png?
I must admit that I don't have a real opinion here, contrary to the
stem length issue. Looking at the issue from a `classical' printing
point of view, I think that the flags with the gaps are
30 matches
Mail list logo
