On Sat, Dec 12, 2009 at 10:45:58PM -0800, Mark Polesky wrote:
> I don't know if there's an easy solution to this, but when I
> run `make check', CPU1 runs at or near 100% for about 6
> minutes while the other 3 cores sit idly by (for the most
> part).
> Is there a way to improve this? I don't wan
On 12/12/09 2:27 PM, "Joe Neeman" wrote:
> On Sat, 2009-12-12 at 14:15 -0700, Carl Sorensen wrote:
>> So I've finally gotten to a point where I think I know what to do with the
>> autobeaming code to make it work properly in 4/4 time with a 1/16 note in
>> the second beat.
>>
>> I've written
Am Samstag, 12. Dezember 2009 15:43:37 schrieb 胡海鹏 - Hu Haipeng:
> Sorry, Since the bad frustrating Midi tie problem persists, I have to roll
> back to 2.13.7, and wait for a version with fixed tie playback.
Okay, thanks to Joe spotting the cause of the memory corruption (of course,
stupid shado
On Sat, Dec 12, 2009 at 3:23 PM, Mark Polesky wrote:
> Hey everyone,
>
> Pardon my confusion; I've been doing a lot of stuff here and
> I've not yet figured out what causes what. Among the many
> things I've done recently is this command (from CG 2.1.2
> "Requirements"): $ sudo apt-get build-dep
Hi Mark,
I'm pleased to see you back on the lists :-)
Le samedi 12 décembre 2009 à 13:23 -0800, Mark Polesky a écrit :
> Hey everyone,
>
> Pardon my confusion; I've been doing a lot of stuff here and
> I've not yet figured out what causes what. Among the many
> things I've done recently is this
On Sat, 2009-12-12 at 14:15 -0700, Carl Sorensen wrote:
> So I've finally gotten to a point where I think I know what to do with the
> autobeaming code to make it work properly in 4/4 time with a 1/16 note in
> the second beat.
>
> I've written code to try to fix it. The code seems to execute pro
Hey everyone,
Pardon my confusion; I've been doing a lot of stuff here and
I've not yet figured out what causes what. Among the many
things I've done recently is this command (from CG 2.1.2
"Requirements"): $ sudo apt-get build-dep lilypond
Not sure if that was what put texi2html on my system, b
So I've finally gotten to a point where I think I know what to do with the
autobeaming code to make it work properly in 4/4 time with a 1/16 note in
the second beat.
I've written code to try to fix it. The code seems to execute properly
through my changes, but then it gets into a problem, and I g
On Sat, 2009-12-12 at 17:22 +0100, Reinhold Kainhofer wrote:
> Am Samstag, 12. Dezember 2009 15:43:37 schrieb 胡海鹏 - Hu Haipeng:
> > Sorry, Since the bad frustrating Midi tie problem persists, I have to roll
> > back to 2.13.7, and wait for a version with fixed tie playback.
>
> I've tried to fix
And yes, this solved the problem! You're right, flex is among the dependencies.
Concluding it, I think two things may be worth adding to the CG 2.1.6:
* the workaround of the C++ related problem: perl -pi -e
's|__vector|lily_vector|g' flower/include/std-vector.hh
* in case someone isn't familiar w
On 12/12/09 9:07 AM, "Harmath Dénes" wrote:
> On 2009.12.11., at 16:34, Carl Sorensen wrote:
>
>> Have you set the flelexer file in config.make to opt/local instead of
>> use?
>>
>> Carl Sorensen
>
> Strangely, I have no /opt/local/include/FlexLexer.h, but I indeed have
> /usr/include/FlexL
Nicolas Sceaux wrote Saturday, December 12, 2009 3:39 PM
Le 12 déc. 2009 à 14:01, David Kastrup a écrit :
{ G4 g D // | /// // / // | \time 3/4 G g / | D // // | /// // //
| }
Memorizing more than one chord/note (e.g. 3 chords/notes), and
accessing
them using q, qq, qqq, would do it?
Am Samstag, 12. Dezember 2009 15:43:37 schrieb 胡海鹏 - Hu Haipeng:
> Sorry, Since the bad frustrating Midi tie problem persists, I have to roll
> back to 2.13.7, and wait for a version with fixed tie playback.
I've tried to fix the bug, but I'm always running into memory corruption
issues, and I h
Begin forwarded message:
On 2009.12.11., at 16:34, Carl Sorensen wrote:
> Have you set the flelexer file in config.make to opt/local instead of
> use?
>
> Carl Sorensen
Strangely, I have no /opt/local/include/FlexLexer.h, but I indeed have
/usr/include/FlexLexer.h
Setting FLEXLEXER_FILE = /o
Le 12 déc. 2009 à 14:01, David Kastrup a écrit :
>
> { G4 g D // | /// // / // | \time 3/4 G g / | D // // | /// // // | }
Memorizing more than one chord/note (e.g. 3 chords/notes), and accessing
them using q, qq, qqq, would do it?
___
lilypond-devel
Le 12 déc. 2009 à 16:00, Reinhold Kainhofer a écrit :
> Am Samstag, 12. Dezember 2009 13:29:57 schrieb Nicolas Sceaux:
>> In particular, I've get rid off the user-settable
>> memorization function: only chords (with angle brackets) are memorized.
>> This should be the more useful to users, and at
Am Samstag, 12. Dezember 2009 13:29:57 schrieb Nicolas Sceaux:
> In particular, I've get rid off the user-settable
> memorization function: only chords (with angle brackets) are memorized.
> This should be the more useful to users, and at the same time easy
> enough for LilyPond-aware editors to ha
Werner LEMBERG wrote:
Hmm. I won't mind if `q' is able to repeat a single note too, for the
sake of consistency. Nicolas, would this be difficult to implement?
I don't think so - that's what Nicolas had in mind (and implemented)
first. I suppose I'm the one who made him thinking about the o
Werner LEMBERG writes:
>> So I'd think it would be nice to write something like
>>
>> { G4 g D // | // // | \time 3/4 G g / | D // / | // // / | }
>>
>> (number of slashes corresponds with how far you have to look
>> backwards, in this case counting slash sequences new when they
>
> So I'd think it would be nice to write something like
>
> { G4 g D // | // // | \time 3/4 G g / | D // / | // // / | }
>
> (number of slashes corresponds with how far you have to look
> backwards, in this case counting slash sequences new when they
> appear) or without reslash mem
Nicolas Sceaux writes:
> I'm taking into account remarks from previous discussions regarding
> chord repetition. In particular, I've get rid off the user-settable
> memorization function: only chords (with angle brackets) are memorized.
> This should be the more useful to users, and at the same
> Two options:
>
> %% The second upper "c" octave is computed from the first "c"
> %% i.e. the last explicite note.
> \relative c' {
> 8 c' q c r4 q
> }
>
> %% The second upper "c" octave is computed from the previous
> %% repeated chord ("q")
> \relative c' {
> 8 c' q c' r4 q
> }
>
> I'd fa
Hi,
I'm taking into account remarks from previous discussions regarding
chord repetition. In particular, I've get rid off the user-settable
memorization function: only chords (with angle brackets) are memorized.
This should be the more useful to users, and at the same time easy
enough for LilyPon
Mark Polesky wrote Saturday, December 12, 2009 11:18 AM
So, I'm changing my initial proposal. Now I think:
1) marcato should remain quantized.
2) staccatissimo should become quantized.
3) accent should either be
a) de-quantized, or even better,
b) programmed "smart", ie. conditional quan
Neil Puttock wrote:
> LGTM.
>
> > do I need to do anything described in CG 8.7 "Adding or
> > modifying features"? Should I add a @item to
> > changes.tely?
>
> No and no. :)
Well, I did a little more research into this and
unfortunately the situation is a little more complicated
than I had init
Neil,
have you finished your work on fixing #305? I can vaguely remember
something into this direction ...
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Sat, Dec 12, 2009 at 7:45 AM, Joe Neeman wrote:
> On Sat, 2009-12-12 at 07:00 +, Graham Percival wrote:
>> To assist in this, in the near future I'll set up a daily out-of-tree
>> building system for lilypond (I've done it before for marsyas). If
>> any build fails, it will send rude messa
>> Could someone please check issue #774 with a stable release (either
>> 2.10 or 2.12) so that I can probably set the regression flag? At
>> the time of my report, I only had 2.11.13 for comparison, which is
>> a developer's version, and I still don't have any stable releases
>> installed.
>
>
28 matches
Mail list logo
