Re: Cues and Rest Collision Warning

Thank you, Jean, for these very detailed explanations about how the voices are to be used -- and the alternate way to achieve the same result.  I hugely appreciate your input. Archer On 14/03/2023 19:09, Jean Abou Samra wrote: Le mardi 14 mars 2023 à 14:36 +, Archer Endrich a écrit : Th

Re: Cues and Rest Collision Warning

Le mardi 14 mars 2023 à 14:36 +, Archer Endrich a écrit : > Thank you Xavier and Jean.  The warnings have disappeared and the > MMrest with #-6 is perfectly placed on the E line of the staff. > The revised version looks like this: > \score { > >   \new Staff { >   

Re: Cues and Rest Collision Warning

Thank you Xavier and Jean.  The warnings have disappeared and the MMrest with #-6 is perfectly placed on the E line of the staff. The revised version looks like this: \score {   \new Staff {     \time 4/4     \clef treble     g'1^\markup{Fl 1} |   <<   { \voiceTwo   \once

Re: Cues and Rest Collision Warning

Le mardi 14 mars 2023 à 13:13 +0100, Xavier Scheuer a écrit : > On Tue, 14 Mar 2023 at 12:55, Archer Endrich > <[archer...@gmail.com](mailto:archer...@gmail.com)> wrote: > > > > The reason I used c'1\rest was so that the rest would be placed on the > > bottom line of the Staff.  I would real

Re: Cues and Rest Collision Warning

On Tue, 14 Mar 2023 at 12:55, Archer Endrich wrote: > > The reason I used c'1\rest was so that the rest would be placed on the > bottom line of the Staff. I would really like a centered rest (R1) but > this automatically places it on the 2nd line from the top, which does > conflict with the music

Cues and Rest Collision Warning

the definition outside \book made it all work perfectly. I have another problem with a very simple use of cues, using code as in the Notation Manual.  This is my example: %CuesandRestCollisions.ly \version "2.22.1" \header {   title = "Cues and Rest Collision Warning" }

Re: MMR vs Rest collision

Hi Phil, 2017-09-22 11:17 GMT-04:00 Phil Holmes : > http://lilypond.org/doc/v2.19/Documentation/notation/writing-rests#full-measure-rests > See "Positioning multi-measure rests" Thanks for the pointer. I should have mentioned that I'm aware that you can set them manually. But I'm still curious as

Re: MMR vs Rest collision

- Original Message - From: "Pierre-Luc Gauthier" To: "lilypond-user" Sent: Friday, September 22, 2017 3:58 PM Subject: MMR vs Rest collision Hi there, Why is it that rests avoid collisions and MMRs do not? Also, is there a way to tell the MMR to go as far as

MMR vs Rest collision

Hi there, Why is it that rests avoid collisions and MMRs do not? Also, is there a way to tell the MMR to go as far as needed to be bellow voice one? MWE : \version "2.21.0" << \repeat unfold 4 {c8 d} \\ r1 >> << \repeat unfold 4 {c8 d} \\ R1 >> Thank you -- Pierre-Luc Gauthier \ve

RE: Cannot resolve rest collision: rest direction not set

Joseph, You are welcome. Mark -Original Message- From: Joseph N. Srednicki [mailto:jos.sredni...@verizon.net] Sent: Tuesday, February 09, 2016 5:00 AM To: 'Brian Barker' ; 'Mark Stephen Mrotek' ; lilypond-user@gnu.org Subject: RE: Cannot resolve rest collision: re

RE: Cannot resolve rest collision: rest direction not set

. Thanks again. Joe Srednicki -Original Message- From: Brian Barker [mailto:b.m.bar...@btinternet.com] Sent: Monday, February 8, 2016 10:37 PM To: lilypond-user@gnu.org Cc: Joseph N. Srednicki Subject: Re: Cannot resolve rest collision: rest direction not set At 19:26 08/02/2016 -0500

Re: Cannot resolve rest collision: rest direction not set

At 19:26 08/02/2016 -0500, Joseph N. Srednicki wrote: I receive the warning "cannot resolve rest collision: rest direction not set" when I compile the code listed below. Is there anything else that I can do to avoid the warning or am I overlooking something? You need to add

Cannot resolve rest collision: rest direction not set

Hello: I receive the warning "cannot resolve rest collision: rest direction not set" when I compile the code listed below. I tried to follow the recommendation in the attached post to avoid the warning: http://lilypond.1069038.n5.nabble.com/Resolving-quot-cannot-resolve-rest-

Multi-Measure Rest Collision

