Re: Two questions about key signatures

[T. Michael Sommers]

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 help me learn them all.  Thanks for the link.


--
T.M. Sommers -- tmsomme...@gmail.com -- ab2sb

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[Jacques Menu]

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, 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, it's a little annoying.
>> 
>> { \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?
> 
> That's what I said.  My application, though, is not something to be 
> performed, so that's not a problem.  I'm just creating a chart of all the 
> keys in all the modes.
> 
> -- 
> T.M. Sommers -- tmsomme...@gmail.com -- ab2sb
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[T. Michael Sommers]

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 indication that the
key had changed, but for my application, it's a little annoying.  Not
annoying enough to do anything about, though.


Well, the result is misleading in the last bar, but I guess that is what
you are looking for:

\version "2.19.21"

{
   \textLengthOn  % only for this snippet
   \set Staff.printKeyCancellation = ##f  % removes key cancellation
   a'1
   \key d \major
   a'1
   \key f \major
   a'1 ^"no naturals"
   \key c \major
   a'1 ^"natural"
   \key f \major
   a'1
   \once \omit Staff.KeyCancellation % removes it even for C major
   \key c \major
   b'1 ^"no natural"
}


Thanks.  I think, though, that eventually I will end up putting the keys 
with no sharps or flats first, thus avoiding the problem (it's also the 
natural order to put the keys in).



--
T.M. Sommers -- tmsomme...@gmail.com -- ab2sb

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[T. Michael Sommers]

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 the
key had changed, but for my application, it's a little annoying.


{ \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?


That's what I said.  My application, though, is not something to be 
performed, so that's not a problem.  I'm just creating a chart of all 
the keys in all the modes.


--
T.M. Sommers -- tmsomme...@gmail.com -- ab2sb

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[Simon Albrecht]

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, it's a little annoying.


{ \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?


Yours, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[Robert Schmaus]

> 
> { \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, 

Best, Robert 
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[Robert Schmaus]

Hi T.M.,

Check the Notation Reference, section 5.4.6 - you'll find the answers to your 
questions there. 

http://lilypond.org/doc/v2.18/Documentation/notation/visibility-of-objects

Best, Robert 

__

Truth does not change according to our ability to stomach 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 any way to suppress 
> that?
> 
> 2) When the key changes, the new key signature includes a bunch of naturals 
> to negate the effects of the previous key.  Is there any way to suppress 
> that?  My application is not an actual score to be played by others, but just 
> a cheat sheet for me, and all those naturals get in the way, so complying 
> with any standards is not an issue, if those naturals are standard notation.
> 
> Thanks for any help.
> 
> -- 
> T.M. Sommers -- tmsomme...@gmail.com -- ab2sb
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[Robert Schmaus]

Actually, so save you some time finding the relevant passages, your question 1 
is answered in the section called "Using break-visibility", and Q2 in section 
"Visibility of cancelling accidentals". 

Best, Robert 

__

Truth does not change according to our ability to stomach 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 any way to suppress 
> that?
> 
> 2) When the key changes, the new key signature includes a bunch of naturals 
> to negate the effects of the previous key.  Is there any way to suppress 
> that?  My application is not an actual score to be played by others, but just 
> a cheat sheet for me, and all those naturals get in the way, so complying 
> with any standards is not an issue, if those naturals are standard notation.
> 
> Thanks for any help.
> 
> -- 
> T.M. Sommers -- tmsomme...@gmail.com -- ab2sb
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[T. Michael Sommers]

On 10/5/2015 3:33 AM, Robert Schmaus wrote:

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?

2) When the key changes, the new key signature includes a bunch of
naturals to negate the effects of the previous key.  Is there any way
to suppress that?  My application is not an actual score to be played
by others, but just a cheat sheet for me, and all those naturals get
in the way, so complying with any standards is not an issue, if those
naturals are standard notation.


Check the Notation Reference, section 5.4.6 - you'll find the answers to
your questions there.

http://lilypond.org/doc/v2.18/Documentation/notation/visibility-of-objects


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 
the empty staff lines it had occupied dangling off the end of the staff, 
with was a bit unsatisfactory.


--
T.M. Sommers -- tmsomme...@gmail.com -- ab2sb

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[T. Michael Sommers]

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

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[T. Michael Sommers]

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 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, it's a little annoying.  Not 
annoying enough to do anything about, though.


--
T.M. Sommers -- tmsomme...@gmail.com -- ab2sb

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[Robert Schmaus]

> 
> 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 the empty staff lines it had 
> occupied dangling off the end of the staff, with was a bit unsatisfactory.

I just checked - there seem to be special considerations for the Time Signature 
case. 
You'll need to set the
"explicitKeySignatureVisibility" and possibly the "printKeyCancellation" 
properties - those are also described on that page. 

Best, Robert 



> -- 
> T.M. Sommers -- tmsomme...@gmail.com -- ab2sb
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[T. Michael Sommers]

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 removed the signature, it
left the empty staff lines it had occupied dangling off the end of
the staff, with was a bit unsatisfactory.


I just checked - there seem to be special considerations for the Time
Signature case. You'll need to set the
"explicitKeySignatureVisibility" and possibly the
"printKeyCancellation" properties - those are also described on that
page.


Thanks.  I should have read on.  Doing this:

\set Staff.explicitKeySignatureVisibility = #end-of-line-invisible

seems to have done the trick.  printKeyCancellation was already set to 
#f following the suggestion in your other post.


--
T.M. Sommers -- tmsomme...@gmail.com -- ab2sb

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Two questions about key signatures

[Noeck]

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, but for my application, it's a little annoying.  Not
> annoying enough to do anything about, though.

Well, the result is misleading in the last bar, but I guess that is what
you are looking for:

\version "2.19.21"

{
  \textLengthOn  % only for this snippet
  \set Staff.printKeyCancellation = ##f  % removes key cancellation
  a'1
  \key d \major
  a'1
  \key f \major
  a'1 ^"no naturals"
  \key c \major
  a'1 ^"natural"
  \key f \major
  a'1
  \once \omit Staff.KeyCancellation % removes it even for C major
  \key c \major
  b'1 ^"no natural"
}

Cheers,
Joram

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user