Le 22/11/2022 à 16:51, Abraham Lee a écrit :
Ok, I can confirm that it works as expected. Thanks, again, Jean! No
doubt I will be using this quite a lot over the coming months.
Now added as https://lsr.di.unimi.it/LSR/Item?id=1154
(I didn't bother "downgrading" it to 2.22 because 2.24
On Mon, Nov 21, 2022 at 11:21 PM Abraham Lee
wrote:
>
>
> On Mon, Nov 21, 2022 at 6:36 PM Jean Abou Samra
> wrote:
>
>> Hi,
>>
>>
>> Le 20/11/2022 à 21:50, Kieren MacMillan a écrit :
>> >> Kieren, you've got to try this out! It will blow your mind!
>> > I just took Jean’s example, and compared
On Mon, Nov 21, 2022 at 6:36 PM Jean Abou Samra wrote:
> Hi,
>
>
> Le 20/11/2022 à 21:50, Kieren MacMillan a écrit :
> >> Kieren, you've got to try this out! It will blow your mind!
> > I just took Jean’s example, and compared the output with and without the
> \include step… Truly astonishing.
>
Hi,
Le 20/11/2022 à 21:50, Kieren MacMillan a écrit :
Kieren, you've got to try this out! It will blow your mind!
I just took Jean’s example, and compared the output with and without the
\include step… Truly astonishing.
(I haven’t tried it with my Real World Scores™, but can’t wait to do
Hi all,
> Kieren, you've got to try this out! It will blow your mind!
I just took Jean’s example, and compared the output with and without the
\include step… Truly astonishing.
(I haven’t tried it with my Real World Scores™, but can’t wait to do so!)
> Jean, seriously, this is amazing!
Hi Jean,
> This is a vast refinement of the initial \autoMove function
I love that you generate “magic” solutions with such facility, and that you
still care enough to respect existing parameters (e.g., minimum-distance) and
include new useful ones (e.g., details.strength).
> - As said in a
On Sat, Nov 19, 2022 at 6:59 PM Abraham Lee
wrote:
>
>
> On Sat, Nov 19, 2022 at 6:50 PM Abraham Lee
> wrote:
>
>>
>>
>> On Sat, Nov 19, 2022 at 5:16 PM Jean Abou Samra
>> wrote:
>>
>>>
>>>
>>> Le 20 nov. 2022 à 01:11, Abraham Lee a
>>> écrit :
>>>
>>> Still running into compiler errors. I
On Sat, Nov 19, 2022 at 6:50 PM Abraham Lee
wrote:
>
>
> On Sat, Nov 19, 2022 at 5:16 PM Jean Abou Samra
> wrote:
>
>>
>>
>> Le 20 nov. 2022 à 01:11, Abraham Lee a
>> écrit :
>>
>> Still running into compiler errors. I figured my version was just out of
>> date, but after downloading 2.23.81,
On Sat, Nov 19, 2022 at 5:16 PM Jean Abou Samra wrote:
>
>
> Le 20 nov. 2022 à 01:11, Abraham Lee a
> écrit :
>
> Still running into compiler errors. I figured my version was just out of
> date, but after downloading 2.23.81, I still get the following log:
>
>
Le 20 nov. 2022 à 01:11, Abraham Lee a écrit :Still running into compiler errors. I figured my version was just out of date, but after downloading 2.23.81, I still get the following log:%<-SNIP---Starting lilypond.exe 2.23.81 [tricky-lyrics.ly]...Processing
On Sat, Nov 19, 2022 at 4:34 PM Abraham Lee
wrote:
>
>
> On Sat, Nov 19, 2022 at 3:23 PM Jean Abou Samra
> wrote:
>
>> Le 17/11/2022 à 23:02, Jean Abou Samra a écrit :
>> > Le 17/11/2022 à 23:01, Werner LEMBERG a écrit :
>> > But how do you take into account the constraints from lyrics
On Sat, Nov 19, 2022 at 3:23 PM Jean Abou Samra wrote:
> Le 17/11/2022 à 23:02, Jean Abou Samra a écrit :
> > Le 17/11/2022 à 23:01, Werner LEMBERG a écrit :
> > But how do you take into account the constraints from lyrics here?
> > That is the whole problem.
> They should be
Le 17/11/2022 à 23:02, Jean Abou Samra a écrit :
Le 17/11/2022 à 23:01, Werner LEMBERG a écrit :
But how do you take into account the constraints from lyrics here?
That is the whole problem.
They should be completely ignored.
In that case, it should be completely doable even in Scheme now.
(I
Jean Abou Samra writes:
> Le 17/11/2022 à 23:01, Werner LEMBERG a écrit :
> But how do you take into account the constraints from lyrics here?
> That is the whole problem.
They should be completely ignored.
>>> In that case, it should be completely doable even in Scheme now.
>>> (I
Le 17/11/2022 à 23:01, Werner LEMBERG a écrit :
But how do you take into account the constraints from lyrics here?
That is the whole problem.
They should be completely ignored.
In that case, it should be completely doable even in Scheme now.
(I started writing some code yesterday in response
>>> But how do you take into account the constraints from lyrics here?
>>> That is the whole problem.
>>
>> They should be completely ignored.
>
> In that case, it should be completely doable even in Scheme now.
> (I started writing some code yesterday in response to Abraham that
> does
Le 17/11/2022 à 08:06, Werner LEMBERG a écrit :
* In the first pass, typeset everything without stuff marked for a
follow-up pass.
Namely, typeset all notes?
Yes.
But how do you take into account the constraints from lyrics here?
That is the whole problem.
They should be completely
>> * In the first pass, typeset everything without stuff marked for a
>> follow-up pass.
>
> Namely, typeset all notes?
Yes.
> But how do you take into account the constraints from lyrics here?
> That is the whole problem.
They should be completely ignored. My idea was to make the first
Jean Abou Samra writes:
> Le 16/11/2022 à 10:05, Werner LEMBERG a écrit :
>> I draw my idea from LaTeX, for example handling multi-page tables (see
>> the 'longtable' package).
>
>
> I looked at the documentation
>
Le 16/11/2022 à 10:05, Werner LEMBERG a écrit :
I draw my idea from LaTeX, for example handling multi-page tables (see
the 'longtable' package).
I looked at the documentation
(https://distrib-coffee.ipsl.jussieu.fr/pub/mirrors/ctan/macros/latex/required/tools/longtable.pdf).
The footnote on
>> I think that such a fine granularity of automatic lyric adjustment
>> would only be possible with LilyPond doing (at least) two
>> typesetting passes, if at all.
>
> Can you elaborate? What would it help with?
I draw my idea from LaTeX, for example handling multi-page tables (see
the
> Le 16 nov. 2022 à 09:36, Werner LEMBERG a écrit :
>
> I think that such a fine granularity of automatic lyric adjustment
> would only be possible with LilyPond doing (at least) two typesetting
> passes, if at all.
Can you elaborate? What would it help with?
> In general, implementing
> The main problematic measures are 5, 7, and 9/10. My tweaks are
> good bandaids, but not ideal, nor perfect, but they get the job
> done.
I think that such a fine granularity of automatic lyric adjustment
would only be possible with LilyPond doing (at least) two typesetting
passes, if at all.
Ok, I realize this isn't really a MWE, but I needed a more real example of
some of the issues I ran into. So, here we go. You'll find some of my
favorite preferences for Lyrics in the extra global overrides. And, yes, I
realize they are part of the problem, but even without them, the problems
are
This looks awesome, Jean! Thanks so much for this great start! And thanks
to everyone else who has chimes in on this. We may get to a great solution
yet!
In my recent score, again, a single vocal staff with two piano staves
below, I had instances where there were 2, 3, and 4-syllable clusters
Hi again!
Given the success of my first sortie, here's another snippet that might be
automated. (Note that this one matches the OP's situation.)
This is definitely a tweak I do on a very regular basis in my music-with-text
scores: sliding a text backwards, potentially under previous grobs.
Hi Jean,
> this example isn't specific to lyrics, although this situation
> probably occurs more often in lyrics than in other contexts.
Definitely.
> Here's one way to do this, but don't be too excited: not only
> is it hacky (in "fixable" ways), but it makes lots of assumptions
> that hold in
Hi Jean,
> This just removes the lyric syllable's presence in horizontal
> spacing, then adjusts its placement if it collides with its
> right neighbor. It works in this case because there is nothing
> on the left that the lyric syllable in question could collide
> with. (It also does not handle
Le 14/11/2022 à 17:11, Kieren MacMillan a écrit :
Hi again!
Given the success of my first sortie, here's another snippet that might be
automated. (Note that this one matches the OP's situation.)
This is definitely a tweak I do on a very regular basis in my music-with-text
scores: sliding a
The bit with LyricHyphen was not working, this will be better:
\version "2.23.81"
#(ly:set-option 'compile-scheme-code)
\layout {
\context {
\Lyrics
\consists
#(lambda (context)
(let ((previous #f))
(make-engraver
(acknowledgers
Le 12/11/2022 à 16:38, Kieren MacMillan a écrit :
Hi all,
I know many of you follow a “Do first” process… so even though that’s not my
process, here goes. ;)
Here's a small example of this spacing “thorn”, and one way I might tweak it to
fix the problem.
Notes:
– I realize it's constructed
Hi all,
I know many of you follow a “Do first” process… so even though that’s not my
process, here goes. ;)
Here's a small example of this spacing “thorn”, and one way I might tweak it to
fix the problem.
Notes:
– I realize it's constructed to avoid the very issue(s) that Jean raises (i.e.,
Le 12/11/2022 à 00:23, Carl Sorensen a écrit :
IIUC, columns are spaced with springs and rods considering collisions
between adjacent columns.
The hope was that one could create negative space in the column with
no lyricText, thus allowing the adjacent column to overlap the column
with no
On Fri, Nov 11, 2022 at 12:33 PM Jean Abou Samra wrote:
>
>
> > Le 10 nov. 2022 à 18:22, Carl Sorensen a
> écrit :
> >
> > Thinking about this in terms of Excel cells, where they can extend as
> far as possible as long as there are no contents in adjacent cells
> >
> > Might it be possible
> Le 11 nov. 2022 à 15:11, Kieren MacMillan a
> écrit :
> Now of course I realize the implementation of this idea is not necessarily
> trivial… but I don't think we need to throw the whole spacing engine under
> the bus on the first step of an [attempted] improvement plan.
Before being
> Le 10 nov. 2022 à 18:22, Carl Sorensen a écrit :
>
> Thinking about this in terms of Excel cells, where they can extend as far as
> possible as long as there are no contents in adjacent cells
>
> Might it be possible for the lyrics engraver to add something like a
> lyricPlaceholder
Hi Carl,
> Thinking about this in terms of Excel cells, where they can extend as far as
> possible as long as there are no contents in adjacent cells
>
> Might it be possible for the lyrics engraver to add something like a
> lyricPlaceholder grob into adjacent note columns that had no
On Wed, Nov 9, 2022 at 3:05 PM Jean Abou Samra wrote:
>
> To tackle this, the first step would be sitting down with paper,
> formulating what new kind of problem we want, and figuring out
> an algorithm to solve it, maybe a variant of the existing algorithm
> to solve springs problems (in
Le 10/11/2022 à 00:16, Kieren MacMillan a écrit :
As I've described to you before, that is my preferred approach to coding. :)
Would be more than happy to do that — with or without you "live" (via
video-conference) — and then watch as you take the next step(s):
Sorry, I already have some
Hi Jean,
> This is not easy to do and it cannot be done with Scheme only.
That was clear the moment Janek and I started working on the problem…
> To tackle this, the first step would be sitting down with paper,
> formulating what new kind of problem we want, and figuring out
> an algorithm to
Le 09/11/2022 à 19:51, Kieren MacMillan a écrit :
Thoughts? I'm afraid my own Scheme skills aren't up to the task for this. I'm
also fully aware that I can adjust this manually at the problematic places. I'd
like to avoid that if possible, but will do that if needed.
Please let's talk with
Hi Abraham,
(Great to see you on-list again!)
> It's been some time since I've posted anything here, but a recent project has
> caused me to jump back into creating scores. I'm working on a relatively
> simple choral piece with piano accompaniment and seeing all the ways the
> lyric syllables
42 matches
Mail list logo
