horizontal shift of note column - hardly works!

[Tom Cloyd]

I need help with this construction: \once \override NoteColumn 
#'force-hshift = #{doesn't matter what you put here 'cause it rarely 
works anyway}


My ly code problem demo snippet is here: http://pastie.org/8433947

After two hours of futility tonight, and a review of my previous go 
around with this problem, I still can't figure this out. Never really 
understood "the fix", although I did get it work, once.


- the previous problem: 
http://lilypond.1069038.n5.nabble.com/horizontal-shift-of-note-column-not-working-td15374.html


- the fix: 
http://lists.gnu.org/archive/html/lilypond-user/2010-04/msg00030.html


Am I the only one who ever needs to shift notes horizontally to clean up 
a score? Seem hard to believe. But it doesn't work reliably, and the 
documentation is minimal at best.


In the code snippet, in the bass voice, measures 2, 3, & 4 there is no 
column collision. Then suddenly in m. 5 - BAM. But it's fixable (and 
fixed, in the code). An attempt to fix the collision by moving the alto 
voice in the same measure failed. Why?


Measure 7 bass and alto voices won't budge, period. Am baffled by this.

Beat 1 of measures 8, 9 have the same problem (as does much of my score).

There appears to be NO other way to move notes out of vertical 
collisions. With this barely working, what do people do?


Thanks for any help!

--

~~
Tom Cloyd
Cedar City / St. George, Utah, U.S.A: (435) 272-3332
~~


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

Re: id's for svg elements

[Bric]

On 10/26/2013 04:15 AM, Mike Solomon wrote:

On Oct 26, 2013, at 10:51 AM, Bric  wrote:


can someone help scope out the task of adding semantically sound unique 
identifiers to the svg elements?

Such that the id bears info on, at least, the staff, (maybe bar), and 
note/chord index (consecutive integer index, for instance)

the "output-svg.scm" script has various routines to build the svg 
elements/tags/attributes, and these are implemented by other scm scripts (e.g., 
"round-filled-box")...

Before I spend hours (days?) trying to figure out the precise subroutine 
chain/tree , perhaps someone can lead me directly to the top-level code that 
feeds lilypond info into these scripts? And whereby one can feed staff/movement 
info, along with note index down to the final svg output?

And is this a realistic goal, I wonder?  I think even just identifying CLASS information in the 
"id=..." attribute might help. Just to set the stem "rect" apart from the staff line 
"rect", for instance, would already be an improvement; but, of course, I prefer even more 
specifics, as I described above.

thanks.


There is a grob property that is called "id" that is called far downstream 
(right when the backends are getting the last information about the grobs before drawing 
them).  That means that, if you create a callback for this property, you can feed it all 
sorts of info.  The resulting SVG object will be wrapped in a group with this id.

For example…

\version "2.17.30"

