Re: Empty chord construct and \break.

[Hwaen Ch'uqi]

I suppose I spoke too soon, for when I compiled the code, the result was
actually the same.

HC


On Sun, Apr 28, 2024 at 7:47 AM Hwaen Ch'uqi  wrote:

> Indeed, that helps tremendously. Thank you so much!!!
>
> Hwaen Ch'uqi
>
>
> On Sun, Apr 28, 2024 at 7:24 AM Thomas Morley 
> wrote:
>
>> Am So., 28. Apr. 2024 um 06:25 Uhr schrieb Hwaen Ch'uqi <
>> hwaench...@gmail.com>:
>> >
>> > Greetings,
>> >
>> > I am trying to typeset a stack of spoken lines above a multimeasure
>> rest. This works fine when preceded by notes in the same system. However,
>> when it follows a forced break, the output is not so desirable. Can anyone
>> explain what I am missing? MWE below.
>> >
>> > \version "2.24.3"
>> >
>> > \score {
>> >   \new Staff = contrabass {
>> > \relative c' {
>> >   \key des \major \time 3/4 \clef bass
>> >   des,2. %!
>> >   des %2
>> >   des %3
>> >   des %4
>> >   \break
>> > \textLengthOn
>> > <>^\markup \override #'(line-width . 66) \override #'(baseline-skip .
>> 2.3) \wordwrap { But enough with introductions. You are no doubt here to
>> learn about a most difficult episode in the life of our Katz. It was during
>> a particular night of fitful sleep that our beloved Katzlein finally
>> slipped into Traumland, and it is there where our story begins. }
>> > R2.\fermata%29
>> > \textLengthOff
>> > }
>> >   }
>> > }
>> >
>> > Thank you so much.
>> >
>> > Hwaen Ch'uqi
>> >
>>
>> Hi,
>>
>> what happens here is, the TextScript attached to the empty chord is
>> printed at
>> start of the measure. \textLengthOn stretches the measure to fit with
>> the TextScript,
>> and the MultiMeasureRest is centered in this stretched measure.
>> This is correct in both cases with and without \break.
>> Though, with the \break the measure has a lonely MultiMeasureRest and
>> is stretched
>> even more by ragged-right being #f, the default for all but the first
>> line.
>> Thus the MultiMeasureRest is centered in a whole single line, the
>> TextScript not.
>>
>> You probably had the idea to attach text to a MultiMeasureRest with:
>> <>^"markup" R2.
>> Alas, text of a MultiMeasureRest is of type MultiMeasureRestText.
>> Nevertheless, you can do so with a little more code. Though,
>> \textLengthOn will
>> then not work, you'll need to stretch the MultiMeasureRest itself:
>>
>>
>> \version "2.24.3"
>>
>> mrkp =
>>   \markup
>> \override #'(line-width . 66)
>> \override #'(baseline-skip . 2.3)
>> \wordwrap {
>>   But enough with introductions. You are no doubt here to learn about
>> a
>>   most difficult episode in the life of our Katz. It was during a
>>   particular night of fitful sleep that our beloved Katzlein finally
>>   slipped into Traumland, and it is there where our story begins.
>> }
>>
>> mmrText =
>>   #(make-music
>> 'MultiMeasureTextEvent
>> 'direction 1
>> 'text mrkp)
>>
>> \score {
>>   \new Staff = contrabass {
>> \relative c' {
>>   \key des \major \time 3/4 \clef bass
>>   des,2. %!
>>   des %2
>>   des %3
>>   des %4
>>   \break
>>   %% stretch by aprox. half the width of the MultiMeasureRestText:
>>   \once \override MultiMeasureRest.bound-padding = 32
>>   <>^\mmrText
>>   R2.\fermata %29
>> }
>>   }
>> }
>>
>>
>> HTH,
>>   Harm
>>
>

Re: Frescobaldi?

[Jean Abou Samra]

> […]
> Well, the explanation wasn't that brief. Sorry that I didn't have
> time to write a shorter one, as they say.


PS: Maybe I should mention that at the time I went down the rabbit
hole of Python packaging in general because of Frescobaldi, I wrote
two articles on the LinuxFR site, which may be of interest here if
one reads French:

