On Saturday, 11 March 2000, Alain CULOS writes:
> First of all thanks very much for this fantastic software that is Lilypond.
Thanks again :-)
> I eventually got it working after frustrating hours and I'm still in the dark
+ as
> to how I made it work, but I guess that's life. Yes Miktex seems to be pretty
> complex.
You could try using postscript output:
lilypond -f ps foo.ly
gv foo.ps
> My problem may not be a lilypond issue but a miktex one, though I'm sure you'
+ d
> know better on this list. When I tried the angels.ly test, I got the dvi OK,
+ but
> yap complains, here's part of the log book :
That's not so difficult:
> - C:\program\texmf\miktex\bin\makemf.exe --verbose feta-nummer10
> Cannot find feta-nummer source file.
Miktex can't find the feta-nummer10.mf file. Try setting something like
this:
set path=c:\texmf\miktex\bin;%path%
set TEXINPUTS=%TEXINPUTS%;c:\lilypond-1.2.0\tex
set MFINPUTS=%MFINPUTS%;c:\lilypond-1.2.0\mf
You should check the path where 'feta20.mf' lives (MFINPUTS), and
`lilyponddefs.tex' (TEXINPUTS).
> I'd appreciate if someone could help or point me to the right doc.
Have a look over here:
http://www.cs.uu.nl/~hanwen/lilypond/Documentation/programmer/out-www/README-W32.html
It seems that this document is orphaned on the webpages (there's no link to
it). Maybe because it contains old and unmaintained information.
> Maybe the problem lies in yap not being able to find a font in a directory wi
+ th
> a space ?
Directories with spaces are evil: that's asking for trouble. In DOS and
UNIX, spaces are traditionally used to separate files in a list of
filenames. Consider these two commands:
c:\> copy foo.ly bar.ly c:\lilypond-1.2
c:\> copy foo.ly bar.ly c:\program files\lilypond-1.2
What does the latter mean?
> Queries :
> 1/
> Does anyone know about utility programs that convert from these formats I don
+ 't
> know yet (filename extensions are : .pmx, .mtx, .mus and .mts) for conversion
+ to
> .ly and/or .midi ?
> Preferred answer would point to portable source code and/or win32 binaries.
> Other answers could point to documented standards for the above formats.
Don't know. Extensions are ambiguous. I can name any music file I want
'.mus'. Maybe that's musedata, you may have a look at lilypond-1.3.31,
it comes with a Python program called:
buildscripts/musadata2ly.py
(why is this in buildscripts?)
For .pmx and .mtx, see http://www.gmd.de/Misc/Music/
> 2/
> Is the Mutopia project interested in everything or just some categories ?
Yes.
> E.g. is the project keen on (clean) drinking songs as well as the best of
> Classical music and whatever else ?
Yes.
> 3/
> Do you lads know about TiMidity++ ? I would guess the answer is some of you d
+ o.
Yes, we do.
> Would it be much to tie in with TiMidity++ as far as instrument names are
> concerned - and to explore the possibility to use more extensive possibilitie
+ s
> of Midi (in order to use the right sound samples if present) ? Sorry I may sa
+ y
To the best of my knowledge, LilyPond knows about all instruments
supported in MIDI (0-127). See the file lily/midi-item.cc. If you
have anything to add, please do so.
> Suggestions :
> Only help I can provide is proof read the docs and misc files at this point
> besides my pretty limited experience of lilypond so far.
If you have useful additions/modifications, please send a patch to the
latest lilypond version. We'll be most thankful.
> 1/
> In italiano.ly : it says that ut is the french for do. In actual fact this is
> not quite right. In ancient times it used to be the case, but do IS the one u
+ sed
> in french (I'm french and I have been a music amateur for quite some time now
+ ).
> The only case where ut has been kept is to name the family of c clefs and do
+ is
> never used for them.
So, to sum it up, you say the comment should be:
For french naming in c clefs, just add 'ut' as an alias to 'do'.
?
> I created a simple frenglish.ly file that includes both english and french
> notations (a combination of english.ly and italiano.ly plus some long names i
+ n
> french to avoid switching from one to the other - I just include this in all
+ my
> files), please see attached file for those interested (should it make it into
> the distribution package ?).
Yes, it might, thanks. I'll have a look.
> 2/
> In glossary.ps, it would be nice to have :
> 2-a/
> A correspondance table for note values in different languages (more readable
> than the reference from english to whichever and works boths ways).
> 2-b/
> A correspondance value of note durations (same as above).
Indeed, want to send a patch?
> 3/
> In lilypond.ps, page "21" (23/76) I think there is an error in the table, [si
+ d]
> should be replaced by [sib] twice : for Italiano and Catalan. and to make it
> nicer for the french one could duplicate the line for italiano, to be named
> fran�ais (and possibly create the file from my frenglish that combines french
> and english).
Noted
> Question : is it possible to use non ascii characters in token names (e.g. to
> include files, to name parts, ...) ?
No (of course not). It is allowed in lyrics, though.
> 4/
> It took me a little while to understand how to put lyrics under two separate
> voices, see the attached Vin-Clairet.ly to see what I mean. This psample piec
+ e I
> attached or some equivalent, or maybe just a simple one liner might be welcom
+ e
> in the tutorial section of lilypond.ps so newcomers like me will find it easi
+ er
> to achieve.
I'll have a look. Have you seen input/test/twinkle.ly, and twinkle-pop.ly?
> 5/
> Tremolo marks page "31" (33/76) of lilypond.ps shows twice the same symbol,
> should it not show two different symbols ?
That's a bug. Thanks.
> 6/
> Give sample for altering margins (to include longer instrument names on the l
+ eft
> for instance), I'd love that.
try:
\paper{
indent = 6.0\cm;
linewidth= 15\cm;
}
You should check out ly2dvi, it handles margins.
> 7/
> The tagline item of the header is not documented, particularly, the usage of
> specials like \\\\ or any other there may be. More generally a better
> documentation (reference material) of the header and its internals. Or maybe
+ I
> just read lilypond.ps too fast.
The 'special' symbols are a hack, really: they're TeX escapes. We din't
want to document that, but maybe we should...
> 8/
> In midi2ly, would it be a big task to guess the key automatically ? And detec
+ t
> that a B-flat should be computed instead of an A-sharp if the key found makes
> this better ?
Yes. However, if you have sane MIDI input, it sets the key, and midi2ly
will read it. Also, you can tell midi2ly the key on the commandline.
See midi2ly --help.
> 9/
> Also in midi2ly, would it be a big task to correct (depending on an option) t
+ he
> length of notes since manual play is rather not exact and assume less skips t
+ han
> detected ? And also display rests rather than skips when these are large enou
+ gh
> and comparable in length to notes prior or following the skip/rest ?
You can choose different types of quantisation, eg
midi2ly --smallest=16
will not produce shorter notes than sixteenths.
> 10/
> That's a comment I left in one of my .ly files :
> \header
> ...
> piece = "Vivace";
> % As Jeff Covey says, it is not correct to use [piece] for the
> % tempo, but it is the one that looks best.
> % Maybe there is room for one more keyword, say call it (I'm
> % being very creative here) [tempo] and place it rigth underneath
> % the [piece] displayed element and shift the whole scores down a
> % bit to make room - or shift the [piece] up a bit.
> % And while you're at it align the left side of the [tempo] with
> % the start of the first staff.
Noted.
> 11/
> In ly2dvi enhance the error messages, they are not always very meaningful to
+ the
> layman (me). A number of times I was looking for the wrong information to try
> and correct simple things (mostly extra or missing ';' not advertised as such
+ in
> the error message : cannot find output file or some such).
Please specify.
Greetings,
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
