Re: brittenPhrygolydian

2017-01-19 Thread Simon Albrecht
On 18.01.2017 23:51, Thomas Morley wrote: Non-default scales are always user defined. How could we predict them? P.e. some FLAT/SHARP-combinations will collide others not... Which is why any automatic approach will have to involve horizontal skylines, as David N. already said. Best, Simon

Re: brittenPhrygolydian

2017-01-18 Thread Noeck
Hi Harm, Am 18.01.2017 um 23:51 schrieb Thomas Morley: > The default of zero is perfectly fine for all predefined scales, imho. You are right. I ran your example and withdraw my simple approach. Joram ___ lilypond-user mailing list

Re: brittenPhrygolydian

2017-01-18 Thread Thomas Morley
2017-01-18 23:00 GMT+01:00 Noeck : > Wouldn't it be an improvement if there was a default padding larger than > 0? Of course, the best option would be some type of kerning which works > between all possible combinations. But something like 0.2 staff spaces > between all

Re: brittenPhrygolydian

2017-01-18 Thread Hans Åberg
> On 17 Jan 2017, at 22:42, Simon Albrecht wrote: > The question came up about a curious key signature used by Britten, which > indicates only Ab and C#, ... Mode names are listed at [1]. Compute the differences in E12: G Ab B C# D E F G 1 3 2 1 2 1 2 and make

Re: brittenPhrygolydian

2017-01-18 Thread Noeck
Wouldn't it be an improvement if there was a default padding larger than 0? Of course, the best option would be some type of kerning which works between all possible combinations. But something like 0.2 staff spaces between all accidentals would probably look better than no space at all. I don't

Re: brittenPhrygolydian

2017-01-18 Thread David Nalesnik
On Wed, Jan 18, 2017 at 10:17 AM, David Nalesnik wrote: > On Wed, Jan 18, 2017 at 10:00 AM, Kieren MacMillan > wrote: > >> >> I understand that there are a huge number of possible key signatures, but >> can’t the collision in the first

Re: brittenPhrygolydian

2017-01-18 Thread David Nalesnik
On Wed, Jan 18, 2017 at 10:00 AM, Kieren MacMillan wrote: > > I understand that there are a huge number of possible key signatures, but > can’t the collision in the first example (does it bother anyone else?) be > "pre-fixed" somehow? > There could be a more

Re: brittenPhrygolydian

2017-01-18 Thread Kieren MacMillan
Hi David, > There is no default setting. Padding controls the overall spacing > (with extra space allotted to naturals); you use padding-pairs to > affect certain collocations. Yes. I just think that there should be a better default than the one that was made apparent by Simon’s post

Re: brittenPhrygolydian

2017-01-18 Thread tisimst
Hey, Kieren! On Wed, Jan 18, 2017 at 7:33 AM, Kieren MacMillan-2 [via Lilypond] < ml-node+s1069038n199307...@n5.nabble.com> wrote: > Hi Simon (et al.), > > >> And LilyPond just has a fabulous, simple, and proper solution: > > > > Which is, by the way, also very well documented. > > But,

Re: brittenPhrygolydian

2017-01-18 Thread Kieren MacMillan
Hi Simon (et al.), >> And LilyPond just has a fabulous, simple, and proper solution: > > Which is, by the way, also very well documented. But, apparently not well defaulted. ;) Where does one find the KeySignature.padding-pairs defaults? I did a file search inside the Contents folder of my

Re: brittenPhrygolydian

2017-01-17 Thread Simon Albrecht
On 17.01.2017 22:42, Simon Albrecht wrote: Hello everybody, this is a big thank you and a shout of joy over having LilyPond! The question came up about a curious key signature used by Britten, which indicates only Ab and C#, and how to replicate this in Sibelius. Which involves a fake clef,