unterminated tie

[Mark Stephen Mrotek]

Hello:

 

I cannot find the "unterminated tie" in the following measures.

 

r4 q2 | r4 <f~ aes~ ces~>2 | q2. |

r4 <f'~ aes~ ces~>2 | r4 <f~ aes~ ces~>2 | % this line highlighted.

<f~ aes~ ces>2. ( | ) |

 

When compiled the notation is correct.

 

Any help from sharper eyes is greatly appreciated.

 

Thank you!

 

Mark

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie

[Malte Meyn]

Am 15.01.2016 um 20:49 schrieb Mark Stephen Mrotek:
> r4 q2 | r4 2 | q2. |
> 
> r4 2 | r4 2 | % this line highlighted.
> 
> 2. ( | ) |

Please give a complete example; I see two possible reasons (maybe there
are more) but can’t tell more from this incomplete code.

1. You are in absolute mode (instead of relative) => two different notes
f' and f cannot be tied.
2. You didn’t set tieWaitForNote to ##t => ties cannot cross rests by
default.

Btw, you can tie chords with just one single tilde:

~ 

This will tie the fs and aess but not the ces and bes.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie

[Nathan Ho]

On 2016-01-15 11:49, Mark Stephen Mrotek wrote:

Hello:

I cannot find the "unterminated tie" in the following measures.

 r4 q2 | r4 <f~ aes~ ces~>2 | q2. |

 r4 <f'~ aes~ ces~>2 | r4 <f~ aes~ ces~>2 | % this line highlighted.


Hi Mark,

Check your octaves on the f. If you're in relative mode, the second f on 
this line ends up an octave higher. If you're in absolute mode, f is of 
course an octave lower than f'.



Nathan

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: unterminated tie

[Mark Stephen Mrotek]

Nathan,

Thank you for your reply and the observation. I did not mention that the
second f is after a clef change - bass to treble - so the ' is necessary.

Since it compiles correctly, perhaps it is just a "glitch" in the program.

Mark

-Original Message-
From: Nathan Ho [mailto:nat...@snappizz.com] 
Sent: Friday, January 15, 2016 11:53 AM
To: Mark Stephen Mrotek <carsonm...@ca.rr.com>
Cc: 'Lilypond-User Mailing List' <lilypond-user@gnu.org>;
lilypond-user-bounces+nathan=snappizz@gnu.org
Subject: Re: unterminated tie

On 2016-01-15 11:49, Mark Stephen Mrotek wrote:
> Hello:
> 
> I cannot find the "unterminated tie" in the following measures.
> 
>  r4 q2 | r4 <f~ aes~ ces~>2 | q2. |
> 
>  r4 <f'~ aes~ ces~>2 | r4 <f~ aes~ ces~>2 | % this line highlighted.

Hi Mark,

Check your octaves on the f. If you're in relative mode, the second f on
this line ends up an octave higher. If you're in absolute mode, f is of
course an octave lower than f'.


Nathan


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: unterminated tie

[Nathan Ho]

On 2016-01-15 12:26, Mark Stephen Mrotek wrote:

Nathan,

Thank you for your reply and the observation. I did not mention that 
the
second f is after a clef change - bass to treble - so the ' is 
necessary.


Since it compiles correctly, perhaps it is just a "glitch" in the 
program.




Hi Mark,

Clef changes do not affect pitch; they only change the way pitches are 
displayed. Are you trying to engrave a cross-clef tie? If so, this 
snippet might help you: http://lsr.di.unimi.it/LSR/Item?id=326


But I can only grasp at straws here. As Malte pointed out, your example 
isn't complete.



Nathan

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: unterminated tie

[Mark Stephen Mrotek]

Nathan and others,

Thank you for the suggestions. I found the error - a tie over a rest.

Mark

