At 17:41 on 01 Mar 2023, Kenneth Wolcott wrote:
> Hi;
> I think that convert-ly should write the current version to the
> converted file(s).
> If that statement is correct, then Lilypond version 2.24.1 writes the
> older version (2.24.0) to the converted file(s).
Please see the -c,
Thanks, Jean.
That makes sense.
But the implication is it should based on the fact that the conversion
history shows all the minor versions along the way...
Thanks,
Ken
On Wed, Mar 1, 2023 at 6:05 PM Jean Abou Samra wrote:
>
> Le mercredi 01 mars 2023 à 17:41 -0800, Kenneth Wolcott a écrit :
Le mercredi 01 mars 2023 à 17:41 -0800, Kenneth Wolcott a écrit :
> Hi;
>
> I think that convert-ly should write the current version to the
> converted file(s).
>
> If that statement is correct, then Lilypond version 2.24.1 writes the
> older version (2.24.0) to the converted file(s).
I
Hi;
I think that convert-ly should write the current version to the
converted file(s).
If that statement is correct, then Lilypond version 2.24.1 writes the
older version (2.24.0) to the converted file(s).
Here's my test script invocation:
./test_conversion_version.bash | tee
I concur on entering all music in concert pitch. You may find the
auto-transpose snippet from OpenLilyLib helpful (
https://github.com/openlilylib/oll-misc/tree/master/pitch), as you can
simply write "\transposition bf" instead of wrapping all transposed blocks
in "\transpose x y { }". This is
On 28/02/2023 22:02, TJ Kolev wrote:
I would appreciate any suggestions for the above issues. Or comments on
how I am putting together the whole score.
I do a load of brass (and concert) band stuff. And because I play
trombone I'm sensitive to transposition issues. So I always store my
parts
I did try to do the first note trick, but obviously I didn't get the syntax
right. Got it now.
Didn't get to tags and quoting. Those look very promising. Will
investigate. Thank you for the references!
tjk :)
On Tue, Feb 28, 2023 at 5:50 PM Saul Tobin
wrote:
>
>
I have run into what may be an "ugly" issue, but I thought I'd post here
first.
If you have a group of notes beamed across staves, you sometimes get an
ugly beam slope.
\version "2.25.2"
\score {
\new PianoStaff <<
\new Staff = "upper" {
\voiceOne
\change Staff = "lower"
very helpful, thx Xavier!
On Wed, 1 Mar 2023 at 13:07, Johannes Roeßler wrote:
>
> Hi List,
>
> how can I change the size of the \slashSeparator?
Hello,
slashSeparator is a markup.
You can scale it for example with the scale command
system-separator-markup = \markup \scale #'(1.5 . 1.5) {
On Wed, 1 Mar 2023 at 13:07, Johannes Roeßler wrote:
>
> Hi List,
>
> how can I change the size of the \slashSeparator?
Hello,
slashSeparator is a markup.
You can scale it for example with the scale command
system-separator-markup = \markup \scale #'(1.5 . 1.5) { \slashSeparator }
% 150% in X
Johan:
Does this work for yoy?
https://lsr.di.unimi.it/LSR/Item?id=907
Mark
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Johan
Smolinski
Sent: Wednesday, March 1, 2023 12:54 AM
To:
Hi List,
how can I change the size of the \slashSeparator?
Best regards
Joei
On Tue, 2023-02-28 at 20:16 +, Timothy Lanfear wrote:
> On 28/02/2023 17:53, Richard Shann wrote:
> In a complex score with a DynamicsStaff placed above the music for
> markups and another below for the dynamics an unusually large space
> opened up below the music and above the dynamics.
> I
Le mercredi 01 mars 2023 à 09:54 +0100, Johan Smolinski a écrit :
> I asked this in the facebook group, but was rdirected to this mailing list,
> so... Here I am. :)
>
> How can I print chordnames as roman numbers relative to given key? For
> instance, in key of C (given by \key c \major), I
I asked this in the facebook group, but was rdirected to this mailing list,
so... Here I am. :)
How can I print chordnames as roman numbers relative to given key? For
instance, in key of C (given by \key c \major), I want the chord c:7
printed as I7 while in key of F, I want c:7 printed as V7.
15 matches
Mail list logo
