[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-user
Subject:    Re: problem of placing "\with {\consists #numbrUP}" on lilypond code
From:       Reinhold Kainhofer <reinhold () kainhofer ! com>
Date:       2012-12-11 22:42:55
Message-ID: 50C7B6EF.3070102 () kainhofer ! com
[Download RAW message or body]

On 11/12/2012 23:24, MING TSANG wrote:
> I have a second problen:  When I code \nup on \new staff level. 
> numbered pitch stack wrong for the last three note on T.B clef bass .
> Please refer to png.  

The reason is that there is no guarantee that at any given moment the
notes of the  first voice will be processed before the notes of the
second voice. In the second-to-last note, apparently the note of the
bass is processed before the note of the tenor, so the test scripts are
created the other way around...

I don't think there is any way to handle this properly at the staff-level...

Cheers,
Reinhold

-- 
------------------------------------------------------------------
Reinhold Kainhofer, reinhold@kainhofer.com, http://www.kainhofer.com
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * Edition Kainhofer, Music Publisher, http://www.edition-kainhofer.com


[Attachment #3 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 11/12/2012 23:24, MING TSANG wrote:<br>
    </div>
    <blockquote
      cite="mid:1355264675.70814.YahooMailNeo@web142604.mail.bf1.yahoo.com"
      type="cite">
      <div style="color:#000; background-color:#fff; font-family:Courier
        New, courier, monaco, monospace, sans-serif;font-size:14pt"><span>I
          have a second problen:&nbsp; When I code \nup on \new staff level.&nbsp;
          numbered pitch stack wrong for the last three note on T.B clef
          bass . Please refer to png. &nbsp; </span></div>
    </blockquote>
    <br>
    The reason is that there is no guarantee that at any given moment
    the notes of the&nbsp; first voice will be processed before the notes of
    the second voice. In the second-to-last note, apparently the note of
    the bass is processed before the note of the tenor, so the test
    scripts are created the other way around...<br>
    <br>
    I don't think there is any way to handle this properly at the
    staff-level...<br>
    <br>
    Cheers,<br>
    Reinhold<br>
    <pre class="moz-signature" cols="72">-- 
------------------------------------------------------------------
Reinhold Kainhofer, <a class="moz-txt-link-abbreviated" \
href="mailto:reinhold@kainhofer.com">reinhold@kainhofer.com</a>, <a \
class="moz-txt-link-freetext" \
                href="http://www.kainhofer.com">http://www.kainhofer.com</a>
 * Financial &amp; Actuarial Math., Vienna Univ. of Technology, Austria
 * <a class="moz-txt-link-freetext" \
                href="http://www.fam.tuwien.ac.at/">http://www.fam.tuwien.ac.at/</a>, \
                DVR: 0005886
 * Edition Kainhofer, Music Publisher, <a class="moz-txt-link-freetext" \
href="http://www.edition-kainhofer.com">http://www.edition-kainhofer.com</a></pre>  \
</body> </html>



[prev in list] [next in list] [prev in thread] [next in thread]

Configure | About | News | Add a list | Sponsored by KoreLogic