-Original Message-
From: Nathan Ho [mailto:nat...@snappizz.com] 
Sent: Friday, January 15, 2016 1:04 PM
To: Mark Stephen Mrotek <carsonm...@ca.rr.com>
Cc: 'Lilypond-User Mailing List' <lilypond-user@gnu.org>;
lilypond-user-bounces+nathan=snappizz@gnu.org
Subject: RE: unterminated tie

On 2016-01-15 12:26, Mark Stephen Mrotek wrote:
> Nathan,
> 
> Thank you for your reply and the observation. I did not mention that 
> the second f is after a clef change - bass to treble - so the ' is 
> necessary.
> 
> Since it compiles correctly, perhaps it is just a "glitch" in the 
> program.
> 

Hi Mark,

Clef changes do not affect pitch; they only change the way pitches are
displayed. Are you trying to engrave a cross-clef tie? If so, this snippet
might help you: http://lsr.di.unimi.it/LSR/Item?id=326

But I can only grasp at straws here. As Malte pointed out, your example
isn't complete.


Nathan


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Unterminated tie

[David Sumbler]

On Sun, 2015-09-13 at 00:46 +0200, Thomas Morley wrote:
> 2015-09-13 0:11 GMT+02:00 David Sumbler <da...@aeolia.co.uk>:
> > I have yet another problem related to repeats.  The piece I am setting
> > has one instrument which is tied from the last note in the
> > first-time-bar to the note at the start of the repeat.  (Moving the
> > repeats does not help, because there are a lot of overlapping ties.)
> >
> > I tried to produce an unterminated tie in the last bar of the first
> > alternative by having a second, invisible voice with two tied notes in
> > the bar:
> >
> > \version "2.19.24"
> >
> > { g'1 ~|
> >   \repeat volta 2 { g'1 | d'1 | }
> >   \alternative {
> >   {
> >   << { g'1 } \\ { \override Dots.stencil = ##f
> >   \override Stem.stencil = ##f
> >   \override Flag.stencil = ##f
> >   g'2... ~ g'16
> >   \revert Flag.stencil
> >   \revert Stem.stencil
> >   \revert Dots.stencil
> >   } >> |
> >   } {
> >   a'1 |
> >   } }
> >   g'1 |
> > }
> >
> > So far, so good, but the note heads in the bar are still there of
> > course.  But when I add "\override NoteHead.stencil = ##f" the compiler
> > gives up with the message:
> >
> > Drawing systems...lilypond:
> > /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/skyline.cc:119:
> > void Building::precompute(Real, Real, Real, Real): Assertion `!isinf
> > (slope_) && !isnan (slope_)' failed.
> >
> > Why does this happen?  And is there perhaps a simpler way of producing
> > my unterminated tie?
> 
> If you set NoteHead.stencil #f, then the Tie has nothing to attach to.
> Use point-stencil instead.
> Scaling durations will save much code:
> 
> \version "2.19.24"
> 
> {
>   g'1 ~|
>   \repeat volta 2 { g'1 | d'1 | }
>   \alternative {
>   {
> g'1*15/16~
> \once \override Stem.stencil = #point-stencil
> \once \override Flag.stencil = #point-stencil
> \once \override NoteHead.stencil = #point-stencil
> \once \override Tie.minimum-length = 10
> g'16
>   }
>   { a'1 | }
>   }
>   g'1 |
> }
> 
> 
> Other possibility would be to use \repeatTie and use \shape on it.
> I doubt it would be the better one ...
> 
> Cheers,
>   Harm

That's brilliant - thank you so much.

I wasn't aware of point-stencil (or had forgotten about it).

The scaling of durations is a neat trick too - I hadn't thought of it.

I find that the override of the tie-length is unnecessary.

David


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Unterminated tie

[David Sumbler]

I have yet another problem related to repeats.  The piece I am setting
has one instrument which is tied from the last note in the
first-time-bar to the note at the start of the repeat.  (Moving the
repeats does not help, because there are a lot of overlapping ties.)

I tried to produce an unterminated tie in the last bar of the first
alternative by having a second, invisible voice with two tied notes in
the bar:

\version "2.19.24"

{ g'1 ~|
  \repeat volta 2 { g'1 | d'1 | }
  \alternative {
  {
  << { g'1 } \\ { \override Dots.stencil = ##f
  \override Stem.stencil = ##f
  \override Flag.stencil = ##f
  g'2... ~ g'16
  \revert Flag.stencil
  \revert Stem.stencil
  \revert Dots.stencil
  } >> |
  } {
  a'1 |
  } }
  g'1 |
}

So far, so good, but the note heads in the bar are still there of
course.  But when I add "\override NoteHead.stencil = ##f" the compiler
gives up with the message:

Drawing systems...lilypond:
/home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/skyline.cc:119:
void Building::precompute(Real, Real, Real, Real): Assertion `!isinf
(slope_) && !isnan (slope_)' failed.

