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

2016-10-26 Thread David Bellows
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?

2016-10-26 Thread David Bellows
> 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?

2016-10-26 Thread Urs Liska
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: Tie settings question

2016-10-26 Thread David Wright
On Wed 26 Oct 2016 at 23:14:20 (+0200), Michael Gerdau wrote: > > please excuse this sidenote: It seems that your mailing client doesn’t > > handle metadata correctly, so each reply of yours is technically > > regarded as starting a new thread. It would be good if you could find a > > way (or can

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

2016-10-26 Thread 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 > > 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?

2016-10-26 Thread David Bellows
> 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?

2016-10-26 Thread H. S. Teoh
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

Re: Problem controlling page numbers in bookparts

2016-10-26 Thread Kieren MacMillan
Hi all, >> I'm trying to control the page numbering for bookparts in a score. >> In particular I want each bookpart start with page #1 and omit it >> on the first page. Therefor I'm adding a paper block inside bookpart >> and set >>first-page-number = #1 >>print-first-page-number = ##f >>

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

2016-10-26 Thread David Bellows
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: Problem controlling page numbers in bookparts

2016-10-26 Thread Thomas Morley
2016-10-26 15:29 GMT+02:00 Michael Gerdau : > Hi list, > > I'm trying to control the page numbering for bookparts in a score. > In particular I want each bookpart start with page #1 and omit it > on the first page. Therefor I'm adding a paper block inside bookpart > and set >

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

2016-10-26 Thread Michael Gerdau
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 That should

Re: Tie settings question

2016-10-26 Thread Michael Gerdau
> please excuse this sidenote: It seems that your mailing client doesn’t > handle metadata correctly, so each reply of yours is technically > regarded as starting a new thread. It would be good if you could find a > way (or can someone help) to fix this. Not only may others have thread > view

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

2016-10-26 Thread David Bellows
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 everything's fine. But I just added a musical style that uses three voices and

Re: polytempi in Lilypond - is it possible?

2016-10-26 Thread David Wright
On Tue 25 Oct 2016 at 21:48:35 (+0200), Bálint Laczkó wrote: > I would like to engrave a polytempical musical material in LilyPond. I am a > newbie to this software so I am still learning the basics, but I saw quite > a few mentions in some forum comments here and there, that LilyPond support >

Re: Google Code-In

2016-10-26 Thread Carl Sorensen
On 10/26/16 9:28 AM, "Urs Liska" wrote: > > >Am 26. Oktober 2016 06:14:42 GMT-07:00, schrieb Kieren MacMillan >: >>Hi Urs, >> >>> Anyone here saying that applying for this >>https://developers.google.com/open-source/gci/ would make sense for

Re: Tie settings question

2016-10-26 Thread David Nalesnik
On Wed, Oct 26, 2016 at 9:59 AM, Karol Majewski wrote: > OK, I resign. But stil I don't get something in the code you posted yesterday: > > % > > raiseTie = > #(lambda (grob) > (let* ((ties (ly:grob-array->list (ly:grob-object grob 'ties))) >

Re: Google Code-In

2016-10-26 Thread Urs Liska
Am 26. Oktober 2016 06:14:42 GMT-07:00, schrieb Kieren MacMillan : >Hi Urs, > >> Anyone here saying that applying for this >https://developers.google.com/open-source/gci/ would make sense for >LilyPond? > >Is there an obvious reason why it wouldn’t make sense? >(I don’t

Re: Tie settings question

2016-10-26 Thread Simon Albrecht
Hello Karol, please excuse this sidenote: It seems that your mailing client doesn’t handle metadata correctly, so each reply of yours is technically regarded as starting a new thread. It would be good if you could find a way (or can someone help) to fix this. Not only may others have thread

Re: Tie settings question

2016-10-26 Thread Karol Majewski
OK, I resign. But stil I don't get something in the code you posted yesterday: % raiseTie = #(lambda (grob) (let* ((ties (ly:grob-array->list (ly:grob-object grob 'ties))) (notehead (ly:spanner-bound (car ties) LEFT)) (stem (ly:grob-object notehead 'stem))

Problem controlling page numbers in bookparts

2016-10-26 Thread Michael Gerdau
Hi list, I'm trying to control the page numbering for bookparts in a score. In particular I want each bookpart start with page #1 and omit it on the first page. Therefor I'm adding a paper block inside bookpart and set first-page-number = #1 print-first-page-number = ##f (see the attached

[no subject]

2016-10-26 Thread Paulo Rios Filho
Cvc VP ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Google Code-In

2016-10-26 Thread Kieren MacMillan
Hi Urs, > Anyone here saying that applying for this > https://developers.google.com/open-source/gci/ would make sense for LilyPond? Is there an obvious reason why it wouldn’t make sense? (I don’t know enough about that program to tell.) Thanks, Kieren. Kieren

Re: polytempi in Lilypond - is it possible?

2016-10-26 Thread Alexander Kobel
On 2016-10-26 14:11, Bálint Laczkó wrote: Hi Alexander, Thanks for the fast reply! "Essentially, you will have one "master staff" that stays true to time, everything else is scaled to fit." -- so I can change the spacing(?) of the staves individually in reference to an original spacing? So if

Re: Tie settings question

2016-10-26 Thread David Nalesnik
On Wed, Oct 26, 2016 at 6:20 AM, Karol Majewski wrote: > OK, David, so let's move one square backward and try to use staff-position. > The following code does compile but doesn't do what I want. Perhaps what I'm > trying to achieve is just not possible. I don't think it is.

Re: polytempi in Lilypond - is it possible?

2016-10-26 Thread Bálint Laczkó
Hi Alexander, Thanks for the fast reply! "Essentially, you will have one "master staff" that stays true to time, everything else is scaled to fit." -- so I can change the spacing(?) of the staves individually in reference to an original spacing? So if staff1 is in default spacing, then can

Re: Augmentation dot positioning

2016-10-26 Thread Carl Sorensen
On 10/26/16 3:28 AM, "David Kastrup" wrote: > >Su why is a symbol needed? Symbols always require some secret lookup >mechanism. Why not just use a list here? When the list needs to be >calculated, it can be a callback, right? That was my hope, but I couldn't make it work.

Re: Tie settings question

2016-10-26 Thread Karol Majewski
OK, David, so let's move one square backward and try to use staff-position. The following code does compile but doesn't do what I want. Perhaps what I'm trying to achieve is just not possible. %% tweakTie = #(lambda (grob) (let* ((ties (ly:grob-array->list

Re: Augmentation dot positioning

2016-10-26 Thread David Kastrup
Carl Sorensen writes: > On 10/25/16 8:57 AM, "Chris Yate" wrote: > >>Hi Carl, >>Firstly, thanks for your work on this! >>At a quick glance, the only two situations that need dots-limit =2 are >>#11 and #23. > > Yes, those were my two cases as well. > >>A

Re: polytempi in Lilypond - is it possible?

2016-10-26 Thread Alexander Kobel
On 2016-10-25 21:48, Bálint Laczkó wrote: Hey Everybody, I would like to engrave a polytempical musical material in LilyPond. [...] Now ideally I would like to see this engraved in a proportional way, so that the lower staff has a wider spacing, and so the notes are distributed in the two