#(define (note-number grob)
   (string-concatenate
 (list
   "NoteHead/"
   (number->string
 (ly:pitch-semitones
   (ly:event-property (ly:grob-property grob 'cause) 'pitch))

\relative c' {
   \override NoteHead.id = #note-number
   a
}

Then

lilypond -dbackend=svg yourfilename.ly

Then open the SVG and look for id="NoteHead/-3"

Cheers,
MS
Hi! I see it. And I can see that you're doing some sort of awesome magic 
here, but it remains a total mystery... looking at the code, and looking 
at the result, alike.


(what's a "grob property"?  I guess it's time to hit the fine manual...)

I can see that your code above generates this in the resulting *.svg file:


d="M217 139c57 0 112 -31 112 -94c0 -72 -55 -121 -102 -149c-35 -21 -74 
-35 -115 -35c-57 0 -112 31 -112 94c0 72 55 121 102 149c35 21 74 35 115 
35z" fill="currentColor"/>



but I have no idea why this is so, and why there's a group with only one 
member in it.  I presume you are suggesting to group the notehead, the 
stem, and maybe accidentals, and what not, under the same group and 
group id?



thanks!

(PS: how is it that you have 2.17.30, when the latest version is 2.17.29 
?  http://download.linuxaudio.org/lilypond/source/v2.17/ )




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

Re: Automatic beaming in vocal cadenzas

[David Kastrup]

Colin Campbell  writes:

> I D/L the patch and applied it, ran make with no errors. I then
> re-compiled my sample file, but saw no difference in behaviour.  I
> gather your patch should have prevented the melisma created in a
> cadenza by manual beaming, but they still seem to happen.

Do you make any explicit settings to autoBeaming ?  In particular, you
should not turn it off.  It will not autobeam anyway inside of cadenze,
except that I consider it possible that a beam might run right across a
cadenza (not counting the cadenza itself in).

> Am I testing the proper thing, in the proper way?

No idea.

-- 
David Kastrup


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

Re: Feedback for Frescobaldi's Preview Mode

[SoundsFromSound]

I absolutely love this new feature. I haven't experienced any terrible bugs
or glitches with it yet, but I don't use it all the time with every project.

But when I do use it, it's awesome. :)

Ben



-
composer | sound designer 
LilyPond Tutorials (for beginners) --> http://bit.ly/bcl-lilypond
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Feedback-for-Frescobaldi-s-Preview-Mode-tp152949p152986.html
Sent from the User mailing list archive at Nabble.com.

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

Re: voice two but yet stems up towards end of piece with addlyrics

[Annette Kusma]

Hi and thanks for the quick reply!

Sorry, I really totally missed the errors. That is, I initially scanned the
log for relevant errors but did (with the original file) not get or not see
the one error you mention; I did get and see "warning: ignoring too many
clashing note columns" instead, which I rather took as stating the obvious
result of what I assumed was a programming error on my behalf (putting some
command somewhere when it should be somewhere else). That's why I sort of
buried myself in finding something in the notational reference that showed
me how/where I should write instead. I have earlier read that the
\addlyrics is not meant for complex pieces, yet if it resides inside a
monophonic voice variable and works the first time around, who could
imagine that this per se is 'complex' and that it stops working the second
time?

Anyway, I'll have a closer look at the example snippet you linked and also
at the \set associatedVoice command (since most of my pieces have one set
of lyrics at the beginning and several at the end of the piece; I did not
know of that command until today...).

Thanks again for your help!

/Annette


2013/10/26 Robin Bannister 

> Annette Kusma wrote:
>
>>  Is this a bug or am I missing something?
>>
>
>
> The example you supplied did not run without errors.
> You didn't mention these errors, so my impression is that you are missing
> the error reports contained in the log file.
>
> Lilypond specifically mentions having trouble with \addlyrics:
>
>>  warning: cannot find Voice `uniqueContext1'
>>
> This does not help you directly but it shows that Lilypond agrees with you
> that something is wrong.
>
> A search for this warning might have led to the user archive thread
> http://lists.gnu.org/archive/**html/lilypond-user/2007-08/**msg00070.html
> Here they are referring to the docs for version 2.10.
>
> The docs for version 2.12 warns about this limitation, just above the
> section "Working with lyrics and variables" in the Notation Reference
> http://lilypond.org/doc/v2.12/**Documentation/user/lilypond/**index#index
>
>   The command \addlyrics cannot handle polyphony settings.
>>
>
>
> So \addlyrics may guess right if it is used once, e.g just in BasCTwo. But
> it is not meant for anything more complicated. This aspect is handled in
> more detail in the 2.14 docs. (N.B. later Lilypond versions have better
> docs!)
>
>
> For an idea how to organise things using \lyricsto instead see
> http://lsr.dsi.unimi.it/LSR/**Item?id=362This
>  is for version 2.14 but it works for version 2.12 too.
>
> Cheers, Robin
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Change page number during score

[David Nalesnik]

Hi,

>
> > You're right, there's no way to set the page number, AFAIK :(
>

Well, no simple way.  It is possible to write a markup function to
increment the page numbers at a certain point.

I retooled a function which does Roman numeral page numbers here:
http://www.mail-archive.com/lilypond-user@gnu.org/msg73483.html

The function below takes a range of "skipped pages."  So, the example
"skips" page numbers 2 through 5.  Thus, the score will be numbered 1, 6,
7...

Hope this helps,
David

%
 \version "2.17.29" % should work with 2.16 too

#(define-markup-command (skip-page-number-range layout props arg)
(number-list?)
  (let ((page-number (chain-assoc-get 'page:page-number props -1)))
(interpret-markup layout props
  (if (>= page-number (car arg))
  (number->string (+ page-number (1+ (- (cadr arg) (car arg)
  (chain-assoc-get 'page:page-number-string props -1)


\paper {
  print-first-page-number = ##t
  print-page-number = ##t
  oddHeaderMarkup = \markup
\fill-line {
  " "
  \on-the-fly #not-first-page \fromproperty #'header:instrument
  \on-the-fly #print-page-number-check-first \skip-page-number-range
#'(2 5)
}
  evenHeaderMarkup = \markup
\fill-line {
  \on-the-fly #print-page-number-check-first \skip-page-number-range
#'(2 5)
  \on-the-fly #not-first-page \fromproperty #'header:instrument
  " "
  }
}

\score {
  \new Staff {
\repeat unfold 6 {
  s1
  \pageBreak
}
  }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Automatic beaming in vocal cadenzas

[Colin Campbell]

On 13-10-26 02:39 AM, David Kastrup wrote:

Colin Campbell  writes:


After wrestling with a transcription of an unmetered piece by Mark
Sirett (Thou Shalt Know Him), my wife and I were going bonkers trying
to get lyrics aligned to the notes. The piece has no time signature
and bars of uneven length. We tried using \cadenzaOn to get the
unmetered aspect, but the fundamental problem is that \cadenzaOn turns
off autoBeam, which in turn means that manual beaming in a cadenza
creates unwanted melismata. We worked out that taking out the
\cadenzaOn(Off) would help, and getting rid of a default time
signature is easy enough, by removing the engraver in the Staff
context and entering explicit bars ( \bl = \bar "|" ), but we had to
beam by hand and we still got barlines in unexpected (i.e. we didn't
enter them!) places. The last pieces of the puzzle were to go to the
Layout block and a Score context, to set automaticBars = ##f , then
back to our \global for a time signature of 1/4 so that autoBeam would
group eighths in twos, Bob's your uncle, and so to bed!

Can you check out issue 3633?  The principal problem I see is that auto
beaming will likely not occur at all, and I don't really see how this
can be avoided in unmetered music.  But unless you switch autoBeam off
explicitly, manual beams should not create melismata.



I D/L the patch and applied it, ran make with no errors. I then 
re-compiled my sample file, but saw no difference in behaviour.  I 
gather your patch should have prevented the melisma created in a cadenza 
by manual beaming, but they still seem to happen. Am I testing the 
proper thing, in the proper way? Admittedly, my problem comes from a 
fairly narrow set of conditions: an entirely unmetered piece, with 
lyrics, and needing to be beamed for singers.


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

RE: Placing clef change *after* bar line

[Mark Stephen Mrotek]

Jelle,

I have encountered this a few times and with the help of others have used
this:

http://www.lilypond.org/doc/v2.16/Documentation/internals/breakalignment

Mark

-Original Message-
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
Jelle
Sent: Saturday, October 26, 2013 8:46 AM
To: lilypond-user@gnu.org
Subject: Re: Placing clef change *after* bar line

  umpquanet.com> writes:

> 
> Most times, placing a clef change before a bar line is appropriate.  
> When combined with repeated sections though, sometimes it is clearer 
> to place a clef change after the bar line.


I've read a couple of ways to get a clef after instead of before a bar line.
I had the same question, for a sax-orchestra score with percussion intro,
and I came to yet another solution, with less code. It may have other flaws
and I have only been working with lilypond for a couple of days now, but I'd
say it's simple enough to give it a try.

Below you'll find an excerpt with a bit of the context. The main point is
line 3 in sopranoSax with the " s \set Staff.forceClef = ##t " 
By using "s" you avoid defining and blending out a short-time bar, in fact
you change nothing in the time (4/4 in this case) at all.

In context:

\version "2.14.2"

clave = \drummode 
  {  \numericTimeSignature \time 4/4  
{ \repeat volta 2 
  { \override NoteHead #'style = #'cross 
  \mark \markup \smaller \italic { \hspace #35.0 "intro rumba clave" }  
  cl4  r8 cl r4 r8 cl   r4 cl cl r   cl r8 cl r4 r8 cl   r4 cl cl r
  \revert NoteHead #'style  
  }
}
  } 
  
sopranoSax = \notemode { 
 \relative c'' { 
 s \set Staff.forceClef = ##t  %forcing a clef to be inserted
 \key g \major  
\time 4/4  %if you want the time to be repeated here
 a4 r2.
}
}

sopranoSaxPart = \new Staff { 
\once \override Staff.Clef #'stencil = ##f  %no treble clef at the
beginning
\clave \sopranoSax }

\score { 
 << 
 \sopranoSaxPart 
 >>
}



___
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: Extra Bar

[Mark Stephen Mrotek]

Mr. Morley,

Thank you for your reply and the instructions. They work. And I know what
they do. Yet I do not know why they would be necessary since both of the
alternative endings are "complete," i.e., have the correct mensuration to
match either the measure repeated to and the measure that follows.

Mark

-Original Message-
From: Thomas Morley [mailto:thomasmorle...@gmail.com] 
Sent: Friday, October 25, 2013 4:15 PM
To: Mark Stephen Mrotek
Cc: lilypond-user
Subject: Re: Extra Bar

2013/10/26 Mark Stephen Mrotek :
> Hello,
>
>
>
> What should be done to get rid of the unnecessary bar in the second
ending?
>
>
>
> Thank you.
>
>
>
> Mark

Hi,

not sure whether it's the best way, though, changing 'right' to the code
below seems to work:

right = \relative c'' {
  \global

  \repeat volta 2 {
  \partial 16*5 ees16 ees8. ees16 |
  \times 2/3 {
  bes'8 c bes aes g f ees-2 [ d f ] } | }
  \alternative { { \set Timing.measureLength = #(ly:make-moment 7/16) ees4
r8. }
 { \set Timing.measureLength = #(ly:make-moment 3/8) ees4 r8
} }


  \repeat volta 2 {
  \key ees \minor
  bes8^\markup { \large \bold { "Trio" } } ( [ ges ees ] ) |
  d4 ( ees8 ) bes' ( ges ees-2 ) |


}


Cheers,
  Harm


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

Re: Change page number during score

[Hwaen Ch'uqi]

Greetings Ed,
  I realize this is quite the crude solution, and perhaps you have
already considered it, but could you not simply include unneeded
measures at that particular area, inserting a \pageBreak between each?
At the page with the correct page number, you could then resume your
actual music, using \set Score.currentBarNumber to adjust the measure
number accordingly. Finally, you can remove the unneeded pages and
replace them with those containing your graphic notation. This can be
easily done with a tool like pdftk.
  I hope this helps.
Hwaen Ch'uqi


On 10/26/13, Trevor Daniels  wrote:
>
> Ed, you wrote Saturday, October 26, 2013 11:15 AM
>
>> Hi Trevor, sorry all I can see in those pages is how to change the bar
>> number? I'm after a way to change the page number, much like the \set
>> Score.currentBarNumber but for pages. I'm assuming that because LP
>> paginates
>> things near the end of the engraving process then such a command like
>> this
>> doesn't exist, but I live in hope of being wrong!
>
> Sorry - I shouldn't dash off a reply before breakfast, at least not without
> reading the post carefully.
>
> You're right, there's no way to set the page number, AFAIK :(
>
> Trevor
> ___
> 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: Placing clef change *after* bar line

[Jelle]

  umpquanet.com> writes:

> 
> Most times, placing a clef change before a bar line is
> appropriate.  When combined with repeated sections though,
> sometimes it is clearer to place a clef change after the bar
> line. 


I've read a couple of ways to get a clef after instead of before a bar line.
I had the same question, for a sax-orchestra score with percussion intro,
and I came to yet another solution, with less code. It may have other flaws
and I have only been working with lilypond for a couple of days now, but I'd
say it's simple enough to give it a try.

Below you'll find an excerpt with a bit of the context. The main point is
line 3 in sopranoSax with the " s \set Staff.forceClef = ##t " 
By using "s" you avoid defining and blending out a short-time bar, in fact
you change nothing in the time (4/4 in this case) at all.

In context:

\version "2.14.2"

clave = \drummode 
  {  \numericTimeSignature \time 4/4  
{ \repeat volta 2 
  { \override NoteHead #'style = #'cross 
  \mark \markup \smaller \italic { \hspace #35.0 "intro rumba clave" }  
  cl4  r8 cl r4 r8 cl   r4 cl cl r   cl r8 cl r4 r8 cl   r4 cl cl r
  \revert NoteHead #'style  
  }
}
  } 
  
sopranoSax = \notemode { 
 \relative c'' { 
 s \set Staff.forceClef = ##t  %forcing a clef to be inserted
 \key g \major  
\time 4/4  %if you want the time to be repeated here
 a4 r2.
}
}

sopranoSaxPart = \new Staff { 
\once \override Staff.Clef #'stencil = ##f  %no treble clef at the
beginning
\clave \sopranoSax }

\score { 
 << 
 \sopranoSaxPart 
 >>
}



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

Re: lilypond-book: warning: cannot detect textwidth from LaTeX

[Marcos Press]

Absolutly right.
You really have some perception powers :)
I was not telling lilypond-book to use xelatex.
Now it detects the marging and the result is much much better than before :)

Thanks.


2013/10/25 Marc Hohl 

> Am 25.10.2013 15:45, schrieb Marcos Press:
>
>> Hi all!
>>
>>
>> Every time I run lilypond-book I have the same first three lines:
>>
>> 
>> Running `pdflatex' on file `/tmp/tmpk95zdA.tex' to detect default page
>> settings.
>>
>> lilypond-book: warning: Unable to auto-detect default settings:
>>
>> lilypond-book: warning: cannot detect textwidth from LaTeX
>> 
>>
>> Then, it ends up rendering the hole thing completly, nearly without
>> problem except my ouns wich are allways there. :)
>>
>> Is there any way to solve these auto-detection?
>>
>
> Without knowing how your file looks like and how you invoke
> lilybond-book, there is probably some extrasensory perception
> needed ;-)
>
>
>  If not, how can I tell lilypond-book the textwidth of my tex file? And
>> how can I know it?
>>
>
> I had a similar case some time ago due to the fact that I used
> xelatex for processing the file but forgot to tell lilypond-book
> to use xelatex for auto-detection.
>
>
>
> __**_
> 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: lilypond-book: warning: cannot detect textwidth from LaTeX

[Marcos Press]

You hit one spot :)
I'm trying to put examples in multicolumn. Which I resolve in doing two
thing.

Ono is to put the example in the three columns.
The other is to end the table, put the example centered and then start the
table again.
A time ago I been trying the \multicolumn command but I couldn't remember
why I couldn't use it :)

About my orginal question, Marc answer was the reason I keep getting that
warning.


2013/10/25 Urs Liska 

>  Am 25.10.2013 15:45, schrieb Marcos Press:
>
>   Hi all!
>
>  Every time I run lilypond-book I have the same first three lines:
>
> 
> Running `pdflatex' on file `/tmp/tmpk95zdA.tex' to detect default page
> settings.
>
> lilypond-book: warning: Unable to auto-detect default settings:
>
> lilypond-book: warning: cannot detect textwidth from LaTeX
> 
>
>  Then, it ends up rendering the hole thing completly, nearly without
> problem except my ouns wich are allways there. :)
>
>  Is there any way to solve these auto-detection?
>  If not, how can I tell lilypond-book the textwidth of my tex file? And
> how can I know it?
>
>
> I don't know.
> But this is one of the reasons I *want* to improve my musicexamples
> package. When all this isn't run from an external Python script but from
> within the running latex it is of course possible to detect the textwidth.
> It's even possible to access the _currently_ active textwidth. For example
> if you want to place examples in multicolumn text.
>
> In general it says lilypond-book will _try_ to guess the correct width but
> will fail in some circumstances.
>
> For determining the textwidth manually maybe this will help you:
> http://stackoverflow.com/questions/1168551/printing-out-latex-variables
>
> HTH
> Urs
>
>
>  Thanks!
>
>  Marcos
>
>
> ___
> lilypond-user mailing 
> listlilypond-user@gnu.orghttps://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Change page number during score

[Trevor Daniels]

Ed, you wrote Saturday, October 26, 2013 11:15 AM

> Hi Trevor, sorry all I can see in those pages is how to change the bar
> number? I'm after a way to change the page number, much like the \set
> Score.currentBarNumber but for pages. I'm assuming that because LP paginates
> things near the end of the engraving process then such a command like this
> doesn't exist, but I live in hope of being wrong!

Sorry - I shouldn't dash off a reply before breakfast, at least not without
reading the post carefully.

You're right, there's no way to set the page number, AFAIK :(

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

Re: Automatic beaming in vocal cadenzas

[David Kastrup]

"Phil Holmes"  writes:

> - Original Message - 
> From: "David Kastrup" 
> To: 
> Sent: Saturday, October 26, 2013 4:49 AM
> Subject: Re: Automatic beaming in vocal cadenzas
>
>
>> Matthew Collett  writes:
>>
>>> On 26/10/2013, at 4:10 pm, Colin Campbell  wrote:
>>>
 We tried using \cadenzaOn to get the unmetered aspect, but the
 fundamental problem is that \cadenzaOn turns off autoBeam, which in
 turn means that manual beaming in a cadenza creates unwanted
 melismata.
>>>
>>> So turn the autobeaming back on.  I often use the combination of
>>> \cadenzaOn \autoBeamOn', for exactly this reason.
>>
>> Huh.  Sounds like LilyPond does something wrong here.  Should \cadenzaOn
>> leave autobeaming alone?  Would this have more effects than different
>> melismata?
>
> I don't think autobeaming in cadenzas makes any sense at all, given
> that they're free time.

No disagreement from myself with that, but you might want to look at
http://lists.gnu.org/archive/html/bug-lilypond/2010-09/msg00455.html>
and surroundings.  In my opinion, that does not make sense since within
a cadenza, you don't even know where the current beats synchronize and
often the given note durations are approximate, a cadenza usually
allowing for heavy rubato.

Of course, that's partly my opinion because of "technicalities"
(issue 3633 does not leave any information required for autobeaming).

-- 
David Kastrup

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

Re: Automatic beaming in vocal cadenzas

[Phil Holmes]

- Original Message - 
From: "David Kastrup" 

To: 
Sent: Saturday, October 26, 2013 4:49 AM
Subject: Re: Automatic beaming in vocal cadenzas



Matthew Collett  writes:


On 26/10/2013, at 4:10 pm, Colin Campbell  wrote:


We tried using \cadenzaOn to get the unmetered aspect, but the
fundamental problem is that \cadenzaOn turns off autoBeam, which in
turn means that manual beaming in a cadenza creates unwanted
melismata.


So turn the autobeaming back on.  I often use the combination of
\cadenzaOn \autoBeamOn', for exactly this reason.


Huh.  Sounds like LilyPond does something wrong here.  Should \cadenzaOn
leave autobeaming alone?  Would this have more effects than different
melismata?

--
David Kastrup



I don't think autobeaming in cadenzas makes any sense at all, given that 
they're free time.


--
Phil Holmes 



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

Re: Automatic beaming in vocal cadenzas

[Phil Holmes]

- Original Message - 
From: "Matthew Collett" 

To: "Colin Campbell" 
Cc: "LilyPond User Group" 
Sent: Saturday, October 26, 2013 4:28 AM
Subject: Re: Automatic beaming in vocal cadenzas



On 26/10/2013, at 4:10 pm, Colin Campbell  wrote:

We tried using \cadenzaOn to get the unmetered aspect, but the 
fundamental problem is that \cadenzaOn turns off autoBeam, which in turn 
means that manual beaming in a cadenza creates unwanted melismata.


So turn the autobeaming back on.  I often use the combination of 
'\cadenzaOn \autoBeamOn', for exactly this reason.


Best wishes,
Matthew


To avoid beams producing melismata, use:

\set melismaBusyProperties = #'(melismaBusy slurMelismaBusy tieMelismaBusy 
completionBusy)



