Re: lilypond-user Digest, Vol 147, Issue 46

[David Thorp]

Sent from my LG Mobile

address@hidden wrote:

>Send lilypond-user mailing list submissions to
>       address@hidden
>
>To subscribe or unsubscribe via the World Wide Web, visit
>       https://lists.gnu.org/mailman/listinfo/lilypond-user
>or, via email, send a message with subject or body 'help' to
>       address@hidden
>
>You can reach the person managing the list at
>       address@hidden
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of lilypond-user digest..."
>
>
>Today's Topics:
>
>   1. Re:Annotate and Lilyglyphs (Urs Liska)
>   2. Re:Annotate and Lilyglyphs (Br. Samuel Springuel)
>   3. Re:Annotate and Lilyglyphs (Urs Liska)
>   4. Re:Adding lyrics to basic drum beat (Thomas Morley)
>   5. Re:Annotate and Lilyglyphs (Craig Dabelstein)
>   6. Re:Annotate and Lilyglyphs (Urs Liska)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Fri, 06 Feb 2015 22:36:25 +0100
>From: Urs Liska <address@hidden>
>To: Craig Dabelstein <address@hidden>,
>       address@hidden
>Subject: Re: Annotate and Lilyglyphs
>Message-ID: <address@hidden>
>Content-Type: text/plain; charset=utf-8; format=flowed
>
>
>Am 06.02.2015 um 20:28 schrieb Craig Dabelstein:
>> I still can't get italic text to work.
>> @\textit{cresc.}@
>>
>
>OK, I see now that when annotate takes the text inside the @-s as 
>literal the "\t" is interpreted as a tabulator character ...
>So this must be addressed (except that the discussed reconsideration of 
>message formats should make that obsolete, don't know).
>
>Urs
>
>
>
>------------------------------
>
>Message: 2
>Date: Fri, 06 Feb 2015 16:46:28 -0500
>From: "Br. Samuel Springuel" <address@hidden>
>To: address@hidden
>Subject: Re: Annotate and Lilyglyphs
>Message-ID: <address@hidden>
>Content-Type: text/plain; charset=utf-8; format=flowed
>
>On 2015-02-06 4:18 PM, Noeck wrote:
>> You could also enforce this by now allowing all characters between the @:
>> e.g. @[-a-zA-Z\\_]*@
>
>Rather than include all characters not "@" it would be better to simply 
>exclude "@".  I.e.:
>
>@address@hidden@
>
>The "^", when it is the first character inside a brace changes the brace 
>from meaning "anything in this group" to meaning "anything not in this 
>group".  As a result this expression will match an string contained 
>between to "@" characters which does not itself contain an @ character.
>
>I'm fairly certain this is standard for regular expressions.
>
>
>?????????????????????????
>Br. Samuel, OSB
>(R. Padraic Springuel)
>
>PAX ? ???????
>
>
>
>------------------------------
>
>Message: 3
>Date: Fri, 06 Feb 2015 22:49:04 +0100
>From: Urs Liska <address@hidden>
>To: address@hidden
>Subject: Re: Annotate and Lilyglyphs
>Message-ID: <address@hidden>
>Content-Type: text/plain; charset=utf-8; format=flowed
>
>
>Am 06.02.2015 um 22:46 schrieb Br. Samuel Springuel:
>> On 2015-02-06 4:18 PM, Noeck wrote:
>>> You could also enforce this by now allowing all characters between 
>>> the @:
>>> e.g. @[-a-zA-Z\\_]*@
>>
>> Rather than include all characters not "@" it would be better to 
>> simply exclude "@".  I.e.:
>>
>> @address@hidden@
>>
>> The "^", when it is the first character inside a brace changes the 
>> brace from meaning "anything in this group" to meaning "anything not 
>> in this group".  As a result this expression will match an string 
>> contained between to "@" characters which does not itself contain an @ 
>> character.
>>
>> I'm fairly certain this is standard for regular expressions.
>
>Maybe. In any case it seems to work for the problem at hand, while 
>"@.*?@" did not work.
>
>Thanks
>Urs
>
>>
>>
>> ?????????????????????????
>> Br. Samuel, OSB
>> (R. Padraic Springuel)
>>
>> PAX ? ???????
>>
>> _______________________________________________
>> lilypond-user mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
>
>
>------------------------------
>
>Message: 4
>Date: Fri, 6 Feb 2015 23:31:59 +0100
>From: Thomas Morley <address@hidden>
>To: Kevin Tough <address@hidden>
>Cc: David Kastrup <address@hidden>, lilypond-user <address@hidden>
>Subject: Re: Adding lyrics to basic drum beat
>Message-ID:
>       <address@hidden>
>Content-Type: text/plain; charset=UTF-8
>
>Hi Kevin,
>
>I cc David Kastrup, he recently worked on addlyrics and the like.
>
>2015-02-06 9:11 GMT+01:00 Kevin Tough <address@hidden>:
>> Hi Again,
>>
>> I thought I better be a little clearer. Lilypond states it cannot find
>> voice. The pdf includes the high hat notes. The high hat notes are
>> missing from the midi file???
>>
>> Namaste,
>> Kevin
>>
>> On Fri, 2015-02-06 at 09:04 +0100, Kevin Tough wrote:
>>> Hi Joram,
>>>
>>> I've been reading and trying to get this to work, experimenting.
>>> In order to output midi and pdf your code must be put in a score block
>>> with a layout and midi block inside. As soon as I enclose the code in
>>> the \score block Lilypond says it cannot find voice "voice". I tried
>>> using quotes around "voice" as in the documentation, no improvement. I
>>> changed voice to voicehh thinking perhaps voice is a keyword, no
>>> improvement. I took my \include statements for my favorite printing
>>> scheme in and out. Nothing appears to work so far. Why should the \score
>>> block effect Lilypond to find this voices name??
>
>It doesn't.
>It's \midi {} in \score triggering the problem.
>
>>>
>>> Here is my minimal code as it now stands. I've commented out the \score
>>> block and the *.pdf is fine but no midi.
>>>
>>> \version "2.18.2"
>>>
>>> %\score {
>>>   <<
>>>     \new DrumStaff  <<
>>>       \new DrumVoice = voice { \stemUp \drummode { hh4 hh hh hh }}
>>>       \new DrumVoice { \stemDown \drummode { bd4 sn bd sn }}
>>>     >>
>>>     \new Lyrics \lyricsto voice { One Two Three Four }
>>>   >>
>
>In general better use a \score for printing and another \score for \midi
>
>>>   \layout {
>>>   indent = 0.0\cm
>>>   }
>>>   \midi {
>>>     \tempo 4 = 120
>>>   }
>>> %} % End of score block
>>>
>>>
>>> On Fri, 2015-02-06 at 01:27 +0100, Noeck wrote:
>>> > Hi Kevin,
>>> >
>>> > is this something you like?
>>> >
>>> > \version "2.18.2"
>>> >
>>> > <<
>>> >   \new DrumStaff  <<
>>> >     \new DrumVoice = voice { \stemUp \drummode { hh4 hh hh hh }}
>>> >     \new DrumVoice { \stemDown \drummode { bd4 sn bd sn }}
>>> >   >>
>>> >   \new Lyrics \lyricsto voice { One Two Three Four }
>>> > >>
>>> >
>>> > If the text does not follow a name voice (= voice in the example) using
>>> > \lyricsto, the syllables need duration like notes do.
>>> > I think addlyrics is a short-hand that only works with normal Staffs or 
>>> > at least
>>> > not with multiple voices:
>>> > http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-vocal-music#automatic-syllable-durations
>
>\addlyrics used to work with Voice-context only.
>I think with latest devel-version other contexts are accepted, iirc.
>
>>> >
>>> > Cheers,
>>> > Joram
>
>Here a minimal example demonstrating that lyricsto can't find the
>DrumVoice-context in midi:
>
>\version "2.19.15"
>
> \score {
>   <<
>     \new DrumVoice = "DV" \drummode { hh4 hh hh r hh }
>     \new Lyrics \lyricsto "DV"  { One Two Three Four }
>   >>
>   \midi { }
> }
>
>returns:
>warning: cannot find Voice `DV'
>
>     \new Lyrics
>                 \lyricsto "DV"  { One Two Three Four }
>
>Coding \layout instead of \midi (or commenting it) will show correct
>assigned lyrics, though.
>
>%%%%
>
>Trying to code as shown here:
>https://code.google.com/p/lilypond/issues/detail?id=4097#c10
>and compiling with a build from latest master:
>
>\version "2.19.16"
>
> \score {
>   <<
>     \new DrumVoice = "DV" \drummode { hh4 hh hh r hh }
>     \new Lyrics \lyricsto DrumVoice = "DV"  { One Two Three Four }
>   >>
>   \midi { }
> }
>
>returns:
>
>GNU LilyPond 2.19.16
>Processing `tiny.ly'
>Parsing.../home/harm/lilypond-git/build/out/share/lilypond/current/scm/lily.scm:1041:21:
>In procedure module-lookup in expression (ly:parse-file file-name):
>/home/harm/lilypond-git/build/out/share/lilypond/current/scm/lily.scm:1041:21:
>unbound variable: lyric_combine
>
>%%%%
>
>I'm not aware of a workaround in 2.18.2, with 2.19.15 you can do:
>
>\version "2.19.15"
>
>\paper { ragged-right = ##f }
>
>m =
>  <<
>    \new DrumStaff
>      <<
>       \new DrumVoice \drummode { \voiceOne hh4 hh hh r hh }
>       \new DrumVoice = "dv" \drummode { \voiceTwo bd4 sn bd r sn }
>      >>
>    \new Lyrics
>      \with {
>        associatedVoiceType = #'DrumVoice
>        associatedVoice = "dv"
>      }
>      \lyricsto "dv" { One Two Three Four  }
>  >>
>
>\score {
>  \m
>  \layout { }
>}
>
>\score {
>  \m
>  \midi { }
>}
>
>The need to do both:
>associatedVoice = "dv"
>_and_
>\lyricsto "dv"
>is strange, though.
>
>
>HTH a bit,
>  Harm
>
>
>
>------------------------------
>
>Message: 5
>Date: Fri, 06 Feb 2015 23:39:42 +0000
>From: Craig Dabelstein <address@hidden>
>To: Urs Liska <address@hidden>, address@hidden
>Subject: Re: Annotate and Lilyglyphs
>Message-ID:
>       <address@hidden>
>Content-Type: text/plain; charset="utf-8"
>
>Hi List,
>
>Sorry for the frustrating question, but how do I combine Samuel's code
>-- @address@hidden@
>-- with an annotate message such as -- "Should the @\textit{cresc.} begin
>here or immediately after the preceeding address@hidden"
>
>Craig
>
>
>On Sat Feb 07 2015 at 7:49:15 AM Urs Liska <address@hidden> wrote:
>
>>
>> Am 06.02.2015 um 22:46 schrieb Br. Samuel Springuel:
>> > On 2015-02-06 4:18 PM, Noeck wrote:
>> >> You could also enforce this by now allowing all characters between
>> >> the @:
>> >> e.g. @[-a-zA-Z\\_]*@
>> >
>> > Rather than include all characters not "@" it would be better to
>> > simply exclude "@".  I.e.:
>> >
>> > @address@hidden@
>> >
>> > The "^", when it is the first character inside a brace changes the
>> > brace from meaning "anything in this group" to meaning "anything not
>> > in this group".  As a result this expression will match an string
>> > contained between to "@" characters which does not itself contain an @
>> > character.
>> >
>> > I'm fairly certain this is standard for regular expressions.
>>
>> Maybe. In any case it seems to work for the problem at hand, while
>> "@.*?@" did not work.
>>
>> Thanks
>> Urs
>>
>> >
>> >
>> > ?????????????????????????
>> > Br. Samuel, OSB
>> > (R. Padraic Springuel)
>> >
>> > PAX ? ???????
>> >
>> > _______________________________________________
>> > lilypond-user mailing list
>> > address@hidden
>> > https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>>
>> _______________________________________________
>> lilypond-user mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: 
><http://lists.gnu.org/archive/html/lilypond-user/attachments/20150206/8882f3c6/attachment.html>
>
>------------------------------
>
>Message: 6
>Date: Sat, 07 Feb 2015 00:40:58 +0100
>From: Urs Liska <address@hidden>
>To: Craig Dabelstein <address@hidden>,
>       address@hidden
>Subject: Re: Annotate and Lilyglyphs
>Message-ID: <address@hidden>
>Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
>
>Am 07.02.2015 um 00:39 schrieb Craig Dabelstein:
>> Hi List,
>>
>> Sorry for the frustrating question, but how do I combine Samuel's code 
>> -- @address@hidden@ -- with an annotate message such as -- "Should the 
>> @\textit{cresc.} begin here or immediately after the preceeding 
>> address@hidden"
>
>You don't do that at all. You simply wait until I have managed to update 
>everything and upload it ;-)
>
>>
>> Craig
>>
>>
>> On Sat Feb 07 2015 at 7:49:15 AM Urs Liska <address@hidden 
>> <mailto:address@hidden>> wrote:
>>
>>
>>     Am 06.02.2015 um 22:46 schrieb Br. Samuel Springuel:
>>     > On 2015-02-06 4:18 PM, Noeck wrote:
>>     >> You could also enforce this by now allowing all characters between
>>     >> the @:
>>     >> e.g. @[-a-zA-Z\\_]*@
>>     >
>>     > Rather than include all characters not "@" it would be better to
>>     > simply exclude "@".  I.e.:
>>     >
>>     > @address@hidden@
>>     >
>>     > The "^", when it is the first character inside a brace changes the
>>     > brace from meaning "anything in this group" to meaning "anything not
>>     > in this group".  As a result this expression will match an string
>>     > contained between to "@" characters which does not itself
>>     contain an @
>>     > character.
>>     >
>>     > I'm fairly certain this is standard for regular expressions.
>>
>>     Maybe. In any case it seems to work for the problem at hand, while
>>     "@.*?@" did not work.
>>
>>     Thanks
>>     Urs
>>
>>     >
>>     >
>>     > ?????????????????????????
>>     > Br. Samuel, OSB
>>     > (R. Padraic Springuel)
>>     >
>>     > PAX ? ???????
>>     >
>>     > _______________________________________________
>>     > lilypond-user mailing list
>>     > address@hidden <mailto:address@hidden>
>>     > https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>>
>>     _______________________________________________
>>     lilypond-user mailing list
>>     address@hidden <mailto:address@hidden>
>>     https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: 
><http://lists.gnu.org/archive/html/lilypond-user/attachments/20150207/d8896f2f/attachment.html>
>
>------------------------------
>
>_______________________________________________
>lilypond-user mailing list
>address@hidden
>https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
>End of lilypond-user Digest, Vol 147, Issue 46
>**********************************************