Hi Carl,
Am 15.06.2010 21:52, schrieb Carl Sorensen:
...
By now I understand the logic behind this from a programmer's perspective.
But I have to say it seems quite counterintuitive from a musical or
typesetter's point of view. If I change the beatLength setting I'd expect that
beams are now gr
Hi Carl,
> Well, I think the new code will have a very easy solution for you.
> If you want to always have beaming follow beatLength, you can simply do
> \set Score.beamSettings = "#'()
> Then beatLength will control the beaming.
THAT SOUNDS AMAZING!!
This has been an irritation of mine for a whi
On 6/15/10 11:17 AM, "Urs Liska" wrote:
> Today I tried to use the \overrideBeamSetting (near the bottom of this email)
> in my real score and I am very happy that it works perfectly now.
>
> By now I understand the logic behind this from a programmer's perspective.
> But I have to say it see
Today I tried to use the \overrideBeamSetting (near the bottom of this
email) in my real score and I am very happy that it works perfectly now.
By now I understand the logic behind this from a programmer's perspective.
But I have to say it seems quite counterintuitive from a musical or
typesett
On 6/14/10 5:45 PM, "Xavier Scheuer" wrote:
> 2010/6/15 Carl Sorensen :
>
>> The _default_ behavior, as you call it, is not really the _default_
>> behavior. beatLength should not affect beaming if a default rule is
>> defined. The fact that it does is a bug that will be fixed in the
>> new
2010/6/15 Carl Sorensen :
> The _default_ behavior, as you call it, is not really the _default_
> behavior. beatLength should not affect beaming if a default rule is
> defined. The fact that it does is a bug that will be fixed in the
> new code.
OK, but it was still *unconsistent*. ;D
> Yes,
On 6/14/10 5:07 PM, "Xavier Scheuer" wrote:
> 2010/6/15 u_li :
>
>> Sorry, this is not necessary anymore. I fixed it (my problem and my
>> not understanding) with
>>
>> \overrideBeamSettings #'Score #'(4 . 4) #'end
>> #'(((1 . 8) . (4 4))
>> ((1 . 16) . (2 2 2 2 2 2 2 2))
>>
2010/6/15 u_li :
> Sorry, this is not necessary anymore. I fixed it (my problem and my
> not understanding) with
>
> \overrideBeamSettings #'Score #'(4 . 4) #'end
> #'(((1 . 8) . (4 4))
> ((1 . 16) . (2 2 2 2 2 2 2 2))
> ((1 . 32) . (4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4)))
>
> i.e.
Am 15.06.2010 00:33, schrieb u_li:
Am 14.06.2010 15:37, schrieb Carl Sorensen:
On 6/14/10 7:18 AM, "u_li" wrote:
Am 14.06.2010 15:04, schrieb Carl Sorensen:
On 6/14/10 5:24 AM, "u_li" wrote:
[sorry if this should be a double post. When I first sent the message I
didn'
Am 14.06.2010 15:37, schrieb Carl Sorensen:
On 6/14/10 7:18 AM, "u_li" wrote:
Am 14.06.2010 15:04, schrieb Carl Sorensen:
On 6/14/10 5:24 AM, "u_li" wrote:
[sorry if this should be a double post. When I first sent the message I
didn't
configure my current email clien
For these sort of situtaions I turn \autoBeamOff and use
[ ] to write beams as required.
Gerard
- Original Message -
From: u_li
To: lilypond-user@gnu.org
Sent: Monday, June 14, 2010 12:24 PM
Subject: beatLength / beaming in 4/4
[sorry if this should be a double post
On 6/14/10 7:18 AM, "u_li" wrote:
> Am 14.06.2010 15:04, schrieb Carl Sorensen:
>>
>>
>> On 6/14/10 5:24 AM, "u_li" wrote:
>>
>>
>>> [sorry if this should be a double post. When I first sent the message I
>>> didn't
>>> configure my current email client to use my registered address. As
Am 14.06.2010 15:04, schrieb Carl Sorensen:
On 6/14/10 5:24 AM, "u_li" wrote:
[sorry if this should be a double post. When I first sent the message I didn't
configure my current email client to use my registered address. As I don't see
my post on the list I assume it didn't get through.
On 6/14/10 5:24 AM, "u_li" wrote:
> [sorry if this should be a double post. When I first sent the message I didn't
> configure my current email client to use my registered address. As I don't see
> my post on the list I assume it didn't get through. If it did please ignore
> this second post ]
14 matches
Mail list logo