--
Phil Holmes 



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

Re: Defining bar checks in a variable

[David Kastrup]

Mike Solomon  writes:

> On Oct 14, 2013, at 6:20 PM, David Kastrup  wrote:
>
>> David Kastrup  writes:
>> 
>>> Mike Solomon  writes:
>>> 
 hmm…for a slightly less minimal example, I'm trying to do:
 
 bc = |
 
 foo = { \bc \bar "|" }
 
 {
 a a a a a \foo
 }
 
 Any ideas on how to accomplish that?
>>> 
>>> Simple.  First fix
>>> http://code.google.com/p/lilypond/issues/detail?id=2392>

Fixed.

> Probably a separate issue, but when I do:
>
> \version "2.17.30"
>
> mybarcheck = { | }
>
> { a \mybarcheck }
>
> I get
>
> GNU LilyPond 2.17.30
> Processing `foo.ly'
> Parsing...
> Interpreting music...
> foo.ly:3:14: warning: barcheck failed at: 1/4
> mybarcheck = 
>  { | }
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> Layout output to `foo.ps'...
> Converting to `./foo.pdf'…
>
> Is there anyway to have the parser spit out the line number of the bar
> check failure instead of the line number of the definition of the
> variable?

No, and it would imply that if you wrote
violinI = { 500 bars of music }

\new Staff { \violinI }

that error messages would point to \new Staff only.  As long as the
input origin is a file location rather than a _stack_ of file locations,
one has to make a choice, and this choice makes a lot of sense.  Now you
are lucky since if you really need it, you can write

mybarcheck = #(define-music-function (parser location) () #{ { | } #})
{ a \mybarcheck }

and get what you want.  That's issue 3153 I think, as of 2.17.13.

-- 
David Kastrup

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

Re: voice two but yet stems up towards end of piece with addlyrics

[Robin Bannister]

Annette Kusma wrote: 


 Is this a bug or am I missing something?



The example you supplied did not run without errors. 

You didn't mention these errors, so my impression is that 
you are missing the error reports contained in the log file. 



Lilypond specifically mentions having trouble with \addlyrics: 
 warning: cannot find Voice `uniqueContext1' 