adenzaOn section, unless there is a way to get the same look while fixing the problem via a workaround. Thanks! Carl -- View this message in context: http://lilypond.1069038.n5.nabble.com/Multi-Measure-Rest-Collision-tp186873.html Sent from the User mailing list archive at Nabble.com. ___

Re: Multi-Measure Rest Collision

> Abraham > > > > > > View this message in context: Re: Multi-Measure Rest Collision > > Sent from the User mailing list archive at Nabble.com. > > > > ___ > > l

Re: Multi-Measure Rest Collision

> d'4^\markup { \left-column { \circle 3 } } > d'4^\markup { \left-column { \circle 4 } } > d'4^\markup { \left-column { \circle 5 } } > d'4^\markup { \left-column { \circle 6 } } > } > } > \newSpacingSection > \revert Score.SpacingSpanner.spacing-in

Re: Multi-Measure Rest Collision

\newSpacingSection \revert Score.SpacingSpanner.spacing-increment \compressFullBarRests R2.*26 R2.*13 \bar "|." } HTH, Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Multi-Measure-Rest-Collision-tp186873p186874.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: Cannot resolve rest collision: rest direction not set

appdata/local/temp/frescobaldi-ywvkwd/tmpivikeh/document.ly:1 > : warning: no \version statement found, please add > > \version "2.18.2" > > for future compatibility > > Interpreting music... > > Preprocessing graphical objects... > > Finding the ideal number

Cannot resolve rest collision: rest direction not set

document.ly:1 <0>: warning: no \version statement found, please add \version "2.18.2" for future compatibility Interpreting music... Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... c:/users/chris/appdata/local/te

Re: Unresolvable rest collision?

- View this message in context: http://lilypond.1069038.n5.nabble.com/Unresolvable-rest-collision-tp169585p169768.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/m

Re: Unresolvable rest collision?

Am 27.12.2014 08:27, schrieb Jayaratna: Just a few days ago I had to correct the following incipit: In the original the longae rests at the beginning of the piece indicate that the Modus Longarum is imperfect, thus:

Re: Unresolvable rest collision?

.com/file/n169753/dentestui02.png> -- View this message in context: http://lilypond.1069038.n5.nabble.com/Unresolvable-rest-collision-tp169585p169753.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-

Re: Unresolvable rest collision?

tter of design balance, but can be meaningful per se. A -- View this message in context: http://lilypond.1069038.n5.nabble.com/Unresolvable-rest-collision-tp169585p169680.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-use

Re: Unresolvable rest collision?

On Dec 23, 2014, at 5:41 AM, Phil Holmes wrote: > According to typesetting rules (see Behind Bars by Elaine Gould, for example) > rests should remain consistently placed with respect to staff lines. This > means that when they are moved, they should be moved in 2 pitch increments, > not one.

Re: Unresolvable rest collision?

Am 23. Dezember 2014 11:41:38 MEZ, schrieb Phil Holmes : >- Original Message - >From: "Ted Lemon" >To: "Kieren MacMillan" >Cc: "Lilypond-User Mailing List" >Sent: Monday, December 22, 2014 2:37 PM >Subject: Re: Unresolvable rest colli

Re: Unresolvable rest collision?

- Original Message - From: "Ted Lemon" To: "Kieren MacMillan" Cc: "Lilypond-User Mailing List" Sent: Monday, December 22, 2014 2:37 PM Subject: Re: Unresolvable rest collision? On Dec 22, 2014, at 9:26 AM, Kieren MacMillan wrote: \new Voice = "b

Re: Unresolvable rest collision?

On Dec 22, 2014, at 9:55 AM, Kieren MacMillan wrote: > Unless you tell her otherwise, Lily will move things around to avoid > collisions, maintain minimum padding values, etc. > > Hope this helps! You have been tremendously helpful--thank you! I'm typesetting this for my dad, who was really

Re: Unresolvable rest collision?

Hi Ted, > The placement of the rests isn't exactly what I want Maybe use a \tweak, then? > I am a bit puzzled that even with explicit marking, I don't actually have > that much control over where the head of the rest lands. Unless you tell her otherwise, Lily will move things around to avoid

Re: Unresolvable rest collision?

On Dec 22, 2014, at 9:26 AM, Kieren MacMillan wrote: > \new Voice = "bass-a" { \voiceOne \relative c \vba } > \new Voice = "bass-b" { \voiceTwo \relative c \vbb } > \new Voice = "bass-c" { \voiceThree \relative c \vbc } Thanks, that fixed it. The placement of the rests isn't

Re: Unresolvable rest collision?

