Re: problems with release 2.24 on iMac M1 with Ventura 13.0.1

[Jean Abou Samra]

Le 07/01/2023 à 00:46, Jean Abou Samra a écrit :

Le 06/01/2023 à 22:22, Mario Bolognani a écrit :
Thanks a lot Jean, apparently with Terminal convert.ly operates 
correctly, but of course this is not a practical procedure for 
frequent use.




If you start using the command line more, you will find that it is
actually incredibly practical for more than you would have imagined.

For example, if you want to do a batch upgrade of all .ly files in
a directory, say "Scores" on your desktop, while making backups of
the unconverted sources just in case, it is as easy as

"/Users/mariobol/Library/CloudStorage/Dropbox/ M U S I C 
A/lilypond-2.24.0/bin/convert-ly" /Users/mariobol/Desktop/Scores/*.ly




Sorry, make that

"/Users/mariobol/Library/CloudStorage/Dropbox/ M U S I C 
A/lilypond-2.24.0/bin/convert-ly" -e /Users/mariobol/Desktop/Scores/*.ly





OpenPGP_signature
Description: OpenPGP digital signature

Re: problems with release 2.24 on iMac M1 with Ventura 13.0.1

[Jean Abou Samra]

Le 06/01/2023 à 22:22, Mario Bolognani a écrit :
Thanks a lot Jean, apparently with Terminal convert.ly operates 
correctly, but of course this is not a practical procedure for 
frequent use.




If you start using the command line more, you will find that it is
actually incredibly practical for more than you would have imagined.

For example, if you want to do a batch upgrade of all .ly files in
a directory, say "Scores" on your desktop, while making backups of
the unconverted sources just in case, it is as easy as

"/Users/mariobol/Library/CloudStorage/Dropbox/ M U S I C 
A/lilypond-2.24.0/bin/convert-ly" /Users/mariobol/Desktop/Scores/*.ly


Not to say that I wouldn't like Frescobaldi to work better on macOS,
of course.

Best,
Jean



OpenPGP_signature
Description: OpenPGP digital signature

Re: problems with release 2.24 on iMac M1 with Ventura 13.0.1

[Mario Bolognani]

Thanks a lot Jean, apparently with Terminal convert.ly operates correctly, but 
of course this is not a practical procedure for frequent use.

Anyway it is best then nothing…

Thanks again

Mario

Mario Bolognani
mario.bologn...@gmail.com



> Il giorno 6 gen 2023, alle ore 18:31, Jean Abou Samra  ha 
> scritto:
> 
> 
> 
> Le 30/12/2022 à 17:00, Mario Bolognani a écrit :
>> Ok, I’ll try to explain what I have done for convert.ly:
>> 
>> First, following your suggestion, I forced the use of the tools’ #! lines:
>> 
>> 
>> 
>> Then in Frescobaldi after having used the command convert.ly, this was the 
>> result:
>> 
>> 
>> 
>> And, after this Fatal Phyton error… what I have to do?
>> 
> 
> 
> 
> Sorry for forgetting to reply here. Well, Frescobaldi on macOS is a 
> complicated story. First, have you tried running convert-ly on the terminal? 
> You should open the terminal application and paste this command:
> 
> "/Users/mariobol/Library/CloudStorage/Dropbox/ M U S I C 
> A/lilypond-2.24.0/bin/convert-ly" /Users/mariobol/Desktop/file.ly
> 
> assuming that your file is file.ly in your Desktop folder, you should the 
> second part to match the actual location.
> 
> See if that works.
> 

Re: CrossStaff and Slashed grace

[Gregory Evans]

Hi Paul,
I would guess that someone here has a better solution (I'm basically
ignorantly chiming in because I was thinking about grace slashes recently),
but here’s what I’ve been doing to slash-beamed graces, in order to show an
option other than \slash. And it visually matches the slashed flags a
little more consistently.