This does not help you directly but it shows that 
Lilypond agrees with you that something is wrong. 



A search for this warning might have led to the user archive thread 
http://lists.gnu.org/archive/html/lilypond-user/2007-08/msg00070.html
Here they are referring to the docs for version 2.10. 



The docs for version 2.12 warns about this limitation, just above the section 
"Working with lyrics and variables" in the Notation Reference 
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/index#index


 The command \addlyrics cannot handle polyphony settings. 



So \addlyrics may guess right if it is used once, e.g just in BasCTwo. 
But it is not meant for anything more complicated. 
This aspect is handled in more detail in the 2.14 docs. 
(N.B. later Lilypond versions have better docs!)



For an idea how to organise things using \lyricsto instead see 
http://lsr.dsi.unimi.it/LSR/Item?id=362 
This is for version 2.14 but it works for version 2.12 too. 



Cheers, 
Robin


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

Re: Change page number during score

[EdBeesley]

Trevor Daniels wrote
> EdBeesley wrote Saturday, October 26, 2013 12:25 AM
> 
>> I was just wondering is there an easier way to get around this, for
>> example
>> a bit of code that will 'reset' the page count to the number I want, e.g:
>> "set current page number to 7"
> 
> There is.  See
> 
> http://www.lilypond.org/doc/v2.17/Documentation/notation/special-rhythmic-concerns#time-administration
> 
> for the background and
> 
> http://www.lilypond.org/doc/v2.17/Documentation/notation/bars#bar-numbers
> 
> for this explicit facility.
> 
> Trevor
> ___
> lilypond-user mailing list