Why does this happen?  And is there perhaps a simpler way of producing
my unterminated tie?


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Unterminated tie

[Thomas Morley]

2015-09-13 0:11 GMT+02:00 David Sumbler <da...@aeolia.co.uk>:
> I have yet another problem related to repeats.  The piece I am setting
> has one instrument which is tied from the last note in the
> first-time-bar to the note at the start of the repeat.  (Moving the
> repeats does not help, because there are a lot of overlapping ties.)
>
> I tried to produce an unterminated tie in the last bar of the first
> alternative by having a second, invisible voice with two tied notes in
> the bar:
>
> \version "2.19.24"
>
> { g'1 ~|
>   \repeat volta 2 { g'1 | d'1 | }
>   \alternative {
>   {
>   << { g'1 } \\ { \override Dots.stencil = ##f
>   \override Stem.stencil = ##f
>   \override Flag.stencil = ##f
>   g'2... ~ g'16
>   \revert Flag.stencil
>   \revert Stem.stencil
>   \revert Dots.stencil
>   } >> |
>   } {
>   a'1 |
>   } }
>   g'1 |
> }
>
> So far, so good, but the note heads in the bar are still there of
> course.  But when I add "\override NoteHead.stencil = ##f" the compiler
> gives up with the message:
>
> Drawing systems...lilypond:
> /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/skyline.cc:119:
> void Building::precompute(Real, Real, Real, Real): Assertion `!isinf
> (slope_) && !isnan (slope_)' failed.
>
> Why does this happen?  And is there perhaps a simpler way of producing
> my unterminated tie?

If you set NoteHead.stencil #f, then the Tie has nothing to attach to.
Use point-stencil instead.
Scaling durations will save much code:

\version "2.19.24"

{
  g'1 ~|
  \repeat volta 2 { g'1 | d'1 | }
  \alternative {
  {
g'1*15/16~
\once \override Stem.stencil = #point-stencil
\once \override Flag.stencil = #point-stencil
\once \override NoteHead.stencil = #point-stencil
\once \override Tie.minimum-length = 10
g'16
  }
  { a'1 | }
  }
  g'1 |
}


Other possibility would be to use \repeatTie and use \shape on it.
I doubt it would be the better one ...

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

warning of unterminated tie

[Jinsong Zhao]

Hi there,

The LilyPond can't determinate the tie in the following snippet. Why? 
and how to get a tie between the bes and bes2? Thanks!


\version 2.19.15
\relative c'' {
  \clef treble
  \key ees \major
 g'4 f8 ees ees4 g,8 bes ~ |%m70
   { bes2 g4 g8 bes } \\ {  g ees 4  f d  ees2 } 
}

Best regards,
Jinsong

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: warning of unterminated tie

[Thomas Morley]

2014-12-29 19:27 GMT+01:00 Jinsong Zhao jsz...@yeah.net:
 Hi there,

 The LilyPond can't determinate the tie in the following snippet. Why? and
 how to get a tie between the bes and bes2? Thanks!

 \version 2.19.15
 \relative c'' {
   \clef treble
   \key ees \major
  g'4 f8 ees ees4 g,8 bes ~ |%m70
{ bes2 g4 g8 bes } \\ {  g ees 4  f d  ees2 } 
 }

 Best regards,
 Jinsong



Try:

\relative c'' {
  \clef treble
  \key ees \major
  g'4 f8 ees ees4 g,8 \once \tieUp bes~ |%m70
  
{ \voiceOne  bes2 g4 g8 bes }
\new Voice { \voiceTwo  g ees 4  f d  ees2 }
  
}

The  \\  returns far to often problems. I use it only for most
simple and short things.

HTH,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: warning of unterminated tie

[Jinsong Zhao]

On 2014/12/29 10:35, Thomas Morley wrote:

snip

Try:

\relative c'' {
   \clef treble
   \key ees \major
   g'4 f8 ees ees4 g,8 \once \tieUp bes~ |%m70
   
 { \voiceOne  bes2 g4 g8 bes }
 \new Voice { \voiceTwo  g ees 4  f d  ees2 }
   
}

The  \\  returns far to often problems. I use it only for most
simple and short things.

HTH,
   Harm


Thank you very much. It works.

Best regards,
Jinsong

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie?

[Marc Weber]

Thanks for your fast help.
I don't quite understand why its important to disambuigate.

One of the following would have helped me:
- nicer error message
- hint in documentation such as ties only connect notes of same pitch

Marc Weber

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie?

[Pierre Perol-Schneider]

Hi Mark,

2014-06-20 8:27 GMT+02:00 Marc Weber marco-owe...@gmx.de:

 Thanks for your fast help.
 I don't quite understand why its important to disambuigate.

 One of the following would have helped me:
 - nicer error message
 - hint in documentation such as ties only connect notes of same pitch


Another trick to help you : carefully read and understand the tuto manual
(not very long):
http://lilypond.org/doc/v2.18/Documentation/learning/ties-and-slurs

Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie?

[Thomas Morley]

2014-06-20 8:27 GMT+02:00 Marc Weber marco-owe...@gmx.de:
 Thanks for your fast help.
 I don't quite understand why its important to disambuigate.


As a musician I know different curves with different meanings.
LilyPond mirrors this with the possibility to write Ties, Slurs and
PhrasingSlurs. The printed output for a single curve of each kind is
(very) slightly different.
The broadest diffference can be watched typesetting some chords with
Ties as opposed to using the same chords with Slurs.

Look at the output from:

\relative c'' { c e g1~ q ~q }
\relative c'' { c e g1( q q) }

Every note of each chord _needs_ a Tie to the corresponding note of
the next chord.
Though it does not make sense to print more than _one_ Slur (as long
as the chord is in one voice).

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie?

[David Kastrup]

Marc Weber marco-owe...@gmx.de writes:

 Thanks for your fast help.
 I don't quite understand why its important to disambuigate.

A tie is basic notation, meaning that there is only a single note and a
single attack.

A slur is not a notational element but rather an instruction for
execution.  As an example, if I write

{ c8 d8( e4) c2 | c8 d8( d4) c2 }

for a single-manual instrument (like piano or accordion), the intent is
to play the second phrase with comparable articulation to the first
phrase.  Usually you will try to use the same fingering, consequently
doing a finger switch on the d4.

In contrast, with

{ c8 d8( e4) c2 | c8 d8~ d4 c2 }

the second measure basically has a d4. in the middle.

That's quite an important distinction.  Since the tie is a notational
instrument for indicating a single note, it does not make sense to write
it for connecting different pitches (the special case of a single note
ending at a different pitch than it started from is called glissando
and notated differently).

 One of the following would have helped me:
 - nicer error message
 - hint in documentation such as ties only connect notes of same pitch

The learning manual directly references the glossary which states

1.311 tie
=

ES: ligadura de unión (o de prolongación), I: legatura (di valore), F:
liaison (de tenue), D: Haltebogen, Bindebogen, NL: overbinding,
bindingsboog, DK: bindebue, S: bindebåge, överbindning, FI: sitominen.

   A curved line, identical in appearance with the *note slur::, which
connects two succesive notes of the same pitch, and which has the
function of uniting them into a single sound (tone) equal to the
combined durations.


Ties and slurs are followed by a section

Warnings: slurs vs. ties


Music Glossary: *note (music-glossary)articulation::, *note
(music-glossary)slur::, *note (music-glossary)tie::.

   A slur looks like a tie, but it has a different meaning.  A tie
simply makes the first note longer, and can only be used on pairs of
notes with the same pitch.  Slurs indicate the articulation of notes,
and can be used on larger groups of notes.  Slurs and ties can be
nested.

 c4~( c8 d~ 4 e)
[image src=lilypond/47/lily-e3ec48f4.png alt=[image of music] text=image 
of music]


So let's look at the notational manual now.  It starts with

Ties


A tie connects two adjacent note heads of the same pitch.  The tie in
effect extends the duration of a note.

  Note: Ties should not be confused with _slurs_, which indicate
  articulation, or _phrasing slurs_, which indicate musical
  phrasing.  A tie is just a way of extending a note duration,
  similar to the augmentation dot.


So how do you suggest improving this, and where?

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie?

[Marc Weber]

Excerpts from Pierre Perol-Schneider's message of Fri Jun 20 07:01:58 + 
2014:
 [..] carefully read and understand [..] manual
Eventually the error message could still be changed from:
unterminated tie to unterminated tie, note/chord of same pitch expected

I agree I had a RTFM problem. Thanks for helping.

Is it correct to say that every tie is also a slur? Maybe I only
expected slurs to exist for that reason.

Marc Weber

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie?

[Urs Liska]

Am 20.06.2014 11:04, schrieb Marc Weber:

Excerpts from Pierre Perol-Schneider's message of Fri Jun 20 07:01:58 + 
2014:

[..] carefully read and understand [..] manual

Eventually the error message could still be changed from:
unterminated tie to unterminated tie, note/chord of same pitch expected

I agree I had a RTFM problem. Thanks for helping.

Is it correct to say that every tie is also a slur? Maybe I only
expected slurs to exist for that reason.


Not really. A tie is a tie and a slur is a slur.
They are only engraved with a very similar (or sometimes identical) shape.

Urs



Marc Weber

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user




--
Urs Liska
www.openlilylib.org

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie?

[Urs Liska]

Am 20.06.2014 10:00, schrieb David Kastrup:

it does not make sense to write
it for connecting different pitches (the special case of a single note
ending at a different pitch than it started from is called glissando
and notated differently).


There is another special case which isn't handled appropriately by 
LilyPond yet: a tied note followed by the same note in another clef, 
another staff (in piano notation) or enharmonically exchanged. All three 
are rather rare cases but valid notation.
To achieve that I have to use a slur, which is semantically incorrect 
(and would produce wrong MIDI if I'd use that).


Urs

--
Urs Liska
www.openlilylib.org

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie?

[Marc Weber]

Excerpts from David Kastrup's message of Fri Jun 20 08:00:47 + 2014:
 So how do you suggest improving this, and where?
http://lilypond.org/doc/v2.18/Documentation/learning/ties-and-slurs
I'd add this information here, too:
A tie connects two notes (or chords) having the same pitch.
It's created by putting a ~ in between.

Eventually adding c e g ~ e g b case to illustrate that this is also
allowed.

Another hint about how to recognize the difference: 
Ties usually touch the note heads wheras slurs don't)

I still don't understand how a violin or brass player would play 
c~c any different from c(c). (glossary says same stroke/breath).

So I'm still interested in understanding whether a tie exists for any
instrument which is not played like a slur.

I agree that the problem was me.

Marc Weber

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie?

[Urs Liska]

Am 20.06.2014 11:19, schrieb Marc Weber:

I still don't understand how a violin or brass player would play
c~c any different from c(c). (glossary says same stroke/breath).


c4~ c is _exactly the same as c2, the tie is usually used to clarify 
something (meter, voicing ...).


c4( c) will probably not be used that way (because there practically is 
no way to differentiate visually).

Slurs are used like that for example:

c4( c c c)
or
c4-.( c-.)

The second one is clearly an articulation, while the first one _could_ 
(depending on the personal style of the composer) be interpreted as four 
notes on one bow, with some stress at the following notes.


HTH
Urs

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie?

[David Kastrup]

Marc Weber marco-owe...@gmx.de writes:

 Excerpts from David Kastrup's message of Fri Jun 20 08:00:47 + 2014:
 So how do you suggest improving this, and where?
 http://lilypond.org/doc/v2.18/Documentation/learning/ties-and-slurs
 I'd add this information here, too:
 A tie connects two notes (or chords) having the same pitch.
 It's created by putting a ~ in between.

 Eventually adding c e g ~ e g b case to illustrate that this is also
 allowed.

 Another hint about how to recognize the difference: 
 Ties usually touch the note heads wheras slurs don't)

 I still don't understand how a violin or brass player would play 
 c~c any different from c(c). (glossary says same stroke/breath).

With a violin player, simple enough: c(c) is often executed by playing
the same note but on a different string.

Take a look at the Ciaconne in the violin solo partita 2 from Bach.  The
last page of it has a number of these bowings IIRC.  There are also a
number of three or four string arpeggios in there that end up, in the
course of the modulation/progression, with several identical notes on
different strings right after another on a single bow.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

unterminated tie?

[Marc Weber]

.ly file:

\version 2.18.2

\context Voice = train_left_medium {
  \relative c' { g4~ b }
}



|| Processing `sheet.ly'
|| Parsing...
|| Interpreting music...
sheet.ly|4 col 28| warning: unterminated tie
||   \relative c' { g4
||~ b }
|| Preprocessing graphical objects...
|| Finding the ideal number of pages...
|| Fitting music on 1 page...
|| Drawing systems...
|| Layout output to `sheet.ps'...
|| Converting to `./sheet.pdf'...
|| Success: compilation successfully completed


