headers
Graham Percival | 1 Aug 2005 06:17
Picon
Favicon

Re: betweensystempadding breaks opus in header in 2.6


On 30-Jul-05, at 8:55 AM, Stephen wrote:

> In this example, betweensystempadding = -1\mm affects the spacing 
> between composer and opus in the header, causing them to overlap whien 
> using Lilypond 2.6.
>
> I do not think the spacing between systems should affect the spacing 
> between lines in the header. Has this bug already been caught?

I don't think this bug has been seen before.  Could you construct a
very small example of this and send it to bug-lilypond ?

Thanks,
- Graham
Permalink | Reply | 501 comments |
headers
Graham Percival | 1 Aug 2005 06:15
Picon
Favicon

Re: Settings for bagpipe music


On 29-Jul-05, at 12:15 AM, Sven Axelsson wrote:

> grace notes used. I suggest this should be included in the official
> distribution to save everyone from the hassle of doing it themselves.

To clarify: we're proposing that we include a
ly/bagpipe.ly
similar to ly/english.ly and whatnot.  I've tested several versions of
bagpipe.ly, and it works, other than...

> Bagpipe music is a bit special since it is written without a key 
> signature
> even though it actually has a signature (D major). The way I deal with 
> this by
> removing the Key_engraver and Accidential_engraver might not be 
> optimal since
> there are instances (though very rare) where you do like to show 
> accidentials
> on certain notes. I provide a \flatten markup for those cases, but 
> maybe there
> is a better way?

... this \flatten thing.  I'm not certain that removing Key_engraver and
Accidental_engraver, and having a special \flatten markup is the best
way to do things.

Other than that, I propose that we accept ly/bagpipe.ly -- particularly 
since
it doesn't change anything for non-bagpipe music.  I've already added
(Continue reading)

Permalink | Reply | 3 comments |
headers
Mats Bengtsson | 1 Aug 2005 09:45
Picon
Picon
Favicon

Re: Full bar rest representation

May I propose that "multi measure rests" is replaced by
"full bar rests" or "full measure rests" in the manual
to avoid this common misconception.

    /Mats

Hans de Rijck wrote:
> Hello Paul,
> 
> Thanks for your answer. This is what I was looking for. I understood from
> the manual that capitalization was only used for multi-measure rests, but
> apparently I was wrong.
> 
> thanks,
> 
> Hans de Rijck.
> 
> ----- Original Message -----
> From: "Paul Scott" <pslist <at> ultrasw.com>
> To: "Hans de Rijck" <hans <at> octet.nl>
> Cc: <lilypond-user <at> gnu.org>
> Sent: Saturday, July 30, 2005 9:05 PM
> Subject: Re: Full bar rest representation
> 
> 
> 
>>Hans de Rijck wrote:
>>
>>
>>>Hi,
(Continue reading)

Permalink | Reply | 2 comments |
headers
Mats Bengtsson | 1 Aug 2005 10:37
Picon
Picon
Favicon

Re: documentation for \displayLilyMusic?


