Re: Key signatures in MIDI output

Yes - that would be the way to go. However, the midi notes will play correctly anyway, and the Lilypond output is far better than the staff view in my sequencer. There is even a virtue to it as when I am playing along to the sequencer and I forget what key I am playing in, all my sharps

Re: Key signatures in MIDI output

Giles Boardman writes: > Hello, > > I have figured "it" out - Cakewalk expects Key Signature to be in > Track 0 of a Midi file and Lilypond puts it in whichever track has it > in, which is much more sensible. I realized this while compiling the > cry for help below,

Re: Key signatures in MIDI output

Hello, I have figured "it" out - Cakewalk expects Key Signature to be in Track 0 of a Midi file and Lilypond puts it in whichever track has it in, which is much more sensible. I realized this while compiling the cry for help below, so I've left my workings out in the message, but

Re: Key signatures in MIDI output

On Sat 11 May 2024 at 15:14:47 (+), Giles Boardman wrote: > You are, of course, right. Your evidence is clear. The position of the \key > command seems a strong candidate but I can't get it into the .MID even in the > simplest of snippet. > > As I mentioned I also have ot

Re: Key signatures in MIDI output

Giles Boardman writes: > You are, of course, right. Your evidence is clear. The position of the \key > command seems a strong candidate but I can't get it into the .MID even in the > simplest of snippet. > > As I mentioned I also have other behaviour I can't explain s

Re: Key signatures in MIDI output

You are, of course, right. Your evidence is clear. The position of the \key command seems a strong candidate but I can't get it into the .MID even in the simplest of snippet. As I mentioned I also have other behaviour I can't explain so it could also be version related. I reinstalled

Re: Key signatures in MIDI output

On Sat, 11 May 2024, Giles Boardman wrote: > I have now been more systematic in my approach and conclude that \key is not > reflected in MIDI output. I tried various positions for events and in each Well, it definitely is reflected in the output in my own tests. The example code I posted

Re: Key signatures in MIDI output

msk...@ansuz.sooke.bc.ca writes: > On Sat, 11 May 2024, Giles Boardman wrote: > >> When I create MIDI output from Lilypond, if I have imported a MIDI file and >> then resaved it with changes made in LilyPond, the output is like that, too. > > Lilypond as such does not import MIDI files. I think

Re: Key signatures in MIDI output

r! I have now been more systematic in my approach and conclude that \key is not reflected in MIDI output. I tried various positions for events and in each case I got Time Signature information in my MID file but not Key Signature when viewed in Staff View. But the conclusive evidence for me is t

Re: Key signatures in MIDI output

ftware other than Lilypond, and that is relevant to the issues you're experiencing. On the off chance that you might be using midi2ly, I tried round-tripping my example code through that, and got suggestive results. I take this code: \score { \new Voice { \key c \major c'4 d'4 e'4 f'4 |

Re: Key signatures in MIDI output

> On 10 May 2024, at 22:21, msk...@ansuz.sooke.bc.ca wrote: > > On Fri, 10 May 2024, Hans Åberg wrote: > >>> signature. The MIDI file does not contain that information; it is up to >>> whatever software reads the MIDI file, to display it appropriately. >> >> So to go back to staff notation

Re: Key signatures in MIDI output

Giles Boardman writes: > However, when I create new files, I am getting output that is as if I > have chosen to write everything in C major, with all the flats and > sharps shown explicitly. Nevertheless, the screen and pdf output are > written in, for example G, with no sharps on the individual

Re: Key signatures in MIDI output

The issue is consistency and I'm perhaps not using the terms precisely enough to describe what I am seeing. I understand about MIDI notes and that they are neither sharpened not flattened, but each has their own value. In my sequencer (Cakewalk ProAudio 9), if my piece has a Key Signature

Re: Key signatures in MIDI output

I notice that my MIDI output doesn't reflect the > key signatures (everything is in C with accidentals) while my > on-screen preview (even when I only have a midi block and no layout > block) and the .pdf have sharps and flats at the beginning of the > staff. > > The snippet abou

Re: Key signatures in MIDI output

