Ted Walther wrote:
On Wed, Aug 23, 2006 at 12:55:26PM -0700, Ted Walther wrote:
I have two different staffs. Each staff usually has two voices going
at once. I've been doing it a bar at a time, and for each bar, putting
in a << { } // { } >> section. Now that I am 10 bars in, I'm noticing
th
Ted Walther wrote:
On Wed, Aug 23, 2006 at 08:50:31PM +0200, Mats Bengtsson wrote:
Just as any other property setting that applies to a certain Staff, you
have to do the setting within the Staff context, for example:
\new Staff {
\time 3/4
\key d \major
\clef treble
\set Sta
Ted Walther wrote:
Is there a Debian-format repository where I can install the latest
stable version of lilypond using apt-get?
I don't believe anyone is packaging LilyPond for Debian. As you
probably the latest Debian package is 2.6.3. The GUB's work fine even
if there may be some redundanc
On Wed, Aug 23, 2006 at 12:55:26PM -0700, Ted Walther wrote:
In relative mode, the definition of , and ' depends on the "last" note.
Because of the behavior I will describe below, I'd appreciate a
clarification of how "the last" note is defined.
I have two different staffs. Each staff usually h
I am learning lilypond by transcribing Blake's "Jerusalem" into Lilypond
format.
In relative mode, the definition of , and ' depends on the "last" note.
Because of the behavior I will describe below, I'd appreciate a
clarification of how "the last" note is defined.
I have two different staffs.
On Wed, Aug 23, 2006 at 08:50:31PM +0200, Mats Bengtsson wrote:
\set Staff.midiInstrument = #"oboe"
I have tried it in the top level, and inside a \score section. It
makes no difference; the resulting midi file always uses the default
grand piano.
Just as any other property setting that appli
Quoting Ted Walther <[EMAIL PROTECTED]>:
I am running Debian unstable, with lilypond 2.6.3 for typesetting,
timidity 2.13.2 to play midi files, and freepats 20060219 to provide the
midi patchsets.
I recommend you to upgrade to the latest stable version, 2.8. The
installation package available
I am running Debian unstable, with lilypond 2.6.3 for typesetting,
timidity 2.13.2 to play midi files, and freepats 20060219 to provide the
midi patchsets.
I notice in the manual it says the patch set has to be named exactly,
with no variance in case allowed. So I have been pasting in different
Erik Sandberg wrote:
Citerar Han-Wen Nienhuys <[EMAIL PROTECTED]>:
Log message:
* python/convertrules.py (conv): warning on \tempo{}
* ly/performer-init.ly: set tempoWholesPerMinute.
* lily/parser.yy (output_def_body): disallow \tempo in \midi{}
Hi,
Citerar Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> Log message:
> * python/convertrules.py (conv): warning on \tempo{}
>
> * ly/performer-init.ly: set tempoWholesPerMinute.
>
> * lily/parser.yy (output_def_body): disallow \tempo in \midi{}
Hi,
Why can't \tempo in \mi
On Sat, 2006-08-19 at 20:00 +0200, Han-Wen Nienhuys wrote:
> Joe Neeman wrote:
> > +vector
> > +Page_breaking::systems ()
>
> this looks like a potential memory error. The SCM vector is allocated
> on the heap, and hence, is not GC scanned, and may be freed prematurely.
> Please double check
O
11 matches
Mail list logo
