Dear list,
in the following example i would have hoped for two whole-bar beams, but
only the second is printed like i expected.
\version "2.13.28"
{
\overrideBeamSettings #'Staff #'(5 . 16) #'end
#'((* . (1))
)
\time 5/16 \times 10/9{c16 c16. c16 c16}
\overrideBeamSet
Arno Waschk wrote:
>
> Dear list,
>
> in the following example i would have hoped for two whole-bar beams, but
> only the second is printed like i expected.
>
>
> \version "2.13.28"
>
> {
> \overrideBeamSettings #'Staff #'(5 . 16) #'end
> #'((* . (1))
> )
> \time 5/16
On 7/8/10 1:51 AM, "Arno Waschk" wrote:
> Dear list,
>
> in the following example i would have hoped for two whole-bar beams, but
> only the second is printed like i expected.
>
>
> \version "2.13.28"
>
> {
> \overrideBeamSettings #'Staff #'(5 . 16) #'end
> #'((* . (1))
> )
Hello,
I noticed an .ly file called
'conducting-signs,-measure-grouping-signs.ly'
In my most recent download of the source.
The snippet text in rhythms.itely matches
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
{conducting-signs,-measure-grouping-signs.ly}
I didn't wan
On 7/8/10 9:58 AM, "James Lowe" wrote:
> Hello,
>
> I noticed an .ly file called
>
> 'conducting-signs,-measure-grouping-signs.ly'
>
> In my most recent download of the source.
>
>
>
> The snippet text in rhythms.itely matches
>
>> @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,d
On Thu, Jul 08, 2010 at 10:16:47AM -0600, Carl Sorensen wrote:
>
> On 7/8/10 9:58 AM, "James Lowe" wrote:
>
> > 'conducting-signs,-measure-grouping-signs.ly'
> >
> >> @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
> >> {conducting-signs,-measure-grouping-signs.ly}
> >
> > I di
On 08/07/2010 18:07, Graham Percival wrote:
On Thu, Jul 08, 2010 at 10:16:47AM -0600, Carl Sorensen wrote:
On 7/8/10 9:58 AM, "James Lowe" wrote:
'conducting-signs,-measure-grouping-signs.ly'
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
{conducting-signs,-measure-groupin
On Thu, Jul 08, 2010 at 06:33:24PM +0100, James Lowe wrote:
> On 08/07/2010 18:07, Graham Percival wrote:
>> On Thu, Jul 08, 2010 at 10:16:47AM -0600, Carl Sorensen wrote:
>>>
>>> This filename has been part of the tree for more than a year, so, while it
>>> could potentially cause problems, it has
On 8 July 2010 18:43, Graham Percival wrote:
> Then please rename it. Patch to Trevor... no, wait, we'll need to
> regnerate the *.snippet-list files.
Arrgh, please no! :)
It shadows the snippet in LSR, which has the same filename: LSR
doesn't strip commas. The LSR version had to be moved int
Hi Joe,
Here's another one:
130 for (vsize i = 0; i < rests.size (); i++)
131 {
132 Grob *r = Note_column::get_rest (rests[i]);
133
134 Direction d = get_grob_direction (r);
135 if (d)
136 ordered_rests[d].push_back (rests[i]);
162 Re
Hello all,
As per earlier discussion on the -user list:
http://www.mail-archive.com/lilypond-u...@gnu.org/msg51183.html
... I finally managed to put some time and mental energy towards
chromatic transposition, in particular, the naturalizeMusic function
from the LSR.
I've attached a draft versio
On Thu, Jul 08, 2010 at 06:49:09PM +0100, Neil Puttock wrote:
> On 8 July 2010 18:43, Graham Percival wrote:
>
> > Then please rename it. Patch to Trevor... no, wait, we'll need to
> > regnerate the *.snippet-list files.
>
> It shadows the snippet in LSR, which has the same filename:
Oops, I f
On 8 July 2010 19:47, Joseph Wakeling wrote:
> (Example: take the music of bb. 9-10 in the sample music, and
> put it through the _original_ naturalizeMusic function. You get
> left with a g-double-flat instead of an f-natural.)
You're using 2.12, I assume?
Since 2.13.14,
On 07/08/2010 10:25 PM, Neil Puttock wrote:
> On 8 July 2010 19:47, Joseph Wakeling wrote:
>
>>(Example: take the music of bb. 9-10 in the sample music, and
>>put it through the _original_ naturalizeMusic function. You get
>>left with a g-double-flat instead of an f-natur
On 8 July 2010 22:06, Joseph Wakeling wrote:
> On 07/08/2010 10:25 PM, Neil Puttock wrote:
> ('original' and 'revised' refer to the original and my version of
> naturalizeMusic?)
Yes.
> So ... other than that it might be nice to have the snippet for 2.12, is
> there any contribution that I can
On 07/09/2010 12:09 AM, Neil Puttock wrote:
> That sounds like a useful enhancement, except that it would be a music
> property rather than a context property, since transposition happens
> before translation.
Can you explain more precisely ... ? This seems like something I should
understand very
On 8 July 2010 23:20, Joseph Wakeling wrote:
> Can you explain more precisely ... ? This seems like something I should
> understand very well in order to provide an effective solution.
Context properties (using \set & \unset) are tied to engravers: they
provide information relevant to the gener
On Tue, Jul 06, 2010 at 11:54:29AM +0100, Wols Lists wrote:
> quote:
>
> The trombones are a special case: although they are said to be 'in F'
> (alto or bass) or 'in B-flat' (tenor), this refers to their fundamental
> note, not to their parts' transposition. (In fact, the trombones' parts
> are
On 2 July 2010 23:47, Benjamin Peterson wrote:
> If you accept this patch, I will also provide one to ban ly:parser-parse-file
> in
> times that it segfaults.
That sounds like a fair deal. :)
The patch looks fine to me (there are just a few minor style nits
which can be squelched when it's app
On 2010/07/02 15:55:27, Carl wrote:
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?
LGTM, save a few style nitpicks.
http://codereview.appspot.com/1345041/show
__
On 2010/06/29 23:58:07, Neil Puttock wrote:
Do you think the property name's OK though? I agree with Carl it
could be a bit
more descriptive, but then there's also the need to keep verbosity to
a minimum.
Yes, I think the property name is fine.
-Patrick
http://codereview.appspot.com/93104
On 07/07/2010 04:06 PM, Wols Lists wrote:
On 07/07/10 19:06, Paul Scott wrote:
On Tue, Jul 06, 2010 at 11:54:29AM +0100, Wols Lists wrote:
quote:
The trombones are a special case: although they are said to be 'in F'
(alto or bass) or 'in B-flat' (tenor), this refers to their fundamental
not
I've got a draft of accordion push and pull symbols. Please let me know
what you think of them.
Thanks,
Carl
accpushpull.pdf
Description: accpushpull.pdf
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/li
> "Paul" == Paul Scott writes:
Paul> On 07/07/2010 04:06 PM, Wols Lists wrote:
>> On 07/07/10 19:06, Paul Scott wrote:
>>> On Tue, Jul 06, 2010 at 11:54:29AM +0100, Wols Lists wrote:
Paul> The lowest note on a woodwind is a fundamental. It's just not
Paul> directly related to how the key of
24 matches
Mail list logo
