http://codereview.appspot.com/1720046
Hey developers,
Today I had time to finish version 2 of my waveform patch that uses glpk
to do smooth linear interpolation of waveforms. As there is a dependency
freeze & glpk is ultimately too big & too everchanging to be part of
lilypond, this won't mak
I'm trying to redo auto-beaming so that it matches better with what I read
in the literature. When I get it done, I hope to have it set up so that the
default properties do the right thing, and all we have to do is define
exceptions. Working in this framework, I think the LilyPond syntax needs to
On 7/2/10 7:50 AM, "Mike Solomon" wrote:
> http://codereview.appspot.com/1720046
>
> Hey developers,
> Today I had time to finish version 2 of my waveform patch that uses glpk
> to do smooth linear interpolation of waveforms. As there is a dependency
> freeze & glpk is ultimately too big
Mike Solomon writes:
> http://codereview.appspot.com/1720046
>
> Hey developers,
> Today I had time to finish version 2 of my waveform patch that uses glpk
> to do smooth linear interpolation of waveforms. As there is a dependency
> freeze & glpk is ultimately too big & too everchanging to b
Hi David,
> It seems nice to be able to add this sort of thing to Lilypond, but I
> think it rather strongly demonstrates Lilypond's lack of modularity:
> this sort of thing should sit in a separate directory and be loaded
> on-demand under user control without needing any resident code parts
> wh
On Fri, Jul 02, 2010 at 08:22:15AM -0600, Carl Sorensen wrote:
> I'm trying to redo auto-beaming so that it matches better with what I read
> in the literature. When I get it done, I hope to have it set up so that the
> default properties do the right thing, and all we have to do is define
> excep
On Fri, Jul 02, 2010 at 04:54:11PM +0200, David Kastrup wrote:
> There is no documentation as far as I can see,
Our stated (albeit probably only on the mailing list) policy is
that new features don't need docs from the programmers; as long as
there's sufficient regtest(s) and the programmer talks
Hi guys,
We're up to 18 patches.
http://code.google.com/p/lilypond/issues/list?q=label:patch
- 1 was abandoned (a python to convert-ly for accented characters)
- 3 fix Critical issues
I'm appealing particularly to *non-developers* to help here.
LilyPond developers are massively overworked, and s
On 7/2/10 9:25 AM, "Graham Percival" wrote:
> On Fri, Jul 02, 2010 at 08:22:15AM -0600, Carl Sorensen wrote:
>> I'm trying to redo auto-beaming so that it matches better with what I read
>> in the literature. When I get it done, I hope to have it set up so that the
>> default properties do th
Please review this patch created by xhero to fix bug 1063.
I found one comment formatting issue, but the original author hasn't
responded. I'll fix that issue before pushing.
Thanks,
Carl
http://codereview.appspot.com/1327043/show
___
lilypond-dev
I'm not sure where we are on this patch; we've had some philosophical
discussion whose end I'm not sure I understand.
Is this OK to push?
http://codereview.appspot.com/1345041/show
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gn
Responses inlined:
On 7/2/10 4:54 PM, "David Kastrup" wrote:
> Mike Solomon writes:
>
>> http://codereview.appspot.com/1720046
>>
>> Hey developers,
>> Today I had time to finish version 2 of my waveform patch that uses glpk
>> to do smooth linear interpolation of waveforms. As there is
Graham Percival writes:
> On Fri, Jul 02, 2010 at 04:54:11PM +0200, David Kastrup wrote:
>> There is no documentation as far as I can see,
>
> Our stated (albeit probably only on the mailing list) policy is
> that new features don't need docs from the programmers; as long as
> there's sufficient
On Fri, Jul 02, 2010 at 06:12:03PM +0200, David Kastrup wrote:
> Graham Percival writes:
>
> >> It seems nice to be able to add this sort of thing to Lilypond, but I
> >> think it rather strongly demonstrates Lilypond's lack of modularity:
> >> this sort of thing should sit in a separate director
--
Michael
>From 7c0fd69ba512a7bdff60e5bf7ea927879add8250 Mon Sep 17 00:00:00 2001
From: Mikemoral
Date: Thu, 1 Jul 2010 22:42:59 -0700
Subject: [PATCH] Edit to the music glossary
Added more to the entry on brass.
---
Documentation/music-glossary.tely |3 ++-
1 files changed, 2 insertions(
On 7/2/10 12:03 PM, "Graham Percival" wrote:
> On Fri, Jul 02, 2010 at 06:12:03PM +0200, David Kastrup wrote:
>> Graham Percival writes:
>>
It seems nice to be able to add this sort of thing to Lilypond, but I
think it rather strongly demonstrates Lilypond's lack of modularity:
t
On 2 Jul 2010, at 16:22, Carl Sorensen wrote:
I'm trying to redo auto-beaming so that it matches better with what
I read
in the literature. When I get it done, I hope to have it set up so
that the
default properties do the right thing, and all we have to do is define
exceptions. Working in
On 7/2/10 1:38 PM, "Hans Aberg" wrote:
> On 2 Jul 2010, at 16:22, Carl Sorensen wrote:
>
>> I'm trying to redo auto-beaming so that it matches better with what
>> I read
>> in the literature. When I get it done, I hope to have it set up so
>> that the
>> default properties do the right thing, a
On Fri, Jul 2, 2010 at 3:31 PM, Carl Sorensen wrote:
> We may be missing iterators and performers, I guess.
Iterators should already be possible. Performers not, but the whole
MIDI thing is broken anyway.
The real kicker for the waveform renderer patch is that it uses
another library, so not de
gmail.com> writes:
>
> I'm not sure where we are on this patch; we've had some philosophical
> discussion whose end I'm not sure I understand.
If you accept this patch, I will also provide one to ban ly:parser-parse-file in
times that it segfaults.
_
On 2 Jul 2010, at 23:11, Carl Sorensen wrote:
By CPP, do you mean Common Practice Period, i.e. western European
Baroque,
Classical, and Romantic?
Yes, it is sort of practical when discussing music; used a lot in
rec.music.theory.
For other types of music, one would like to depart from t
On 7/2/10 4:55 PM, "Hans Aberg" wrote:
> On 2 Jul 2010, at 23:11, Carl Sorensen wrote:
>
>> So, for example, we could have a fundamental unit of 1/8, and then
>> for a
>> time signature of 15/8, we might have a beat structure of
>>
>> (2 3 (2 (3 2)) 3)
>>
>> The first two eighth notes wou
Carl Sorensen wrote Friday, July 02, 2010 3:22 PM
Sounds a promising approach, although some of the details
remain unclear from your lucid but high-level description.
I'm trying to redo auto-beaming so that it matches
better with what I read in the literature. When I
get it done, I hope to h
On 7/2/10 5:19 PM, "Trevor Daniels" wrote:
>
>
> Carl Sorensen wrote Friday, July 02, 2010 3:22 PM
>
> Sounds a promising approach, although some of the details
> remain unclear from your lucid but high-level description.
Yes, to really understand it one needs to see the details.
>
>> I'm t
I completely agree that modularity is a great way to go - I think that
woodwinds could be re-integrated into lilypond this way, as could fretboard
diagrams and other similar features.
For me, the three very beneficial aspects of C++ are its ability to work
with data structures that retain informat
In top directory from commit , I have done:
$ make all && make doc
It stopped after an error in lilypond-book.py (see below).
Frédéric
lilypond-book.py: warning:
/home/bronf/lilypond/out/lybook-db/6f/lily-68fe9560.ly: duplicate
filename but different contents of orginal file,
printing diff again
26 matches
Mail list logo
