Re: Figured Bass support

2003-09-05 Thread Richard Shann
Han-Wen Nienhuys wrote:

For the moment, you could use markup texts. For example:


Thanks for the suggestion - however it is much more important to me that 
the scores I am writing are structurally sound (i.e. the figured basses 
are really figured basses, with their own durations etc - I'm working on 
a graphical editor for LilyPond that understands them) as I won't be 
re-writing the scores later. I really just filed this note about the 
aesthetics of your figured bass output because I understand that you 
want LilyPond to be taken up because the output does not look stiff and 
computer-like. For practical purposes the figures are reasonably easy to 
play from as they are, though overall a bit far away from the notes.

Richard





___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel


Re: Figured Bass support

2003-09-04 Thread Nicolas Sceaux

Tue, 2 Sep 2003 22:22:36 +0200, Han-Wen a dit : 

 > For the moment, you could use markup texts. For example:

 >  \header
 >  {
 >  texidoc = "An alternate method to make bass figures is to use
 >  markup texts."
 >  }
 >  \version "1.9.4"

 >  nat = \markup { \musicglyph #"accidentals-0" }
 >  sh = \markup { \smaller \raise #0.6 \musicglyph #"accidentals-1" }
 >  fl = \markup { \musicglyph #"accidentals--1" }

 >  \score {
 >\context Voice \notes {
 >\clef bass
 >\property Voice.TextScript \set #'font-family = #'number
 >\property Voice.TextScript \set #'font-relative-size = #-3
 >\property Voice.TextScript \set #'baseline-skip = #1.4

 >dis4_\markup { 6 }

 >c_\markup  { 7 }
 >d_\markup { \column < { 6 \sh } \bracket { \nat } >}
 >ais_\markup { \column < 6  5 \bracket { 3 \sh } >}
 >}
 >  }  

Here is the same example using few scheme utilities:

--
#(use-modules (ice-9 optargs)
  (lilypond markups)) ; [1] See below

#(defmacro* fig (#:rest figs)
  "Figured bass as markups. Each of `figs' arguments may be
a number, a variable referencing a markup, a list of
numbers or markups (for lining text), or a (keyworded) markup
command."
  `(markup (#:column ,@(map gen-figures figs

#(define (gen-figures figure)
  (cond ((and (pair? figure) (keyword? (car figure)))
 `(,(car figure) ,@(map gen-figures (cdr figure
((and (pair? figure) (not (null? (cdr figure
 `(#:line ,@(map gen-figures figure)))
((pair? figure)
 (gen-figures (car figure)))
((number? figure)
 `(#:string ,(number->string figure)))
(else
 figure)))

nat = \markup { \musicglyph #"accidentals-0" }
sh = \markup { \smaller \raise #0.6 \musicglyph #"accidentals-1" }
fl = \markup { \musicglyph #"accidentals--1" }

\score {
\context Voice \notes {
\clef bass
\property Voice.TextScript \set #'font-family = #'number
\property Voice.TextScript \set #'font-relative-size = #-3
\property Voice.TextScript \set #'baseline-skip = #1.4

dis4_#(fig 6)
c_#(fig 7)
d_#(fig (6 sh) (#:bracket nat))
ais_#(fig 6 5 (#:bracket 3 sh))
}
} 
-- 

nicolas

---
[1] the module named (lilypond markups) can be found here:
http://nicolas.sceaux.free.fr/lilypond/scheme-hacks.html



___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel


Re: Figured Bass support

2003-09-03 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes:
> I sent a sample output from 1.8.0 to a composer (who had only seen 
> finale, sibelius etc before) he commented
> 
> < Thanks for sending it to me. The quality is very impressive, and
> aesthetically pleasing. >

Good to hear!

> One thing he pointed out (amongst other things I am working through)
> is that the figures in the bass are unconventionally far from the
> notes they refer to. The figures all begin at the same vertical
> offset, computed to miss the worst case note. In the hand engraved
> scores I've looked at the figures start a short distance below the
> note, or the bottom staff line if the note is entirely within the
> staff. (i.e. they are ragged top and bottom).

> This is rather verbose - is there some tweak available to make the 
> figures automatically sit just below whatever is above? I have a 

In effect, you are saying that you want the bass figures to behave
like texts and fingerings wrt. notes. Implementing this is possible,
and not even that difficult - but not very high on my current priority
list.

For the moment, you could use markup texts. For example:

\header
{
texidoc = "An alternate method to make bass figures is to use
markup texts."
}
\version "1.9.4"

nat = \markup { \musicglyph #"accidentals-0" }
sh = \markup { \smaller \raise #0.6 \musicglyph #"accidentals-1" }
fl = \markup { \musicglyph #"accidentals--1" }

\score {
  \context Voice \notes {
  \clef bass
  \property Voice.TextScript \set #'font-family = #'number
  \property Voice.TextScript \set #'font-relative-size = #-3
  \property Voice.TextScript \set #'baseline-skip = #1.4

  dis4_\markup { 6 }

  c_\markup  { 7 }
  d_\markup { \column < { 6 \sh } \bracket { \nat } >}
  ais_\markup { \column < 6  5 \bracket { 3 \sh } >}
  }
}  


Use << >>  iso. < > for 1.8, and quote the numbers, i.e.

 \column << { "6" \sh } ...



-- 

Han-Wen Nienhuys   |   [EMAIL PROTECTED]   |   http://www.xs4all.nl/~hanwen 


___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel


Re: Figured Bass support

2003-09-03 Thread Richard Shann
 Han-Wen Nienhuys wrote:

[EMAIL PROTECTED] writes:
 

The last problem is easily fixed:

\property FiguredBass.BassFigure \override #'font-relative-size = #-3

just before the figures does the trick.
   

I've added this to scm/grob-description.scm

 

This change seems to have got lost  - in 1.8.0 in scm/define-grobs.scm 
there is (font-relative-size . -1)

I sent a sample output from 1.8.0 to a composer (who had only seen 
finale, sibelius etc before) he commented

< Thanks for sending it to me. The quality is very impressive, and
aesthetically pleasing. >
One thing he pointed out (amongst other things I am working through) is that the figures in the bass are unconventionally far from the notes they refer to. The figures all begin at the same vertical offset, computed to miss the worst case note. In the hand engraved scores I've looked at the figures start a short distance below the note, or the bottom staff line if the note is entirely within the staff. (i.e. they are ragged top and bottom).

Also the example in the 1.8.0 documentation assumed that the default 
direction was going to be #-1, so as it stands it generates a 
back-to-front set of figures.
With all this in mind,  the following revised example works with 1.8.0

\score {
<
 \context Voice \notes { \clef bass dis4  c d ais}
 \context FiguredBass
   \figures {
\property FiguredBass.BassFigure \override #'font-relative-size = #-3
\property FiguredBass.BassFigure \set #'direction = #-1
\property FiguredBass.BassFigure \set #'extra-offset = #'(0 . 3.5)
\once \property FiguredBass.BassFigure \set #'extra-offset = #'(0 . 2.5) 
< 6 >4
< 7 >8 < 6+ [_!] >
\once \property FiguredBass.BassFigure \set #'extra-offset = #'(0 . 2.5) 
< 6 >4
<6 5 [3+] >
   }
 >
}

This is rather verbose - is there some tweak available to make the 
figures automatically sit just below whatever is above? I have a 
sneaking suspicion that this bit is the right bit to tweak
(BassFigure
...
(Y-offset-callbacks . (,Self_alignment_interface::aligned_on_self))
...

but have no idea how (aligned_on_something_else? :-\ )

Richard





___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel


Re: Figured Bass support

2002-12-27 Thread Richard Shann
Han-Wen Nienhuys wrote:


[EMAIL PROTECTED] writes:
 

(a first attempt to post seemed to go into a black hole ... try again 
...)

The figured bass support in lilypond (wonderful!) is a little tricky 
to use
for three reasons:
1) The figures have to be entered in the reverse order (that is a 
six-four
chord is entered <4 6>). Of course, this assumes that you do call it 
that and
not a four-six chord, but I *think* is universally so.
  


In dutch, <> (absolute pitches) is called a 4-6 chord, not
6-4; that's what you mean, right? 

yes


I'm not sure about the proper names
in English.

Can you do some more research to find out what is the Right Way?


yes - with classic anglo-saxon myopia I referred to the English 
nomenclature as "universal" ...
the research for the Right Way turned out to be very easy - typing "six 
four chord" into Google yielded 137 hits and  "four six chord"  yielded 
7 hits. For example:

"Six-four chord (siks for kord) A chord consisting of three notes, the 
bass note, the interval of a fourth above the bass note, and a sixth 
above the bass note. ..."
from this site
www.music.vt.edu/musicdictionary/texts/Six-fourchord.html

and likewise for "four six chord", though less common.

However, it occurs to me that I've started us thinking along the wrong 
lines here - what matters is what people who may want to write figured 
basses into lilypond will find most natural. I jumped to the conclusion 
that the reason I write 6 followed by 4 when writing out figured basses 
was because I call it a six four chord. In fact, since the figures are 
always aligned at the top there is a much stronger reason why, when 
writing out the figures you start at the top and work downwards, and 
hence why you write them out as six followed by four (to continue the 
example). If you didn't write downwards, you would have to guess where 
to start writing the figures, judging by how many figures you had to 
fill in.
This all presupposes that figured basses are indeed aligned horizontally 
at the top: I am sure this is always so, based on sampling Italian, 
French, English and German 17th & 18th c. sonatas from my bookshelf and 
thirty odd years of knocking round in early music circles. In fact, I 
think anything else would appear outlandish, because the commonest 
figures (a # or b or a six on their own) would have to be placed at some 
distance from the bass note, depending on the maximum number of figures 
to be found on any one note in the piece. A # would then frequently 
appear to be associated with some note on the next line, which usually 
either means that the editor thinks *that* note should be sharpened (or 
if ornamented, the ornament should be sharpened). (I feel perhaps I'm 
labouring the point now ...).


I've added #'direction for the BassFigure grob, so you can the
stacking direction. (1.7 cvs)


The default should be the normal direction else we risk creating another 
standard in figured bass notation!

Best regards,

Richard Shann




___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel


Re: Figured Bass support

2002-12-19 Thread Juergen Reuter


On Wed, 18 Dec 2002, Han-Wen Nienhuys wrote:

> ...
> > 1) The figures have to be entered in the reverse order (that is a six-four
> > chord is entered <4 6>). Of course, this assumes that you do call it
> > that and
> > not a four-six chord, but I *think* is universally so.
>
> In dutch, <> (absolute pitches) is called a 4-6 chord, not
> 6-4; that's what you mean, right?  I'm not sure about the proper names
> in English.
>

FYI, in German language, <> is called "Quart-Sext-Akkord",
i.e. we also first consider the 4th, and then the 6th.

Greetings,
Juergen



___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel