Hi all,
how can I tie the notes in the following example?
16
<< { \once \override NoteColumn.force-hshift = #-0.6 \once \override
Stem.direction = #DOWN d2 }
\\ { \once \override NoteColumn.force-hshift = #0.6 \once \override
Stem.direction = #up ees2^\trill } >>
the ~ do not show in
Putting the d~ and ees~ inside the <<...>> block gets a bit closer. You can
see the ties, but has other differences from your original example. I'm not
sure exactly what your final goal is:
\relative c' {
<< { d16~ \once \override NoteColumn.force-hshift = #-0.6 \once \override
Stem.direction = #D
Hi Luca, hi Steve,
Luca, do you mean :
\version "2.18.2"
\transpose c c' {
%16 ~
<<
{
\once\stemDown
\once\hideNotes ees16~
\once\override NoteColumn.force-hshift = #0.6
ees2^\trill
}
\\
{
\once\stemUp
16
\once\override NoteColumn.for
My contribution of two days ago hasn't turned up on the list (yet),
so here goes again:
Here is a variant of Pierre's proposal:
\transpose c c' {
%16 ~
<<
{
\once \override NoteColumn #'ignore-collision = ##t
\once \hideNotes 16
\once \override NoteColumn.force-
Is there a better way to do this?
I am trying to end a repeated section with a tie to the first note back at
the beginning of the section. This is written as an unterminated tie. I can
get it to look right with this code, but I get an error message
"programming error: bounds of this piece a
On 2021-08-06 11:29 am, Ernie Braganza wrote:
Is there a better way to do this?
I am trying to end a repeated section with a tie to the first note back
at
the beginning of the section. This is written as an unterminated tie. I
can
get it to look right with this code, but I get an error
Thank you. I had never heard of semi-ties before. Always something new to
learn,
On Fri, Aug 6, 2021 at 3:05 PM Aaron Hill wrote:
> On 2021-08-06 11:29 am, Ernie Braganza wrote:
> > Is there a better way to do this?
> >
> > I am trying to end a repeated section with a tie t
nyone experienced
this before? or know a better way to do single note dynamics? Thanks.
r c'( a
fis'\< a, d,)
g2.~\mp
<< { g2. } \\ { s4\> s4 s4\! } >> %no tie
--
View this message in context:
http://old.nabble.com/tie-to-note-inside-double-backslashing-voicing-tp3363725
Hi,
On Fri, Apr 6, 2012 at 6:00 PM, trandrusiii wrote:
> The only way I've found to create dynamics for a single note is to use
> voicing with spacers. This worked ok for a while but now I have a note that
> is tied to the upper voice and I get an error message saying that the tie is
> not termin
score. Has anyone experienced
> this before? or know a better way to do single note dynamics? Thanks.
>
> r c'( a
> fis'\< a, d,)
> g2.~\mp
> << { g2. } \\ { s4\> s4 s4\! } >> %no tie
> --
> View this message in context:
> http://old.
t;> is tied to the upper voice and I get an error message saying that the tie
>> is
>> not terminated and nothing shows up on the score. Has anyone experienced
>> this before? or know a better way to do single note dynamics? Thanks.
>>
>> r c'( a
>> fis&#
On Sat, Apr 7, 2012 at 4:29 PM, trandrusiii wrote:
>
> Thanks for your input. I've tried both methods and I have the same problem.
> When I add a cresc. to the measure, the spacing of my entire piece gets
> completely messed up. I don't understand why Lilypond won't allow me to
> create dynamics w
u posted.
> Can you post sample code again, with an illustration of what you want
> to achieve?
>
> cheers,
> Janek
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lily
On 2012-04-06 18:00, trandrusiii wrote:
The only way I've found to create dynamics for a single note is to use
voicing with spacers. This worked ok for a while but now I have a note that
is tied to the upper voice and I get an error message saying that the tie is
not terminated and nothing shows
On Sat, Apr 7, 2012 at 11:27 PM, trandrusiii wrote:
>
> Hi. The problem I am having now is different. When I attempt to add a hairpin
> decres the spacing of my entire piece gets corrupted. I've attached a
> screencap to illustrate. I would like the spacing to remain at 31 or 32
> pages.
> http://
On Apr 9, 2012, at 8:13 AM, Janek Warchoł wrote:
> On Sat, Apr 7, 2012 at 11:27 PM, trandrusiii wrote:
>>
>> Hi. The problem I am having now is different. When I attempt to add a hairpin
>> decres the spacing of my entire piece gets corrupted. I've attached a
>> screencap to illustrate. I would
I have a piece I'm typesetting where an internal voice needs a tie, but
\tieDown isn't enough. The tie spanner needs to be at the bottom (in this
case) of the stems. Here is a snippet that illustrates the problem:
\version "2.18.2"
\new Staff {
\key bes \major
\time 5/4
<<
{
4
8[ ]
}
Does the tie need to connect the eeses? This looks good, but maybe not to your
specs.
\version "2.18.2"
\new Staff {
\key bes \major
\time 5/4
<<
{
4
8[ ]
} \\
{
\override Stem.length = #8.0
\stemDown ees'2. ees'4^~ ees'8 r8
}
>>
}
Best,
Conor Cook
On Apr 21, 2014, at 5:01 PM, Knute Snortu
Alternatively, use the override inserted below.
Best, Simon
Am 22.04.2014 00:40, schrieb Conor Cook:
Does the tie need to connect the eeses? This looks good, but maybe not to your
specs.
\version "2.18.2"
\new Staff {
\key bes \major
\time 5/4
<<
{
4
8[ ]
} \\
{
\override Stem.length = #
That's it, Simon! Thanks. And thanks for the suggestion, Conor. That did
look better.
Knute Snortum
(via Gmail)
On Mon, Apr 21, 2014 at 3:43 PM, Simon Albrecht wrote:
> Alternatively, use the override inserted below.
>
> Best, Simon
>
> Am 22.04.2014 00:40, schrieb Conor Cook:
>
> Does the
You’re welcome. But Simon’s definitely looks better :)
~Conor Cook
On Apr 21, 2014, at 7:59 PM, Knute Snortum wrote:
> That's it, Simon! Thanks. And thanks for the suggestion, Conor. That did
> look better.
>
>
> Knute Snortum
> (via Gmail)
>
>
> On Mon, Apr 21, 2014 at 3:43 PM, Simon
2014-04-22 0:43 GMT+02:00 Simon Albrecht :
>
>> On Apr 21, 2014, at 5:01 PM, Knute Snortum wrote:
>>
>>> I have a piece I'm typesetting where an internal voice needs a tie, but
>>> \tieDown isn't enough. The tie spanner needs to be at the bottom (in this
>>> case) of the stems. Here is a snippet
I can see your point. I'm trying to get the LilyPond score to look like
the original, but maybe in this case a slavish concern for exactness isn't
appropriate.
Knute Snortum
(via Gmail)
On Mon, Apr 21, 2014 at 11:10 PM, Janek Warchoł wrote:
> 2014-04-22 0:43 GMT+02:00 Simon Albrecht :
> >
> >
Greetings Ken,
I wonder if this isn't a place for \laissezVibrer
Hwaen Ch'uqi
On 7/28/22, Kenneth Wolcott wrote:
> Hi;
>
> I must be missing something obvious here.
>
> The last note of a first alternative is a tie to the first note in the
> repeat.
>
On Wed 27 Jul 2022 at 21:27:53 (-0700), Kenneth Wolcott wrote:
>
> I must be missing something obvious here.
>
> The last note of a first alternative is a tie to the first note in the
> repeat.
>
> Lilypond 2.22.2 complains:
>
> La_Bamba.ly:67:40: warning: un
ot;gotcha" list.
Ken
On Wed, Jul 27, 2022 at 9:55 PM David Wright wrote:
>
> On Wed 27 Jul 2022 at 21:27:53 (-0700), Kenneth Wolcott wrote:
> >
> > I must be missing something obvious here.
> >
> > The last note of a first alternative is a tie to the first
Kenneth Wolcott writes:
> Hi Hwaen and David;
>
> Thank you very much for your replies.
>
> It does solve the problem.
>
> I saw that command but, for some reason I did not think it applied
> to my situation.
The current naming is a drag.
"\repeatTie" and "\laissezvibrer" are a stupid com
On Thu, Jul 28, 2022 at 7:30 AM David Kastrup wrote:
>
> The current naming is a drag.
>
> "\repeatTie" and "\laissezvibrer" are a stupid combination of terms for
> the two different half ties you need to deal with in the context of
> repeats or other visual non-linearities.
>
I completely agree
Carl Sorensen writes:
> On Thu, Jul 28, 2022 at 7:30 AM David Kastrup wrote:
>
>>
>> The current naming is a drag.
>>
>> "\repeatTie" and "\laissezvibrer" are a stupid combination of terms for
>> the two different half ties you need to deal with in the context of
>> repeats or other visual non-l
> Le 28 juil. 2022 à 16:06, Carl Sorensen a écrit :
>
>
>
>
>> On Thu, Jul 28, 2022 at 7:30 AM David Kastrup wrote:
>>
>> The current naming is a drag.
>>
>> "\repeatTie" and "\laissezvibrer" are a stupid combination of terms for
>> the two different half ties you need to deal with in th
On 28/07/2022 16:25, David Kastrup wrote:
There is also \startTrillSpan/\stopTrillSpan, \startGroup/\stopGroup,
\startGraceSlur/\stopGraceSlur, \startTextSpan/\stopTextSpan,
\startMeasureCount/\stopMeasureCount,
\startMeasureSpanner/\stopMeasureSpanner . On the opposite side, there
is \endSpanne
Simon Albrecht writes:
> On 28/07/2022 16:25, David Kastrup wrote:
>> There is also \startTrillSpan/\stopTrillSpan, \startGroup/\stopGroup,
>> \startGraceSlur/\stopGraceSlur, \startTextSpan/\stopTextSpan,
>> \startMeasureCount/\stopMeasureCount,
>> \startMeasureSpanner/\stopMeasureSpanner . On t
From: David Kastrup
There is also \startTrillSpan/\stopTrillSpan, \startGroup/\stopGroup,
\startGraceSlur/\stopGraceSlur, \startTextSpan/\stopTextSpan,
\startMeasureCount/\stopMeasureCount,
\startMeasureSpanner/\stopMeasureSpanner .
So there is a clear pattern of \startItem and \endItem b
Paul Hodges writes:
> From: David Kastrup
> There is also \startTrillSpan/\stopTrillSpan, \startGroup/\stopGroup,
> \startGraceSlur/\stopGraceSlur, \startTextSpan/\stopTextSpan,
> \startMeasureCount/\stopMeasureCount,
> \startMeasureSpanner/\stopMeasureSpanner .
>
> So there is a clear pa
Hi all,
> I don't see why. They are halfties.
So why not \halftie #LEFT and \halftie #RIGHT?
(i.e., they're both halfties, so just have a direction parameter)
Just a thought.
Kieren.
Kieren MacMillan writes:
> Hi all,
>
>> I don't see why. They are halfties.
>
> So why not \halftie #LEFT and \halftie #RIGHT?
> (i.e., they're both halfties, so just have a direction parameter)
There isn't much of an incentive to ever have the halftie direction
computed in any manner, so givin
Hi David,
> There isn't much of an incentive to ever have the halftie direction
> computed in any manner, so giving the user interface to them another
> hoop does not seem to give any return to the user.
Fair point… I guess I was thinking it might be easier/clearer for
documentation, since peopl
On 2022-07-28 6:29 am, David Kastrup wrote:
\laissezvibrer might be an alias,
though I am not sure whether it would not, in that function, be
deserving of some tweaks giving it a longer minimal visual length.
Isn't it also conventional to annotate it "l.v."?
If we had a more general semi-tie c
rsion of the NR has the index entries
tie, from nothing
tie, to nothing
It is straightforward to add more entries to the index, but which one?
Werner
39 matches
Mail list logo
