Nick Payne wrote:
As an aside, jpedal as included with LilypondTool renders these brackets
incorrectly if you use mitred corners.
Yes, I reported this last week to the LPT bug tracker, and it
is fixed in SVN. Thanks for the mention.
- Mark
Hi,
In the OOoLilyPond templates I have include #(define dump-extents
#t) like it is produced by lilypond-book output. What is the effect
of this line? I haven't found anything about it in the LilyPond
documentation.
I would like to leave it away, if it does not have any effect.
regards,
Hi,
Today's version of OOoLilyPond inserts the whole piece as one png. The
problem is then that page breaks cannot be handled by OpenOffice.org
that way. The solution would be to insert each system of the piece as
a separate image. I have found a way to create eps files of each
system.
When I load the code below, I get the beaming in the picture below.
With subdivideBeams = ##f, I get reasonable beaming, but if it is set
to ##t, the beams go all the way, not respecting the grouping. This
worked in some older LilyPond (modulo some other beaming problems), so
perhaps one
...
The second example can easily be modified to get what you want.
Just add \fatText before the first spacer note.
/Mats
\fatText has now been replaced (V2.12.0) with \textLengthOn
But it doesn't solve the problem completely
I have a multi-voice orchestral piece, needing tempo markings at
There are some functions (mostly on the C++ side) that assume that the
music objects they contain are unique copies, and modify them in
place. If objects are shared, functions like going to relative mode
and transposition may apply transformations multiple times, laeding to
excessive pitches, for
I want to make a shortcut for mordents with accidental below. One can
use
low = \once \override TextScript #'script-priority = #-100
mordentsharp = \mordent^\markup{\sharp}
...
\low f8\mordentsharp
But I would like to be able to skip the \low, here. So I thought of
building it as a
Hans
SubdivideBeams will break beams at intervals
defined by beatLength, which by default is set
to 1 over the denominator of the time signature.
I think you need to set beatLength explicitly with
\set beatLength = #(ly:make-moment 1 8)
HTH
Trevor
- Original Message -
From: Hans
On 21 Jun 2009, at 16:47, Trevor Daniels wrote:
SubdivideBeams will break beams at intervals
defined by beatLength, which by default is set
to 1 over the denominator of the time signature.
Yes, but this is what goes wrong, as my time signature is 7/16, and
then I use
\set beatGrouping =
Hans Aberg wrote:
I want to make a shortcut for mordents with accidental below. One can use
low = \once \override TextScript #'script-priority = #-100
mordentsharp = \mordent^\markup{\sharp}
...
\low f8\mordentsharp
But I would like to be able to skip the \low, here. So I thought
On 21 Jun 2009, at 18:07, Mark Polesky wrote:
I want to make a shortcut for mordents with accidental below.
Try
mordentsharp = ^\markup \left-align \center-column {
\musicglyph #scripts.mordent \sharp
}
This works fine. Thank you! I found the form
mordentsharp = ^\markup \left-align
On 21 Jun 2009, at 16:47, Trevor Daniels wrote:
SubdivideBeams will break beams at intervals
defined by beatLength, which by default is set
to 1 over the denominator of the time signature.
I think you need to set beatLength explicitly with
\set beatLength = #(ly:make-moment 1 8)
I have
Hans Aberg Sunday, June 21, 2009 5:48 PM
On 21 Jun 2009, at 16:47, Trevor Daniels wrote:
SubdivideBeams will break beams at intervals
defined by beatLength, which by default is set
to 1 over the denominator of the time signature.
I think you need to set beatLength explicitly with
\set
On 6/21/09 9:49 AM, Hans Aberg hab...@math.su.se wrote:
On 21 Jun 2009, at 16:47, Trevor Daniels wrote:
SubdivideBeams will break beams at intervals
defined by beatLength, which by default is set
to 1 over the denominator of the time signature.
Yes, but this is what goes wrong, as my
I've forwarded Ian's message from the Frogs mailing list, because I don't
know how to answer his question. I'm sure somebody on -devel will.
Thanks,
Carl
-- Forwarded Message
From: Ian Hulin i...@hulin.org.uk
Reply-To: fr...@lilynet.net
Date: Sat, 20 Jun 2009 17:25:42 -0600
To: Reinhold
On 21 Jun 2009, at 20:16, Carl D. Sorensen wrote:
I think you misunderstand how beatGrouping works.
In previous versions of LilyPond (2.10, and less than 2.11.x, where
I don't
remember what x is -- it was about August 2008), beatGrouping didn't
work
for autoBeaming.
It is rather that
On 6/21/09 3:27 PM, Hans Aberg hab...@math.su.se wrote:
Yes, beatLength will do a (2+2)+(2+1) beaming. Though this is one
possible beaming for what I am writing now, my problem is that I have
bunch of different meters. For example, I may want (2+2)+3,
(2+2)+3+(2+2) and so on.
I have
Carl D. Sorensen wrote:
By default, beatLength is the numerator of the time signature.
Don't you mean denominator? I would call the numerator beatCount
or something. Haven't followed this thread, just wanted to make
sure a misunderstanding wasn't being propagated.
- Mark
On 21 Jun 2009, at 23:35, Carl D. Sorensen wrote:
But there has been a proposal floated to fix this, so maybe it will be
improved
I have a proposal myself, or at least an idea what is going on. I
started to write a Haskell program to make it explicit, but it is off
right now. The
On 22 Jun 2009, at 00:25, Mark Polesky wrote:
By default, beatLength is the numerator of the time signature.
Don't you mean denominator? I would call the numerator beatCount
or something. Haven't followed this thread, just wanted to make
sure a misunderstanding wasn't being propagated.
This
On 6/21/09 4:25 PM, Mark Polesky markpole...@yahoo.com wrote:
Carl D. Sorensen wrote:
By default, beatLength is the numerator of the time signature.
Don't you mean denominator? I would call the numerator beatCount
or something. Haven't followed this thread, just wanted to make
21 matches
Mail list logo
