[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Question about Getting MIDI Output

From: Mel Bellefontaine
Subject: Re: Question about Getting MIDI Output
Date: Fri, 19 Apr 2002 17:06:20 -0700

Hello David:

Thanks for this.

Your suggestions are, of course, the obvious ones, and very good indeed.
But I am not sufficiently familiar with Unix-style command-line syntax to
make the task of following them as easy as I would like it to be.  Have you
any suggestions for a quick way for one to familiarize oneself with this

Anyway, the error I made was to assume that the particular example of source
code I chose to play with in the Tutorial was correctly produced.  After
some patient experimentation I was able to diagnose and resolve the problem.

Mel Bellefontaine

----- Original Message -----
From: David Boersma <address@hidden>
To: Mel Bellefontaine <address@hidden>
Cc: <address@hidden>
Sent: Friday, April 19, 2002 7:13 AM
Subject: Re: Question about Getting MIDI Output

> Hello!
> > I am a new user of Lilypond as of last week.  I love the idea because I
> > have been looking for a way for a blind person to get music into print
> > without sequencing and then having someone else edit the resulting
> > score.  Thanks so much for developing this tool.  Don't ever forget
> > those of us who want and need a text-based interface.
> Wow! I had not yet seen that argument for text-based input (as opposed to
> GUI approaches).
> > Anyway, here is my question:
> >
> > I tried to get version 1.4.12 to output MIDI, but when I ran LY2DVI on
> > the source file with a MIDI block in it (copied from the examples in the
> > tutorial), I got a pile of error messages and no output.
> >
> > What do I do?
> I think the best thing to do is to send a copy of your input file as well
> as the resulting 'pile of error messages' to this list. It is often also
> helpful to give specifications about the operating system (and
> distribution, if relevant) you run on your computer.
> Then a loosely organised team of developers and experienced users will
> perform the autopsy on it (in which stage did the program die and &
> whodunnit).
> EITHER they will immediately come up with a diagnoses & solutions, OR they
> will do suggestions for tests (check for incompatible packages in
> installation) and improvements (point out grammar/syntax errors input) et
> cetera.
> Cheers,
> David Boersma

reply via email to

[Prev in Thread] Current Thread [Next in Thread]