On 10/28/2017 5:38 PM, Mason Hock wrote:
Lilypond by default seems to place all tuplet numbers/brackets so that
they collide with the staff, with the exception of triplets, which it
places outside the staff. I would like all tuplets outside of the
staff like triplets.
/\override
Lilypond by default seems to place all tuplet numbers/brackets so that
they collide with the staff, with the exception of triplets, which it
places outside the staff. I would like all tuplets outside of the staff
like triplets.
\override Staff.TupletNumber #'outside-staff-priority = #1
fixes
On 10/28/2017 10:30 AM, David Kastrup wrote:
Ben writes:
Thank you so much for sharing this function. It will come in handy for
a project I'll be working on shortly.
However, I had one question for you.
I just went to try to use the function 'as is' and I'm seeing
Ben writes:
> Thank you so much for sharing this function. It will come in handy for
> a project I'll be working on shortly.
> However, I had one question for you.
> I just went to try to use the function 'as is' and I'm seeing an
> error. I cannot use the function at
On 10/28/2017 1:43 AM, Andrew Bernard wrote:
Hi James,
This comes up so frequently it puzzles me why it is not considered for
addition to the lilypond baseline.
Here's my function.
Andrew
=== snip
\version "2.19.39"
% Annotation bracket with centred text.
% Andrew Bernard and Thomas Morley
Hi,
On Sat, Oct 28, 2017 at 2:23 AM, James Harkins wrote:
> On Sat, 28 Oct 2017 13:55:49 +0800 Nathan Ho wrote
>
>> On 2017-10-27 21:37, James Harkins wrote:
>> > I couldn't find this quickly: for an unmetered section, I'd like to
>> >
On 10/27/2017 1:33 PM, David Sumbler wrote:
In the above rather silly example, the beam between the 2 cross-staff
notes slopes slightly upwards. If I add a dynamic, say \f , after 2. in line 7, the staves are forced further apart, and the beam
slopes slightly downwards.
If I now add a
Hi Kieren,
thanks a lot!
> but I suppose I do slam out a lot of scores fairly quickly, and I have pretty
> high aesthetic standards.
I like very much what Lilypond offers by default. And I have my own
styles and tweaks to get what I consider more beautiful. But your scores
look so much better!
Am 28.10.2017 um 10:01 schrieb David Kastrup:
James Harkins writes:
That other question...
I would like to notate some clusters, but articulated: blocks instead
of notes, but showing repeated, re-articulated blocks.
\makeClusters doesn't do it. Even if I put a "s"kip
James Harkins writes:
> That other question...
>
> I would like to notate some clusters, but articulated: blocks instead
> of notes, but showing repeated, re-articulated blocks.
>
> \makeClusters doesn't do it. Even if I put a "s"kip in between, it
> still connects them into
That other question...
I would like to notate some clusters, but articulated: blocks instead of notes,
but showing repeated, re-articulated blocks.
\makeClusters doesn't do it. Even if I put a "s"kip in between, it still
connects them into one massive gesture. Plus, I need rhythmic notation.
On Sat, 28 Oct 2017 13:55:49 +0800 Nathan Ho wrote
> On 2017-10-27 21:37, James Harkins wrote:
> > I couldn't find this quickly: for an unmetered section, I'd like to
> > indicate duration by tuplet-style brackets, only not a tuplet (no
> > change to note
Hi James,
This comes up so frequently it puzzles me why it is not considered for
addition to the lilypond baseline.
Here's my function.
Andrew
=== snip
\version "2.19.39"
% Annotation bracket with centred text.
% Andrew Bernard and Thomas Morley
TextSpannerCentredText =
HI Nathan,
Indeed yes. This is clever, and short, but it is a hack, no disrespect
intended. As you say, it hijacks the tuplet concept and introduces tuplet
semantics where there are none. Whether this bothers people or not is
entirely up to them, but I prefer my solution as it keeps the semantics
14 matches
Mail list logo