emacs-orgmode
[Top][All Lists]
Advanced

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

Re: [O] Babel: 1st version for music notation language Fomus


From: Eric Schulte
Subject: Re: [O] Babel: 1st version for music notation language Fomus
Date: Fri, 08 Jul 2011 08:20:26 -0600
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

Torsten Anders <address@hidden> writes:

> Dear Eric,
>
> On 8 Jul 2011, at 02:38, Eric Schulte wrote:
>> 
>> Thanks for sharing this, it looks great, short clear and to the point.
>> 
>> Shall I add it to the contrib/ directory?
>
> If you think it is already at that point, that is certainly fine by me.
>

Great,

I do prefer to fold new languages in early so that they can benefit from
wider use and testing.

This is now located in contrib/babel/langs/.

Thanks for the contribution -- Eric

>
> Best,
> Torsten
>
>
>> 
>> Best -- Eric
>> 
>> Torsten Anders <address@hidden> writes:
>> 
>>> Dear Babel developers, 
>>> 
>>> Inspired by the newly available Lilypond, I hacked up a first version
>>> of language support for Fomus
>>> (http://fomus.sourceforge.net/). Briefly, Fomus is a music notation
>>> system that translates a relatively simple domain specific music
>>> language into multiple output formats, including Lilypond and MusicXML
>>> (the latter is an open format supported by many commercial music
>>> notation systems such as Finale and Sibelius). In a nutshell, Fomus
>>> can simplify the generation of complex scores, because it can add
>>> various score information automatically. Anyway, please find my first
>>> attempt of a Fomus integration attached.
>>> 
>>> This works already fine for standard code blocks such as the following. 
>>> Note that the result of this is a Lilypond file.
>>> 
>>> #+begin_src fomus :file test1.ly
>>> time 0 dur 2 pitch 60; 
>>> time 2 dur 1 pitch 62; 
>>> time 3 dur 1 pitch 63; 
>>> time 4 dur 4 pitch 65; 
>>> #+end_src
>>> 
>>> Of course, because this is a quick hack, various improvements can be
>>> made. For example, it might be a good idea to allow for something like
>>> :file test.pdf, where the resulting Lilypond call would see file.ly,
>>> but the automatically inserted link in the org buffer would be the
>>> resulting file.pdf.
>>> 
>>> Comments are welcome. 
>>> 
>>> Best wishes,
>>> Torsten
>>> 
>>> --
>>> Dr Torsten Anders
>>> Course Leader, Music Technology
>>> University of Bedfordshire
>>> Park Square, Room A315
>>> http://strasheela.sourceforge.net
>>> http://www.torsten-anders.de
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> -- 
>> Eric Schulte
>> http://cs.unm.edu/~eschulte/
>> 
>
>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/



reply via email to

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