On 2/16/22, 7:37 AM, "lilypond-devel on behalf of Thomas Scharkowski"
wrote:
Hi all,
I installed this version today, everything seems to work.
It might be of interest that the MacPorts version of 2.23.6 runs around
three times faster on my MacBookPro M1, macOs 12.1
> Am 20.02.2022 um 10:16 schrieb Jean Abou Samra :
>
>
>
> Le 20/02/2022 à 10:13, Thomas Scharkowski a écrit :
>> Sorry, couldn’t get the patched lily.scm to run - certainly a mistake on my
>> side.
>> If you like you can send a correct patched lily.scm to me?
>>
>> Thomas
>
> Here you go.
causing this slowdown.
> >
> > First, does it look like one step of the compilation in particular
> > is slow (for example, it takes time during "Preprocessing graphical
> > objects"), or do all steps take more time? Pro tip: run lilypond with
> &g
> First, does it look like one step of the compilation in particular
> is slow (for example, it takes time during "Preprocessing graphical
> objects"), or do all steps take more time? Pro tip: run lilypond with
> --verbose to have a more fine-grained view of the process.
>
s.
Second, edit the file lily.scm (should be under
/path/to/lilypond-2.23.6/share/lilypond/2.23.6/scm/lily)
to apply the following diff:
@@ -844,8 +844,11 @@ PIDs or the number of the process."
+(use-modules (statprof))
+
One more test:
I installed both versions on a 2013 iMac intel Core i5.
24,3“ MacPorts version
51,4“ gitab version
Thomas
> Am 18.02.2022 um 12:24 schrieb Thomas Scharkowski :
>
>
>
>> Am 17.02.2022 um 20:42 schrieb Jean Abou Samra :
>>
>>
>>
>> Le 17/02/2022 à 09:08, Thomas Scharkowski a é
> Am 17.02.2022 um 20:42 schrieb Jean Abou Samra :
>
>
>
> Le 17/02/2022 à 09:08, Thomas Scharkowski a écrit :
>> I did GUILE_AUTO_COMPILE=1 lilypond file.ly - there was not much of change
>> afterwards: MSDM.ly still needed 24“ compared to 10“ with MacPorts.
>
> You did see all the logging
Le 17/02/2022 à 09:08, Thomas Scharkowski a écrit :
I did GUILE_AUTO_COMPILE=1 lilypond file.ly - there was not much of change
afterwards: MSDM.ly still needed 24“ compared to 10“ with MacPorts.
You did see all the logging output with warnings about 'possibly
unbound variables' and stuff?
I did GUILE_AUTO_COMPILE=1 lilypond file.ly - there was not much of change
afterwards: MSDM.ly still needed 24“ compared to 10“ with MacPorts.
Thomas
> Am 17.02.2022 um 00:45 schrieb Jean Abou Samra :
>
> Le 16/02/2022 à 15:37, Thomas Scharkowski a écrit :
>> Hi all,
>>
>> I installed this ver
Le 16/02/2022 à 15:37, Thomas Scharkowski a écrit :
Hi all,
I installed this version today, everything seems to work.
It might be of interest that the MacPorts version of 2.23.6 runs around three
times faster on my MacBookPro M1, macOs 12.1
Carver Missa compile times are 28,6“ and 10,3“ MacPor
:07 schrieb Jonas Hahnfeld via LilyPond user discussion
> :
>
> We are happy to announce the release of LilyPond 2.23.6. This is termed
> a development release, but these are usually reliable. If you want to
> use the current stable version of LilyPond, we recommend using the
> 2.22
Am Montag, dem 14.02.2022 um 00:04 +0100 schrieb Hans Aikema:
> Jonas,
>
> My experience for my specific scenario with 2.23.6 is quite bad: it
> appears to have broken PNG transparency (Mac OS 11.6.3 on Intel Mac
> (MacBook Pro Late 2013 and Mac Pro 2013).
>
> Creating PNG images with transparenc
The attached demo lilypond source is a stripped-down version of what I have in
my sources for the slide-images and can be used for reproducing the issues.
Without the pagebreak lilypond 2.23.6 macports build runs without error, so it
looks like Ghostscript in the macports build is breaking at
>
> We are happy to announce the release of LilyPond 2.23.6. This is termed
> a development release, but these are usually reliable. If you want to
> use the current stable version of LilyPond, we recommend using the
> 2.22.1 version.
>
> This release also marks a
Am Samstag, dem 12.02.2022 um 12:50 +0100 schrieb Thomas Morley:
> Am Di., 8. Feb. 2022 um 16:54 Uhr schrieb Jonas Hahnfeld via
> Discussions on LilyPond development :
> >
> > We are happy to announce the release of LilyPond 2.23.6. This is termed
> > a development releas
Am Di., 8. Feb. 2022 um 16:54 Uhr schrieb Jonas Hahnfeld via
Discussions on LilyPond development :
>
> We are happy to announce the release of LilyPond 2.23.6. This is termed
> a development release, but these are usually reliable. If you want to
> use the current stable version of
Sorry for cluttering the list, but the problem is actually with the way
FontConfig 2.13.94 is packaged on NixOS. I'll report it on their Github.
Thanks for the amazing work again.
On Wed, Feb 9, 2022 at 3:59 PM Omid Mo'menzadeh
wrote:
> OK, it seems that I have found where the problem is. I buil
OK, it seems that I have found where the problem is. I built LilyPond
against FontConfig 2.13.1, and it works just like the official binary. But
the version built against FontConfig 2.13.94 and Guile 2.2 emits the same
warning I mentioned. There seems to be some sort of soft incompatibility
with Fo
I can confirm that this is a packaging issue now. I patched the official
binary to see the glibc on my system, and it works without any warnings.
It's also considerably faster than my own compiled version (4.31s vs. 6.43s
on a single file).
I suppose I should go on debugging this on my own, but as
Am Mittwoch, dem 09.02.2022 um 12:50 +0330 schrieb Omid Mo'menzadeh:
> It works with Guile 2.2, but with a lot of the mentioned warnings.
> The .nix files I attached describe a recipe for building LilyPond,
> and two packages are built in the shell.nix file, so yes, I am
> building both, using the
It works with Guile 2.2, but with a lot of the mentioned warnings. The .nix
files I attached describe a recipe for building LilyPond, and two packages
are built in the shell.nix file, so yes, I am building both, using the same
recipe, but one with Guile 1.8, and one with Guile 2.2. Both are using t
Am Mittwoch, dem 09.02.2022 um 00:15 +0330 schrieb Omid Mo'menzadeh:
> Thanks for the amazing work.
> I get a bunch "Fontconfig error: No writable cache directories" warnings
> using Guile 2.2, that I don't get with Lilypond compiled with Guile 1.8.
> This might be a packaging issue, but since I'm
>> ParenthesesItem.stencils = #(lambda (grob)
>>
>>
>> /home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:85:19
>> : error: bad grob property path
>>
>> \once \override
>>
>> ParenthesesItem.stencils = #(lambda
clude file for quite some time. What might
> I need to change to remove the error?
>
>
> Thanks
>
>
> --
>
> “Happiness is the meaning and the purpose of life, the whole aim and end
> of human existence.”
>
> ― Aristotle
>
>
> On Tue, Feb 8, 2022 at 9:57 A
remove the error?
Thanks
--
“Happiness is the meaning and the purpose of life, the whole aim and end of
human existence.”
― Aristotle
On Tue, Feb 8, 2022 at 9:57 AM Jonas Hahnfeld via LilyPond user discussion <
lilypond-u...@gnu.org> wrote:
> We are happy to announce the release o
Guy Stalnaker writes:
> I can report a change in what I see. This code does not produce an error in
> 2.20 but does in 2.23.6:
>
>
> startParenthesis = {
> \once \override ParenthesesItem.stencils = #(lambda (grob)
> (let ((par-list
> (parent
Le 08/02/2022 à 20:02, Guy Stalnaker a écrit :
I can report a change in what I see. This code does not produce an
error in 2.20 but does in 2.23.6:
startParenthesis = {
\once \override ParenthesesItem.stencils = #(lambda (grob)
(let ((par-l
in my standard include file for quite some time. What might I
> need to change to remove the error?
>
> Thanks
>
> --
>
> “Happiness is the meaning and the purpose of life, the whole aim and end of
> human existence.”
>
> ― Aristotle
>
>
>> On Tue, Feb
Hello developers,
Thanks a lot for those excellent news!. I’ve switched to 2.23.6/guile 2.2 on
MacOS and will report about my experience.
JM
> On 8 Feb 2022, at 14:07, Jonas Hahnfeld via LilyPond user discussion
> wrote:
>
> We are happy to announce the release of LilyPond 2.2
We are happy to announce the release of LilyPond 2.23.6. This is termed
a development release, but these are usually reliable. If you want to
use the current stable version of LilyPond, we recommend using the
2.22.1 version.
This release also marks a transition towards Guile 2.2: The binaries
Am Samstag, dem 15.01.2022 um 00:22 +0100 schrieb Jean Abou Samra:
> Le 14/01/2022 à 23:25, Dan Eble a écrit :
> > Would it be reasonable to release 2.23.6 soon? The documentation
> > of \jump (!1134, in review) is the last of the documentation
> > related to \repeat segno, and it would be nice to
Le 14/01/2022 à 23:25, Dan Eble a écrit :
Would it be reasonable to release 2.23.6 soon? The documentation of \jump
(!1134, in review) is the last of the documentation related to \repeat segno,
and it would be nice to let users get their hands on the feature.
https://gitlab.com/lilypond/lil
Would it be reasonable to release 2.23.6 soon? The documentation of \jump
(!1134, in review) is the last of the documentation related to \repeat segno,
and it would be nice to let users get their hands on the feature.
—
Dan
33 matches
Mail list logo
