Re: Shifting notes horizontally

On Wed, Dec 19, 2012 at 05:24:01PM +1100, Nick Payne wrote: > On 19/12/12 15:52, Jim Long wrote: > > Is there a way to insert empty horizontal staff space at an > > arbitrary point in a particular voice? Yes, much like \hspace in > > markup. > > Use Staff.Rest #'extra-spacing-width: > > \version

Re: Resolving "cannot resolve rest collision: rest direction not set" warnings

On Wed, Dec 19, 2012 at 08:44:29AM +0100, Arle Lommel wrote: > Hi all, I am working on the same score that spawned discussion about stem > lengths and now have another, hopefully less controversial, question. > > I keep getting warnings like the following when I run Lilypond: > > warning: cannot

Re: Resolving "cannot resolve rest collision: rest direction not set" warnings

Thanks Jim. Your example solved it for me. I thought I was using explicit voices because I declared voices using a "\new Voice {}" construct, but I hadn't named them explicitly, and that seems to be the difference. Now I am seeing "real" warnings rather than these ones about rests and that helps

Re: Tempo sliding over key signature changes

Hi Mike, > My guess is that this is a bug with multi-measure rests. Yes — I think this is [at least related to] a known bug: Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://

Re: Resolving "cannot resolve rest collision: rest direction not set" warnings

Actually, I spoke too soon. It looked like they were gone, but when I started checking, my score was severely messed up in other ways by what I had done. When I reverted and then tried again, the rest collision errors were back, so the apparent absence was likely unrelated to the change in voice

Re: Resolving "cannot resolve rest collision: rest direction not set"warnings

Arle Lommel wrote Wednesday, December 19, 2012 9:41 AM > For what it is worth, all of the conflicts seem to be between the voices > "ornamentsVoice" and "rightVoice," both of which often have simultaneous > rests. The rests from rightVoice are placed automatically (and correctly) in > the prop

Re: Resolving "cannot resolve rest collision: rest direction not set"warnings

