organizing shared libraries

2024-04-03 Thread Tom Brennan
Hello

I'm going through documentation, refamiliarizing myself with Lilypond,
and trying to define a process for daily work that I like. One thing
I'm pretty sure I'll want is to create a shared library that will live
in its own repository. Perhaps more than one.

Looking at [this
documentation](https://lilypond.org/doc/v2.24/Documentation/notation/including-lilypond-files),
what I think makes sense is to bundle the `*.ly` files into a guile
module like `lib.scm`, using something like `ly:parse-init` to import
`lib.ly` which would `\include` all the other `*.ly` files, sort of
like the way it's done in `lily.scm` for `declarations-init.ly`. And
then I would import the guile module that would bootstrap everything
like `#(use-modules (special module))` in a particular project.
Assuming the guile module makes it into the %load-path.

There's probably a simpler way to do this and I'm just overthinking
it. What do other people like doing for shared ly libraries?

Thanks
Tom



Re: Raising all metronome marks

2024-04-03 Thread Ben Bradshaw
Ah man! Forgetting the Score context in my override strikes again! The
padding was my initial choice, but that wasn't working either.

Thanks for the help, one of these days I'll remember to check that first
when something isn't working how I think it should.

Best,
Ben

On Wed, Apr 3, 2024, 12:03 AM Sebastien Richard 
wrote:

>
> Hello,
>
> Here is what I mostly use :
>
> \override Score.MetronomeMark.padding = #6
>
> just before the tempo mark (works with lilypond 2.24.2)
>
>
> I have another example with a markup but it's much more complex (I can
> send it if you want)
>
> BR,
>
> ---
>  Sébastien
>
>
> --
> *From:* lilypond-user-bounces+richardsgjm=hotmail@gnu.org
>  on behalf of Ben
> Bradshaw 
> *Sent:* Wednesday, April 3, 2024 05:52
> *To:* Lily Pond 
> *Subject:* Raising all metronome marks
>
> Hello,
> I like my tempo markings to be a bit higher than the default in lilypond.
> I'm struggling to figure out how to globally raise them. I can do it
> locally with \offset Y-offset 3 for instance, of \tweak Y-offset #3, but I
> can't get it to work globally. I've tried \override MetronomeMark.Y-offset
> = #3 as well as \offset Y-offset 3 MetronomeMark , but neither seems to
> work. Any suggestions?
>
> Thanks,
> Ben
>


Re: Raising all metronome marks

2024-04-03 Thread Sebastien Richard

Hello,

Here is what I mostly use :

\override Score.MetronomeMark.padding = #6

just before the tempo mark (works with lilypond 2.24.2)


I have another example with a markup but it's much more complex (I can send it 
if you want)

BR,

---
 Sébastien



From: lilypond-user-bounces+richardsgjm=hotmail@gnu.org 
 on behalf of Ben 
Bradshaw 
Sent: Wednesday, April 3, 2024 05:52
To: Lily Pond 
Subject: Raising all metronome marks

Hello,
I like my tempo markings to be a bit higher than the default in lilypond. I'm 
struggling to figure out how to globally raise them. I can do it locally with 
\offset Y-offset 3 for instance, of \tweak Y-offset #3, but I can't get it to 
work globally. I've tried \override MetronomeMark.Y-offset = #3 as well as 
\offset Y-offset 3 MetronomeMark , but neither seems to work. Any suggestions?

Thanks,
Ben