> lilypond-user@

> https://lists.gnu.org/mailman/listinfo/lilypond-user

Hi Trevor, sorry all I can see in those pages is how to change the bar
number? I'm after a way to change the page number, much like the \set
Score.currentBarNumber but for pages. I'm assuming that because LP paginates
things near the end of the engraving process then such a command like this
doesn't exist, but I live in hope of being wrong!




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Change-page-number-during-score-tp152936p152956.html
Sent from the User mailing list archive at Nabble.com.

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

Re: Change page number during score

[Trevor Daniels]

EdBeesley wrote Saturday, October 26, 2013 12:25 AM

> I was just wondering is there an easier way to get around this, for example
> a bit of code that will 'reset' the page count to the number I want, e.g:
> "set current page number to 7"

There is.  See

http://www.lilypond.org/doc/v2.17/Documentation/notation/special-rhythmic-concerns#time-administration

for the background and

http://www.lilypond.org/doc/v2.17/Documentation/notation/bars#bar-numbers

for this explicit facility.

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

Re: Defining bar checks in a variable

[Mike Solomon]

On Oct 14, 2013, at 6:20 PM, David Kastrup  wrote:

> David Kastrup  writes:
> 
>> Mike Solomon  writes:
>> 
>>> hmm…for a slightly less minimal example, I'm trying to do:
>>> 
>>> bc = |
>>> 
>>> foo = { \bc \bar "|" }
>>> 
>>> {
>>> a a a a a \foo
>>> }
>>> 
>>> Any ideas on how to accomplish that?
>> 
>> Simple.  First fix
>> http://code.google.com/p/lilypond/issues/detail?id=2392>
> 
> See also
> http://code.google.com/p/lilypond/issues/detail?id=3610>
> 
> -- 
> David Kastrup
> 

