Re: Interesting glitch when using tags ...
On 04.02.2018 21:27, Wols Lists wrote: The problem here is that your two melody passages are all in the same voice, and that means that f4 is_not_ the next note after f4. ~ but rather the d8 in the previous line of entry is. Oh ... so lily is being its usual rather non-intuitive self :-) That’s a misleading way to see it. You need to grasp basic concepts in order to successfully work with LilyPond, one of them being what a Voice is and how two Voices are a different thing than two parallel music expressions. Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Interesting glitch when using tags ...
Wols Lists writes: > On 04/02/18 19:20, David Kastrup wrote: > >> So can we agree that diagnosing this required an actual complete example >> showing the context in which this problem occured? >> > (Which, while it wasn't a compilable example, was why I included the > context in my first post :-) Doesn't show which tags are left in, and when preceding it with something like \new ChoirStaff puts the lines in different contexts. Also is missing the language and isn't compilable so that people have to either not compile at all and guess, or fantasize something to add that may or may not show the effect. Maybe 5 people will be ready to help: why make all those 5 work harder so that you can save a minute when you are the one actually wanting help? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Interesting glitch when using tags ...
On 04/02/18 19:20, David Kastrup wrote:
> Wol's lists writes:
>
>> Okay. You wanted a minimal example ...
>>
>> But surely, "f4. ~ f4" is clearly something wrong if it's complaining
>> about an unterminated tie? Yes you might need a bit more information
>> to debug it, but on the face of it it's a blatant bug ...
>
> And when looking closer at an actual example, it isn't.
>
> \version "2.18.2"
>
> \include "english.ly"
>
>
> \score {
> \new Staff {
> \time 6/8
> \key bf \major
> \clef "treble_8"
> <<
> {
> \repeat percent 4 { bf8[ r bf] bf[ r bf] } | c4( d8 c4) r8 |
> c8-> r4 c8-> r4 | c2. | c2. ~
> }
> {
> \repeat percent 4 { f8[ r f] f[ r f] } | f4. ~ f4 r8 | a8->
> r4 a8-> r4 | a2. | bf2.
> }
> >>
> }
> }
>
> The problem here is that your two melody passages are all in the same
> voice, and that means that f4 is _not_ the next note after f4. ~ but
> rather the d8 in the previous line of entry is.
Oh ... so lily is being its usual rather non-intuitive self :-) (Of
course, being a command line tool, with power comes responsibility :-)
>
> LilyPond cannot deal sensibly with overlapping notes in the same voice.
> You need two separate voices. Indeed, putting \\ between the two { }
> groups in the parallel music stops the problem. Of course, with awful
> voice crossing.
I'll see what doing that does. Bear in mind, in the full example they
are tagged ...
Putting \voices 2,1 before the << ... >> looks better
> (but I have no idea whether the voice crossing then in the first half is
> intentional, or even whether you wanted the original in which case you'd
> like be better off with two staves).
The original is a part with two instruments, so no, two staves is very
definitely not what is wanted - and the tags are so that I can print it
out for my own purposes as two separate parts, but print it combined for
checking purposes. Can be painful :-(
Maybe I should have done it as two separate parts, and used partcombine
for checking purposes. Would probably have been easier ...
>
> So can we agree that diagnosing this required an actual complete example
> showing the context in which this problem occured?
>
(Which, while it wasn't a compilable example, was why I included the
context in my first post :-)
Anyways, thanks. Now I know why it's happening, I can either choose to
ignore it, or I can fix it. And next time it happens, I'll know what's
going on.
Cheers,
Wol
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Interesting glitch when using tags ...
Wol's lists writes:
> Okay. You wanted a minimal example ...
>
> But surely, "f4. ~ f4" is clearly something wrong if it's complaining
> about an unterminated tie? Yes you might need a bit more information
> to debug it, but on the face of it it's a blatant bug ...
And when looking closer at an actual example, it isn't.
\version "2.18.2"
\include "english.ly"
\score {
\new Staff {
\time 6/8
\key bf \major
\clef "treble_8"
<<
{
\repeat percent 4 { bf8[ r bf] bf[ r bf] } | c4( d8 c4) r8 |
c8-> r4 c8-> r4 | c2. | c2. ~
}
{
\repeat percent 4 { f8[ r f] f[ r f] } | f4. ~ f4 r8 | a8-> r4
a8-> r4 | a2. | bf2.
}
>>
}
}
The problem here is that your two melody passages are all in the same
voice, and that means that f4 is _not_ the next note after f4. ~ but
rather the d8 in the previous line of entry is.
LilyPond cannot deal sensibly with overlapping notes in the same voice.
You need two separate voices. Indeed, putting \\ between the two { }
groups in the parallel music stops the problem. Of course, with awful
voice crossing. Putting \voices 2,1 before the << ... >> looks better
(but I have no idea whether the voice crossing then in the first half is
intentional, or even whether you wanted the original in which case you'd
like be better off with two staves).
So can we agree that diagnosing this required an actual complete example
showing the context in which this problem occured?
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Interesting glitch when using tags ...
Whoops - I've just spotted a genuine unterminated tie at the end of the
first line of notes - but removing it does not get rid of the warning...
So this minimal example demonstrates both a genuine unterminated tie
that doesn't warn, and a terminated tie that warns when it shouldn't...
Cheers,
Wol
On 04/02/18 18:49, Wol's lists wrote:
Okay. You wanted a minimal example ...
But surely, "f4. ~ f4" is clearly something wrong if it's complaining
about an unterminated tie? Yes you might need a bit more information to
debug it, but on the face of it it's a blatant bug ...
Cheers,
Wol
On 04/02/18 00:59, David Kastrup wrote:
Wols Lists writes:
On 04/02/18 00:33, David Kastrup wrote:
Wol's lists writes:
I suspect the cause is that I'm mixing slurs and ties, but I'm getting
the following error ...
voiceTrombone.ily:30:59: warning: unterminated tie
\repeat percent 4 { f,8[ r f] f[ r f] } | f4.
~ f4 r8 | a8-> r4
a8-> r4 | a2. | bf2.(
Yes I know. But looking at the error message, I am quite clearly tying
an f to an f. So why is it complaining "unterminated tie"?
This very likely depends on details you don't quote.
I can try and make a minimal example if you like - I'm just puzzled why
what is - as far as I can see - perfectly correct syntax is generating
an error message.
NB - the lilypond version is SUSE's latest ...
And of course everybody uses SUSE and knows which is their "latest",
regardless whether we are talking about final releases or test releases
or whatever else. And naturally there is only a single architecture
they support.
Sigh. If you are interested in getting help, try investing a minimum of
work to actually make that possible. If not, why bother?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Interesting glitch when using tags ...
Okay. You wanted a minimal example ...
But surely, "f4. ~ f4" is clearly something wrong if it's complaining
about an unterminated tie? Yes you might need a bit more information to
debug it, but on the face of it it's a blatant bug ...
Cheers,
Wol
On 04/02/18 00:59, David Kastrup wrote:
Wols Lists writes:
On 04/02/18 00:33, David Kastrup wrote:
Wol's lists writes:
I suspect the cause is that I'm mixing slurs and ties, but I'm getting
the following error ...
voiceTrombone.ily:30:59: warning: unterminated tie
\repeat percent 4 { f,8[ r f] f[ r f] } | f4.
~ f4 r8 | a8-> r4
a8-> r4 | a2. | bf2.(
Yes I know. But looking at the error message, I am quite clearly tying
an f to an f. So why is it complaining "unterminated tie"?
This very likely depends on details you don't quote.
I can try and make a minimal example if you like - I'm just puzzled why
what is - as far as I can see - perfectly correct syntax is generating
an error message.
NB - the lilypond version is SUSE's latest ...
And of course everybody uses SUSE and knows which is their "latest",
regardless whether we are talking about final releases or test releases
or whatever else. And naturally there is only a single architecture
they support.
Sigh. If you are interested in getting help, try investing a minimum of
work to actually make that possible. If not, why bother?
\version "2.18.2"
\include "english.ly"
\score {
\new Staff {
\time 6/8
\key bf \major
\clef "treble_8"
<<
{
\repeat percent 4 { bf8[ r bf] bf[ r bf] } | c4( d8 c4) r8 | c8-> r4 c8-> r4 | c2. | c2. ~
}
{
\repeat percent 4 { f8[ r f] f[ r f] } | f4. ~ f4 r8 | a8-> r4 a8-> r4 | a2. | bf2.
}
>>
}
}
test.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Interesting glitch when using tags ...
2018-02-04 1:54 GMT+01:00 Wols Lists :
> On 04/02/18 00:33, David Kastrup wrote:
>> Wol's lists writes:
>>
>>> I suspect the cause is that I'm mixing slurs and ties, but I'm getting
>>> the following error ...
>>>
>>> voiceTrombone.ily:30:59: warning: unterminated tie
>>> \repeat percent 4 { f,8[ r f] f[ r f] } | f4.
>>> ~ f4 r8 | a8-> r4
>>> a8-> r4 | a2. | bf2.(
>>>
>
>>
>>
>>
> Yes I know. But looking at the error message, I am quite clearly tying
> an f to an f. So why is it complaining "unterminated tie"?
>
> I can try and make a minimal example if you like - I'm just puzzled why
> what is - as far as I can see - perfectly correct syntax is generating
> an error message.
>
> NB - the lilypond version is SUSE's latest ...
>
> Cheers,
> Wol
The error message I get is:
Processing `atest-70.ly'
Parsing...
atest-70.ly:342:33: error: not a note name: bf
\repeat percent 4 {
bf8[ r bf] bf[ r bf] } | c4( d8 c4) r8
| c8-> r4 c8-> r4 | c2. | c2. ~
atest-70.ly:342:40: error: not a note name: bf
\repeat percent 4 { bf8[ r
bf] bf[ r bf] } | c4( d8 c4) r8
| c8-> r4 c8-> r4 | c2. | c2. ~
atest-70.ly:342:44: error: not a note name: bf
\repeat percent 4 { bf8[ r bf]
bf[ r bf] } | c4( d8 c4) r8
| c8-> r4 c8-> r4 | c2. | c2. ~
atest-70.ly:342:50: error: not a note name: bf
\repeat percent 4 { bf8[ r bf] bf[ r
bf] } | c4( d8 c4) r8
| c8-> r4 c8-> r4 | c2. | c2. ~
atest-70.ly:345:93: error: not a note name: bf
\repeat percent 4 { f,8[ r f] f[ r f] } | f4. ~ f4 r8 |
a8-> r4 a8-> r4 | a2. |
bf2.(
Interpreting music...
atest-70.ly:342:72: warning: barcheck failed at: 3/4
\repeat percent 4 { bf8[ r bf] bf[ r bf] } | c4( d8 c4) r8
| c8-> r4 c8-> r4 | c2. | c2. ~
atest-70.ly:345:67: warning: barcheck failed at: 3/4
\repeat percent 4 { f,8[ r f] f[ r f] } | f4. ~ f4 r8
|
a8-> r4 a8-> r4 | a2. | bf2.(
atest-70.ly:342:90: warning: barcheck failed at: 1/2
\repeat percent 4 { bf8[ r bf] bf[ r bf] } | c4( d8 c4) r8
| c8-> r4 c8-> r4
| c2. | c2. ~
atest-70.ly:345:85: warning: barcheck failed at: 1/2
\repeat percent 4 { f,8[ r f] f[ r f] } | f4. ~ f4 r8 |
a8-> r4 a8-> r4
| a2. | bf2.(
atest-70.ly:342:96: warning: barcheck failed at: 1/4
\repeat percent 4 { bf8[ r bf] bf[ r bf] } | c4( d8 c4) r8
| c8-> r4 c8-> r4 | c2.
| c2. ~
atest-70.ly:345:91: warning: barcheck failed at: 1/4
\repeat percent 4 { f,8[ r f] f[ r f] } | f4. ~ f4 r8 |
a8-> r4 a8-> r4 | a2.
| bf2.(
atest-70.ly:345:97: warning: unterminated slur
\repeat percent 4 { f,8[ r f] f[ r f] } | f4. ~ f4 r8 |
a8-> r4 a8-> r4 | a2. | bf2.
(
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
programming error: Grob direction requested while calculation in progress.
continuing, cross fingers
programming error: The beam should have a direction by now.
continuing, cross fingers
programming error: Improbable offset for stencil: -2147483646.50 staff space
Setting to zero.
continuing, cross fingers
programming error: Grob direction requested while calculation in progress.
continuing, cross fingers
programming error: The beam should have a direction by now.
continuing, cross fingers
programming error: Improbable offset for stencil: -2147483646.50 staff space
Setting to zero.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Interesting glitch when using tags ...
Wols Lists writes:
> On 04/02/18 00:33, David Kastrup wrote:
>> Wol's lists writes:
>>
>>> I suspect the cause is that I'm mixing slurs and ties, but I'm getting
>>> the following error ...
>>>
>>> voiceTrombone.ily:30:59: warning: unterminated tie
>>> \repeat percent 4 { f,8[ r f] f[ r f] } | f4.
>>> ~ f4 r8 | a8-> r4
>>> a8-> r4 | a2. | bf2.(
>>>
>
>>
>>
>>
> Yes I know. But looking at the error message, I am quite clearly tying
> an f to an f. So why is it complaining "unterminated tie"?
This very likely depends on details you don't quote.
> I can try and make a minimal example if you like - I'm just puzzled why
> what is - as far as I can see - perfectly correct syntax is generating
> an error message.
>
> NB - the lilypond version is SUSE's latest ...
And of course everybody uses SUSE and knows which is their "latest",
regardless whether we are talking about final releases or test releases
or whatever else. And naturally there is only a single architecture
they support.
Sigh. If you are interested in getting help, try investing a minimum of
work to actually make that possible. If not, why bother?
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Interesting glitch when using tags ...
On 04/02/18 00:33, David Kastrup wrote:
> Wol's lists writes:
>
>> I suspect the cause is that I'm mixing slurs and ties, but I'm getting
>> the following error ...
>>
>> voiceTrombone.ily:30:59: warning: unterminated tie
>> \repeat percent 4 { f,8[ r f] f[ r f] } | f4.
>> ~ f4 r8 | a8-> r4
>> a8-> r4 | a2. | bf2.(
>>
>
>
>
Yes I know. But looking at the error message, I am quite clearly tying
an f to an f. So why is it complaining "unterminated tie"?
I can try and make a minimal example if you like - I'm just puzzled why
what is - as far as I can see - perfectly correct syntax is generating
an error message.
NB - the lilypond version is SUSE's latest ...
Cheers,
Wol
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Interesting glitch when using tags ...
Wol's lists writes:
> I suspect the cause is that I'm mixing slurs and ties, but I'm getting
> the following error ...
>
> voiceTrombone.ily:30:59: warning: unterminated tie
> \repeat percent 4 { f,8[ r f] f[ r f] } | f4.
> ~ f4 r8 | a8-> r4
> a8-> r4 | a2. | bf2.(
>
> but as you can see, I'm tying two f's together ... the crucial point
> is it does print correctly (well, it should be an inverted tie, but at
> least it prints a tie).
>
> The context is:
>
> <<
> \tag #'TromI {
> \repeat percent 4 { bf8[ r bf] bf[ r bf] } | c4( d8 c4) r8
> | c8-> r4 c8-> r4 | c2. | c2. ~
> }
> \tag #'TromII {
> \repeat percent 4 { f,8[ r f] f[ r f] } | f4. ~ f4 r8 |
> a8-> r4 a8-> r4 | a2. | bf2.(
> }
> >>
>
> you'll see that TromII has the tie, and TromI has a slur. BUT. If I
> change the tie to a slur, the error message disappears, but so does
> the slur joining the f's if I'm printing both parts ...
>
> Interestingly, the eagle-eyed will notice that the last note of each
> part also ends with a tie in one part and a slur in the other, but
> this prints fine and doesn't generate an error ... odd ...
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
