Re: convert-ly doesn't convert figured bass
Thanks, I added this comment to bugs/convert-ly.txt
On Wednesday 24 November 2004 10.51, Mats Bengtsson wrote:
> Now I understand how your file is supposed to work!
> I attach a version modified to version 2.2. To be able to run convert-ly
> on it, I first replaced all occurencies of '{<' to some dummy like '{#'
> and similarly I replaced '>}' with '&}'. After the conversion, I could
> then change back from '{ #' to '{ <' and from '& }' to '> }'.
> The only other thing I had to update was the text markup with the title,
> see the attached file.
>
> /Mats
>
> Laura Conrad wrote:
> >>"Mats" == Mats Bengtsson <[EMAIL PROTECTED]> writes:
> >
> > Mats> I actually don't remember version 1.6 well enough to understand
> > how Mats> your example ever has worked. Did really the FiguredBass
> > context Mats> typeset also ordinary music at that time?
> >
> > No, it didn't typeset the music, but it ignored it except for the
> > lengths. So once you had the bass line entered, you just found the
> > notes with the figures on them and added them.
> >
> > Mats> Nowadays, the idea is to have a separate FiguredBass context
> > which Mats> only contains the figures.
> >
> > But then you have to tell it (again) what the lengths of the notes
> > between the figures are. And proofread that again.
> >
> > Mats> Another possibility would be to use text markup commands
> > instead, Mats> see for example
> > Mats>
> > http://lists.gnu.org/archive/html/lilypond-user/2004-10/msg00352.html
> >
> > If that's what the input/test/figured-bass-alternate.ly example is
> > doing, I tried it and wasn't able to get it to work. That is, the
> > example file works, and as long as I'm only adding one figure to a
> > note, it works in my file, but when I try to add two figures, like
> > this:
> >
> > f_\markup { \column <6 5>}
> >
> > lily tells me:
> >
> >
> > Now processing: `testfigures-markup.ly'
> > Parsing...
> > /home/lconrad/music/telemann/solo5/testfigures-markup.ly:24:30: error:
> > syntax error, unexpected STRING, expecting '<': f_\markup { \column <
> > 6 5>}
> >
> > /home/lconrad/music/telemann/solo5/testfigures-markup.ly:24:33: error:
> > Have to be in Lyric mode for lyrics: f_\markup { \column <6 5
> >
> > >}
> >
> > /home/lconrad/music/telemann/solo5/testfigures-markup.ly:24:34: error:
> > syntax error, unexpected '}':
> >
> > }
> >
> > I'm attaching the test file. Obviously I have the syntax wrong, but
> > it looks to me like what the example's doing.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ___
> > lilypond-devel mailing list
> > [EMAIL PROTECTED]
> > http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: convert-ly doesn't convert figured bass
Now I understand how your file is supposed to work!
I attach a version modified to version 2.2. To be able to run convert-ly
on it, I first replaced all occurencies of '{<' to some dummy like '{#'
and similarly I replaced '>}' with '&}'. After the conversion, I could
then change back from '{ #' to '{ <' and from '& }' to '> }'.
The only other thing I had to update was the text markup with the title,
see the attached file.
/Mats
Laura Conrad wrote:
"Mats" == Mats Bengtsson <[EMAIL PROTECTED]> writes:
Mats> I actually don't remember version 1.6 well enough to understand how
Mats> your example ever has worked. Did really the FiguredBass context
Mats> typeset also ordinary music at that time?
No, it didn't typeset the music, but it ignored it except for the
lengths. So once you had the bass line entered, you just found the
notes with the figures on them and added them.
Mats> Nowadays, the idea is to have a separate FiguredBass context which
Mats> only contains the figures.
But then you have to tell it (again) what the lengths of the notes
between the figures are. And proofread that again.
Mats> Another possibility would be to use text markup commands instead,
Mats> see for example
Mats> http://lists.gnu.org/archive/html/lilypond-user/2004-10/msg00352.html
If that's what the input/test/figured-bass-alternate.ly example is
doing, I tried it and wasn't able to get it to work. That is, the
example file works, and as long as I'm only adding one figure to a
note, it works in my file, but when I try to add two figures, like
this:
f_\markup { \column <6 5>}
lily tells me:
Now processing: `testfigures-markup.ly'
Parsing...
/home/lconrad/music/telemann/solo5/testfigures-markup.ly:24:30: error: syntax
error, unexpected STRING, expecting '<':
f_\markup { \column <
6 5>}
/home/lconrad/music/telemann/solo5/testfigures-markup.ly:24:33: error: Have to
be in Lyric mode for lyrics:
f_\markup { \column <6 5
>}
/home/lconrad/music/telemann/solo5/testfigures-markup.ly:24:34: error: syntax
error, unexpected '}':
}
I'm attaching the test file. Obviously I have the syntax wrong, but
it looks to me like what the example's doing.
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=
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: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
\version "2.2.0"
\header {
composer = "Francesco Maria Veracini (1690-1768)"
crossRefNumber = "1"
footnotes = ""
tagline = "Lily was here 1.6.8 -- automatically converted from ABC"
title = "Sonata Sesta"
}
voiceB = \notes {
\set Score.defaultBarType = "empty"
\set Staff.instrument = treble
r4 ^\markup{ \italic \huge "Largo" } e''4)f''4\bar "|" f''4
e''4b''4\bar "|"
b''8gis''8b''8f''16e''16b''8d''8\bar "|" d''4
c''4a''4\bar "|" f''8d''8b''8g''8d'''8f''8
\bar "|" e''4.g''8e''8c''8\bar "|" a''8f''8a''8
d''8d'''8f''8\bar "|" b''4.g''8c'''4 ~\bar "|"
% 9
c'''8a''8b''4.c'''8\bar "|" c'''4r8 e''8f''8
g''8\bar "|" bes'4g''4bes'4\bar "|" bes'4a'8f''8
g''8a''8\bar "|" c''4a''4c''4\bar "|" c''4b'!8
g''8a''8b''8\bar "|" d''4b''4d''4\bar "|" d''4
c''8e''8a''8g''8\bar "|" % 17
f''4.d''8b''8a''8\bar "|" gis''4.e''8a''4 ~
\bar "|" a''8fis''8gis''4.a''8\bar "|" a''2f''!4
\bar "|" f''4e''8b''8e''8e''8\bar "|" e''4dis''8
a''8d''!8d''8\bar "|" d''4.b'8c''4 ~\bar "|" c''8
d''8b'4.a'8\bar "|" a'2. ^\fermata \bar "|."
}
voiceC = \notes {
\set Score.defaultBarType = "empty"
\set Staff.instrument = bass
\key a \minor \clef bass
a,2a4\bar "|" gis2.\bar "|" e2.\bar "|" a,2c4
\bar "|" d2b,4\bar "|" c2r4 \bar "|" f2f4\bar "|"
g2e4 ~\bar "|" % 9
e8f8g4g,4\bar "|" c4c,4c4\bar "|" d4e4
c4\bar "|" f2.\bar "|" fis2.\bar "|" g2.\bar "|" gis2.
\bar "|" a2c4
Re: convert-ly doesn't convert figured bass
[EMAIL PROTECTED] writes:
> If that's what the input/test/figured-bass-alternate.ly example is
> doing, I tried it and wasn't able to get it to work. That is, the
> example file works, and as long as I'm only adding one figure to a
> note, it works in my file, but when I try to add two figures, like
> this:
>
> f_\markup { \column <6 5>}
>
> lily tells me:
this is an unfortunate bug. The < and > must be separated in order
not to be recognized as strings, i.e.
< 6 5 >
(fixed in CVS.)
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: convert-ly doesn't convert figured bass
[EMAIL PROTECTED] writes:
> And it isn't at all clear to me what the changes to figured bass
> between 1.6 and 2.4 have accomplished. It doesn't sound like any
> reader of the list has entered a whole sonata (or even a movement) in
> the new syntax. I don't see a way to do it without entering a lot of
> redundant information that has to be proofread. And I did enter 3
> sonatas in the old syntax.
\figures has been renamed to \figuremode. The change of chord syntax
(during 1.8 and 2.0) cause convert-ly to do the Wrong Thing;
\figures { <6 4> }
should be
\figuresmode { <6 4> }
and not
\figuresmode { <<6 4>> }
I can't recall any further changes to the syntax, which raises the
question with me how much effort you have put into reading the NEWS
file.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: convert-ly doesn't convert figured bass
> "Han-Wen" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: Han-Wen> [EMAIL PROTECTED] writes: >> I was really hoping this sonata would be an easy project, since I'd >> already been through the learning curve. Adding a new learning curve >> every 6 months isn't the best route to world domination. Han-Wen> I think that that is not a fair comment - 1.6 is over two years old Han-Wen> now. But I was still using it up until a few months ago. I think there's a little bit of insensitivity towards people working on large projects on this list. Even when I can just run my lilypond through convert-ly, I have to rewrite all my scripts and check the paging on the lilypond-book output, and it just isn't anything I can do as often as you produce major releases. So I went from 1.6 to 2.0, and I was only just finishing converting the Dowland to 2.0 when you came out with 2.2. So I decided to wait for 2.4, but it looks like the changes to that are pretty major, and you're talking about 3.0 being even more changes, so it's likely I'll skip 2.4 as well, although I am doing some testing on Pedro's snapshots. I'd like to help with development, but I'm really doing this to publish music, not to learn new music description possibilities. And it isn't at all clear to me what the changes to figured bass between 1.6 and 2.4 have accomplished. It doesn't sound like any reader of the list has entered a whole sonata (or even a movement) in the new syntax. I don't see a way to do it without entering a lot of redundant information that has to be proofread. And I did enter 3 sonatas in the old syntax. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: convert-ly doesn't convert figured bass
[EMAIL PROTECTED] writes: > I was really hoping this sonata would be an easy project, since I'd > already been through the learning curve. Adding a new learning curve > every 6 months isn't the best route to world domination. I think that that is not a fair comment - 1.6 is over two years old now. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: convert-ly doesn't convert figured bass
> "Mats" == Mats Bengtsson <[EMAIL PROTECTED]> writes:
Mats> I actually don't remember version 1.6 well enough to understand how
Mats> your example ever has worked. Did really the FiguredBass context
Mats> typeset also ordinary music at that time?
No, it didn't typeset the music, but it ignored it except for the
lengths. So once you had the bass line entered, you just found the
notes with the figures on them and added them.
Mats> Nowadays, the idea is to have a separate FiguredBass context which
Mats> only contains the figures.
But then you have to tell it (again) what the lengths of the notes
between the figures are. And proofread that again.
Mats> Another possibility would be to use text markup commands instead,
Mats> see for example
Mats> http://lists.gnu.org/archive/html/lilypond-user/2004-10/msg00352.html
If that's what the input/test/figured-bass-alternate.ly example is
doing, I tried it and wasn't able to get it to work. That is, the
example file works, and as long as I'm only adding one figure to a
note, it works in my file, but when I try to add two figures, like
this:
f_\markup { \column <6 5>}
lily tells me:
Now processing: `testfigures-markup.ly'
Parsing...
/home/lconrad/music/telemann/solo5/testfigures-markup.ly:24:30: error: syntax
error, unexpected STRING, expecting '<':
f_\markup { \column <
6 5>}
/home/lconrad/music/telemann/solo5/testfigures-markup.ly:24:33: error: Have to
be in Lyric mode for lyrics:
f_\markup { \column <6 5
>}
/home/lconrad/music/telemann/solo5/testfigures-markup.ly:24:34: error: syntax
error, unexpected '}':
}
I'm attaching the test file. Obviously I have the syntax wrong, but
it looks to me like what the example's doing.
testfigures-markup.ly
Description: Binary data
--
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097 fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: convert-ly doesn't convert figured bass
I actually don't remember version 1.6 well enough to understand how
your example ever has worked. Did really the FiguredBass context
typeset also ordinary music at that time?
Nowadays, the idea is to have a separate FiguredBass context which
only contains the figures.
One solution is something like:
\score{ <<
\new Staff \relative c{
\time 3/4
\clef bass
a2<}>> |
<}>>
<}>> |
<< e4. \context FiguredBass=fig \figuremode{<3+ 7>} >> gis8 a4
}
\context FiguredBass=fig {}
>>
}
Note that you need to declare the FiguredBass context from the beginning
of the score to keep it alive, otherwise you get a new context for each
new figure which is typeset some millimeters below the previous one.
Another possibility would be to use text markup commands instead,
see for example
http://lists.gnu.org/archive/html/lilypond-user/2004-10/msg00352.html
/Mats
Laura Conrad wrote:
"Mats" == Mats Bengtsson <[EMAIL PROTECTED]> writes:
Mats> Take a look at the example called figured-bass.ly in the Regression
Mats> Test document. The Regression Test and the Tips and Tricks documents
Mats> are the places to look for examples, even though more and more of the
Mats> examples have been integrated into the actual manual in version 2.4.
Thanks. I was only looking on the test level; I see now that I have
to go down to the regression level.
"Juergen" == Juergen Reuter <[EMAIL PROTECTED]> writes:
Juergen> Is the example in the user manual, section 5.16.13, sufficient?
No.
Neither of these examples are anything like what I had in 1.6, where I
duplicated the bass line and added \figure markups to the notes that
had figures on them. Han-Wen implies that I can do something like
that if I can guess the right number of angle brackets to use.
Note that both examples have almost all notes the same length, and no
notes without figures. This is not very much like the actual music
anyone writes figured bass on. A real-world example, such as I'm
hoping I might get out of convert-ly if I can ever decipher Han-Wen's
workaround would be more useful.
An explanation of what changed between 1.6 and 2.0 and why might also
be some use.
I was really hoping this sonata would be an easy project, since I'd
already been through the learning curve. Adding a new learning curve
every 6 months isn't the best route to world domination.
--
=
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: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: convert-ly doesn't convert figured bass
> "Mats" == Mats Bengtsson <[EMAIL PROTECTED]> writes: Mats> Take a look at the example called figured-bass.ly in the Regression Mats> Test document. The Regression Test and the Tips and Tricks documents Mats> are the places to look for examples, even though more and more of the Mats> examples have been integrated into the actual manual in version 2.4. Thanks. I was only looking on the test level; I see now that I have to go down to the regression level. > "Juergen" == Juergen Reuter <[EMAIL PROTECTED]> writes: Juergen> Is the example in the user manual, section 5.16.13, sufficient? No. Neither of these examples are anything like what I had in 1.6, where I duplicated the bass line and added \figure markups to the notes that had figures on them. Han-Wen implies that I can do something like that if I can guess the right number of angle brackets to use. Note that both examples have almost all notes the same length, and no notes without figures. This is not very much like the actual music anyone writes figured bass on. A real-world example, such as I'm hoping I might get out of convert-ly if I can ever decipher Han-Wen's workaround would be more useful. An explanation of what changed between 1.6 and 2.0 and why might also be some use. I was really hoping this sonata would be an easy project, since I'd already been through the learning curve. Adding a new learning curve every 6 months isn't the best route to world domination. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: convert-ly doesn't convert figured bass
> "Han-Wen" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: >> Neither the 2.0.1 convert-ly nor the 2.4 convert-ly-snapshot converts >> this file to a file lilypond can run on. Han-Wen> You are right, but I cannot fix this. A workaround is to change <<>> Han-Wen> in \figure into <> before feeding it to convert-ly. I don't understand. What I have is things like: a,2}> How should I change the angle brackets? -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: convert-ly doesn't convert figured bass
Is the example in the user manual, section 5.16.13, sufficient? See: http://lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Figured-bass.html#Figured-bass Greetings, Jürgen On Tue, 23 Nov 2004, Laura Conrad wrote: > > "Han-Wen" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > > >> Attached is a lilypond 1.6.8 file with figured bass. > >> > >> Neither the 2.0.1 convert-ly nor the 2.4 convert-ly-snapshot converts > >> this file to a file lilypond can run on. > > Han-Wen> You are right, but I cannot fix this. A workaround is to change > <<>> > Han-Wen> in \figure into <> before feeding it to convert-ly. > > > It isn't actually that I want to convert the piece I already have; I > wanted to see what figured bass was like in the current version. And > I don't see an example file anywhere. Does someone have one for > either 2.0 or 2.4? > > > > -- > Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) > (617) 661-8097fax: (501) 641-5011 > 233 Broadway, Cambridge, MA 02139 > > > > > ___ > lilypond-devel mailing list > [EMAIL PROTECTED] > http://lists.gnu.org/mailman/listinfo/lilypond-devel > ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: convert-ly doesn't convert figured bass
Take a look at the example called figured-bass.ly in the Regression Test document. The Regression Test and the Tips and Tricks documents are the places to look for examples, even though more and more of the examples have been integrated into the actual manual in version 2.4. /Mats Laura Conrad wrote: "Han-Wen" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: >> Attached is a lilypond 1.6.8 file with figured bass. >> >> Neither the 2.0.1 convert-ly nor the 2.4 convert-ly-snapshot converts >> this file to a file lilypond can run on. Han-Wen> You are right, but I cannot fix this. A workaround is to change <<>> Han-Wen> in \figure into <> before feeding it to convert-ly. It isn't actually that I want to convert the piece I already have; I wanted to see what figured bass was like in the current version. And I don't see an example file anywhere. Does someone have one for either 2.0 or 2.4? -- = 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: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: convert-ly doesn't convert figured bass
> "Han-Wen" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: >> Attached is a lilypond 1.6.8 file with figured bass. >> >> Neither the 2.0.1 convert-ly nor the 2.4 convert-ly-snapshot converts >> this file to a file lilypond can run on. Han-Wen> You are right, but I cannot fix this. A workaround is to change <<>> Han-Wen> in \figure into <> before feeding it to convert-ly. It isn't actually that I want to convert the piece I already have; I wanted to see what figured bass was like in the current version. And I don't see an example file anywhere. Does someone have one for either 2.0 or 2.4? -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
convert-ly doesn't convert figured bass
[EMAIL PROTECTED] writes: > > Attached is a lilypond 1.6.8 file with figured bass. > > Neither the 2.0.1 convert-ly nor the 2.4 convert-ly-snapshot converts > this file to a file lilypond can run on. You are right, but I cannot fix this. A workaround is to change <<>> in \figure into <> before feeding it to convert-ly. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
convert-ly doesn't convert figured bass
Attached is a lilypond 1.6.8 file with figured bass. Neither the 2.0.1 convert-ly nor the 2.4 convert-ly-snapshot converts this file to a file lilypond can run on. I.ly Description: Binary data -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
