Re: Moving key signatures

Knute, >> >> Thanks! Interesting epilogue: Lilypond automatically placed this >> particular key change at the end of a line, and then all the key signatures >> at the beginning of the next system are kicked off the staves to the left: >> >> ... > >> I can force

Re: Moving key signatures

On Fri, Jul 4, 2025 at 3:52 PM Brent Annable wrote: > Hey Knute, > > Thanks! Interesting epilogue: Lilypond automatically placed this > particular key change at the end of a line, and then all the key signatures > at the beginning of the next system are kicked off the sta

Re: Moving key signatures

Hey Knute, Thanks! Interesting epilogue: Lilypond automatically placed this particular key change at the end of a line, and then all the key signatures at the beginning of the next system are kicked off the staves to the left: \version "2.24.4" \score { \new StaffGroup <<

Re: Moving key signatures

On Fri, Jul 4, 2025 at 2:55 PM Brent Annable wrote: > Hi all, > > Rather than having a key-signature change appear at the start of the bar > where it takes effect, I'm trying to move it to the end of the previous bar > (see example). The problem is that Lilypond still reserves space for the > key

Moving key signatures

Hi all, Rather than having a key-signature change appear at the start of the bar where it takes effect, I'm trying to move it to the end of the previous bar (see example). The problem is that Lilypond still reserves space for the key signature in all other staves at the start of the bar where it u

Re: Key cancellation moving key signatures rightwards

> I have a situation with a lot of transposing instruments and some > key changes. I have disabled key cancellations, but of course they > are necessary if the new key has no sharps or flats. When naturals > are required, they push key signatures to the right, even though the >

Key cancellation moving key signatures rightwards

Hi, I have a situation with a lot of transposing instruments and some key changes. I have disabled key cancellations, but of course they are necessary if the new key has no sharps or flats. When naturals are required, they push key signatures to the right, even though the two will never appear

Re: Key signatures in MIDI output

flats will be right there for me to see. I have actually found myself wishing for this on occasion, so all is well. 👍 From: David Kastrup Sent: 14 May 2024 19:33 To: Giles Boardman Cc: msk...@ansuz.sooke.bc.ca ; lilypond-user@gnu.org Subject: Re: Key signatures

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, so I've left my workings out i

Re: Key signatures in MIDI output

0 |Key Sig | D Major |   |On Note   | chan= 1 | pitch=A 4   | vol=90 4: 0 |(Off) Note | chan= 1 | pitch=a 4 followed by lots more Notes On/Off until |End of track| I just noticed this, because I ran David Wright's midi file through MIDIDS

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 other behaviour I can'

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 so it could also > be versi

Re: Key signatures in MIDI output

rt2v1.ly" \score { \time 4/4 \key d\major { \mark "1K002-1a-" { \partial 8 g''8 fis''16 d''8. b'8. d''16 a'4 fis'4 fis'16 a'8. d''8. fis''16 g''16 e''8. e''8. g'

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, when r

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 y

Re: Key signatures in MIDI output

40 To: Giles Boardman Cc: Hans Åberg ; lilypond-user@gnu.org Subject: Re: Key signatures in MIDI output 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 li

Re: Key signatures in MIDI output

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 you must be using some piece of software ot

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 f

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

nippets to the forum. Thanks for your interest. From: msk...@ansuz.sooke.bc.ca Sent: 10 May 2024 21:21 To: Hans Åberg Cc: Giles Boardman ; lilypond-user@gnu.org Subject: Re: Key signatures in MIDI output On Fri, 10 May 2024, Hans Åberg wrote: > > sign

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 abo

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 app

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 asked for that. > > Okay. I didn

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 correct output in the

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

Re: Key signatures in MIDI output

t; 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. &g

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 th

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: 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 ae

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 it

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, bu

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/lilypond/lilyp

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, th

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 >>

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 >

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: Omitting specific symbols from key signatures

Just for the files: Forget all about music functions and a-posteriori manipulations of scales, there is an disturbingly simple solution: (link to my corresponding dev-list posting:) How to set up a key signature definition

Re: Omitting specific symbols from key signatures

accidental glyphs, all > the > non-standard accidental combinations in key signatures music currently > suffer from several spacing problems, because currently, for obvious > reasons, the focus had been solely on standard western accidentals. Excellent let's bring it over there! I&

Re: Omitting specific symbols from key signatures

te a co-operation regarding makam issues. After all, you and Hans can provide valuable practical examples, and one important point after finally having added my new accidental glyphs, all the non-standard accidental combinations in key signatures music currently suffer from several spacing probl

Re: Omitting specific symbols from key signatures

Torsten that's GREAT! Very very nice and works so well. But it's working a little too well for my purposes :) Are you on the dev list? If you'd be willing to help me out some more I can send you a couple of files that are under development and we can address specifically the two makams that have t

