Re: Aw: Re: New suggestion to make Lily pond s peed up on multiple CPU cores

Le 17/07/2022 à 18:24, Arno Waschk a écrit :
> Well the hairpin thing mm ight be a bug for itself, as it happens with 
> (for other reasons whatsoever) wanted pagebrakes as well.


Why would that be a bug? It looks just as expected to me.

Hairpins are not the only grobs with such behavior, e.g.,

\version "2.23.11"

{ c'1\tweak breakable ##t \glissando \pageBreak c''1 }
\pageBreak
{ c'1\tweak breakable ##t \glissando \pageBreak c'''1 }


> The difference I meant was that a pagebreak could in theory split a 
> score in separated smaller scores to be compiled in parallel, and that 
> could be done in very early stage of score processing, as opposed (I 
> think) to linebreaks.


There isn't all that much of a difference between page breaks
and line breaks in that regard, I think. If you parallelize
with line breaks, the main non-parallelizable thing is page
layout, which you have to parallelize per page. Most stuff
happens before page layout.


> Still the idea was mainly to have such parallelizing rather for a 
> draft or development mode (where you can live with an odd hairpin), 
> and still having the slow mode as currently for the final run where 
> you don't want to have compromises in quality anywhere.


Understood.


_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond