Re: Any thoughts on how to automatically avoid rest collisions in polyphonic music?

Urs, > I think you're missing something: the double backslash construct that David > uses already creates the voices as \voiceOne \voiceTwo etc. implicitly. So if > that isn't good enough engraving-wise then setting it manually should not > make any difference Thanks for that. I had become

Re: Any thoughts on how to automatically avoid rest collisions in polyphonic music?

> I'm not sure about using << ... // ... >> to make it "infinitely expandable"... wouldn't the output become illegible past 4 voices? If you're mechanically generating these parts, I'd say keep it to 2 voices per staff, which is least problematic. In theory, it should be easy for the program to

Re: Any thoughts on how to automatically avoid rest collisions in polyphonic music?

Am 26. Oktober 2016 16:56:16 GMT-07:00, schrieb "H. S. Teoh" : >On Wed, Oct 26, 2016 at 04:52:18PM -0700, David Bellows wrote: >> > Do you use the \voiceOne, \voiceTwo, \voiceThree commands in the >> > generated parts? Sometimes those can help, by rendering rests for >>

Re: Any thoughts on how to automatically avoid rest collisions in polyphonic music?

On Wed, Oct 26, 2016 at 04:52:18PM -0700, David Bellows wrote: > > Do you use the \voiceOne, \voiceTwo, \voiceThree commands in the > > generated parts? Sometimes those can help, by rendering rests for > > each voice separately. Not sure if this is the solution you're > > looking for, though. >

Re: Any thoughts on how to automatically avoid rest collisions in polyphonic music?

> Do you use the \voiceOne, \voiceTwo, \voiceThree commands in the generated parts? Sometimes those can help, by rendering rests for each voice separately. Not sure if this is the solution you're looking for, though. I had been but keeping it all straight and making the process infinitely

Re: Any thoughts on how to automatically avoid rest collisions in polyphonic music?

On Wed, Oct 26, 2016 at 02:10:49PM -0700, David Bellows wrote: > I have a large computer music generating program that I'm creating. > One of the things it does is generate sheet music for the generated > music using Lilypond. It works really well. > > When dealing with one or two voices

Any thoughts on how to automatically avoid rest collisions in polyphonic music?

So sorry everyone, I forgot to use reply all. Here's my latest message: Ok, this all might be confusing so I've attached two example pngs showing the collisions. The use_rest.png file uses rests like c'4/rest while no_rest just uses regular rests like r4. I know I could manipulate these manually

Re: Any thoughts on how to automatically avoid rest collisions in polyphonic music?

Hi David, > When dealing with one or two voices everything's fine. But I just > added a musical style that uses three voices and collisions with rests > are occurring. [more stuff on avoiding rest collisions snipped] You may wish to look at http://lsr.di.unimi.it/LSR/Snippet?id=336 Th

Any thoughts on how to automatically avoid rest collisions in polyphonic music?

or just run through it again with different data there might be collisions again. These are blunt tools that cannot be used selectively on certain notes -- it's either all or nothing. So what I'm wondering is if there are any other strategies people have for automatically avoiding rest collisions

rest collisions warning but no collision

Hi all, running this code (also in attachment) results in a warning saying there are too many colliding rests. I don't see where the collision could be though, the warning shouldn't be there in my opinion. I know it renders fine, but still, I prefer results without warnings, it makes me worry that

Re: rest collisions warning but no collision

To: lilypond-user@gnu.org Sent: Friday, September 05, 2014 2:53 PM Subject: rest collisions warning but no collision Hi all, running this code (also in attachment) results in a warning saying there are too many colliding rests. I don't see where the collision could be though, the warning

Re: rest collisions warning but no collision

and lower voices. -- Phil Holmes - Original Message - *From:* bart deruyter bart.deruy...@gmail.com *To:* lilypond-user@gnu.org *Sent:* Friday, September 05, 2014 2:53 PM *Subject:* rest collisions warning but no collision Hi all, running this code (also in attachment) results

Re: rest collisions warning but no collision

They are effectively colliding, which you've avoided by moving them as pitched rests. Hmm. `Effectively colliding' isn't user friendly... Is there a way to avoid this warning if pitched rests really don't collide? Werner ___ lilypond-user

rest collisions

Hi all, I've got an issue here with rests. I have three voice score with rests in the second voice . There simply is not enough space for the rest between the highest and the lowest note, so I tried to move the rest to the left using: \once \override Rest #'extra-offset = #'(-1 . 0) Is there a

Re: rest collisions

On 01/07/14 19:50, bart deruyter wrote: Hi all, I've got an issue here with rests. I have three voice score with rests in the second voice . There simply is not enough space for the rest between the highest and the lowest note, so I tried to move the rest to the left using: \once \override

Re: rest collisions

Am 01.07.2014 20:50, schrieb bart deruyter: Hi all, I've got an issue here with rests. I have three voice score with rests in the second voice . There simply is not enough space for the rest between the highest and the lowest note, so I tried to move the rest to the left using: \once

Re: rest collisions

I was about to start writing short version to show how it is in code when I read your mail. I tried it out and it worked! Thank you very much :-) Grtz, Bart http://www.bartart3d.be/ On facebook https://www.facebook.com/pages/BartArt3D/169488999795102 On Twitter

Re: rest collisions

Hi, In those type of cases, when not enough room for offsets, I also use : { %\once\set fontSize = #-2 %or \once\teeny a'4\rest } Cheers, Pierre 2014-07-01 21:34 GMT+02:00 bart deruyter bart.deruy...@gmail.com: I was about to start writing short version to show how it is in code when

Re: rest collisions

Thanks for the tip, I might use that. grtz, Bart http://www.bartart3d.be/ On facebook https://www.facebook.com/pages/BartArt3D/169488999795102 On Twitter https://twitter.com/#%21/Bart_Issimo On Identi.ca http://identi.ca/bartart3d On Google+ https://plus.google.com/u/0/b/116379400376517483499/