Hi Ted, > Can anyone see what it is that I am doing wrong here? Personally, I would start with “you’re using \parallelMusic” and “you’re using \relative”… ;) But seriously: 1. Use r8 instead of (e.g.) c’’8\rest, and letting Lilypond make her [generally excellent] placement choices. 2. Use ex

Unresolvable rest collision?

I'm getting a puzzling error message when I try to typeset the following lilypond source file. The error is being reported in measure 17 in the first bass clef voice (\vba). The error that's reported is "romanza.ly:143:47: warning: cannot resolve rest collision: rest di

Re: More "cannot resolve rest collision" warnings

Daniel, you wrote Sunday, December 30, 2012 8:28 PM > I figured it out: it's the use of \oneVoice in the lower voice. > The problem is solved by leaving it as \voiceTwo and explicitly > specifying the rest positions like I'm already doing in the upper voice. > A little tedious, but it works a

RE: More "cannot resolve rest collision" warnings

ginal Message- > From: Daniel Rosen > Sent: Sunday, December 30, 2012 3:21 PM > To: 'Trevor Daniels'; lilypond-user@gnu.org > Subject: RE: More "cannot resolve rest collision" warnings > > OK... but that doesn't fix my problem. I get the same thing when I

RE: More "cannot resolve rest collision" warnings

mber 30, 2012 3:19 PM > To: Daniel Rosen; lilypond-user@gnu.org > Subject: Re: More "cannot resolve rest collision" warnings > > > Daniel, you wrote Sunday, December 30, 2012 8:04 PM > > > > In the example below, I'd like to use the music that appears a

Re: More "cannot resolve rest collision" warnings

> > document.ly:6:7: warning: cannot resolve rest collision: rest direction not > set > g16[ > f\rest f] | > > How do I make this go away? Take out the \\. It is unnecessary when you are creating the Voice contexts explicitly. Have a look at this again: http://

More "cannot resolve rest collision" warnings

In the example below, I'd like to use the music that appears after the barline because it lines up the rests visually with their respective voices. It looks exactly the way I want it to, but I'm getting this warning: document.ly:6:7: warning: cannot resolve rest collision: rest dir

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

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

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: 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: 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: 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

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: 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

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

--- Original Message - From: Arle Lommel To: Phil Holmes Cc: lilypond-user@gnu.org ; Trevor Daniels Sent: Wednesday, December 19, 2012 3:54 PM Subject: Re: Resolving "cannot resolve rest collision: rest direction notset"warnings Thanks. The (probably deserved) chastis

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

- 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 issu

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

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

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

lilypond-user@gnu.org Sent: Wednesday, December 19, 2012 11:03 AM Subject: Re: Resolving "cannot resolve rest collision: rest direction notset"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 s

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 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

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

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

ths and now have another, hopefully less controversial, question. >> >> I keep getting warnings like the following when I run Lilypond: >> >> warning: cannot resolve rest collision: rest direction not set > > I've run into this or a similar problem before. > &g

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

> > warning: cannot resolve rest collision: rest direction not set I've run into this or a similar problem before. Cultivate the habit of using separate, explicit voice constructs: \new Voice = "upper" \relative c'' { ... } % upper

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

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 resolve rest collision: rest direction not set They appear from

Re: rest collision

fiëé visuëlle wrote: I need the alternate voice only in some places. This may be implying that you don't want to set the main voice as \voiceOne, but rather keep it as (the implicit) \oneVoice. If this rest collision behaviour is the only thing that is bothering you, try the foll

Re: rest collision