Re: Omitting specific symbols from key signatures

Adam Good-3 wrote > Thank you Torsten, unfortunately this doesn't satisfy the criteria of #3 > request, working across transpositions. If I ask for: > \key c \KeySig > > ...it prints a ces in the key signature. […] Hi Adam, Yes, unfortunately, my trickery only works for keys with a "sharp" tonic

Re: Omitting specific symbols from key signatures

Thank you Torsten, unfortunately this doesn't satisfy the criteria of #3 request, working across transpositions. If I ask for: \key c \KeySig ...it prints a ces in the key signature. Although irrelevant, the example I'm giving is much much simpler than my actual needs which in

Re: Omitting specific symbols from key signatures

Hi Adam, the KeySig you've defined is nothing but \locrian. If you don't want the F# to be shown (that's the tonic in F# locrian), you just need to define a ,FLAT for step 0 (the tonic), because this will lower the tonic and thus eliminate the F# from your key signature. That way, the F# will not

Omitting specific symbols from key signatures

Hi everyone, I would greatly appreciate any help assistance. In the snippet below, I define a key signature that gives accidentals for a locrian mode and then show this mode as if the tonic = fis (F#). I would like three things... 1. to suppress printing of the "fis" in the key signature (yet sti

Re: \cadenzaOn: clefs, key signatures on line breaks

Robert Kubosz wrote > Still I have question refering the breaks: is there any other method for > line breaking (preferably auto-breaking)? I don't understand your question. In your exemple, the breakings are working because you have added the barlines in your \repeat command. Then LP automatically

Re: \cadenzaOn: clefs, key signatures on line breaks

Hi Thomas! I added the post via web page with use of markup. It looks like the mail engine ignored it. Nevermind, I repost the example: \version "2.19.81" \relative f' { \clef treble \key f \major \repeat unfold 10 f4 \break \repeat unfold 10 g4 \

Re: \cadenzaOn: clefs, key signatures on line breaks

2018-05-13 18:30 GMT+02:00 Robert Kubosz : > The example below Hello, there is no code visible for me in your mail. Neither here: https://lists.gnu.org/archive/html/lilypond-user/2018-05/msg00317.html Please provide plain text mails or attach a file or a link to it. Thanks, Harm

Re: \cadenzaOn: clefs, key signatures on line breaks

Robert Kubosz wrote > Hello! > I write a music piece with \cadenzaOn and \cadenzaOff. The example below > produces output without the clef and key signature after line break. Is > there a possibility to display them? > Also, I have second question: can the lines auto break in cadenza mode? > > Wi

\cadenzaOn: clefs, key signatures on line breaks

Hello! I write a music piece with \cadenzaOn and \cadenzaOff. The example below produces output without the clef and key signature after line break. Is there a possibility to display them? Also, I have second question: can the lines auto break in cadenza mode? With best regards Robert -- Sen

Re: Key signatures in modes other than Ionian & Aeolian

ecognize D as > the tonic and play C sharp all the time (since this is what they're used to > in a major-like tune with tonic D), or they look at the key signature, > think "G major" and try to relate everything in the tune to some elusive > "tonic" G. > > N

Re: Key signatures in modes other than Ionian & Aeolian

the pretty large and vivid community of Irish/Celtic traditional music, where key signatures usually written corresponding to the actual mode (so e.g. a tune in D mixolydian would be written with only one sharp). This makes sense as the music is (for the most part) strictly modal and diatonic.

Re: Key signatures in modes other than Ionian & Aeolian

Am 2018-04-17 um 07:47 schrieb Lukas-Fabian Moser : > Am 17.04.2018 um 01:24 schrieb Torsten Hämmerle: > >> Even if my opinion may differ from the general opinion here, I think that in >> popular music, one would use standard D major key signature. >> Reason: Two sharps clearly show D major tonic

Re: Key signatures in modes other than Ionian & Aeolian

ink "G major" and try to relate everything in the tune to some elusive "tonic" G. Nowadays, I think the key signatures are read not as combinations of alterations but of fixed code sets designating one of the standard keys, expressed as a combination of tonic plus "majo

Re: Key signatures in modes other than Ionian & Aeolian

Peter Crighton wrote > I am transcribing a song in D Mixolydian > [...] > in this case it is a pop song Hi Peter, Even if my opinion may differ from the general opinion here, I think that in popular music, one would use standard D major key signature. Reason: Two sharps clearly show D major tonic

Re: Key signatures in modes other than Ionian & Aeolian

: Key signatures in modes other than Ionian & Aeolian Hello all, my question is not exclusive to LilyPond, but I hope you can enlighten me anyway. I am transcribing a song in D Mixolydian and am wondering which key signature to notate it in – d \mixolydian (because that is the mode it is in

Re: Key signatures in modes other than Ionian & Aeolian

Also, could the style of music matter? In Early Music I’d be even more > inclined to notate in d \mixolydian, but in this case it is a pop song where > people might only expect to see major or minor keys. Strictly, the key signature is there to simplify notation, so any way you prefer is

Re: Key signatures in modes other than Ionian & Aeolian

Peter Crighton writes: > Hello all, > > my question is not exclusive to LilyPond, but I hope you can enlighten me > anyway. > > I am transcribing a song in D Mixolydian and am wondering which key > signature to notate it in – d \mixolydian (because that is the mode it is > in) or d \major (becaus

Re: Key signatures in modes other than Ionian & Aeolian

2018-04-16 21:18 GMT+02:00 Peter Crighton : > Hello all, > > my question is not exclusive to LilyPond, but I hope you can enlighten me > anyway. > > I am transcribing a song in D Mixolydian and am wondering which key > signature to notate it in – d \mixolydian (because that is the mode it is > in)

Key signatures in modes other than Ionian & Aeolian

Hello all, my question is not exclusive to LilyPond, but I hope you can enlighten me anyway. I am transcribing a song in D Mixolydian and am wondering which key signature to notate it in – d \mixolydian (because that is the mode it is in) or d \major (because a D major chord clearly is the tonic

Re: Key signatures repeated on every staff

On 16/04/17 02:36, David Wright wrote: > Quite understandable though. No page turns, so every inch of real > estate is precious. You lose the clef too. Which explains my occasional :-) moans on this list about trying to get rid of wasted space and pack everything in on one page with lilypond. Tha

Re: Key signatures repeated on every staff

On Sat 15 Apr 2017 at 23:12:36 (+0100), Wols Lists wrote: > On 15/04/17 21:55, Kieren MacMillan wrote: > > Hi Wol, > > > >> > most of the music I see from the turn of last century does NOT. > > > Does not repeat the key signature? Fascinating! What field/genre are you > > working in? > > Mostly

Re: Key signatures repeated on every staff

On 15/04/17 21:55, Kieren MacMillan wrote: > Hi Wol, > >> > most of the music I see from the turn of last century does NOT. > Does not repeat the key signature? Fascinating! What field/genre are you > working in? Mostly published by either Boosey, or Hawkes. They merged about 1920 ... :-) I th

Re: Key signatures repeated on every staff

Hi Wol, > most of the music I see from the turn of last century does NOT. Does not repeat the key signature? Fascinating! What field/genre are you working in? I studied, and now work in the classical (both “old” and “new”), jazz (instrumental and vocal/choral), and musical theatre worlds, and

Re: Key signatures repeated on every staff

makes it quite difficult to read, so one of the reasons for me re-doing the music is to put those key signatures in. (Along with changing the clef, or transposition, or taking an almost illegible copy and fixing it :-) Cheers, Wol ___ lilypond-user

Re: Key signatures repeated on every staff

I do? > May I ask how much sheet music you have seen so far? All (!) classical > sheet music repeats key signature at every line. And many editions [...] Yes, all the sheet music I saw had the key signatures repeated. But I was unsure; that was a question that wonders me. > Generally yo

Re: Key signatures repeated on every staff

Am 15.04.2017 um 16:41 schrieb Son_V: > I dare to try a minimal example! :-) > But I hope it's self-explaining. \version "2.18.2" { \key d \major R1*20 } That’s not too hard ;) But yes, it’s self-explaining this time. > On my scores, the key signature appears on every beginni

Key signatures repeated on every staff

//lilypond.1069038.n5.nabble.com/Key-signatures-repeated-on-every-staff-tp202308.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: NR 2.10.2 - arabic key signatures

Am 05.07.2016 11:43, schrieb Federico Bruni: Il giorno lun 4 lug 2016 alle 12:10, Carl Sorensen ha scritto: On 7/1/16 5:08 AM, "Federico Bruni" wrote: Hi all In the following paragraph, taken from http://lilypond.org/doc/v2.19/Documentation/notation/arabic-music#arabic-k ey-signatures

Re: NR 2.10.2 - arabic key signatures

Il giorno lun 4 lug 2016 alle 12:10, Carl Sorensen ha scritto: On 7/1/16 5:08 AM, "Federico Bruni" wrote: Hi all In the following paragraph, taken from http://lilypond.org/doc/v2.19/Documentation/notation/arabic-music#arabic-k ey-signatures Other maqams in the same bayati group, as show

Re: NR 2.10.2 - arabic key signatures

On 7/1/16 5:08 AM, "Federico Bruni" wrote: >Hi all > >In the following paragraph, taken from >http://lilypond.org/doc/v2.19/Documentation/notation/arabic-music#arabic-k >ey-signatures > >> Other maqams in the same bayati group, as shown in the table below: >> (bayati, hussaini, saba, and ushaq)

NR 2.10.2 - arabic key signatures

Hi all In the following paragraph, taken from http://lilypond.org/doc/v2.19/Documentation/notation/arabic-music#arabic-key-signatures Other maqams in the same bayati group, as shown in the table below: (bayati, hussaini, saba, and ushaq) can be indicated in the same way. These are all

Manual Chapter 2.10.2 Arabic music subchapter Selected Snippets Non-traditional key signatures

\include "arabic.ly" \relative do' { \set Staff.keyAlterations = #`( (0 . ,SEMI-FLAT) (1 . ,SEMI-FLAT) (2 . ,FLAT) (5 . ,FLAT) (6 . ,SEMI-FLAT) ) %\set Staff.extraNatural = ##f re reb \dwn reb resd dod dob dosd \dwn dob | dobsb dodsd do do | } The key accidentals i

Re: "bitonal" key signatures

4:40 GMT+01:00 Phil Holmes : >>> >>>> Better would be to add \tweak X-extent #'(0 . 0) just before the C >>>> major key sig in the right hand? >>>> >>>> >>>> -- >>>> Phil Holmes >>>> >>>> >>

Re: "bitonal" key signatures

mes >>> >>> >>> - Original Message ----- From: Pierre Perol-Schneider >>> To: N. Andrew Walsh >>> Cc: lilypond-user >>> Sent: Wednesday, February 10, 2016 1:19 PM >>> Subject: Re: "bitonal" key signatures >>> >>>

Re: "bitonal" key signatures

ke-moment 1/8) >> \set beatStructure = #'(2 2 2 2) >> } >> >> >> rhMusic = \relative c'' { >>\key es \major >> \time 4/8 >> r16 bes d bes d bes d bes | >> \key c \major >> \beambreakOn \tuplet 3/2 { es,\( f g } \tuplet 3/2 { a b cis

Re: "bitonal" key signatures

To: N. Andrew Walsh > Cc: lilypond-user > Sent: Wednesday, February 10, 2016 1:19 PM > Subject: Re: "bitonal" key signatures > > > > ... but is probably not the "better" way! > > > > 2016-02-10 14:18 GMT+01:00 Pierre Perol-Schneider < > p

Re: "bitonal" key signatures

<< { r16 d f d f d f d | } \\ { bes2 | } >> \key es \major << { es,16 bes' es bes g' d g d | } \\ { es,2 | } >> } \score { \new PianoStaff << \new Staff = "RH" << \rhMusic >> \new Staff =

Re: "bitonal" key signatures

lhMusic = \relative c { >> \clef bass >> \key es \major >> \time 4/8 >> << >> { r16 d f d f d f d | } >> \\ >> { bes2 | } >> >> >> \key es \major >> << >> { es,16 bes'

Re: "bitonal" key signatures

arge of key signatures is > displacing that second "\key es \major" expression in the left hand, > presumably because there was already one in place from the beginning (or > perhaps because it's assuming a possible collision with the "\key c \major" > expression i

"bitonal" key signatures

cause it's assuming a possible collision with the "\key c \major" expression in the right hand). In either case, what I would prefer is that both new key signatures are not displaced horizontally, so that the second "\key es \major" is, in effect, merely a cautionary

Re: Two questions about key signatures

On 10/7/2015 5:50 AM, Jacques Menu wrote: Is that the kind of things you’re aiming at? http://lilypondblog.org/2013/09/automatic-generation-of-scales-in-various-modes-for-all-21-pitches/ Exactly. Except I'm doing it manually, instead of programmatically, since I think that will hel

Re: Two questions about key signatures

Hello TM, Is that the kind of things you’re aiming at? http://lilypondblog.org/2013/09/automatic-generation-of-scales-in-various-modes-for-all-21-pitches/ JM > Le 7 oct. 2015 à 05:24, T. Michael Sommers a écrit : > > On 10/5/2015 2:59 PM, Simon Albrecht wrote: >> On 05.10.2015 11:33,

Re: Two questions about key signatures

On 10/5/2015 2:59 PM, Simon Albrecht wrote: On 05.10.2015 11:33, T. Michael Sommers wrote: Hmmm. When I change from a key with sharps or flats in it to one with no sharps or flats, the cancelling accidentals still appear. I can understand that, since otherwise there would be no indication that

Re: Two questions about key signatures

On 10/5/2015 12:58 PM, Noeck wrote: Hi Michael, Am 05.10.2015 um 11:33 schrieb T. Michael Sommers: Hmmm. When I change from a key with sharps or flats in it to one with no sharps or flats, the cancelling accidentals still appear. I can understand that, since otherwise there would be no indica

Re: Two questions about key signatures

> > { \key as \minor ces \key c \major c } > > How on earth would the performer know that the second one is a c natural if > there is no key cancellation? S/He wouldn't. Unless (and I quote) > My application is not an actual score to be played by others, but just a > cheat sheet for me, Be

Re: Two questions about key signatures

On 05.10.2015 11:33, T. Michael Sommers wrote: Hmmm. When I change from a key with sharps or flats in it to one with no sharps or flats, the cancelling accidentals still appear. I can understand that, since otherwise there would be no indication that the key had changed, but for my application

Re: Two questions about key signatures

Hi Michael, Am 05.10.2015 um 11:33 schrieb T. Michael Sommers: > Hmmm. When I change from a key with sharps or flats in it to one with > no sharps or flats, the cancelling accidentals still appear. I can > understand that, since otherwise there would be no indication that the > key had changed,

Re: Two questions about key signatures

On 10/5/2015 5:33 AM, Robert Schmaus wrote: I tried this: \override Staff.KeySignature.break-visibility = ##(#f #t #t) along with some variations, but it didn't seem to have any effect. Also, I had used that formula in another situation (with the TimeSignature, I think), and, although it remov

Re: Two questions about key signatures

On 10/5/2015 5:13 AM, T. Michael Sommers wrote: On 10/5/2015 3:42 AM, Robert Schmaus wrote: Actually, so save you some time finding the relevant passages, your ... Q2 in section "Visibility of cancelling accidentals". Thanks. I hadn't seen that while searching the manual. Hmmm. When I chan

Re: Two questions about key signatures

> > I tried this: > > \override Staff.KeySignature.break-visibility = ##(#f #t #t) > > along with some variations, but it didn't seem to have any effect. Also, I > had used that formula in another situation (with the TimeSignature, I think), > and, although it removed the signature, it left

Re: Two questions about key signatures

On 10/5/2015 3:42 AM, Robert Schmaus wrote: Actually, so save you some time finding the relevant passages, your ... Q2 in section "Visibility of cancelling accidentals". Thanks. I hadn't seen that while searching the manual. -- T.M. Sommers -- tmsomme...@gmail.com -- ab2sb __

Re: Two questions about key signatures

On 10/5/2015 3:33 AM, Robert Schmaus wrote: On 5 Oct 2015, at 09:16, T. Michael Sommers mailto:tmsomme...@gmail.com>> wrote: I have a couple of questions about key signatures: 1) When a key change occurs at the end of a printed line, the new key signature is printed at the end of th

Re: Two questions about key signatures

mach it. -- Flannery O'Connor > On 5 Oct 2015, at 09:16, T. Michael Sommers wrote: > > I have a couple of questions about key signatures: > > 1) When a key change occurs at the end of a printed line, the new key > signature is printed at the end of the line. Is there an

Re: Two questions about key signatures

or > On 5 Oct 2015, at 09:16, T. Michael Sommers wrote: > > I have a couple of questions about key signatures: > > 1) When a key change occurs at the end of a printed line, the new key > signature is printed at the end of the line. Is there any way to suppress > that? &g

Two questions about key signatures

I have a couple of questions about key signatures: 1) When a key change occurs at the end of a printed line, the new key signature is printed at the end of the line. Is there any way to suppress that? 2) When the key changes, the new key signature includes a bunch of naturals to negate the

  1   2   3   >