Re: combining chords in chords

[Gianmaria Lari]

>
> If the only purpose for using tags is to generate different octaves in the
> midi and the display, it would be much easier to just change the octavation
> of the clef.
>
>
Nice escamotage Carl :))

But no, the visual representation and the midi output do not differ only in
the octave.
g.

Re: combining chords in chords

[David Kastrup]

Carl Sorensen  writes:

> If the only purpose for using tags is to generate different octaves in
> the midi and the display, it would be much easier to just change the
> octavation of the clef.
>
> {
>
>\override Staff.ClefModifier.transparent = ##t
>\clef "treble_8" c1
>
> }
>
> This displays c as c’ in the score, and plays it as c in the midi.

You can also just say

\transposition c

to get the Midi one octave lower.

-- 
David Kastrup

Re: combining chords in chords

[Carl Sorensen]

From: lilypond-user  
on behalf of Carl Sorensen 
Date: Thursday, April 22, 2021 at 4:24 PM
To: Gianmaria Lari , Valentin Petzel 
, Aaron Hill 
Cc: lilypond-user 
Subject: Re: combining chords in chords

If the only purpose for using tags is to generate different octaves in the midi 
and the display, it would be much easier to just change the octavation of the 
clef.

{

   \override Staff.ClefModifier.transparent = ##t
   \clef "treble_8" c1

}

This displays c as c’ in the score, and plays it as c in the midi.

It’s probably better to set the stencil to ##f:

{

   \override Staff.ClefModifier.stencil = ##f
   \clef "treble_8" c1

}

Re: combining chords in chords

[Carl Sorensen]

If the only purpose for using tags is to generate different octaves in the midi 
and the display, it would be much easier to just change the octavation of the 
clef.

{

   \override Staff.ClefModifier.transparent = ##t
   \clef "treble_8" c1

}

This displays c as c’ in the score, and plays it as c in the midi.

Carl

Re: combining chords in chords

[Gianmaria Lari]

Thank you Aaron and Valentin for your help and your codes.
It worked perfectly in my previous example.
Is it possible to make it working also with tags?

Here is a bit of information.
In my code, I use tags to generate two different outputs, one for midi and
one for layout.
So my variables are like this...