https://linuxfr.org/news/l-installation-et-la-distribution-de-paquets-python-1-4
https://linuxfr.org/news/l-installation-et-la-distribution-de-paquets-python-2-4

(Yes, these are ~8 and ~14 pages long. Yes, they're only the two
first articles in a series of four. I haven't given up on publishing
the two others, but it's not my priority at the moment.)



signature.asc
Description: This is a digitally signed message part

Re: Frescobaldi?

[Jean Abou Samra]

> unfortunately, as I noted above, the problem seems to be that frescobaldi
> depends on a now-deprecated version of qtwebengine, and without updating
> it we'll eventually reach a point where it no longer runs. I looked into
> this because qtwebengine-5.15 failed to compile on my machine this morning,
> so I'm worried we're already approaching EOL on it. 

Note that we're talking about Qt as a whole, not just QtWebEngine which
is just a small part of it (well, for some definition of "small" since it
embeds Chromium's Web rendering engine…) that Frescobaldi only uses in a
few places (IIRC, the SVG viewer and the documentation browser).

Qt 5 *is* already EOL upstream, since May 2023.


> Jean: I have a colleague who does UI work and is "fairly" capable of dealing
> with python and Qt dependencies. Can you give me a brief (but as technical
> as it needs to be for a specialist to understand the issue) summary of where
> the sticking points are?

Frescobaldi uses the Poppler library in order to display PDF files. (It cannot
use Qt's native PDF viewer based on Chromium, because that one is not powerful
enough to support point-and-click.) Since Frescobaldi is written in Python and
Poppler is a C++ library, it needs an FFI wrapper, which is called python-
poppler-qt5 and written with a tool called sip that is developed by the
creator and maintainer of PyQt itself and also used for PyQt.

Thus there is a diamond dependency:

   Qt5 --> Poppler  (C++)
||
||
||
vv
  PyQt5 -> python-poppler-qt5  (Python extension modules)


python-poppler-qt5 is a little fiddly to build: it's multiple layers
with sip generating C++ code and QMake project files, then QMake
generating a Makefile and sip finally executing make on that Makefile.

On macOS, the platform favors distributing applications as .app bundles,
which are optimized for being created by the native app development
tools (Swift+XCode). These have a peculiar structure organized into
"frameworks", with data files separated from code files, shared library
lookup paths modified and that sort of thing (the specifics I do not know
or remember). Of course, that doesn't play well with Python packages
relying on a different structure, and Qt + PyQt also needing their
file structure. In fact there are whole tools written just to deploy
PyQt in a .app bundle, see pyqtdeploy.

Now throw python-poppler-qt5 into the mix, which needs to be loaded by
Python and find its linked Poppler and Qt and PyQt, and you should start
to understand the problem.

Basically, it's the Apple flavor of "things will work well but only
if you do it my way with the non-cross-platform tools from my walled
garden" in its full glory.

Add that macOS displays scary warnings to users if the app bundle
hasn't been signed with a certificate that costs real money.
Details are on
https://github.com/frescobaldi/frescobaldi/issues/1584

Also add that the tool Frescobaldi has used so far to create app
bundles, py2app, relies heavily on setuptools, which prevents
Frescobaldi from moving to a more modern and less complicated
build backend like hatchling.

Apart from these packaging issues, there's also an issue with
the global menu (the one at the top of the screen on macOS, it
doesn't appear on other platforms) which isn't really up-to-date
and has been a source of crashes.

There are also miscellaneous bugs that only reproduce on macOS
(they have the macOS label on GitHub) and it's not always easy
to understand why.

Well, the explanation wasn't that brief. Sorry that I didn't have
time to write a shorter one, as they say.



signature.asc
Description: This is a digitally signed message part

Re: Frescobaldi?

[Jean Abou Samra]

> I own a bunch of Macs. In fact, right here in my studio I have two late-2014
> Mac Minis with fresh Monterey installs which are completely unused. I also
> have a *really* excellent [fibre] internet connection — it usually hovers near
> 900Mbps up and down (though right now it’s only at 200Mbps for some reason?!)
> — and I’m happy to put a machine on a DMZ for external access.
> 
> Is there anything, non-programming-wise, I can do to help the cause?



Currently, I don't have the time or honestly the stamina to work on
Frescobaldi again, but if anyone does tackle macOS issues then I'm
sure that they would much appreciate access to these machines.

Perhaps one thing you can do right now is subscribe to notifications on
the Frescobaldi repository on GitHub ("Watch" button on the top right of
https://github.com/frescobaldi/frescobaldi when you're logged in)
so you get informed of any activity.



signature.asc
Description: This is a digitally signed message part

Re: Frescobaldi?

[Jean Abou Samra]

> Just had a quick look. It seems to me we need to create a python-poppler-qt6,
> port qpageview to Qt6 and of course frescobaldi itself. I would hope that
> qpageview and frescobaldi both basically mean moving from PyQt5 to PyQt6 which
> I expect to be mostly busy work. The poppler bindings seem to require
> understanding of what poppler does though.
> 
> All of the above is based on a brief look and thus not a reliable assessment.

Honestly, I have zero idea how hard porting to Qt 6 actually is. I think we
won't know until someone tries and finds out what exactly Frescobaldi uses that
is modified or removed in Qt 6 compared to Qt 5 as well as poppler-qt6 compared
to poppler-qt5.

> In any case, I do rely on Frescobaldi and am willing to help keep it alive.

If you want to attempt the port, of course feel free.



signature.asc
Description: This is a digitally signed message part

Re: Frescobaldi?

[Michael Gerdau]

> Thanks, but unfortunately the kind of work needed is deeply technical, not 
> busy work.
> 

Just had a quick look. It seems to me we need to create a python-poppler-qt6, 
port qpageview to Qt6 and of course frescobaldi itself. I would hope that 
qpageview and frescobaldi both basically mean moving from PyQt5 to PyQt6 which 
I expect to be mostly busy work. The poppler bindings seem to require 
understanding of what poppler does though.

All of the above is based on a brief look and thus not a reliable assessment.

In any case, I do rely on Frescobaldi and am willing to help keep it alive.

Kind regards,
Michael 

Re: Frescobaldi?

[N. Andrew Walsh]

> I understood that. I was responding in particular to Jean’s comment
>
> > NB: I don't own a macOS machine, which of course makes all testing very
> difficult
>
> but also offering the hardware for use in whatever way it might be helpful
> (e.g., compilation, not just testing).
>
> Cheers,
> Kieren.
> __
>
ah, whoops, my mistake. I missed the context. Sorry about that.

N. Andrew Walsh
er/ihn/ihm/sein | he/him/his
Berlin

Re: Frescobaldi?

[Kieren MacMillan]

Hi,

> unfortunately, as I noted above, the problem seems to be that frescobaldi 
> depends on a now-deprecated version of qtwebengine, and without updating it 
> we'll eventually reach a point where it no longer runs.

I understood that. I was responding in particular to Jean’s comment

> NB: I don't own a macOS machine, which of course makes all testing very 
> difficult

but also offering the hardware for use in whatever way it might be helpful 
(e.g., compilation, not just testing).

Cheers,
Kieren.
__

My work day may look different than your work day. Please do not feel obligated 
to read or respond to this email outside of your normal working hours.

Re: Frescobaldi?

[Jun Tamura]

Hi All,

The Qt5 dependency seems a much more serious and important issue than the 
packaging for macOS. Although an app bundle installer is most desirable for 
ordinary macOS users, there are alternatives such as MacPorts and Homebrew. I’m 
currently running Frescobaldi from the latest source pulled from GitHub repo 
with Python310 and Qt5-related libraries installed by MacPorts, and it works 
just fine.

I’m sorry that I’m not a programmer and cannot help with the deeply technical 
work. I sincerely hope that we can find new volunteers to tackle the Qt5 issue. 
Frescobaldi is quite important for many of us.

Jun Tamura
he/him/his
Tokyo

> 2024/04/28 23:22、N. Andrew Walsh のメール:
> 
> Hi Kieren,
> 
> unfortunately, as I noted above, the problem seems to be that frescobaldi 
> depends on a now-deprecated version of qtwebengine, and without updating it 
> we'll eventually reach a point where it no longer runs. I looked into this 
> because qtwebengine-5.15 failed to compile on my machine this morning, so I'm 
> worried we're already approaching EOL on it. 
> 
> Jean: I have a colleague who does UI work and is "fairly" capable of dealing 
> with python and Qt dependencies. Can you give me a brief (but as technical as 
> it needs to be for a specialist to understand the issue) summary of where the 
> sticking points are?
> 
> Cheers,
> 
> N. Andrew Walsh
> er/ihn/ihm/sein | he/him/his
> Berlin
> 
> 
> On Sun, Apr 28, 2024 at 4:08 PM Kieren MacMillan  > wrote:
>> Hi all,
>> 
>> >> If there is busy work that needs to be done on the project, I can do 
>> >> that, but I also don't own a Mac.
>> 
>> I own a bunch of Macs. In fact, right here in my studio I have two late-2014 
>> Mac Minis with fresh Monterey installs which are completely unused. I also 
>> have a *really* excellent [fibre] internet connection — it usually hovers 
>> near 900Mbps up and down (though right now it’s only at 200Mbps for some 
>> reason?!) — and I’m happy to put a machine on a DMZ for external access.
>> 
>> Is there anything, non-programming-wise, I can do to help the cause?
>> 
>> Cheers,
>> Kieren.
>> __
>> 
>> My work day may look different than your work day. Please do not feel 
>> obligated to read or respond to this email outside of your normal working 
>> hours.
>> 

Re: Frescobaldi?

[N. Andrew Walsh]

Hi Kieren,

unfortunately, as I noted above, the problem seems to be that frescobaldi
depends on a now-deprecated version of qtwebengine, and without updating it
we'll eventually reach a point where it no longer runs. I looked into this
because qtwebengine-5.15 failed to compile on my machine this morning, so
I'm worried we're already approaching EOL on it.

Jean: I have a colleague who does UI work and is "fairly" capable of
dealing with python and Qt dependencies. Can you give me a brief (but as
technical as it needs to be for a specialist to understand the issue)
summary of where the sticking points are?

Cheers,

N. Andrew Walsh
er/ihn/ihm/sein | he/him/his
Berlin


On Sun, Apr 28, 2024 at 4:08 PM Kieren MacMillan <
kie...@kierenmacmillan.info> wrote:

> Hi all,
>
> >> If there is busy work that needs to be done on the project, I can do
> that, but I also don't own a Mac.
>
> I own a bunch of Macs. In fact, right here in my studio I have two
> late-2014 Mac Minis with fresh Monterey installs which are completely
> unused. I also have a *really* excellent [fibre] internet connection — it
> usually hovers near 900Mbps up and down (though right now it’s only at
> 200Mbps for some reason?!) — and I’m happy to put a machine on a DMZ for
> external access.
>
> Is there anything, non-programming-wise, I can do to help the cause?
>
> Cheers,
> Kieren.
> __
>
> My work day may look different than your work day. Please do not feel
> obligated to read or respond to this email outside of your normal working
> hours.
>
>

Re: Frescobaldi?

[Kieren MacMillan]

Hi all,

>> If there is busy work that needs to be done on the project, I can do that, 
>> but I also don't own a Mac.

I own a bunch of Macs. In fact, right here in my studio I have two late-2014 
Mac Minis with fresh Monterey installs which are completely unused. I also have 
a *really* excellent [fibre] internet connection — it usually hovers near 
900Mbps up and down (though right now it’s only at 200Mbps for some reason?!) — 
and I’m happy to put a machine on a DMZ for external access.

Is there anything, non-programming-wise, I can do to help the cause?

Cheers,
Kieren.
__

My work day may look different than your work day. Please do not feel obligated 
to read or respond to this email outside of your normal working hours.

Re: Frescobaldi?

[Jean Abou Samra]

> If there is busy work that needs to be done on the project, I can do that, but
> I also don't own a Mac.

Thanks, but unfortunately the kind of work needed is deeply technical, not busy
work.


signature.asc
Description: This is a digitally signed message part

Re: Frescobaldi?

[Knute Snortum]

On Sun, Apr 28, 2024 at 4:15 AM Jean Abou Samra  wrote:

> Doing some system updates today, I see that frescobaldi is the only
> program that requires PyQtWebEngine:5, which in turn requires
> qtwebengine:5. Looking at the frescobaldi page, I see a somewhat concerning
> note that the project is on the verge of being unmaintained, due to this
> dependency on a deprecated version of qtwebengine.
>
> Is there any further information on this? I don't see any other IDE that
> works as well as frescobaldi for editing lilypond files, and I'm a bit
> worried that there hasn't been an update to the program in over a year. Any
> news would be appreciated.
>
>
>
> You've basically nailed the problem. I was the last person to work on
> making Frescobaldi actually work on macOS, and I gave up by lack of time
> (NB: I don't own a macOS machine, which of course makes all testing very
> difficult). Currently, there is close to no activity on the project.
>
> I doubt Linux distributions are going to remove Qt 5 really soon, and the
> Flatpak package can always provide it, but like every toolkit that's
> end-of-life, it's only going to be a source of trouble going forward. For
> example, Frescobaldi has some problems on Wayland (which is increasingly
> becoming the default on the Linux desktop, for good reason) that are caused
> by Qt 5 bugs fixed in Qt 6. I don't recall that anybody even attempted the
> Qt 6 migration.
>
> Yes, if the current state continues, Frescobaldi will ultimately die a
> natural death. Sorry that I cannot exactly bring an optimistic message
> here.
>

If there is busy work that needs to be done on the project, I can do that,
but I also don't own a Mac.


--
Knute Snortum

Re: Frescobaldi?

[Jean Abou Samra]

> Is Frescobaldi the most common tool on Linux, or what do the majority of
> Lilypond users use?

Frescobaldi is the most common LilyPond editor, on all OSes.



signature.asc
Description: This is a digitally signed message part

Re: Empty chord construct and \break.

[Hwaen Ch'uqi]

Indeed, that helps tremendously. Thank you so much!!!

Hwaen Ch'uqi


On Sun, Apr 28, 2024 at 7:24 AM Thomas Morley 
wrote:

> Am So., 28. Apr. 2024 um 06:25 Uhr schrieb Hwaen Ch'uqi <
> hwaench...@gmail.com>:
> >
> > Greetings,
> >
> > I am trying to typeset a stack of spoken lines above a multimeasure
> rest. This works fine when preceded by notes in the same system. However,
> when it follows a forced break, the output is not so desirable. Can anyone
> explain what I am missing? MWE below.
> >
> > \version "2.24.3"
> >
> > \score {
> >   \new Staff = contrabass {
> > \relative c' {
> >   \key des \major \time 3/4 \clef bass
> >   des,2. %!
> >   des %2
> >   des %3
> >   des %4
> >   \break
> > \textLengthOn
> > <>^\markup \override #'(line-width . 66) \override #'(baseline-skip .
> 2.3) \wordwrap { But enough with introductions. You are no doubt here to
> learn about a most difficult episode in the life of our Katz. It was during
> a particular night of fitful sleep that our beloved Katzlein finally
> slipped into Traumland, and it is there where our story begins. }
> > R2.\fermata%29
> > \textLengthOff
> > }
> >   }
> > }
> >
> > Thank you so much.
> >
> > Hwaen Ch'uqi
> >
>
> Hi,
>
> what happens here is, the TextScript attached to the empty chord is
> printed at
> start of the measure. \textLengthOn stretches the measure to fit with
> the TextScript,
> and the MultiMeasureRest is centered in this stretched measure.
> This is correct in both cases with and without \break.
> Though, with the \break the measure has a lonely MultiMeasureRest and
> is stretched
> even more by ragged-right being #f, the default for all but the first line.
> Thus the MultiMeasureRest is centered in a whole single line, the
> TextScript not.
>
> You probably had the idea to attach text to a MultiMeasureRest with:
> <>^"markup" R2.
> Alas, text of a MultiMeasureRest is of type MultiMeasureRestText.
> Nevertheless, you can do so with a little more code. Though, \textLengthOn
> will
> then not work, you'll need to stretch the MultiMeasureRest itself:
>
>
> \version "2.24.3"
>
> mrkp =
>   \markup
> \override #'(line-width . 66)
> \override #'(baseline-skip . 2.3)
> \wordwrap {
>   But enough with introductions. You are no doubt here to learn about a
>   most difficult episode in the life of our Katz. It was during a
>   particular night of fitful sleep that our beloved Katzlein finally
>   slipped into Traumland, and it is there where our story begins.
> }
>
> mmrText =
>   #(make-music
> 'MultiMeasureTextEvent
> 'direction 1
> 'text mrkp)
>
> \score {
>   \new Staff = contrabass {
> \relative c' {
>   \key des \major \time 3/4 \clef bass
>   des,2. %!
>   des %2
>   des %3
>   des %4
>   \break
>   %% stretch by aprox. half the width of the MultiMeasureRestText:
>   \once \override MultiMeasureRest.bound-padding = 32
>   <>^\mmrText
>   R2.\fermata %29
> }
>   }
> }
>
>
> HTH,
>   Harm
>

Re: Frescobaldi?

[Mats-Olof Liljegren]

I use Frescobaldi on all of my Macs with slightly different operating systems. 
It works well, but I'm concerned about the future. Unfortunately, I'm not a 
programmer, so I can't contribute with coding. This is exciting, perhaps a bit 
too exciting, considering how we'll be able to continue with Lilypond. Is 
Frescobaldi the most common tool on Linux, or what do the majority of Lilypond 
users use?

Regards 
/MO

> 28 apr. 2024 kl. 13:15 skrev Jean Abou Samra :
> 
> 
>> 
>> Doing some system updates today, I see that frescobaldi is the only program 
>> that requires PyQtWebEngine:5, which in turn requires qtwebengine:5. Looking 
>> at the frescobaldi page, I see a somewhat concerning note that the project 
>> is on the verge of being unmaintained, due to this dependency on a 
>> deprecated version of qtwebengine. 
>> 
>> Is there any further information on this? I don't see any other IDE that 
>> works as well as frescobaldi for editing lilypond files, and I'm a bit 
>> worried that there hasn't been an update to the program in over a year. Any 
>> news would be appreciated.
> 
> 
> You've basically nailed the problem. I was the last person to work on making 
> Frescobaldi actually work on macOS, and I gave up by lack of time (NB: I 
> don't own a macOS machine, which of course makes all testing very difficult). 
> Currently, there is close to no activity on the project.
> 
> I doubt Linux distributions are going to remove Qt 5 really soon, and the 
> Flatpak package can always provide it, but like every toolkit that's 
> end-of-life, it's only going to be a source of trouble going forward. For 
> example, Frescobaldi has some problems on Wayland (which is increasingly 
> becoming the default on the Linux desktop, for good reason) that are caused 
> by Qt 5 bugs fixed in Qt 6. I don't recall that anybody even attempted the Qt 
> 6 migration.
> 
> Yes, if the current state continues, Frescobaldi will ultimately die a 
> natural death. Sorry that I cannot exactly bring an optimistic message here.
> 
> Best,
> Jean
> 
> 

Re: Empty chord construct and \break.

[Thomas Morley]

Am So., 28. Apr. 2024 um 06:25 Uhr schrieb Hwaen Ch'uqi :
>
> Greetings,
>
> I am trying to typeset a stack of spoken lines above a multimeasure rest. 
> This works fine when preceded by notes in the same system. However, when it 
> follows a forced break, the output is not so desirable. Can anyone explain 
> what I am missing? MWE below.
>
> \version "2.24.3"
>
> \score {
>   \new Staff = contrabass {
> \relative c' {
>   \key des \major \time 3/4 \clef bass
>   des,2. %!
>   des %2
>   des %3
>   des %4
>   \break
> \textLengthOn
> <>^\markup \override #'(line-width . 66) \override #'(baseline-skip . 2.3) 
> \wordwrap { But enough with introductions. You are no doubt here to learn 
> about a most difficult episode in the life of our Katz. It was during a 
> particular night of fitful sleep that our beloved Katzlein finally slipped 
> into Traumland, and it is there where our story begins. }
> R2.\fermata%29
> \textLengthOff
> }
>   }
> }
>
> Thank you so much.
>
> Hwaen Ch'uqi
>

Hi,

what happens here is, the TextScript attached to the empty chord is printed at
start of the measure. \textLengthOn stretches the measure to fit with
the TextScript,
and the MultiMeasureRest is centered in this stretched measure.
This is correct in both cases with and without \break.
Though, with the \break the measure has a lonely MultiMeasureRest and
is stretched
even more by ragged-right being #f, the default for all but the first line.
Thus the MultiMeasureRest is centered in a whole single line, the
TextScript not.

You probably had the idea to attach text to a MultiMeasureRest with:
<>^"markup" R2.
Alas, text of a MultiMeasureRest is of type MultiMeasureRestText.
Nevertheless, you can do so with a little more code. Though, \textLengthOn will
then not work, you'll need to stretch the MultiMeasureRest itself:


\version "2.24.3"

mrkp =
  \markup
\override #'(line-width . 66)
\override #'(baseline-skip . 2.3)
\wordwrap {
  But enough with introductions. You are no doubt here to learn about a
  most difficult episode in the life of our Katz. It was during a
  particular night of fitful sleep that our beloved Katzlein finally
  slipped into Traumland, and it is there where our story begins.
}

mmrText =
  #(make-music
'MultiMeasureTextEvent
'direction 1
'text mrkp)

\score {
  \new Staff = contrabass {
\relative c' {
  \key des \major \time 3/4 \clef bass
  des,2. %!
  des %2
  des %3
  des %4
  \break
  %% stretch by aprox. half the width of the MultiMeasureRestText:
  \once \override MultiMeasureRest.bound-padding = 32
  <>^\mmrText
  R2.\fermata %29
}
  }
}


HTH,
  Harm

Re: Frescobaldi?

[Jean Abou Samra]

> Doing some system updates today, I see that frescobaldi is the only program
> that requires PyQtWebEngine:5, which in turn requires qtwebengine:5. Looking
> at the frescobaldi page, I see a somewhat concerning note that the project is
> on the verge of being unmaintained, due to this dependency on a deprecated
> version of qtwebengine. 
> 
> Is there any further information on this? I don't see any other IDE that works
> as well as frescobaldi for editing lilypond files, and I'm a bit worried that
> there hasn't been an update to the program in over a year. Any news would be
> appreciated.


You've basically nailed the problem. I was the last person to work on making
Frescobaldi actually work on macOS, and I gave up by lack of time (NB: I don't
own a macOS machine, which of course makes all testing very
difficult). Currently, there is close to no activity on the project.

I doubt Linux distributions are going to remove Qt 5 really soon, and the
Flatpak package can always provide it, but like every toolkit that's end-of-
life, it's only going to be a source of trouble going forward. For example,
Frescobaldi has some problems on Wayland (which is increasingly becoming the
default on the Linux desktop, for good reason) that are caused by Qt 5 bugs
fixed in Qt 6. I don't recall that anybody even attempted the Qt 6 migration.

Yes, if the current state continues, Frescobaldi will ultimately die a natural
death. Sorry that I cannot exactly bring an optimistic message here.

Best,
Jean



signature.asc
Description: This is a digitally signed message part

Re: Transparent box around notes

[Robin Bannister]

Paolo Prete wrote:

Note that there's also this (no trial-and-error):

https://lists.gnu.org/archive/html/lilypond-user/2015-01/msg00142.html

But it doesn't compile with 2.24...



That's due to merge request !818 [1], applied between 2.23.3 and 2.23.4.

Simon Albrecht ran into the same problem in another case, and Jean 
helped him out [2] by adapting just the add-grob-definition part.


Doing the same to David N's add-grob-definition gets his code running 
again.  Maybe that's all you need to do.



[1] https://gitlab.com/lilypond/lilypond/-/merge_requests/818
[2] https://lists.gnu.org/archive/html/lilypond-user/2021-12/msg00045.html


Cheers,
Robin

Frescobaldi?

[N. Andrew Walsh]

Hi List,

Doing some system updates today, I see that frescobaldi is the only program
that requires PyQtWebEngine:5, which in turn requires qtwebengine:5.
Looking at the frescobaldi page, I see a somewhat concerning note that the
project is on the verge of being unmaintained, due to this dependency on a
deprecated version of qtwebengine.

Is there any further information on this? I don't see any other IDE that
works as well as frescobaldi for editing lilypond files, and I'm a bit
worried that there hasn't been an update to the program in over a year. Any
news would be appreciated.

Cheers,

N. Andrew Walsh
er/ihn/ihm/sein | he/him/his
Berlin