my-hack-slash = {
 \once \override Stem.stencil =
   #(lambda (grob)
  (let* ((x-parent (ly:grob-parent grob X))
 (is-rest? (ly:grob? (ly:grob-object x-parent 'rest
(if is-rest?
empty-stencil
(ly:stencil-combine-at-edge
 (ly:stem::print grob)
 Y
 (+ (ly:grob-property grob 'direction))
 (grob-interpret-markup grob
(markup #:hspace 0.25 #:fontsize 3
#:musicglyph "flags.ugrace"))
 -0.9
}

Here I print the font’s flag slash on the first stem of the grace notes.
You can fiddle with the positioning or even use the downward slash symbol
as needed. I haven’t tested it in cross-staff situations. And by Cross
Staff, I assume you mean the use of Span_stem_engraver and \crossStaff?
Because \slash appears to handle the following kind of cross-staff grace
music as seen in the LSR: https://lsr.di.unimi.it/LSR/Item?id=721

regards,
GR

On Fri, Jan 6, 2023 at 12:33 PM Paul Hodges  wrote:

> I am using a function "\slash" from the snippets repository to add a slash
> to acciaccaturas with multiple notes.  This works fine in isolation.
>
> However, if I use CrossStaff on the same notes, the slash no longer
> appears.  I presume this is because both the slash code and the CrossStaff
> code are modifying the same stem definition, and the CrossStaff code wins.
> But I have no idea how to overcome this, other than by generating this
> particular slash as markup.
>
> Any pointers?
>
> Regards,
> Paul
>


-- 
gregory rowland evans
http://www.gregoryrowlandevans.com
https://github.com/GregoryREvans
https://soundcloud.com/gregory-rowland-evans

CrossStaff and Slashed grace

[Paul Hodges]

I am using a function "\slash" from the snippets repository to add a slash to 
acciaccaturas with multiple notes.  This works fine in isolation.


However, if I use CrossStaff on the same notes, the slash no longer appears.  I 
presume this is because both the slash code and the CrossStaff code are 
modifying the same stem definition, and the CrossStaff code wins.  But I have 
no idea how to overcome this, other than by generating this particular slash as 
markup.


Any pointers?


Regards,
Paul

CrossStaff and Slash.ly
Description: Binary data

Re: problems with release 2.24 on iMac M1 with Ventura 13.0.1

[Jean Abou Samra]

Le 30/12/2022 à 17:00, Mario Bolognani a écrit :

Ok, I’ll try to explain what I have done for convert.ly:

First, following your suggestion, I forced the use of the tools’ #! lines:



Then in Frescobaldi after having used the command convert.ly, this was the 
result:



And, after this Fatal Phyton error… what I have to do?





Sorry for forgetting to reply here. Well, Frescobaldi on macOS is a 
complicated story. First, have you tried running convert-ly on the 
terminal? You should open the terminal application and paste this command:


"/Users/mariobol/Library/CloudStorage/Dropbox/ M U S I C 
A/lilypond-2.24.0/bin/convert-ly" /Users/mariobol/Desktop/file.ly


assuming that your file is file.ly in your Desktop folder, you should 
the second part to match the actual location.


See if that works.



OpenPGP_signature
Description: OpenPGP digital signature

Re: Supress Instrument after P. 1

[Mark Mathias]

On Thu, Jan 5, 2023 at 4:33 PM Wol  wrote:

> On 05/01/2023 20:29, Xavier Scheuer wrote:
> > On Thu, 5 Jan 2023 at 21:11, Mark Mathias  > > wrote:
> >  >
> >  > Partly to duplicate a 1910 popular song layout, and partly to
> > continue growing in LilyPond skill, I'm wanting to suppress the
> > bookTitleMarkup instrument field after page 1.
> >  >
> >  > I've read the sections on Titles and Headers, Customizing, etc., and
> > other parts of the manual, and I've made a number of attempts, but I'm
> > not yet at the point where I understand what to do.
> >
> > Hello,
> >
> > The best way is to look at the definition of oddHeaderMarkup and
> > evenHeaderMarkup in ‘ly/titling-init.ly ’ and
> to
> > modify it accordingly.
> > If you comment (or remove) the lines containing \fromproperty
> > #'header:instrument, you get what you want (see below).
> >
> > \paper {
> >oddHeaderMarkup = \markup
> >\fill-line {
> >  ""
> >  % \unless \on-first-page-of-part \fromproperty #'header:instrument
> >  \if \should-print-page-number \fromproperty
> #'page:page-number-string
> >}
> >evenHeaderMarkup = \markup
> >\fill-line {
> >  \if \should-print-page-number \fromproperty
> #'page:page-number-string
> >  % \unless \on-first-page-of-part \fromproperty #'header:instrument
> >  ""
> >}
> > }
> >
> And, because it's a system file, you have a choice. Do you want to
> modify the system file, or do you want to copy it.
>
> I've done this with header.ly or whatever it's called, and while others
> might disagree, I've got my own copy of this file which I include in my
> projects (don't remember off the top of my head how I did it).
>
> But imho this is the best way to do it. When the system is updated, your
> changes don't get over-written. And you remember, because your layout is
> different from the default, that you have a modified version of a system
> file.
>
> (My header file lays out the piece title, composer, instrument etc in
> typical brass band layout which is both noticeably different and more
> compact from lily's default orchestral layout.)
>
> Cheers,
> Wol
>
>
 Thank you, Xavier. I recognize this now as similar to when I added a boxed
"Score" in the upper LH corner on a previous project, but understand it more
this time.

And, thank you, Wol! That's actually a habit I had already picked up!

(And this time I remembered to bottom-post...)

Blessing,
Mark

Re: \sustainOff on \alternative

[Lukas-Fabian Moser]

Could you consider upgrading to LilyPond 2.24? That's the current 
stable version (and my code was written for it). If that's 
impossible, I can sidestep the use of \after, but frankly, it's 
easier to help you if you provide a working example yourself.


I am fairly certain David K. wrote \after back in the 2.19 era, so 
there should be no particular need to run 2.24.  I found this version 
on an old thread:



after =
#(define-music-function (t e m) (ly:duration? ly:music? ly:music?)
  #{
    \context Bottom <<
  #m
  { \skip $t <> -\tweak extra-spacing-width #empty-interval $e }
    >>
  #})



When I researched variants of \after while working on getting it into 
standard LilyPond (which happened somewhere in the 2.23 line), the 
earliest incarnation I could find was 
https://lists.gnu.org/archive/html/lilypond-devel/2012-09/msg00342.html 
- so that's 2.16 era.


Of course you're right that I might just as well have provided the OP 
with a simple implementation of \after. (But upgrading is a good idea 
anyway, I think - there has been marvelous progress during 2.23.xx I 
think, all due to the work done by Jean, Dan and others.)


Lukas

Re: flat symbol in text?

[Matthew Pierce]

After A/B testing, here is what I ended up using:

  instrumentName = \markup \concat { B \raise #0.8 \magnify #0.6 \flat " Major"}

Adding the \magnify property to the \concat string resized the flat to my 
satisfaction. Thanks for the help!

From: lilypond-user-bounces+piercello=hotmail@gnu.org 
 on behalf of David 
Kastrup 
Sent: Tuesday, January 3, 2023 11:52 AM
To: Matthew Pierce 
Cc: lilypond-user@gnu.org 
Subject: Re: flat symbol in text?

Matthew Pierce  writes:

> How might I display the text "Bb Major," but with the flat symbol
> instead of a lower case "b"?

I'd just use Unicode, namely "B♭ Major".  If you don't get this via
input methods (on my keyboard, it's "[Compose key] # b"), you can
copy&paste from a browser with Unicode tables or from this mail
message...

In contrast to LilyPond's \flat, this will be a text font flat, usually
fitting better with the text font.  If the text font has it, of course.

--
David Kastrup

Re: \sustainOff on \alternative

[Aaron Hill]

On 2023-01-06 5:39 am, Lukas-Fabian Moser wrote:

Hi, I am using 2.22.2,
\after 4 \sustainOff b2 r
​is useless, because of *unknown escaped string*


"Useless" sounds a bit harsh.


In the event OP's native language is not English, it might just be 
unfortunate word choice rather than a criticism of the function's value.


Could you consider upgrading to LilyPond 2.24? That's the current 
stable version (and my code was written for it). If that's impossible, 
I can sidestep the use of \after, but frankly, it's easier to help you 
if you provide a working example yourself.


I am fairly certain David K. wrote \after back in the 2.19 era, so there 
should be no particular need to run 2.24.  I found this version on an 
old thread:



after =
#(define-music-function (t e m) (ly:duration? ly:music? ly:music?)
  #{
\context Bottom <<
  #m
  { \skip $t <> -\tweak extra-spacing-width #empty-interval $e }
>>
  #})



-- Aaron Hill

Re: Frescobaldi & edition engraver

[Federico Bruni]

Il giorno ven 6 gen 2023 alle 01:01:46 +0100, Michael Dietz 
 ha scritto:
I still hope for a native apt installation, but until then with this 
solution, I can use custom fonts, any lilypond version I want, call 
git from Scheme and the "real files on disk" are opened when clicking 
inside Frescobaldi.


For your information, only git is not available on Frescobaldi flatpak 
(it may be added if Frescobaldi will add a proper git support... 
something was done in the past but never finished IIRC).


You can open any file and add custom fonts in the lilypond.org binary 
>=2.24, as long as you grant the right permissions using Flatseal.


https://github.com/flathub/org.frescobaldi.Frescobaldi/

Re: \sustainOff on \alternative

[Lukas-Fabian Moser]

Hi, I am using 2.22.2,
\after 4 \sustainOff b2 r
​is useless, because of *unknown escaped string*


"Useless" sounds a bit harsh.

Could you consider upgrading to LilyPond 2.24? That's the current stable 
version (and my code was written for it). If that's impossible, I can 
sidestep the use of \after, but frankly, it's easier to help you if you 
provide a working example yourself.


Lukas

Re: \sustainOff on \alternative

[cc0_knight--- via LilyPond user discussion]

-- 
 已通过Tutanota 安全发送，立即注册您的加密无广告邮箱！ 
 https://tutanota.com


2023年1月6日 19:23 来自 l...@gmx.de:

>
> Hi,
>
> Am 06.01.23 um 07:54 schrieb  cc0_knight--- via LilyPond user discussion:
>
>> Hi Everyone, Sorry for my english.
>> Skip the first pedal stop(Because it's off-topic),when I write like 
>> this:
>>
>> \repeat volta 2 {
>>    \sustainOn
>> }
>> \alternative {
>>   {  \sustainOff }
>>   { >> \sustainOff >> }
>> }
>>
>
> (Please always give short and compilable code examples!)
>
>
> Perhaps something like:
>
>
>
> \version "2.24.0"
>  
>  {
>    \repeat volta 2 \relative {
>      r4 e'\sustainOn d c
>    }
>    \alternative {
>      {
>    \after 4 \sustainOff b2 r
>      }
>      {
>    \once\omit Staff.SustainPedal
>    <>\sustainOn
>    \after 4 \sustainOff b2 r
>      }
>    }
>  }
>
>
>
> Of course, in a perfect world, spanners like the sustain pedal  would be 
> "reset" to their pre-alternative state at the start of  each alternative. 
> IIRC the world of LilyPond's alternatives  handling has gotten much 
> closer to perfection thanks to Dan's work  over the last few months, but 
> this does not seem to have been part  of it.
>
>
> Lukas
>
>
Hi, I am using 2.22.2,
\after 4 \sustainOff b2 r
​is useless, because of unknown escaped string

Re: \sustainOff on \alternative

[Adam M. Griggs]

Hello, let me quickly ask:

Would that include handling of ties in MIDI output?

On Fri, 6 Jan 2023, 20:24 Lukas-Fabian Moser,  wrote:

> Hi,
> Am 06.01.23 um 07:54 schrieb cc0_knight--- via LilyPond user discussion:
>
> Hi Everyone, Sorry for my english.
> Skip the first pedal stop(Because it's off-topic), when I write like this:
>
> \repeat volta 2 {
>\sustainOn
> }
> \alternative {
>   {  \sustainOff }
>   {  \sustainOff }
> }
>
> (Please always give short and compilable code examples!)
>
> Perhaps something like:
>
> \version "2.24.0"
>
> {
>   \repeat volta 2 \relative {
> r4 e'\sustainOn d c
>   }
>   \alternative {
> {
>   \after 4 \sustainOff b2 r
> }
> {
>   \once\omit Staff.SustainPedal
>   <>\sustainOn
>   \after 4 \sustainOff b2 r
> }
>   }
> }
>
> Of course, in a perfect world, spanners like the sustain pedal would be
> "reset" to their pre-alternative state at the start of each alternative.
> IIRC the world of LilyPond's alternatives handling has gotten much closer
> to perfection thanks to Dan's work over the last few months, but this does
> not seem to have been part of it.
>
> Lukas
>

Re: \sustainOff on \alternative

[Lukas-Fabian Moser]

Hi,

Am 06.01.23 um 07:54 schrieb cc0_knight--- via LilyPond user discussion:

Hi Everyone, Sorry for my english.
Skip the first pedal stop(Because it's off-topic), when I write like this:

\repeat volta 2 {
   \sustainOn
}
\alternative {
  {  \sustainOff }
  {  \sustainOff }
}


(Please always give short and compilable code examples!)

Perhaps something like:

\version "2.24.0"

{
  \repeat volta 2 \relative {
    r4 e'\sustainOn d c
  }
  \alternative {
    {
  \after 4 \sustainOff b2 r
    }
    {
  \once\omit Staff.SustainPedal
  <>\sustainOn
  \after 4 \sustainOff b2 r
    }
  }
}

Of course, in a perfect world, spanners like the sustain pedal would be 
"reset" to their pre-alternative state at the start of each alternative. 
IIRC the world of LilyPond's alternatives handling has gotten much 
closer to perfection thanks to Dan's work over the last few months, but 
this does not seem to have been part of it.


Lukas