Am 2009-10-10 um 19:57 schrieb James E. Bailey: please consider this snippet: \context Staff = StOne << \time 3/4 \context Voice = "main" { \relative c' { e4 r e } } \context Voice = "secondary" {

Re: rest collision

On 10.10.2009, at 17:42, fiëé visuëlle wrote: Ahoi, please consider this snippet: \context Staff = StOne << \time 3/4 \context Voice = "main" { \relative c' { e4 r e } } \context Voice = "secondary" {

rest collision

Ahoi, please consider this snippet: \context Staff = StOne << \time 3/4 \context Voice = "main" { \relative c' { e4 r e } } \context Voice = "secondary" { \relative c' {

Re: rest collision in tabstaff

On 2/20/07, hernan gonzalez <[EMAIL PROTECTED]> wrote: > Hi Hernan, > > That warning shows up when you have rests in two different voices > which coincide. Here's a minimal example. > > %%% BEGIN %%% > > \version "2.11.18" > > \new Staff << >\new Voice { > r4 >} >\new Voice { >

Re: rest collision in tabstaff

On 2/19/07, Hernan <[EMAIL PROTECTED]> wrote: I don't understand why this simple .ly file gives me the warning (a lot ; i copy here only one measure) which states (twice) : "warning: can't resolve rest collision: r

rest collision in tabstaff

I don't understand why this simple .ly file gives me the warning (a lot ; i copy here only one measure) which states (twice) : "warning: can't resolve rest collision: rest direction not set " %%% top = \tra

Re: Problem with rest collision

#x27; g' a' b' c'' d'' e'' f'' g'' a''} \\ {r8 r r r r r r r r r r r r r r r } >> } Jefferson 2006/4/19, Jefferson dos Santos Felix <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>: I tr

RE: Problem with rest collision

On 4/18/06 10:31 PM, "Jefferson dos Santos Felix" <[EMAIL PROTECTED]> wrote: > \version "2.8.1" > \score > { > << > {a8 d' f' a'} \\ {r8 c' d' r} >>> > } Try this it seems to work here. \version "2.8.1" \score { << {a8 d' f' a'} \\ {d8\rest c' d' r} >> } Section 6.1.6 makes it clear tha

Re: Problem with rest collision

27;'} \\   {r8 r r r  r  r  r  r  r  r  r   r   r   r   r   r  }  >> } Jefferson2006/4/19, Jefferson dos Santos Felix <[EMAIL PROTECTED]>: I try to remove the rest collision of the example below, but no success: \version "2.8.1" \score {  <<   {a8 d' f' a&#

Problem with rest collision

I try to remove the rest collision of the example below, but no success: \version "2.8.1" \score {  <<   {a8 d' f' a'} \\ {r8 c' d' r}  >> } I try to use this:  \override Score.RestCollision #'minimum-distance = #1.75 but the collision pers

Re: Rest Collision Bug

o bottom voice === What more do you need to add to handle rest collision? You've already done the hard part. Now *please* do the easy part. daveA -- The only technical exercises for guitar which are worthy of the instrument c

Re: Rest Collision Bug

On Sunday 23 January 2005 03.16, David Raleigh Arnold wrote: > There is a rule which is quite obscure now about collision of > rests and notes when there are three or four voices on a staff. If > there is not enough space between the upper and lower voices for a > rest for an inside voice, that re

Rest Collision Bug

There is a rule which is quite obscure now about collision of rests and notes when there are three or four voices on a staff. If there is not enough space between the upper and lower voices for a rest for an inside voice, that rest is placed *before* a stem, *always*, never tucked in under the low

Re: rest collision

On Tuesday 13 April 2004 20:12, Roland Goretzki wrote: > Hello list, hello Stan, > > You wrote: > > In the attached example, eighth rests collide with note stems. I'd > > appreciate suggestions about how to make it look better. > > > > The code for the measure(s) is > > > > 8 | > > <<{d8\rest [

Re: rest collision

Roland, Thank you for your reply. I'm very appreciative of the work which has gone into lilypond to make it so flexible, and of the kindness of those on the list to beginners such as I. Stan On Apr 13, 2004, at 7:12 PM, Roland Goretzki wrote: Hello list, hello Stan, You wrote: In the attach

Re: rest collision

Hello list, hello Stan, You wrote: > In the attached example, eighth rests collide with note stems. I'd > appreciate suggestions about how to make it look better. > > The code for the measure(s) is > > 8 | > <<{d8\rest [ c8\rest ]}\\{4 }>> | > %%% measure 86 > 8 Give the following

rest collision

(Lilypond v.2.2.0, Mac OSX v10.3.3) In the attached example, eighth rests collide with note stems. I'd appreciate suggestions about how to make it look better. The code for the measure(s) is 8 | <<{d8\rest [ c8\rest ]}\\{4 }>> | %%% measure 86 8 The \rest coding was used to brin

Rest collision

Hello, Doesn't rest collision take in account ties? I have a somewhat complex polyphonic piece in which there are two voices by staff, and the rest are place right in the middle of ties. The solution I'm going to resort to is the very useful vertical rest positioning system

Rest Collision

t rest *must* stay in the middle no matter what. If >[..] Yes, the rest-collision code is broken; it doesn't look at where the rests are coming from, merely what other stem directions are found at that point. Patches are appreciated. -- Han-Wen Nienhuys | [EMAIL PROTECTED]| h

Rest Collision

I cannot begin to tell you how disappointed I was to finish this simple two part arrangement, which does considerable violence to Haendel but is made very easy for beginners, to find that the augmentation dots are not down when \stemDowm is in effect. What possible reason could there be not to