lilypond 2.16.2 shows the same result so it must be me missunderstanding
something?

http://www.lilypond.org/doc/v2.16/Documentation/learning/ties-and-slurs
clearly says: A tie is created by appending a tilde ~ to the first note being 
tied.

Thanks for any help

Marc Weber

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie?

[Thomas Morley]

2014-06-20 0:01 GMT+02:00 Marc Weber marco-owe...@gmx.de:
 .ly file:

 \version 2.18.2
 
 \context Voice = train_left_medium {
   \relative c' { g4~ b }
 }


 Hi Marc,

a Tie (Haltebogen) can only appear between Note of some height.
You likely want a Slur (Legatobogen) here:

\relative c' { g4( b) }

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unterminated tie?

[Colin Campbell]

On 14-06-19 04:01 PM, Marc Weber wrote:

.ly file:

\version 2.18.2

\context Voice = train_left_medium {
   \relative c' { g4~ b }
}

|| Processing `sheet.ly'
|| Parsing...
|| Interpreting music...
sheet.ly|4 col 28| warning: unterminated tie
||   \relative c' { g4
||~ b }
|| Preprocessing graphical objects...
|| Finding the ideal number of pages...
|| Fitting music on 1 page...
|| Drawing systems...
|| Layout output to `sheet.ps'...
|| Converting to `./sheet.pdf'...
|| Success: compilation successfully completed


lilypond 2.16.2 shows the same result so it must be me missunderstanding
something?

http://www.lilypond.org/doc/v2.16/Documentation/learning/ties-and-slurs
clearly says: A tie is created by appending a tilde ~ to the first note being 
tied.





I think you want a slur, between *different* pitches, rather than a tie 
between like ones. Your notes then become


{ g4 ( b ) }

Cheers,
Colin

--
I've learned that you shouldn't go through life with a catcher's mitt on both 
hands.
You need to be able to throw something back.
-Maya Angelou, poet (1928- )


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Unterminated tie with tuplets

[Jimmie Felidae]

Hello List,

I got a warning of unterminated tie. The warning message is:

```
/tmp/frescobaldi-k7Gcla/tmpqo6ujA/document.ly:3:2: warning: unterminated tie
  c''2.~  \times 2/3 {a'4 g'8~} | g'2 r2|
