James, Thomas & Phil:
Thank you for the work around by adding
\layout {
\context {
\Staff
\accepts NullVoice
}
}
to the \score block, it works for both v2.19.12 and v2.19.13
Thanks,
Emmanuel,
Ming.
On Thursday, September 4, 2014 5:31:02 AM, James <[email protected]> wrote:
Ming,
Did you see Thomas' last response?
Putting the
\layout { \context { \Staff \accepts NullVoice }
}
In your score may now work around this issue.
What I would suggest is that if this works, that you put a comment
in your *.ly file to remind you that was why you had to do it.
Obviously this isn't an explanation of why it no longer works, but
with these 'one-off' scheme constructs that are not part of the
core-code of LilyPond then it is difficult to keep those
compatible as we update the code.
If this does work, I think it would be nice to know and for you to
say on the user email list for all those other users that may also
run into the same problem when they eventually move to 2.19 (and
so 2.20 when it becomes 'stable version').
James
-------- Forwarded Message --------
Delivered-To: [email protected]
Received: by 10.152.121.73 with SMTP id li9csp933937lab; Thu, 4 Sep 2014
01:24:48 -0700 (PDT)
Return-Path: <[email protected]>
Received-SPF: pass (google.com: domain of [email protected] designates
10.194.95.234 as permitted sender) client-ip=10.194.95.234
Authentication-Results: mr.google.com; spf=pass (google.com: domain of
[email protected] designates 10.194.95.234 as permitted sender)
[email protected]; dkim=pass [email protected]
X-Received: from mr.google.com ([10.194.95.234]) by 10.194.95.234 with SMTP id
dn10mr2019990wjb.73.1409819088403 (num_hops = 1); Thu, 04 Sep 2014 01:24:48
-0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
bh=hzjzxh2p+n09uJfUgTTEPxWM/kJrOt1bPjgqsnoq1iI=;
b=bdxHXD+IXqnx9s4xnrKBQxOMe2MARlAT48VrQe62JmDCmVDAMXbl84l1jwzUA1cS6M
LXIgXWnrRp7OhR4PMhwbpPzJyPyOWn5V24psoWeYmB0GAC9PrWh7rDPWE9zEqTJUPitm
d0cG6OYL4wlZ6Nj2U4egjwAc7qlzUhYvoydnd1oDULE2sSvpzU3i+3AIItxlsa5rHF0a
rK1eZfM2doFrvqSpJS7EbVwMWd4vBMHwTZzid4ugt6VdjiQbr51OlRCGZbIZe1k3bO6d
dK6pZ+ywC6B5JzQ9hjqp5bTo/nzT1n5RaTU0pOWvd7gAp5X68MQybLPUVbZbXohmrMKA Dtkg==
MIME-Version: 1.0
X-Received: by 10.194.95.234 with SMTP id dn10mr3905375wjb.73.1409819088140;
Thu, 04 Sep 2014 01:24:48 -0700 (PDT)
Received: by 10.180.211.78 with HTTP; Thu, 4 Sep 2014 01:24:48 -0700 (PDT)
In-Reply-To: <[email protected]>
References: <[email protected]>
<016BAD9F5B49406BA78A50DC9D5D5361@Advent> <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<CABsfGyWxfHKj-X8RODtW2gChK_DUmuWrb=qyfblzanwobeu...@mail.gmail.com>
<[email protected]>
Date: Thu, 4 Sep 2014 10:24:48 +0200
Message-ID:
<cabsfgywnoyrz-xj2t2ox31mjoq60t3ynja0szsckoc+h_qa...@mail.gmail.com>
Subject: Re: Wrong type argument
From: Thomas Morley <[email protected]>
To: James <[email protected]>
Cc: MING TSANG <[email protected]>, Lilypond bug <[email protected]>,
lilypond-user mailinglist <[email protected]>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
2014-09-03 9:17 GMT+02:00 James <[email protected]>:
> On 02/09/14 21:58, Thomas Morley wrote:
>> 2014-09-02 12:44 GMT+02:00 MING TSANG <[email protected]>:
>>> James & Phil:
>>> I comment out line 421 which call solfege-engravers - both versions run ok.
>>> Un-comment out line 421 - v2.19.12 run ok; but fails with v2.19.13.
>>> I don't know scheme. I cannot not begin debug.
>>> Appreciated if you can help.
>>> Emmanuel,
>>> Ming.
>>
>> It's more an issue with NullVoice, than with the solfege-engraver.
>> In NullVoice the following line returns an empty list:
>> (tonic-pitch (ly:context-property context 'tonic))
>> Seems 'tonic is not "known" in NullVoice.
>>
>> Can't help more, I didn't follow the discussion about NullVoice close
>> enough and my computer is still broken, acting as a guest on another
>> computer (until I've the money to buy a new one ...)
>>
>> Nevertheless, here a boiled down code
>> (The engraver will cause some terminal-output, all other functionality
>> is commented)
>>
>>
>> \version "2.19.13" % work on v2.19.12 but failes with v2.19.13
>>
>> #(define numR➀ '("➀" "➁" "➂" "➃" "➄" "➅" "➆"))
>>
>> #(define (solfege-engraver lst dir)
>> (make-engraver
>> (acknowledgers
>> ((note-head-interface engraver grob source)
>> (let* (
>> (context (ly:translator-context engraver))
>> (tonic-pitch (ly:context-property context 'tonic))
>> ; (tonic-index (ly:pitch-notename tonic-pitch))
>> (event (ly:grob-property grob 'cause))
>> (event-copy (ly:event-deep-copy event))
>> (grob-pitch (ly:event-property event 'pitch))
>> (grob-index (ly:pitch-notename grob-pitch))
>> ; (delta (modulo (- grob-index tonic-index) 7))
>> ; (name (list-ref lst delta))
>> ; (newgrob (ly:engraver-make-grob engraver 'TextScript
>> event-copy))
>> )
>>
>> (newline)
>> (display tonic-pitch)
>>
>> ;; clear 'tweaks for newgrob
>> ;; (ly:event-set-property! event-copy 'tweaks '())
>> ; (if (string= name "Hb") (set! name "B"))
>> ;; Give newgrob 'outside-staff-priority depending on
>> ;; grob 'staff-position
>> ; (set! (ly:grob-property newgrob 'outside-staff-priority)
>> ; (+ (ly:grob-property newgrob 'outside-staff-priority)
>> ; (* dir (ly:grob-property grob 'staff-position))))
>> ; (set! (ly:grob-property newgrob 'text) name)
>> ; (set! (ly:grob-property newgrob 'direction) dir)
>> )))))
>>
>>
>> \layout {
>> \context {
>> \NullVoice
>> \consists #(solfege-engraver numR➀ UP)
>> }
>> }
>>
>> \new Staff
>> \new NullVoice
>> { d'4 }
>>
>>
>>
>> Cheers,
>> Harm
>>
>
>
> Is it because NullVoice is has now been moved in terms of its context
> 'position' (if that is the right word)?
>
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=fc8c2d680464130af497c386ed5f0033d3fd7470
> >
> (ccing - bug in case this is a bug or not).
>
> James
>
> Hi James, partly undoing the patch infile with adding \layout { \context {
> \Staff \accepts NullVoice }
} works.
Though, I'm not sure it's a bug. I doubt it make much sense to add an
engraver like the solfege-engraver to NullVoice.
I've the feeling it negates the sense of NullVoice. Nevertheless, thanks for
the hint. Cheers, Harm _______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