On Fri, 10 May 2024, Hans Åberg wrote: > > signature. The MIDI file does not contain that information; it is up to > > whatever software reads the MIDI file, to display it appropriately. > > So to go back to staff notation from MIDI, one must know what enharmonic > equivalences that have been

Re: Key signatures in MIDI output

> On 10 May 2024, at 21:50, msk...@ansuz.sooke.bc.ca wrote: > > On Fri, 10 May 2024, Hans Åberg wrote: > >> Programs like ABC work so that one writes the music without accidentals, >> and then apply a key signature to get them. It was my reading that the >> OP

Re: Key signatures in MIDI output

On Fri, 10 May 2024, Hans Åberg wrote: > Programs like ABC work so that one writes the music without accidentals, > and then apply a key signature to get them. It was my reading that the > OP asked for that. Okay. I didn't read it that way because the OP said he was getting corre

Re: Key signatures in MIDI output

> On 10 May 2024, at 20:18, msk...@ansuz.sooke.bc.ca wrote: > > On Fri, 10 May 2024, Hans Åberg wrote: > >> To change the MIDI output, you will need to change the notes, say by >> transposing or something else. > > MIDI files can include events ("

Re: Key signatures in MIDI output

On Fri, 10 May 2024, Hans Åberg wrote: > To change the MIDI output, you will need to change the notes, say by > transposing or something else. MIDI files can include events ("key-change meta messages") for key signatures, each specifying a root and whether it's major or minor

Re: Key signatures in MIDI output

gt; > So, I tried it and I notice that my MIDI output doesn't reflect the key > signatures (everything is in C with accidentals) while my on-screen preview > (even when I only have a midi block and no layout block) and the .pdf have > sharps and flats at the beginning of the staff. >

Key signatures in MIDI output

Hello, I am reading that I can create MIDI output which is different from the printed output. For example, I can unfold repeats in the midi output but use alternative endings and double barlines in my score. Awesome! So, I tried it and I notice that my MIDI output doesn't reflect the key

Re: Minimize flats or sharps in transposed key signature?

> I'm using \transpose pretty heavily, and I'm running into an issue I don't > quite know how to solve. I'm aware of the \naturalizeMusic hack described > in the LilyPond documentation. I'm looking for something similar, but for > key signatures. This was discussed in the past, f

Minimize flats or sharps in transposed key signature?

I'm using \transpose pretty heavily, and I'm running into an issue I don't quite know how to solve. I'm aware of the \naturalizeMusic hack described in the LilyPond documentation. I'm looking for something similar, but for key signatures. When a \key specification gets transposed, I would like

Re: remove key change at end of line

That did the trick! Thank you, Xavier. > From: "Xavier Scheuer" > To: "bobroff" > Cc: "Lillypond Users Mailing List" > Sent: Monday, March 25, 2024 9:37:38 PM > Subject: Re: remove key change at end of line > On Mon, 25 Mar 2024 at 22:19, [ m

Re: remove key change at end of line

On Mon, 25 Mar 2024 at 22:19, bobr...@centrum.is wrote: > > I want to remove a key change from the ends of lines/systems. I am *not* referring to just key cancellation, which I do also want. I mean, at the end of a line the new key should not appear before the new line. I haven't worked

Re: remove key change at end of line

On 2024-03-25 2:18 pm, bobr...@centrum.is wrote: I want to remove a key change from the ends of lines/systems. I am *not* referring to just key cancellation, which I do also want. I mean, at the end of a line the new key should not appear before the new line. I haven't worked it out

remove key change at end of line

I want to remove a key change from the ends of lines/systems. I am *not* referring to just key cancellation, which I do also want. I mean, at the end of a line the new key should not appear before the new line. I haven't worked it out. -David

Re: Transpose from major to minor key

namely octave, "note name" and alteration. Wol's remarks (I think) alluded to the difference between LilyPond and, e.g., MuseScore, in that in LilyPond the meaning of naked note names does not change when selecting a new key signature: In MuseScore, if I switch to e-flat major and hit

Re: Transpose from major to minor key

On Thu, 11 Jan 2024, Wol wrote: > You need to remember lilypond thinks in terms of pitch, not note names. Unlike > some (most?) other music software. So "\transpose g e" says "transpose EVERY > note up A TONE". I'm not sure it's quite right to say that Lilypond thinks in terms of pitch, not note

Re: Transpose from major to minor key

On 10/01/2024 21:26, Butter Cream wrote: Hi, I have a piece of music written in the key of G major and I want the pitches to transpose to e minor. How do I do this. When I use the command \transpose g e it changes to E major (all g notes are sharped) You need to remember lilypond thinks

Re: Transpose from major to minor key

-transformations On Wed, Jan 10, 2024 at 5:20 PM Aaron Hill via LilyPond user discussion < lilypond-user@gnu.org> wrote: On 2024-01-10 1:26 pm, Butter Cream wrote: > Hi, I have a piece of music written in the key of G major and I want > the pitches to transpose to e minor. How do I do this

Re: Transpose from major to minor key

On 2024-01-10 1:26 pm, Butter Cream wrote: Hi, I have a piece of music written in the key of G major and I want the pitches to transpose to e minor. How do I do this. When I use the command \transpose g e it changes to E major (all g notes are sharped) I think you'll need to use

Transpose from major to minor key

Hi, I have a piece of music written in the key of G major and I want the pitches to transpose to e minor. How do I do this. When I use the command \transpose g e it changes to E major (all g notes are sharped) Steve

Re: clefs, time signatures, and key signatures

> does the new proposed spacing mean that the time signatures are not > aligned across staves any more but were before? No, they are aligned as before. Werner

Re: clefs, time signatures, and key signatures

Hi Werner, does the new proposed spacing mean that the time signatures are not aligned across staves any more but were before? Best, Michael

Re: clefs, time signatures, and key signatures

>>> please have a look at Merge Request 2188 and comment there on how >>> to proceed with the new distances between clefs and time >>> signatures, together with the new distances between clefs and key >>> signatures. >>> >>> http

Re: Continuation slur and key signature with many sharps

On Wed, Dec 13, 2023 at 12:03 PM Jean Abou Samra wrote: > See issue #6639 . > Thanks. I searched for "continued" but not "broken." I'll know better next time (maybe). -- Knute Snortum

Re: Continuation slur and key signature with many sharps

See [issue #6639](https://gitlab.com/lilypond/lilypond/-/issues/6639). signature.asc Description: This is a digitally signed message part

Continuation slur and key signature with many sharps

Hi List, Here is something that pops up now and then when I'm engraving with LilyPond: if a key signature has a lot of sharps, like the key of e major, sometimes a continuation slur will be too close to the key signature. Here is a snippet: %%% \version "2.25.11" \paper { ragged-r

Re: clefs, time signatures, and key signatures

For what it's worth, I think the original suggestion (with the top-left clef adjusted by -4.4%) is the better of the two. I do understand that there's an argument to be made against adjusting clefs that aren't /too/ bad, but the adjusted versions of the treble clefs /are/ better imo. With

Re: clefs, time signatures, and key signatures

> Thanks, but I would like to know whether you prefer the top > (alto-based) or bottom (treble-based) image on > > https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 Top (alto-based) is 6 days ago and bottom (treble-based) is 4 days ago as of today? Of those two I prefer bottom as

Re: clefs, time signatures, and key signatures

> I’ve just looked at the images and especially w/r to the Alto clef I > strongly prefer the new spacing. For the others there are spots > where I’m not sure it is too tight but overall the new spacing > appears to be more balanced. > > I thus think the new spacing is better overall. Thanks,

Re: clefs, time signatures, and key signatures

Mobil gesendet > Am 09.12.2023 um 08:12 schrieb Werner LEMBERG : > >  >>> please have a look at Merge Request 2188 and comment there on how >>> to proceed with the new distances between clefs and time >>> signatures, together with the new distances

Re: clefs, time signatures, and key signatures

>> please have a look at Merge Request 2188 and comment there on how >> to proceed with the new distances between clefs and time >> signatures, together with the new distances between clefs and key >> signatures. >> >> https://gitlab.com/lil

Re: clefs, time signatures, and key signatures

>> please have a look at Merge Request 2188 and comment there on how >> to proceed with the new distances between clefs and time >> signatures, [...] > > FWIW, I think the Petrucci clef distances are a big improvement and > make incipits closer to what they usually look like in sources. Yes,

Re: clefs, time signatures, and key signatures

On Tue, 5 Dec 2023, 07:42 Werner LEMBERG, wrote: > > Folks, > > > please have a look at Merge Request 2188 and comment there on how to > proceed with the new distances between clefs and time signatures, > together with the new distances between clefs and key signatures. >

Re: clefs, time signatures, and key signatures

ith the new distances between clefs and time signatures, >> together with the new distances between clefs and key signatures. >> >> https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 >> >> The question is whether the new distances should be based on the &g

Re: clefs, time signatures, and key signatures

> please have a look at Merge Request 2188 and comment there on how to > proceed with the new distances between clefs and time signatures, > together with the new distances between clefs and key signatures. > > https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 &g

clefs, time signatures, and key signatures

Folks, please have a look at Merge Request 2188 and comment there on how to proceed with the new distances between clefs and time signatures, together with the new distances between clefs and key signatures. https://gitlab.com/lilypond/lilypond/-/merge_requests/2188 The question is whether

Re: Overwrite key signature with numbers

Alright, thanks for your time. I really appreciate it. Robert El vie, 13 oct 2023 18:41, Jean Abou Samra escribió: > From what you say, I believe you are worried about chords, am I right? > > > > It's more fundamental than that: there is only *one* StaffSymbol per > staff, for the duration of

Re: Overwrite key signature with numbers

> From what you say, I believe you are worried about chords, am I right? It's more fundamental than that: there is only *one* StaffSymbol per staff, for the duration of the *entire* score. That StaffSymbol has a ledger-extra property that applies to *all* ledger lines on that staff anywhere in

Re: Overwrite key signature with numbers

Thanks for your response Jean, So, the music notation system I am writing has assimetrical staves with only 4 lines, which means there is a blank space wider than the other two white spaces. For notes that fall into the wider blank space, I want a ledger line value of 2, but for the note that

Re: Overwrite key signature with numbers

Le vendredi 13 octobre 2023 à 15:36 +0200, Robert Mengual a écrit : > In the example below, I am receiving the following error:  Wrong type argument > in position 1 (expecting Stream_event): #f > > I think I am not receiving a grob in this case. You are, but this grob doesn't have an event

Re: Overwrite key signature with numbers

Thank you again Valentin, this is extremely helpful for me. In fact, I have been able to override other properties based on the solution you provided. I'm slowly making progress. However there is something I am stuck with, based on your response above: > If an overriden property expects a

Re: Overwrite key signature with numbers

Valentin Petzel writes: > Damn it, turns out the key engraver has an hardcoded path to always create > Key > Cancellations for keys with no alteration. > > So one would need to do > > \override KeyCancellation.stencil = ##f > > which is of course a bit wonky as c

Re: Overwrite key signature with numbers

Oh David's right, if the music ends with no alterations it is printing the key cancellation, even when it has been explicitely set to false.[image: image.png] What can I do in this case? I would like to keep the number+alteration but remove the 7 natural signs before that. Thank you, Robert El

Re: Overwrite key signature with numbers

Am Dienstag, 3. Oktober 2023, 12:55:21 CEST schrieb Robert Mengual: > Thanks a lot Valentin, that's simply perfect! > > However, after reading a lot of the documentation I think I would have > never been able to find any solution close to yours. I am very confused > with a few things, and I can't

Re: Overwrite key signature with numbers

Damn it, turns out the key engraver has an hardcoded path to always create Key Cancellations for keys with no alteration. So one would need to do \override KeyCancellation.stencil = ##f which is of course a bit wonky as compared to telling Lilypond to not create Cancellations in the first

Re: Overwrite key signature with numbers

Robert Mengual writes: > Oh David's right, if the music ends with no alterations it is printing the > key cancellation, even when it has been explicitely set to false.[image: > image.png] > What can I do in this case? I would like to keep the number+alteration but > remove the

Re: Overwrite key signature with numbers

enter #:number (number->string (abs tot)) acc))) > \override KeySignature.stencil = #ly:text-interface::print > printKeyCancellation = ##f > } > } > > expt = { \key c \major c d e f } > > { > \clef bass > \expt > \transpose c cis \expt > \tran

Re: Overwrite key signature with numbers

> (else (markup #:vcenter #:musicglyph > "accidentals.flat") > (markup #:vcenter #:number (number->string (abs tot)) acc))) > \override KeySignature.stencil = #ly:text-interface::print > printKeyCancellation = ##f > } > } >

Re: Overwrite key signature with numbers

#:vcenter #:number (number->string (abs tot)) acc))) \override KeySignature.stencil = #ly:text-interface::print printKeyCancellation = ##f } } expt = { \key c \major c d e f } { \clef bass \expt \transpose c cis \expt \transpose c des \expt \transpose c d \expt \transpose c di

Overwrite key signature with numbers

Hi, I am trying to overwrite the key signature for my custom music notation so that instead of displaying the sharp and flat icons, it shows a given number and the alteration. So, for example, E Major would show 4# instead of . I have been able to get the desired output by hardcodeing

Re: Print brace, clef and key signature at start of Coda separated by blank space

still a complex matter. Now if i understand correctly, this code only handles start brace, but cross-staff vertical line is drawn manually with markup? I've actually did it similarly with markup: \version "2.24.1" upper = { \key as \minor c'1 \stopStaff s1*4 \once \omit Sta

Re: Print brace, clef and key signature at start of Coda separated by blank space

> Oops: I am so sorry, Jean. Must work out how to turn AutoCorrect off, or > actually read messages before I send them.  > > Apologies, once again No worries, I didn't take it personally, I was just amused at seeing *yet another* spelling for my name :) (You're far from the only one

Re: Print brace, clef and key signature at start of Coda separated by blank space

Oops: I am so sorry, Jean. Must work out how to turn AutoCorrect off, or actually read messages before I send them.  Apologies, once again Alex > On Aug 18, 2023, at 12:07 PM, Jean Abou Samra wrote: >> Le 18 août 2023 à 12:59, Alex Voice via LilyPond user discussion >> a écrit : >> >>

Re: Print brace, clef and key signature at start of Coda separated by blank space

> Le 18 août 2023 à 12:59, Alex Voice via LilyPond user discussion > a écrit : > > There is a way that was devised by Jean About Samoa earlier this year Jean Abou Samra would like to say hi :)

Re: Print brace, clef and key signature at start of Coda separated by blank space

Hi Vlado, > Hello everyone, example: > > > > \version "2.24.1" > > > > > upper = { > > \key as \minor > > c'1 > > \stopStaff > > s1*4 > > \startStaff > > \section > > \sectionLabel "Co

Print brace, clef and key signature at start of Coda separated by blank space

Hello everyone, example: \version "2.24.1" upper = { \key as \minor c'1 \stopStaff s1*4 \startStaff \section \sectionLabel "Coda" c'1 \bar ".|" } lower = { \key as \minor c'1 \stopStaff s1*4 \startStaff \section \sectionLabel "Coda" c'1 \bar "|."

Re: Broken Slur + Key Signature Collision

roperty is used to control the spacing between the second part of a > broken slur's left control point and the preceding key signature? I'd like > to increase this spacing a bit as the current collision is quite > bothersome. Here's what I mean: > > [image: image.png] > >

Re: Broken Slur + Key Signature Collision

Le mercredi 05 juillet 2023 à 18:45 -0600, Abraham Lee a écrit : > All, > > What property is used to control the spacing between the second part of a > broken slur's left control point and the preceding key signature? I'd like to > increase this spacing a bit as the current col

Broken Slur + Key Signature Collision

All, What property is used to control the spacing between the second part of a broken slur's left control point and the preceding key signature? I'd like to increase this spacing a bit as the current collision is quite bothersome. Here's what I mean: [image: image.png] Thanks, Abraham

Alternative Key on satb template

was to use \alternativeKey c f \major within the Key variable of the template a second attempt was to declare a normal \key c \major on the Key variable and then put the \alternativeKey c f \major at the beginning of a voice variable such as SopranoMusic. Either way compiles successfully but doesn’t

Re: Middle-C position doesn't move key signature

thats funny ;) - you answered my other question regarding the clef here (for completeness, I've added your solution to the other thread)- but this issue is, though the same source,  a different one - its regarding the key signature. The source is like this: and by |\version "2

Re: Middle-C position doesn't move key signature

Le lundi 10 avril 2023 à 11:55 +0200, Johannes Roeßler a écrit : > Hi, > neither the clef position (which is mentioned in the documentation, so > this is expected) - nor the middelCPosition move the key signature. > How do I have to move it? > >

Middle-C position doesn't move key signature

Hi, neither the clef position (which is mentioned in the documentation, so this is expected) - nor the middelCPosition move the key signature. How do I have to move it? \version "2.24.0" {   \key f\major   bes'2   \key c\major   bes'2   \set Staff.clefPosition =

Re: Key and time change at end of piece

' a' b' c'' c'4 d' e' f' g' a' b' c'' c'4 d' e' f' g' a' b' c'' } \score { \new Staff { \override Staff.StaffSymbol.break-align-symbols = #'(time-signature key-cancellation key-signature staff-bar break-alignment) \key f \major \time 4/4 \music \bar "||" %\tweak X-ex

Re: Key and time change at end of piece

ndividual pieces one at a time, one file per piece. I >> intend to combine them later with a superseding file into a book. My >> problem is this: Sometimes, a piece ends with a key change or time change >> in anticipation of the next piece. In such cases a piece typically ends &

Re: Key and time change at end of piece

em later with a superseding file into a book. My problem > is this: Sometimes, a piece ends with a key change or time change in > anticipation of the next piece. In such cases a piece typically ends with a > double barline, because it is not the real end of the piece, followed by the

Re: Key and time change at end of piece

Sometimes, a piece ends with a key change or time change in anticipation of the next piece. In such cases a piece typically ends with a double barline, because it is not the real end of the piece, followed by the key change and time change symbols and open ended s

Re: Key and time change at end of piece

ork on individual pieces one at a time, one file per piece. I >> intend to combine them later with a superseding file into a book. My >> problem is this: Sometimes, a piece ends with a key change or time change >> in anticipation of the next piece. In such cases a piece typically ends >

Re: Key and time change at end of piece

To keep things > manageable I work on individual pieces one at a time, one file per piece. I > intend to combine them later with a superseding file into a book. My > problem is this: Sometimes, a piece ends with a key change or time change > in anticipation of the next piece. In such c

Re: Key and time change at end of piece

ividual pieces one at a time, one file per piece. I > intend to combine them later with a superseding file into a book. My > problem is this: Sometimes, a piece ends with a key change or time change > in anticipation of the next piece. In such cases a piece typically ends > with a double

Key and time change at end of piece

Hello, I am working on a complete piano vocal score for an opera. To keep things manageable I work on individual pieces one at a time, one file per piece. I intend to combine them later with a superseding file into a book. My problem is this: Sometimes, a piece ends with a key change or time

Re: Key Signature Bug in 2.24.0,Re: Key Signature Bug in 2.24.0

irst note of each measures after the Key Signature. > > But you were right, it is the default spacing. > > > > About the distance between different accidentals, consider the example > > bellow. You can see a difference between the "Reference staff" and number >

Re: Key Signature Bug in 2.24.0,Re: Key Signature Bug in 2.24.0

Le 13/01/2023 à 10:16, Werner LEMBERG a écrit : Regardless of that, it is indeed a severe bug: No need to ever align key signatures vertically, AFAIK. Simply left-align them. I have opened an issue for this: https://gitlab.com/lilypond/lilypond/-/issues/6520 OpenPGP_signature Description

Re: Key Signature Bug in 2.24.0,Re: Key Signature Bug in 2.24.0

On Fri 13 Jan 2023 at 19:30:29 (+), nitra...@posteo.net wrote: > I was talking about the first note of each measures after the Key Signature. > But you were right, it is the default spacing. > > About the distance between different accidentals, consider the example > bell

Re: Key Signature Bug in 2.24.0,Re: Key Signature Bug in 2.24.0

I was talking about the first note of each measures after the Key Signature. But you were right, it is the default spacing. About the distance between different accidentals, consider the example bellow. You can see a difference between the "Reference staff" and number "C" in t

Re: Key Signature Bug in 2.24.0,Re: Key Signature Bug in 2.24.0

the first notes in any measure has an accidental, so I'm not sure what you mean. If, by the last accidental, you mean the last symbol in the key signature, then you certainly shouldn't place the first note in the measure too close to the key signature. > - I don't understand why the distance

Re: Key Signature Bug in 2.24.0,Re: Key Signature Bug in 2.24.0

n't in the previous version. > > > What previous version did you test this with? For me, the output is > > > the same in 2.22 and in 2.18.2. > > Regardless of that, it is indeed a severe bug: No need to ever align > > key signatures vertically, AFAIK. Simply left-align them. &

Re: Key Signature Bug in 2.24.0,Re: Key Signature Bug in 2.24.0

bug: No need to ever align key signatures vertically, AFAIK. Simply left-align them. Do you mean like this, or something else? (NB this is unreliable code, I was surprised that it even works) \version "2.24.0" music = \relative c' {   \override Staff.KeyCancellation.break-align-symb

Re: Key Signature Bug in 2.24.0

You're right, I worked for my last score on 2.22.0 and the bug was there and I didn't notice it... So it isn't specific to 2.22.4 as written in the subject. Le vendredi 13 janvier 2023 à 09:17, Jean Abou Samra a écrit : > Le 13/01/2023 à 09:34, nitra...@posteo.net a écrit : > > Hi all, > > > > I

Re: Key Signature Bug in 2.24.0,Re: Key Signature Bug in 2.24.0

>> I just discovered this huge bug in the recent release of 2.24.0 >> which wasn't in the previous version. > > What previous version did you test this with? For me, the output is > the same in 2.22 and in 2.18.2. Regardless of that, it is indeed a severe bug: No n

Re: Key Signature Bug in 2.24.0

Le 13/01/2023 à 09:34, nitra...@posteo.net a écrit : Hi all, I just discovered this huge bug in the recent release of 2.24.0 which wasn't in the previous version. What previous version did you test this with? For me, the output is the same in 2.22 and in 2.18.2. Best, Jean

Key Signature Bug in 2.24.0

Hi all, I just discovered this huge bug in the recent release of 2.24.0 which wasn't in the previous version. Placement of key signatures on multiple staves with transposed instrument behaves very poorly. Consider this example : \version "2.24.0" music = \relative c' { \key es\major

Re: extension fingerings, key sigs

Hi Matthew, How do I keep the new key signature from also appearing at the end of the previous line? Also, how can I write { 1 x 2 4 } in the fingering font, adding an "x" between the notes to signify the extension between "1" and "2"? One possibility would be

Re: extension fingerings, key sigs

_ From: William Rehwinkel Sent: Tuesday, December 20, 2022 7:28 PM To: Matthew Pierce; lilypond-user@gnu.org Subject: Re: extension fingerings, key sigs Dear Matt, This snippet should answer both of your questions, let me know if you have any other questions about this. Depending on exactl

Re: extension fingerings, key sigs

wrote: I am writing a scale page for my cello students. Since each line is a new scale, each line has a new key signature. Two basic questions: How do I keep the new key signature from also appearing at the end of the previous line? Also, how can I write { 1 x 2 4 } in the fingering font, ad

extension fingerings, key sigs

I am writing a scale page for my cello students. Since each line is a new scale, each line has a new key signature. Two basic questions: How do I keep the new key signature from also appearing at the end of the previous line? Also, how can I write { 1 x 2 4 } in the fingering font, adding

Re: Extra treble key on PianoStaff with two bass keys and \acciaccatura

Thank you Jean for your help! Below follows the solution Example \version "2.23.14" \score { \new PianoStaff = bayan { << \new Staff = rightHand { \tempo Lento \clef bass \key c \minor \time 2/4 \relative { \acciacc

  1   2   3   4   5   6   7   8   9   10   >