```

Related tiny example:

```
\version 2.14.0
{
  c''2.~  \times 2/3 {a'4 g'8~} | g'2 r2|
}
```

If anyone understands why it happens, please let me know !

Thanks,
Jimmie

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Unterminated tie with tuplets

[Urs Liska]

Am 18.03.2014 09:17, schrieb Jimmie Felidae:

Hello List,

I got a warning of unterminated tie. The warning message is:

```
/tmp/frescobaldi-k7Gcla/tmpqo6ujA/document.ly:3:2: warning: unterminated tie
   c''2.~  \times 2/3 {a'4 g'8~} | g'2 r2|
```

Related tiny example:

```
\version 2.14.0
{
   c''2.~  \times 2/3 {a'4 g'8~} | g'2 r2|
}
```

If anyone understands why it happens, please let me know !


Of course, you're trying to tie a c to an a. This isn't related to the 
tuplets at all.


Either there's something wrong with your example or you actually want a 
slur:



\version 2.14.0
{
  c''2.(  \times 2/3 {a'4) g'8~} | g'2 r2|
}

Urs



Thanks,
Jimmie




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Unterminated tie with tuplets

[David Kastrup]

Jimmie Felidae evolution.ji...@gmail.com writes:

 Hello List,

 I got a warning of unterminated tie. The warning message is:

 ```
 /tmp/frescobaldi-k7Gcla/tmpqo6ujA/document.ly:3:2: warning: unterminated tie
   c''2.~  \times 2/3 {a'4 g'8~} | g'2 r2|
 ```

 Related tiny example:

 ```
 \version 2.14.0
 {
   c''2.~  \times 2/3 {a'4 g'8~} | g'2 r2|
 }
 ```

 If anyone understands why it happens, please let me know !

This has nothing to do with tuplets.  The first tie, namely c''2.~ is
unterminated.  At any rate, 2.14 is old.  Like really, really, old.
2.16 has been released almost 2 years ago, 2.18 has been released last
year.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Unterminated tie with tuplets

[Jimmie Felidae]

Thanks guys. With your help I realize what I tried to do -- it should
be a slur here...

Best,
Jimmie

2014-03-18 16:30 GMT+08:00, David Kastrup d...@gnu.org:
 Jimmie Felidae evolution.ji...@gmail.com writes:

 Hello List,

 I got a warning of unterminated tie. The warning message is:

 ```
 /tmp/frescobaldi-k7Gcla/tmpqo6ujA/document.ly:3:2: warning: unterminated
 tie
   c''2.~  \times 2/3 {a'4 g'8~} | g'2 r2|
 ```

 Related tiny example:

 ```
 \version 2.14.0
 {
   c''2.~  \times 2/3 {a'4 g'8~} | g'2 r2|
 }
 ```

 If anyone understands why it happens, please let me know !

 This has nothing to do with tuplets.  The first tie, namely c''2.~ is
 unterminated.  At any rate, 2.14 is old.  Like really, really, old.
 2.16 has been released almost 2 years ago, 2.18 has been released last
 year.

 --
 David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user