Carl Sorensen writes:
> On 9/25/16, 2:46 PM, "Simon Albrecht" wrote:
>
>>On 25.09.2016 22:06, Trevor Daniels wrote:
>>> When needed, isn't this adequate?
>>>
>>> \version "2.19.48"
>>> triplet = \tuplet 3/2 \etc
>>> \triplet { a'4 a' a' }
>>
>>That¹s what I meant by Œimplementation is a no-brain
So much thanks!
If it is some help, the exact Y-offset value is 1.25.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Fret-diagram-in-tablature-tp194865p194942.html
Sent from the User mailing list archive at Nabble.com.
___
li
Hi Urs,
Thanks for the link/help. Tried to implement this, but there were a couple of
problems (that I have no time to hunt down), so I backed it out. (This is
definitely the right direction, though, as opposed to the baling-wire fix [due
to Harm] that I’m using now…)
Hopefully one day, we can
Harm (et al.),
Right after hitting “Send”, I realized the fix: ye olde empty chord!
The version below seems to work fine in both MWE and — at least, on first
glance — in my RWS (real-world score).
Thanks!
Kieren.
%%% SNIPPET BEGINS
\version "2.19.48"
terminateHairpin =
#(define-music-function
Hi Harm,
> below a very bad workaround, found deep, deep in the quick n' dirty junk room.
Thanks for the attempt!
Works great on this MWE…
But in my real-world score, Lily’s long-standing \grace-timing “feature” (read:
bug) comes crashing down. =(
The hint/idea is possibly a good one, suffici
On 9/25/16, 2:46 PM, "Simon Albrecht" wrote:
>On 25.09.2016 22:06, Trevor Daniels wrote:
>> When needed, isn't this adequate?
>>
>> \version "2.19.48"
>> triplet = \tuplet 3/2 \etc
>> \triplet { a'4 a' a' }
>
>That¹s what I meant by Œimplementation is a no-brainer¹ :-)
>Best, Simon
I¹m general
\crossStaff is intended for chords with notes in two staves that are
connected by one *stem*.
What you want is the \change command:
http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-keyboards#changing-staff-manually
HTH
Urs
Am 26.09.2016 um 00:11 schrieb Ryan Michael:
>
I have an upper and lower part of a piano staff.
In the upper staff I have the following phrase which I would like the last
note, a Gb in the second octave of the instrument be engraved on the bass
clef of the second staff. Currently it is just placed below the treble with
ledger lines:
\
2016-09-25 19:16 GMT+02:00 Kieren MacMillan :
> Hi all,
>
> Apologies for the rapid repost/crosspost, but this feature/bug is keeping me
> from being able to put together a full score for a commission which is due
> ASAP. Does anyone have a viable** workaround for the issue demonstrated by
> the
On 25.09.2016 20:51, Noeck wrote:
after = ...
When will this handy function be part of lilypond?
I mean, are there objections? Would there be more to do than putting it
in the appropriate ly or scm file
music-functions-init.ly – that’s for sure.
and document it?
My gut feeling from this li
On 25.09.2016 22:06, Trevor Daniels wrote:
When needed, isn't this adequate?
\version "2.19.48"
triplet = \tuplet 3/2 \etc
\triplet { a'4 a' a' }
That’s what I meant by ‘implementation is a no-brainer’ :-)
Best, Simon
___
lilypond-user mailing list
Hi Paul,
Pretty interesting.
Cheers,
Pierre
2016-09-25 20:24 GMT+02:00 Paul :
> Hi all,
>
> I discovered some useful LilyPond hooks: "toplevel-music-handler" and
> friends.
>
> Often I will create a version of a piece that shows it on two types of
> staff, as simultaneous music. For example, the
Urs Liska wrote Sunday, September 25, 2016 8:51 PM
>
> Am 25. September 2016 19:41:33 MESZ, schrieb Simon Albrecht
> :
>>On 25.09.2016 19:29, Simon Albrecht wrote:
>>>
>>> is it just me or does \tuplet get 3/2 as first argument >90% of the
>>time?
>>> And, assuming that it’s not just me, should
Simon Albrecht writes:
> On 25.09.2016 19:29, Simon Albrecht wrote:
>> Hello everybody,
>>
>> is it just me or does \tuplet get 3/2 as first argument >90% of the time?
>> And, assuming that it’s not just me, should we introduce an extra
>> command \triplet to save typing & clutter, especially whe
Urs Liska writes:
> Am 25. September 2016 19:41:33 MESZ, schrieb Simon Albrecht
> :
>>On 25.09.2016 19:29, Simon Albrecht wrote:
>>> Hello everybody,
>>>
>>> is it just me or does \tuplet get 3/2 as first argument >90% of the
>>time?
>>> And, assuming that it’s not just me, should we introduce an
Hi Kieren,
no time to really look into it. But in
https://git.openlilylib.org/bfsc/das-trunkne-lied/tree/master/library/ly/to-lilylib
are two "remove-" files that deal with this issue IIRC. Maybe they're if help.
Urs
Am 25. September 2016 19:16:42 MESZ, schrieb Kieren MacMillan
:
>Hi all,
>
Am 25. September 2016 19:41:33 MESZ, schrieb Simon Albrecht
:
>On 25.09.2016 19:29, Simon Albrecht wrote:
>> Hello everybody,
>>
>> is it just me or does \tuplet get 3/2 as first argument >90% of the
>time?
>> And, assuming that it’s not just me, should we introduce an extra
>> command \triplet
>>> https://bugs.freedesktop.org/show_bug.cgi?id=97546
>>>
>>> The proposed fix hasn't been applied yet to the fontconfig git
>>> repository – maybe we should downgrade GUB's fontconfig version to
>>> 2.12.0 until this is fixed.
>>
>> I think that there is another possible solution. To use the
>> Even better, you can place it at the exact (or approximate) time when
>> the bow change should happen, using a music function. ...
>> % Thanks to David Kastrup for the inspiration!
>> after = ...
When will this handy function be part of lilypond?
I mean, are there objections? Would there be mo
Hello Simon,
Thanks!
JM
> Le 25 sept. 2016 à 18:52, Simon Albrecht a écrit :
>
> On 25.09.2016 18:38, Menu Jacques wrote:
>> Hello folks,
>>
>> The NR as of 2.19 is not restrictive regarding where a command such as:
>>
>> #(set-global-staff-size 26)
>>
>> can be placed, but I remember
Hi all,
I discovered some useful LilyPond hooks: "toplevel-music-handler" and
friends.
Often I will create a version of a piece that shows it on two types of
staff, as simultaneous music. For example, the same music on a regular
Staff and a TabStaff. That's easy enough to do by putting the
On 25.09.2016 19:29, Simon Albrecht wrote:
Hello everybody,
is it just me or does \tuplet get 3/2 as first argument >90% of the time?
And, assuming that it’s not just me, should we introduce an extra
command \triplet to save typing & clutter, especially where triple and
duple segments constant
Hello everybody,
is it just me or does \tuplet get 3/2 as first argument >90% of the time?
And, assuming that it’s not just me, should we introduce an extra
command \triplet to save typing & clutter, especially where triple and
duple segments constantly alternate?
Best, Simon
__
Hi all,
Apologies for the rapid repost/crosspost, but this feature/bug is keeping me
from being able to put together a full score for a commission which is due
ASAP. Does anyone have a viable** workaround for the issue demonstrated by the
snippet, below?
Thanks,
Kieren.
** n.b. For me, “viabl
On 25.09.2016 18:38, Menu Jacques wrote:
Hello folks,
The NR as of 2.19 is not restrictive regarding where a command such as:
#(set-global-staff-size 26)
can be placed, but I remember someone on this list saying that it should be
before the \paper block.
What is the exact recommendat
Hello folks,
The NR as of 2.19 is not restrictive regarding where a command such as:
#(set-global-staff-size 26)
can be placed, but I remember someone on this list saying that it should be
before the \paper block.
What is the exact recommendation/limitation?
Thanks for the help!
JM
Sorry, just saw that I accidentally attached your original file. Now
again with the modified version…
On 25.09.2016 14:24, Simon Albrecht wrote:
On 25.09.2016 13:34, B~M wrote:
Dear All, I would like to add an up bow symbol to the
middle of a tie between two notes. The file seg.pdf is a snipp
Hello Simon,
Thanks for the clarification!
JM
> Le 23 sept. 2016 à 23:51, Simon Albrecht a écrit :
>
> On 23.09.2016 17:43, Menu Jacques wrote:
>> Hello folks,
>>
>> musicxml2ly as delivered with LP 2.19.35 produces score specifications such
>> as:
>>
>> % The score definition
>> \score {
>
On 25.09.2016 13:34, B~M wrote:
Dear All, I would like to add an up bow symbol to the
middle of a tie between two notes. The file seg.pdf is a snippet
of the problem. In the second tie I would like to place a V to denote
up bow. However, the up bow and down bow symbols are attached
to notes in th
Pierre you are a genius !!
Thanks so much, this will be very helpful and I doubt I would have figured
such a solution out.
Kind regards Paul
On Sun, Sep 25, 2016 at 10:12 PM, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> wrote:
> Hi Paul,
>
> How about :
>
> %%
> \version "2.14.
Or even:
\version "2.14.2"
DB = \downbow
UB = \upbow
DUB = -\tweak #'outside-staff-priority #0
-\markup {
\hspace #.7
\musicglyph #"scripts.downbow"
\hspace#2.6 %% <= set space
\musicglyph #"scripts.upbow"
}
UDB = -\tweak #'outside-staff-priority #0
Hi Paul,
How about :
%%
\version "2.14.2"
DB = \downbow
UB = \upbow
DUB = -\tweak #'outside-staff-priority #0
-\markup {
\musicglyph #"scripts.downbow"
\hspace#3 %% <= set space
\musicglyph #"scripts.upbow"
}
UDB = -\tweak #'outside-staff-priority #0
Dear All, I would like to add an up bow symbol to the
middle of a tie between two notes. The file seg.pdf is a snippet
of the problem. In the second tie I would like to place a V to denote
up bow. However, the up bow and down bow symbols are attached
to notes in the lilypond file.
Is there some way
On 25.09.2016 09:03, Knut Petersen wrote:
Am 19.09.2016 um 19:01 schrieb Phil Holmes:
Generally, songs with lyrics are set with a ChoirStaff rather than a
StaffGroup. These do not have barlines spanning the space between
the staves, and so the problem does not occur.
IMHO: The LyricHyphen c
Am 19.09.2016 um 19:01 schrieb Phil Holmes:
Generally, songs with lyrics are set with a ChoirStaff rather than a
StaffGroup. These do not have barlines spanning the space between the staves,
and so the problem does not occur.
IMHO: The LyricHyphen code in lilypond is able to handle only the
35 matches
Mail list logo
