lilypond-devel
[Top][All Lists]
Advanced

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

Re: lilypond -> midi -> ogg vorbis


From: Mats Bengtsson
Subject: Re: lilypond -> midi -> ogg vorbis
Date: Wed, 27 Oct 2004 14:57:41 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913

As far as I know, the ambition of the LilyPond MIDI output has never
been to produce an output of high listening quality, rather it's
mainly intended to help proofreading a score. Then, I don't really see
the point of including this conversion into LilyPond. If you want to
use LilyPond as a sequencer, it feels much more relevant to start by
improving the MIDI generation.

   /Mats

address@hidden wrote:
Hi all,

The last few months saw the creation of the freepats sound patterns package and updates to timidity. Creating an Ogg vorbis file from midi is now as simple as:

$ timidity -Ov lilypondgenerated.midi

It would be trivial to add Ogg vorbis output to lilypond and/or lilypond-book.

Does that fit into the Lilypond philosophy? I don't know, but I see a few
advantages of integrating Ogg vorbis output support, especially with
lilypond-book:

* eliminates a conversion step for Lilypond users
* easier to burn to CD, use on portable player (this would help me as a music
teacher)
* helps spread the free Ogg vorbis audio compression format
* ...

This would of course add timidity and/or freepats dependencies...

Any thoughts?

Mark



_______________________________________________
lilypond-devel mailing list
address@hidden
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: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================




reply via email to

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