ja = {\tag #'midiOut 8 \tag #'screenOut 8}


...and my "score" part is like this:

\score { \keepWithTag #'screenOut \music \layout {} }
\score { \keepWithTag #'midiOut \music \midi{} }


In this way I can specify a visual representation that is very different
from the midi output.

Now let's go back to my problem.
Here it is my code with tags:

\version "2.23.2"
ja = {\tag #'midiOut 8 \tag #'screenOut 8}
jb = {\tag #'midiOut 8 \tag #'screenOut 8 }

music = \new Voice \fixed c << \ja \jb >>

\score { \keepWithTag #'screenOut \music \layout {} }
\score { \keepWithTag #'midiOut \music \layout{} } %here \layout{} should
be \midi{}


This works perfectly and generates two scores:

<< { \tag #'screenOut < c' e' >8 } { \tag #'screenOut < g' b' >8 } >>

<< { \tag #'midiOut   < c e >8   } { \tag #'midiOut   < g b >8   } >>


Now I would like to make it work also with a manual beam. These are the
solution I tried that don't work:

music = \new Voice \fixed c << \ja [\jb] >> % trivial wrong solution

music = \new Voice \fixed c \mergeChords \ja \jb  % Aaron solution

music = \new Voice \fixed c \ja s[ \jb s] % Valentin solution


If you have any suggestion to fix it you're welcome.
Thanks, g.

Re: combining chords in chords

[Gianmaria Lari]

Ciao Valentin,

thanks for your code, it works and it is very simple.

Before asking my question, I had tried a solution similar to yours, I used
<>. Unfortunately it didn't work because I forgot to specify it also after
\kc.

Thanks for your help and the explanation.

Best regards, g.


On Thu, 22 Apr 2021 at 18:48, Valentin Petzel  wrote:

> Hello Gianmaria,
>
> Your problem here is that the postfixed [ adds an event the the note it is
> applied to. Now, this does not work with macros. In such cases you can do
> something like this
>
> << \ka s[ >> \kb << \kc s] >>
>
> So just apply the event to a simultaneous skip.
>
> Cheers,
> Valentin

Re: Lilypond 64-bit binaries

[Jacques Menu]

> Le 22 avr. 2021 à 21:07, Marnen Laibow-Koser  a écrit :
> 
> 
> 
> On Thu, Apr 22, 2021 at 3:04 PM Jacques Menu  > wrote:
> Hello,
> 
> Starting yesterday, I ‘m now running LilyPond 2.20.0  on a Apple mini M1 
> running under Big Sur 11.2.3.
> 
> Cool!
> 
> I can contribute to building Mac OS versions on my machine.
> 
> The reason we’re currently doing Mac builds on MacStadium is that I do not 
> want the availability of Mac builds to depend on someone happening to have a 
> personal Mac available.  So while I appreciate your offer, I’d much rather 
> that we get some public infrastructure set up (if what we already have isn’t 
> sufficient). 
> 
> I’ll try to take a look at this more over the weekend. 
> 
> 
> 
> For my own work, I use AppVeyor, as has been setup by Grame’s Dom Fober, to 
> build installable Mac OS versions.
> 
> Installable on what?


I don’t know all the details. I’ll contact Dom and let you know.

JM

Re: Examples for centered bar numbers

[Jean Abou Samra]

Le 18/04/2021 à 13:18, Jean Abou Samra a écrit :

Please test and comment!


Gentle ping?

Re: Lilypond 64-bit binaries

[Marnen Laibow-Koser]

On Thu, Apr 22, 2021 at 3:04 PM Jacques Menu  wrote:

> Hello,
>
> Starting yesterday, I ‘m now running LilyPond 2.20.0  on a Apple mini M1
> running under Big Sur 11.2.3.
>

Cool!

I can contribute to building Mac OS versions on my machine.
>

The reason we’re currently doing Mac builds on MacStadium is that I do not
want the availability of Mac builds to depend on someone happening to have
a personal Mac available.  So while I appreciate your offer, I’d much
rather that we get some public infrastructure set up (if what we already
have isn’t sufficient).

I’ll try to take a look at this more over the weekend.

>


> For my own work, I use AppVeyor, as has been setup by Grame’s Dom Fober,
> to build installable Mac OS versions.
>

Installable on what?

Is that something that could help solve this issue?
>
> JM
>
-- 
Marnen Laibow-Koser mar...@marnen.org http://www.marnen.org Sent from Gmail
Mobile

Re: Lilypond 64-bit binaries

[Jacques Menu]

Hello,

Starting yesterday, I ‘m now running LilyPond 2.20.0  on a Apple mini M1 
running under Big Sur 11.2.3.
I can contribute to building Mac OS versions on my machine.

For my own work, I use AppVeyor, as has been setup by Grame’s Dom Fober, to 
build installable Mac OS versions. Is that something that could help solve this 
issue?

JM

> Le 22 avr. 2021 à 20:16, Carl Sorensen  a écrit :
> 
> Marnen,
>  
> This is a response to an email from more than a year ago.  Our situation 
> hasn’t improved since then, even though you did all your great work.
>  
> What do you think it would take to make this bundle part of the core project?
>  
> I agree with you that it should be part of our core.  But it doesn’t match up 
> with our current build process, because it cannot be done on non-Apple 
> hardware.
>  
> I see from some old emails that you envision some sort of CI that builds an 
> app bundle.  It would need to have access to Apple hardware to do that, IIUC. 
>  Do you have thoughts about how we would get access to that Apple hardware?
>  
> Thanks,
>  
> Carl
>  
>  
> From: Marnen Laibow-Koser mailto:mar...@marnen.org>>
> Date: Thursday, April 2, 2020 at 2:18 PM
> To: Carl Sorensen mailto:c_soren...@byu.edu>>
> Cc: LilyPond Users mailto:lilypond-user@gnu.org>>, 
> Moritz Heffter mailto:mxo...@me.com>>
> Subject: Re: Lilypond 64-bit binaries
>  
>  
>  
> On Thu, Apr 2, 2020 at 1:49 PM Carl Sorensen  > wrote:
>>  
>>  
>> From: Marnen Laibow-Koser mailto:mar...@marnen.org>>
>> Date: Thursday, April 2, 2020 at 11:07 AM
>> To: Carl Sorensen mailto:c_soren...@byu.edu>>
>> Cc: LilyPond Users mailto:lilypond-user@gnu.org>>, 
>> Moritz Heffter mailto:mxo...@me.com>>
>> Subject: Re: Lilypond 64-bit binaries
>>  
>>  
>>  
>> On Thu, Apr 2, 2020 at 1:02 PM Carl Sorensen > > wrote:
>>> I note that Moritz mentions he gets the same results from the MacPorts 
>>> build.  Perhaps the MacPorts people could provide some insight.
>>  
>> Hmm.  I wonder if I should try using a more recent version of Mac OS and 
>> Xcode on the build box.  I was using the oldest possible version in order to 
>> produce the most backward-compatible build. 
>>  
>> But...if this is a general issue with Catalina, why are so few users 
>> affected by it, and why are users on Mojave among those affected?
>>  
>> I don’t think it’s a general issue.  I think it’s a specific issue, that 
>> varies from machine to machine.  My only suggestion was that perhaps 
>> somebody in the MacPorts group might be able to provide some debugging 
>> helps.  Hopefully the issue is the same in MacPorts as in your app bundle, 
>> so if it can be resolved in MacPorts it can be resolved in the app bundle….
>  
> Yeah, that might be a good point.  I think this is the first time we've seen 
> a MacPorts build have this same problem.
>  
> Also: it's not *my* bundle, except in that I figured out the process to build 
> it.  Ideally, it is the LilyPond project's bundle: I want this to be accepted 
> into the core project, not remain my own personal thing.
>  
>>  
>> Carl
>  
> Best, 
> -- 
> Marnen Laibow-Koser
> mar...@marnen.org 
> http://www.marnen.org 

Re: Lilypond 64-bit binaries

[Marnen Laibow-Koser]

On Thu, Apr 22, 2021 at 2:32 PM Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:

> Hi Carl,
>
> > Do you have thoughts about how we would get access to that Apple
> hardware?
>
> I believe I have a client who might be willing to donate time on an
> internet-accessible Apple server. Feel free to ping me off-list if that
> option is worth pursuing.
>

We already have an Internet-accessible Mac available—our current build box
at MacStadium.  Is that insufficient?


> Cheers,
> Kieren.


Best,
-- 
Marnen Laibow-Koser
mar...@marnen.org
http://www.marnen.org

Re: Lilypond 64-bit binaries

[Marnen Laibow-Koser]

On Thu, Apr 22, 2021 at 2:48 PM Karlin High  wrote:

> On 4/22/2021 1:32 PM, Kieren MacMillan wrote:
> > I believe I have a client who might be willing to donate time on an
> internet-accessible Apple server.
>
> I'm pretty sure the original discussion mentioned MacStadium, a macOS
> hosting service.
>
> 
>
> "To support the FOSS community, MacStadium is offering FREE Mac mini
> hosting for developers working on open source projects."
>

I think we typed our messages at the same time.  A free OSS account at
MacStadium is in fact our current build box.


> --
> Karlin High
> Missouri, USA
>

Best,
-- 
Marnen Laibow-Koser
mar...@marnen.org
http://www.marnen.org

Re: Lilypond 64-bit binaries

[Karlin High]

On 4/22/2021 1:32 PM, Kieren MacMillan wrote:

I believe I have a client who might be willing to donate time on an 
internet-accessible Apple server.


I'm pretty sure the original discussion mentioned MacStadium, a macOS 
hosting service.




"To support the FOSS community, MacStadium is offering FREE Mac mini 
hosting for developers working on open source projects."

--
Karlin High
Missouri, USA

Re: Lilypond 64-bit binaries

[Kieren MacMillan]

Hi Carl,

> Do you have thoughts about how we would get access to that Apple hardware?

I believe I have a client who might be willing to donate time on an 
internet-accessible Apple server. Feel free to ping me off-list if that option 
is worth pursuing.

Cheers,
Kieren.


Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: kie...@kierenmacmillan.info

Re: Lilypond 64-bit binaries

[Carl Sorensen]

Marnen,

This is a response to an email from more than a year ago.  Our situation hasn’t 
improved since then, even though you did all your great work.

What do you think it would take to make this bundle part of the core project?

I agree with you that it should be part of our core.  But it doesn’t match up 
with our current build process, because it cannot be done on non-Apple hardware.

I see from some old emails that you envision some sort of CI that builds an app 
bundle.  It would need to have access to Apple hardware to do that, IIUC.  Do 
you have thoughts about how we would get access to that Apple hardware?

Thanks,

Carl


From: Marnen Laibow-Koser 
Date: Thursday, April 2, 2020 at 2:18 PM
To: Carl Sorensen 
Cc: LilyPond Users , Moritz Heffter 
Subject: Re: Lilypond 64-bit binaries



On Thu, Apr 2, 2020 at 1:49 PM Carl Sorensen 
mailto:c_soren...@byu.edu>> wrote:


From: Marnen Laibow-Koser mailto:mar...@marnen.org>>
Date: Thursday, April 2, 2020 at 11:07 AM
To: Carl Sorensen mailto:c_soren...@byu.edu>>
Cc: LilyPond Users mailto:lilypond-user@gnu.org>>, 
Moritz Heffter mailto:mxo...@me.com>>
Subject: Re: Lilypond 64-bit binaries



On Thu, Apr 2, 2020 at 1:02 PM Carl Sorensen 
mailto:c_soren...@byu.edu>> wrote:
I note that Moritz mentions he gets the same results from the MacPorts build.  
Perhaps the MacPorts people could provide some insight.

Hmm.  I wonder if I should try using a more recent version of Mac OS and Xcode 
on the build box.  I was using the oldest possible version in order to produce 
the most backward-compatible build.

But...if this is a general issue with Catalina, why are so few users affected 
by it, and why are users on Mojave among those affected?

I don’t think it’s a general issue.  I think it’s a specific issue, that varies 
from machine to machine.  My only suggestion was that perhaps somebody in the 
MacPorts group might be able to provide some debugging helps.  Hopefully the 
issue is the same in MacPorts as in your app bundle, so if it can be resolved 
in MacPorts it can be resolved in the app bundle….

Yeah, that might be a good point.  I think this is the first time we've seen a 
MacPorts build have this same problem.

Also: it's not *my* bundle, except in that I figured out the process to build 
it.  Ideally, it is the LilyPond project's bundle: I want this to be accepted 
into the core project, not remain my own personal thing.


Carl

Best,
--
Marnen Laibow-Koser
mar...@marnen.org
http://www.marnen.org

Re: 2nd stanza lyrics cont

[Valentin Petzel]

Hello Stephane,

You need to use \new Lyrics to create a new Lyrics context, not \context 
Lyrics.

So basically put a \new everywhere where you put a \context. Basically \new 
creates a new Context, while \context is used in \layout Blocks to specify a 
Context as a sort of namespace, so instead of writing \override 
Context.property you can simply \override property.

Cheers,
Valentin

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

Re: combining chords in chords

[Valentin Petzel]

Hello Gianmaria,

Your problem here is that the postfixed [ adds an event the the note it is 
applied to. Now, this does not work with macros. In such cases you can do 
something like this

<< \ka s[ >> \kb << \kc s] >>

So just apply the event to a simultaneous skip.

Cheers,
Valentin

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

Re: combining chords in chords

[Gianmaria Lari]

Dear Aaron,

> How can I solve this?
>
> Here's a way that involves merging the elements of the two EventChords:
> [...]


that's great It seems to work perfectly.

Thanks a lot Aaron!!
Gianmaria

Re: Confirming no color gradients

[Kevin Barry]

Hi Michael,

There isn't an inbuilt way to gradually change a color, but it's
certainly doable using some scheme.  This snippet isn't what you're
asking for, but it does show how to programmatically manipulate
colors: 
http://lilypond.org/doc/v2.18/Documentation/snippets/pitches#pitches-coloring-notes-depending-on-their-pitch.

Kevin

On Thu, 22 Apr 2021 at 02:38, Michael Blankenship  wrote:
>
> I'm just hoping to confirm that Lilypond does not have any way to generate or 
> apply continuous color gradients to grobs. It certainly doesn't seem like it, 
> since a search for the term returns zero results, a first for me.
> So, no color gradients, right?
> M

Re: combining chords in chords

[Aaron Hill]

On 2021-04-22 6:01 am, Gianmaria Lari wrote:

I have some variables, each containing one chord as in the following
example:

[...]

How can I solve this?


Here's a way that involves merging the elements of the two EventChords:


\version "2.22.0"

ja = 8
jb = 8
jc = 8

mergeChords =
#(begin
  (define (event-chord-music? arg)
   (music-type-predicate 'event-chord))
  (define-music-function
   (first second)
   (event-chord-music? event-chord-music?)
   (set! first (ly:music-deep-copy first))
   (ly:music-set-property! first 'elements
(append
 (ly:music-property first 'elements)
 (ly:music-property second 'elements)))
   first))

ka = \mergeChords \ja \jb
kb = \mergeChords \ja \jc
kc = \mergeChords \jb \jc

\new Voice \fixed c' { \ka[ \kb \kc] }


Could be some hidden quirks with this approach, but it does seem to 
allow the manual beaming to work.



-- Aaron Hill

combining chords in chords

[Gianmaria Lari]

I have some variables, each containing one chord as in the following
example:

ja = 8
jb = 8
jc = 8



and some other variables combining them, like this:

ka = <<\ja \jb>>
kb = <<\ja \jc>>
kc = <<\jb \jc>>



This is a working example engraving \ka \kb and \kc:

\version "2.23.2"
ja = 8
jb = 8
jc = 8

ka = <<\ja \jb>>
kb = <<\ja \jc>>
kc = <<\jb \jc>>

\new Voice \fixed c' {\ka \kb \kc}


Now I would like to manually beam my pseudo-chords ka,kb,kc like this (it
doesn't work):

\new Voice \fixed c' {\ka[ \kb \kc]}


but I get:

warning: Unattached BeamEvent
\new Voice \fixed c' {\ka[ \kb \kc
  ]}


If I'm not wrong this is because \ka, \kb and \kc are not chords, they are
more complex musical expressions and beaming is not defined for that.
My code would work if \ka would be

8


but instead \ka is something like

<<   >>




How can I solve this?
Thanks, g.

RE: Noob can't make 2nd stanza lyrics

[Gregory Hollands]

Stéphane,

Take a look at:
   http://lilypond.org/doc/v2.19/Documentation/notation/vocal-music

http://lilypond.org/doc/v2.19/Documentation/notation/techniques-specific-to-lyrics

Best Regards,
Greg