Graham Percival wrote:
> 
> On 27-Jul-05, at 4:30 PM, Cameron Horsburgh wrote:
> 
>> I'm not subscribed to lilypond-developer, so you might like to forward 
>> this as appropriate.
> 
> 
> You can send stuff to lilypond-devel as a non-member; we CC emails to
> individuals, so you can also take part in the discussion.
> 
>> I would find the \displayLilyMusic useful as an external utility. Most 
>> of my serious typesetting involves transposing instruments, and I 
>> frequently need to have subtle differences between different 
>> instruments playing similar parts. For example, a trumpet and a horn 
>> may have essentially the same harmony line, but one instrument may 
>> have to change octave part way through, depending on how I have scored 
>> the piece. Or there may be some instrument specific instructions that 
>> need to be added on one part. This is very difficult to do without 
>> manually typing each part separately.
> 
> 
> You can get around this problem by using \transpose, \transposition, and 
> copying.
> (not that \displayLilyMusic isn't useful; see below)

Also, read "8.2.8 Different editions from one source" in the manual.

    /Mats
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mats Bengtsson | 1 Aug 2005 14:56
Picon
Picon
Favicon

Regarding the Musica ficta accidentals

I noticed the new support for suggested accidentals and am a bit
surprised that this wasn't added as a new possible style for the
cautionary-style property instead. I seem to recall that such a
solution was discussed when the cautionary-style property was
added several years ago. This would also be more in line with
what Nancho Alvarez requested in
http://lists.gnu.org/archive/html/lilypond-user/2004-11/msg00292.html

    /Mats

--

-- 
=============================================
	Mats Bengtsson
	Signal Processing
	Signals, Sensors and Systems
	Royal Institute of Technology
	SE-100 44  STOCKHOLM
	Sweden
	Phone: (+46) 8 790 8463				
         Fax:   (+46) 8 790 7260
	Email: mats.bengtsson <at> s3.kth.se
	WWW: http://www.s3.kth.se/~mabe
=============================================
Permalink | Reply | 3 comments |
headers
Han-Wen Nienhuys | 1 Aug 2005 15:32
Picon
Picon
Favicon

Re: Regarding the Musica ficta accidentals

Mats Bengtsson wrote:
> I noticed the new support for suggested accidentals and am a bit
> surprised that this wasn't added as a new possible style for the
> cautionary-style property instead. I seem to recall that such a

This is technically impossible, since the suggested accidentals have 
different roles in the placement strategies. This implies that they have 
to be of a different Grob type.

--

-- 
  Han-Wen Nienhuys - hanwen <at> xs4all.nl - http://www.xs4all.nl/~hanwen
Permalink | Reply | 2 comments |
headers
Stephen | 1 Aug 2005 16:20

Re: Settings for bagpipe music


----- Original Message ----- 
From: "Graham Percival" <gperlist <at> shaw.ca>
To: "lily-devel" <lilypond-devel <at> gnu.org>
Sent: Sunday, July 31, 2005 11:15 PM
Subject: Re: Settings for bagpipe music

>
> On 29-Jul-05, at 12:15 AM, Sven Axelsson wrote:
>
>> grace notes used. I suggest this should be included in the official
>> distribution to save everyone from the hassle of doing it themselves.
>
> To clarify: we're proposing that we include a
> ly/bagpipe.ly
> similar to ly/english.ly and whatnot.  I've tested several versions of
> bagpipe.ly, and it works, other than...
>
>> Bagpipe music is a bit special since it is written without a key 
>> signature
>> even though it actually has a signature (D major). The way I deal with 
>> this by
>> removing the Key_engraver and Accidential_engraver might not be optimal 
>> since
>> there are instances (though very rare) where you do like to show 
>> accidentials
>> on certain notes. I provide a \flatten markup for those cases, but maybe 
>> there
>> is a better way?
>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Mats Bengtsson | 1 Aug 2005 16:32
Picon
Picon
Favicon

Re: Regarding the Musica ficta accidentals

OK! However, wouldn't it still make sense to only typeset the
suggested accidentals for accidentals marked as cautionary in
the input? At least in music from early 17th century, it was
indeed common to print some but not all accidentals explicitly.
With the current implementation, you would have to repeatedly
switch suggestAccidentals between true and false. It would be
easier to just mark the ones added by the editor with a "?" in
the input. (Hmm, how to distinguish these from automatically
generated cautionaries)?

One alternative to my proposal below might be to set the
cautionary style using a context property.

    /Mats

Han-Wen Nienhuys wrote:
> Mats Bengtsson wrote:
> 
>> I noticed the new support for suggested accidentals and am a bit
>> surprised that this wasn't added as a new possible style for the
>> cautionary-style property instead. I seem to recall that such a
> 
> 
> This is technically impossible, since the suggested accidentals have 
> different roles in the placement strategies. This implies that they have 
> to be of a different Grob type.
> 

--

-- 
=============================================
(Continue reading)

Permalink | Reply | 1 comment |
headers
Han-Wen Nienhuys | 1 Aug 2005 16:57
Picon
Picon
Favicon

Re: Regarding the Musica ficta accidentals

Mats Bengtsson wrote:
> OK! However, wouldn't it still make sense to only typeset the
> suggested accidentals for accidentals marked as cautionary in
> the input? At least in music from early 17th century, it was
> indeed common to print some but not all accidentals explicitly.
> With the current implementation, you would have to repeatedly
> switch suggestAccidentals between true and false. It would be
> easier to just mark the ones added by the editor with a "?" in

That would be great! Patches appreciated.

--

-- 
  Han-Wen Nienhuys - hanwen <at> xs4all.nl - http://www.xs4all.nl/~hanwen
Permalink | Reply | 0 comments |
headers
Sven Axelsson | 1 Aug 2005 17:54
Picon

RE: Settings for bagpipe music

> From: Stephen [mailto:stecmccarthy <at> hotpop.com] 
> >
> > On 29-Jul-05, at 12:15 AM, Sven Axelsson wrote:
> >
> I agree. What about my idea of  not removing the Key_engraver and 
> Accicental_engraver, putting it in the key of D major, and 
> supressing the 
> key signature with the line:
> 
> \override Score . KeySignature #'print-function = ##f

Yes, that is probably the way to go. What is the proper of specifying 
the key signature as default in the bagpipe.ly file rather than 
entering it in the score? I see that I could do

\set Score.KeySignature = #'((1 . 1) (3 . 1)) 

somewhere in the music, but what is the syntax for doing that in a

\layout { \context { \Score ... } } setting?

> And also creating special note names for notes with flats like:
> 
> (bb . ,(ly:make-pitch 0 6 FLAT))
> (Bb . ,(ly:make-pitch 1 6 FLAT))

Yep, I will do that.

--

-- 
Sven Axelsson
(Continue reading)

Permalink | Reply | 0 comments |

Gmane