Here is a minimal (real) example of one measure that generates four warnings. As you can see the rests in the third voice are simply invoked as "r4" while the ones in the second voice are given explicit locations (which, again, I want to do in this case). (I realize the notation convention here

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

Please re-read the section in the NR concerning explicit use of voices: http://lilypond.org/doc/v2.16/Documentation/notation/multiple-voices. By doing it this way: \parallelMusic #'(ossia ornaments righthand lefthand pedal) { s2. | \voiceOne \tiny c''4\rest c8\rest^\pp \ottava #1 d'32[ a' d

Re: Aligning multiple verses to alternative notes in the melody

Two options I can see: \once \override NoteColumn #'ignore-collision = ##t or use lyricmode: { \new Staff << \override Score.LyricText #'self-alignment-X = #LEFT \new Voice = "Upper" { \voiceOne a'4 b'2 a'4 g'4 } \new Lyrics \lyricsto "Upper" { to you, my love } \ne

VoltaBracket flipped vertically

I'm trying to get VoltaBrackets to appear both above and below the Score. I've come up with the solution below, which works quite well, but I'd like to get the volta text to appear inside the bracket, as it does when VoltaBracket #'direction is not altered. Is there a way to do this? I can't see

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

Thanks much. This is what I was missing. I had thought, somehow, from reading that portion (a number of times) that the voiceOne and voiceTwo bits were automatically and implicitly assigned and did not realize that they have to be explicitly invoked. Earliest suggestions got me part of the way t

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

Just realized another issue. Is there a way to tell Lilypond where in the staff a voice’s rests should go? While Phil’s guidance to use \voiceOne and \voiceTwo took care of the warnings, it also means that the rests from one of the voices that had previously been centered in the staff now sit lo

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

Arle Lommel writes: > Thanks much. This is what I was missing. I had thought, somehow, from > reading that portion (a number of times) that the voiceOne and > voiceTwo bits were automatically and implicitly assigned and did not > realize that they have to be explicitly invoked. They are in voice

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

- Original Message - From: "Arle Lommel" To: Cc: "Phil Holmes" ; "Trevor Daniels" Sent: Wednesday, December 19, 2012 3:28 PM Subject: Re: Resolving "cannot resolve rest collision: rest direction notset"warnings Just realized another issue. Is there a way to tell Lilypond where in

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

Thanks. The (probably deserved) chastisement aside, finding things in the documentation does require knowing how to find them. Finding even obvious things in the documentation isn't always easy if you don't already know what to look for. As I had spent some time earlier looking for this and not

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

I use the PDF documentation, and looked in the index under "rests, collisions of", having decided it would be good to look at the index for "rests". The index is your friend. This gave me the syntax for MultiMeasureRest and it was easy to adapt. -- Phil Holmes - Original Message -

Markup and stencil formatting questions

Dear all, I cannot seem yet to get certain textual output rendered the way I intend. Here are the questions I still have: 1. How can I combine header fields without adding whitespace between header properties? I'm referring to snippets as: \fromproperty #'header:composer (\fromproperty #'header

Counters in markup (LSR 543) - getcounter addition

Hi all, I propose to extend LSR snippet 543 (counters in markup, http://lsr.dsi.unimi.it/LSR/Snippet?id=543) by adding a "getcounter" command that does NOT increment a counter when called (as opposed to the current "counter" command): #(define-markup-command (getcounter layout props name) (string

Re: Writing to the console (debug info)

2012/12/18 Olivier Biot > In Frescobaldi you can choose the verbose output option in the custom run > > > Hi Federico, > > I could not find where this can be set. There's no "custom run" > configuration setting on my version (2.0.8) of Frescobaldi. It's the menu LilyPond>Engrave (custom) I have

Re: Markup and stencil formatting questions

shutterfreak wrote > Dear all, > > I cannot seem yet to get certain textual output rendered the way I intend. > Here are the questions I still have: > > > 1. How can I combine header fields without adding whitespace between > header > properties? I'm referring to snippets as: > > \fromproperty

Re: Markup and stencil formatting questions

On Wed, Dec 19, 2012 at 5:54 PM, Eluze wrote: > shutterfreak wrote > > 1. How can I combine header fields without adding whitespace between > > header > > properties? I'm referring to snippets as: > > > > \fromproperty #'header:composer (\fromproperty #'header:opus) > > > > Using \concat doesn't

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

Arle Lommel writes: > Thanks. > > The (probably deserved) chastisement aside, finding things in the > documentation does require knowing how to find them. There is a table of contents, there is an index, there is plain text search. The index contains "rest, specifying vertical position". There

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

On 19/12/2012 17:04, David Kastrup wrote: >> Finding even obvious things in the documentation isn't always easy if >> you don't already know what to look for. As I had spent some time >> earlier looking for this and not found it, I can only state that it >> wasn't also terribly easy for me to find

MetronomeMark alignment after break

In the example below, "Tempo II" is aligned differently from "Tempo I," and the only difference between the two that I can see is that there's a full measure rest in the top staff immediately after "Tempo II" occurs. How can I get "Tempo II" to align the same as "Tempo I?" I've tried playing aro

Re: MetronomeMark alignment after break

On 19 December 2012 20:00, Daniel Rosen wrote: > In the example below, "Tempo II" is aligned differently from >"Tempo I," and the only difference between the two that I can see is > that there's a full measure rest in the top staff immediately after > "Tempo II" occurs. How can I get "Tempo II" to

RE: MetronomeMark alignment after break

> -Original Message- > From: Xavier Scheuer [mailto:x.sche...@gmail.com] > Sent: Wednesday, December 19, 2012 2:20 PM > To: Daniel Rosen > Cc: lilypond-user@gnu.org; Mike Solomon > Subject: Re: MetronomeMark alignment after break > > On 19 December 2012 20:00, Daniel Rosen wrote: > > In t

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

On 20/12/12 02:54, Arle Lommel wrote: Thanks. The (probably deserved) chastisement aside, finding things in the documentation does require knowing how to find them. Finding even obvious things in the documentation isn't always easy if you don't already know what to look for. As I had spent so

Re: MetronomeMark alignment after break

Hi Daniel, > Any ideas as to how to work around it in the meantime? This hack (can't remember who did this for me?) seems to work. Hope it helps! Kieren. \layout { \context { \Score \override MetronomeMark #'after-line-breaking = #(lambda (grob) (and ;; proba

RE: MetronomeMark alignment after break

> -Original Message- > From: Kieren MacMillan [mailto:kieren_macmil...@sympatico.ca] > Sent: Wednesday, December 19, 2012 2:38 PM > To: Daniel Rosen > Cc: Xavier Scheuer; lilypond-user@gnu.org > Subject: Re: MetronomeMark alignment after break > > Hi Daniel, > > > Any ideas as to how to w

Re: MetronomeMark alignment after break

Daniel Rosen gmail.com> writes: > > From: Xavier Scheuer [mailto:x.scheuer gmail.com] > > > > This is indeed a bug. > > Mike encountered it as recently as yesterday. > > > > He is currently fixing it, enjoy! > > http://code.google.com/p/lilypond/issues/detail?id=1263 > > Any ideas as to how

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

David, Sorry for the long response, but maybe it will be useful for project insiders to see how someone mostly on the outside experiences the documentation and the ways for finding things. I think part of the problem is the sheer volume and being able to recognize what is directly relevant. Fo

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

Reinhold, The position there is a perfect example of where the search probably should be for the main documentation. The way you have it actively encourages use. The way the main site has it discourages use unless someone has a big enough screen to spot it. > Does an AJAX search field (current

Re: Markup and stencil formatting questions

On Wed, Dec 19, 2012 at 5:26 PM, Olivier Biot wrote: > Dear all, > > I cannot seem yet to get certain textual output rendered the way I intend. > Here are the questions I still have: > > > 2. Why does a strut have a nonzero width? Can it be used and set to zero? > Maybe it has zero width, but bec

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

On Wed, Dec 19, 2012 at 7:34 PM, Reinhold Kainhofer wrote: > On 19/12/2012 17:04, David Kastrup wrote: > >> Finding even obvious things in the documentation isn't always easy if > >> you don't already know what to look for. As I had spent some time > >> earlier looking for this and not found it, I

Re: Markup and stencil formatting questions

shutterfreak wrote > 2. Why does a strut have a nonzero width? Can it be used and set to zero? > Maybe it has zero width, but because of some internal processing every > markup element automatically gets white space glued to it (this may > explain > my first question in part too). you can find the

RE: MetronomeMark alignment after break

> -Original Message- > From: Keith OHara [mailto:k-ohara5...@oco.net] > > The workaround is in the link above. Generally, bug-trackers try to include a > workaround. > Oh, I didn't see it the first time. Thanks. DR ___ lilypond-user mailing

Re: Markup and stencil formatting questions

On Wed, Dec 19, 2012 at 11:09 PM, Eluze wrote: > shutterfreak wrote > > 2. Why does a strut have a nonzero width? Can it be used and set to zero? > > Maybe it has zero width, but because of some internal processing every > > markup element automatically gets white space glued to it (this may > >

Re: Markup and stencil formatting questions

shutterfreak wrote > I don't know, all I wanted was to "fix" the baseline skips at start and > end > of line-wrapped text sections by adding this "construct" at start and end > of each "text section". Probably this is not eh way to go. I'm not sure this meets your needs: -use \vspace #number -set

Custom Time Signature

Dear LilyPond experts, I would like to display the time signature 4/2 as two struck Cs next to one another (no 'plus' sign), as in the score here: http://petrucci.mus.auth.gr/imglnks/usimg/4/4d/IMSLP39751-PMLP02062-Schubert-Impromptu-Op90No3.pdf The best I can do with \compoundtime is to get it t

Re: Resolving "cannot resolve rest collision: rest direction notset"warnings

>> So how could this have been made easier? > > Does an AJAX search field (currently simply greps through the index) > help in this regard (the input field in the upper left corner): > > http://kainhofer.com/~lilypond/Documentation/notation/ > Wow, that search is nice! I would appreciate it on t

Re: Custom Time Signature

Kevin Patrick Barry wrote > Dear LilyPond experts, > > I would like to display the time signature 4/2 as two struck Cs next to > one > another (no 'plus' sign), as in the score here: > http://petrucci.mus.auth.gr/imglnks/usimg/4/4d/IMSLP39751-PMLP02062-Schubert-Impromptu-Op90No3.pdf the quickest

Documentation (was Re: Resolving "cannot resolve rest collision: rest direction notset"warnings)

Hi Arle, I can understand your difficulties with the documentation. Some propositions how to make it easier: 1.) A "visual index": I am currently working on an example staff where the objects are labelled and if you click on an object it points you to the corresponding documentation. I don't kno

Documentation (was Re: Resolving "cannot resolve rest collision: rest direction notset"warnings)

>> So how could this have been made easier? Hi, some more comments on the manuals website (rearrangement basically): http://www.lilypond.org/website/manuals.html Distinguishing between "regular use" and "infrequent use" is a bit arbitrary to me. I very very rarely use "Usage". But I need the "i

Re: zigzag staffline

2012/12/18 Gagi Petrovic : > Hi David, yes indeed. A zigzag or a trillspan-kind-of line would also > suffice. > > Thank you for your tip, seems like it's time for me to dive more deeply into > this matter. When i look at the code i understand it only roughly, i will > need some time for this. So if

Re: Custom Time Signature

2012/12/20 Kevin Patrick Barry : > Dear LilyPond experts, > > I would like to display the time signature 4/2 as two struck Cs next to one > another (no 'plus' sign), Hi, how about: \version "2.16.1" doubledTimeSignature = \override Score.TimeSignature #'stencil = #(lambda (grob) (let* ((s

note heads sharing a beam, some stems without heads

Any thoughts on how to accomplish this notation?: Christopher Brooks violinist 925 Virginia Avenue Lancaster, PA 17603 717-291-9123 cbro...@orpheus-acoustics.com <>___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.