Probably a separate issue, but when I do:

\version "2.17.30"

mybarcheck = { | }

{ a \mybarcheck }

I get

GNU LilyPond 2.17.30
Processing `foo.ly'
Parsing...
Interpreting music...
foo.ly:3:14: warning: barcheck failed at: 1/4
mybarcheck = 
 { | }
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `foo.ps'...
Converting to `./foo.pdf'…

Is there anyway to have the parser spit out the line number of the bar check 
failure instead of the line number of the definition of the variable?

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

Feedback for Frescobaldi's Preview Mode

[Urs Liska]

Hi,

now the new Preview Modes in Frescobaldi have been available for a while 
I would like to have some feedback. I know they aren't 'production 
quality' yet and I want to improve them.


So please report any inconveniences, bugs or additional wishes.
For example I know that 'Display grob anchors' and 'Display grob names' 
don't behave well together, but any feedback on similar issues is welcome.


Best
Urs

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

Re: Automatic beaming in vocal cadenzas

[David Kastrup]

Colin Campbell  writes:

> After wrestling with a transcription of an unmetered piece by Mark
> Sirett (Thou Shalt Know Him), my wife and I were going bonkers trying
> to get lyrics aligned to the notes. The piece has no time signature
> and bars of uneven length. We tried using \cadenzaOn to get the
> unmetered aspect, but the fundamental problem is that \cadenzaOn turns
> off autoBeam, which in turn means that manual beaming in a cadenza
> creates unwanted melismata. We worked out that taking out the
> \cadenzaOn(Off) would help, and getting rid of a default time
> signature is easy enough, by removing the engraver in the Staff
> context and entering explicit bars ( \bl = \bar "|" ), but we had to
> beam by hand and we still got barlines in unexpected (i.e. we didn't
> enter them!) places. The last pieces of the puzzle were to go to the
> Layout block and a Score context, to set automaticBars = ##f , then
> back to our \global for a time signature of 1/4 so that autoBeam would
> group eighths in twos, Bob's your uncle, and so to bed!

Can you check out issue 3633?  The principal problem I see is that auto
beaming will likely not occur at all, and I don't really see how this
can be avoided in unmetered music.  But unless you switch autoBeam off
explicitly, manual beams should not create melismata.

-- 
David Kastrup


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

Re: Automatic beaming in vocal cadenzas

[Matthew Collett]

On 26/10/2013, at 6:58 pm, Colin Campbell  wrote:

 We tried using \cadenzaOn to get the unmetered aspect, but the
 fundamental problem is that \cadenzaOn turns off autoBeam, which in
 turn means that manual beaming in a cadenza creates unwanted
 melismata.
> 
> The aim was to get vocal style beaming in beats, so that two eights are 
> beamed and four eights are beamed in twos. Using \cadenzaOn and autoBeamon 
> gives instrumental beaming, so three eights are beamed together, rather than 
> as a single eigth and a beamed pair. 

If you switch the autobeaming back on, then using manual beams won't create 
melismata.

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

Re: id's for svg elements

[Mike Solomon]

On Oct 26, 2013, at 10:51 AM, Bric  wrote:

> can someone help scope out the task of adding semantically sound unique 
> identifiers to the svg elements?
> 
> Such that the id bears info on, at least, the staff, (maybe bar), and 
> note/chord index (consecutive integer index, for instance)
> 
> the "output-svg.scm" script has various routines to build the svg 
> elements/tags/attributes, and these are implemented by other scm scripts 
> (e.g., "round-filled-box")...
> 
> Before I spend hours (days?) trying to figure out the precise subroutine 
> chain/tree , perhaps someone can lead me directly to the top-level code that 
> feeds lilypond info into these scripts? And whereby one can feed 
> staff/movement info, along with note index down to the final svg output?
> 
> And is this a realistic goal, I wonder?  I think even just identifying CLASS 
> information in the "id=..." attribute might help. Just to set the stem "rect" 
> apart from the staff line "rect", for instance, would already be an 
> improvement; but, of course, I prefer even more specifics, as I described 
> above.
> 
> thanks.
> 

There is a grob property that is called "id" that is called far downstream 
(right when the backends are getting the last information about the grobs 
before drawing them).  That means that, if you create a callback for this 
property, you can feed it all sorts of info.  The resulting SVG object will be 
wrapped in a group with this id.

For example…

\version "2.17.30"

#(define (note-number grob)
  (string-concatenate
(list
  "NoteHead/"
  (number->string
(ly:pitch-semitones
  (ly:event-property (ly:grob-property grob 'cause) 'pitch))

\relative c' {
  \override NoteHead.id = #note-number
  a
}

Then

lilypond -dbackend=svg yourfilename.ly

Then open the SVG and look for id="NoteHead/-3"

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

id's for svg elements

[Bric]

can someone help scope out the task of adding semantically sound unique 
identifiers to the svg elements?


Such that the id bears info on, at least, the staff, (maybe bar), and 
note/chord index (consecutive integer index, for instance)


the "output-svg.scm" script has various routines to build the svg 
elements/tags/attributes, and these are implemented by other scm scripts 
(e.g., "round-filled-box")...


Before I spend hours (days?) trying to figure out the precise subroutine 
chain/tree , perhaps someone can lead me directly to the top-level code 
that feeds lilypond info into these scripts? And whereby one can feed 
staff/movement info, along with note index down to the final svg output?


And is this a realistic goal, I wonder?  I think even just identifying 
CLASS information in the "id=..." attribute might help. Just to set the 
stem "rect" apart from the staff line "rect", for instance, would 
already be an improvement; but, of course, I prefer even more specifics, 
as I described above.


thanks.


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