Re: Integrated solution for converting midi output to wav/mp3?

2007-05-11 Thread Jonas Nyström

Thank you, Graham and Eyolf!
I'll check Timidity out!

Jonas

2007/5/11, Eyolf Oestrem [EMAIL PROTECTED]:


On 10.05.2007 (15:49), Graham Percival wrote:
Jonas Nyström wrote:
Does someone know of a open source solution for converting LilyPond midi
to
wav or (preferrably) to mp3?

timidity (or timidity++) to wav, then lame (or your favorite encoder) to
mp3.

...or if you want a gui, there is a nice frontend called
SoundKonverter. It does the same thing, but in one go, and you don't
have to remember any switches...
If you want to do it automatically, though, a

Shell script.

would be the best solution.

Eyolf

--
I don't like this official/unofficial distinction.  It sound, er,
officious.
  -- Larry Wall in  [EMAIL PROTECTED]


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: error messages while using \include italiano.ly

2007-05-11 Thread Valentin Villenave

2007/5/10, Graham Percival [EMAIL PROTECTED]:

Ledocq-Boccart wrote:



 I try to write music sheet using french syntax  (as do re mi fa ...)



It has been translated into French, if that helps.


There's also a mailing list which is dedicated to French-speaking users:
http://lists.gnu.org/mailman/listinfo/lilypond-user-fr

You're welcome to join our French-related discussions, and we'll be
glad to help you there.

Cheers,
Valentin Villenave.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Coordinates for score objects?

2007-05-11 Thread Mats Bengtsson

See also http://lists.gnu.org/archive/html/lilypond-user/2005-11/msg00273.html
Possibly, the SVG backend to LilyPond may be useful.


  /Mats


Quoting Bertalan Fodor [EMAIL PROTECTED]:


See http://lilypondtool.organum.hu

Bert

Jonas Nyström írta:

Hi!

Is it somehow possible to retrieve the coordinates for score objects
(mainly notes, noteheads, but also systems etc.) in a generated picture?

Could be useful when creating interactive applications based on
lilypond generated pictures... (Clicking on notes resulting in sound
etc.)

Regards / Jonas


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user










___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: partial measure in figured bass

2007-05-11 Thread Mats Bengtsson

Please provide a complete example of what you tried. The following
example seems to work fine:

\new FiguredBass \figuremode {\partial 4 _4 3 3 6 }


  /Mats

Quoting Victor Eijkhout [EMAIL PROTECTED]:


When I write

\partial 4 _4

I get:

Parsing...
fredo, figured.ly:2:13: error: syntax error, unexpected '_',  
expecting  or DRUM_PITCH or MUSIC_FUNCTION or NOTENAME_PITCH

\partial 4 
 _ 4 |

but the music is otherwise typeset correctly.

What's the legal solution?

Victor.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user







___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


sponsorship request: minimum-measure-left-padding

2007-05-11 Thread Kieren MacMillan

Hello, all --

Now that I'm well into engraving several big piano pieces in Lilypond  
2.11.23, it has become even more clear than ever that:
(1) the initial padding in measures is unacceptably small (and,  
in some cases, zero); and
(2) the various known workarounds are overly time-consuming and  
code-cluttering.


For example, in the ragtime solo piano piece I'm currently engraving,  
close to 75% of the measures require some form of initial-padding  
tweaking -- and (grrr!) it's a different (amount of) tweak for almost  
every measure!  =(


Therefore, I would like a quote on what it would cost to include a  
user-adjustable property to set the minimum space which must appear  
in every measure between the last prefatory item (i.e., bar line, key  
signature, time signature, clef; is that it?) and the first musical  
element (i.e., notehead, accidental, arpeggio or other attachment,  
etc.).


Thanks!
Kieren.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


moving bar line engraver to staff level

2007-05-11 Thread Laura Conrad

I think this is a bug, but since I don't usually rely on the default
bar line engraver, I'm sending this to user in case I'm doing
something really dumb.

The attached file is in 2/2, and should start with a partial measure,
in both parts.

If I don't include the \layout section, which moves the barline
engraver to the staff level from the score level, it prints the way I
expect.  

The file as written prints the first part as expected, but ignores the
\partial statement for the second part.



partialscore.ly
Description: Binary data

If it's a bug, does anyone know a workaround?  If not, what am I doing
wrong?

-- 
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097  fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


umlaut trouble; was Weird output

2007-05-11 Thread David Bobroff
I'm post this to both bug- and -user as I'm not sure what's going on.
The following file is essentially self-explanatory:


%%% BEGIN LILYPOND FILE

\version 2.10.20 %% On Windows

\header {
title = \markup {
%% commenting out \italic allows proper rendering
\italic
äëïöüÿ
}
}

\score {
\relative c' {
c1
}
}

%%% END LILYPOND FILE

Leaving in '\italic' causes every umlaut to be rendered incorrectly.
It's looks rather like a single curly quote on its side.

I stumbled upon this problem in an odd way.  My Linux laptop, where I
prefer to do my Lily work had something go wrong.  There's some problem
with Xwindows.  I was able to run it without X running and managed to
upload some work I did not have duplicated elsewhere.  I simply uploaded
it to my web space and then downloaded it to another machine running
Windows.  I was making some minor edits (jEdit) and some test prints.
All was well for a while.  Then I noticed some anomalies.  In a lyric an
umlaut-a had become an upper case A with tilde followed by the universal
currency symbol (I think).  The lower case 'u' with grave was also
different.  This was obviously some sort of encoding issue.  I would
suppose something happened to these characters when they were placed on
the web server, or on their way back to me.

I was able to correct the 'u' with grave but not the umlaut-a nor any
other umlauted vowel.  It's puzzling as I have gone through and tried
editing the input but in the case of the umlaut-a in the lyric line at
prints as A-tilde currency in the PDF.

Help?

-David


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: sponsorship request: minimum-measure-left-padding

2007-05-11 Thread Damian leGassick

i think i second that...

but isn't the collision of (for instance) flats with bar lines a bug/ 
defect?


if not, i'll chip in - i've got hundreds of theory/analysis snippets  
that can't go to print as is and i can't go back to 2.10...i'm hoping  
this will be fixed before  i have to tweak them all by by hand (the  
recent ones have eighth note spacers after each bar/clef).



Cheers

Damian

btw, what are the best workarounds without adding spacers?


On 11 May 2007, at 15:33, Kieren MacMillan wrote:


Hello, all --

Now that I'm well into engraving several big piano pieces in  
Lilypond 2.11.23, it has become even more clear than ever that:
(1) the initial padding in measures is unacceptably small (and,  
in some cases, zero); and
(2) the various known workarounds are overly time-consuming and  
code-cluttering.


For example, in the ragtime solo piano piece I'm currently  
engraving, close to 75% of the measures require some form of  
initial-padding tweaking -- and (grrr!) it's a different (amount  
of) tweak for almost every measure!  =(


Therefore, I would like a quote on what it would cost to include a  
user-adjustable property to set the minimum space which must appear  
in every measure between the last prefatory item (i.e., bar line,  
key signature, time signature, clef; is that it?) and the first  
musical element (i.e., notehead, accidental, arpeggio or other  
attachment, etc.).


Thanks!
Kieren.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: sponsorship request: minimum-measure-left-padding

2007-05-11 Thread Kieren MacMillan

Hi, Damian --

but isn't the collision of (for instance) flats with bar lines a  
bug/defect?


I think so, but currently it's not being given very high priority...  
so I thought I'd try to escalate it!  =)



btw, what are the best workarounds without adding spacers?


The two I've been playing with are:
(1) Adjust the BarLine #'spacing alist: difficult to really  
understand how each setting interacts (or conflicts) with other  
properties, so I avoid this.
(2) Adjust the #'X-extent of the offending element (i.e., the  
one that Lilypond *should* be automatically adjusting): this is  
definitely easier than (1), and essentially every grob responds to an  
#'X-extent adjustment, but it's still a lot of manual labour when  
you're adjusting nearly every measure, and every time the layout  
changes you need to revisit every single adjustment.


Below is an example of fixing a flat-collision problem using method  
(2). Although there is (IMO) a problem with every single measure in  
the default engraving, my favourite is m. 4, where the flat looks  
like it's part of the key signature...  =\


Hope this helps!
Kieren.
___

\version 2.11.23  % Mac OS X 10.4.9
\include english.ly

accTooClose = \relative
{
\time 4/4
\key af \major
\repeat unfold 32 { cf' df8 }
}

accPadded = \relative
{
\time 4/4
\key af \major

\override Accidental #'X-extent = #'(-0.75 . 0.85)
\repeat unfold 8 { cf' df8 }

\override Accidental #'X-extent = #'(-0.5 . 0.85)
\repeat unfold 16 { cf df8 }

\override Accidental #'X-extent = #'(-0.95 . 0.85)
\repeat unfold 8 { cf df8 }
}

\paper
{
ragged-right = ##t
printallheaders = ##t
}

\score
{
\accTooClose
\header
{
subtitle = Default
}
}

\score
{
\accPadded
\header
{
subtitle = Accidental Manually Padded (X-extent)
}
}


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: sponsorship request: minimum-measure-left-padding

2007-05-11 Thread Damian leGassick

hi kieren

thanks for those examples

most of my files are less than one page so this'll help - the layout  
doesn't change that much by the time i've got to adjusting flat- 
placement...


but i would like it to work better out of the box, i'm sure it used  
to though, i've only been getting my hands dirty in the last few months



I think so, but currently it's not being given very high priority.


hope that's not true, but consider this a bump

Damian




On 11 May 2007, at 19:38, Kieren MacMillan wrote:


Hi, Damian --

but isn't the collision of (for instance) flats with bar lines a  
bug/defect?


I think so, but currently it's not being given very high  
priority... so I thought I'd try to escalate it!  =)



btw, what are the best workarounds without adding spacers?


The two I've been playing with are:
(1) Adjust the BarLine #'spacing alist: difficult to really  
understand how each setting interacts (or conflicts) with other  
properties, so I avoid this.
(2) Adjust the #'X-extent of the offending element (i.e., the  
one that Lilypond *should* be automatically adjusting): this is  
definitely easier than (1), and essentially every grob responds to  
an #'X-extent adjustment, but it's still a lot of manual labour  
when you're adjusting nearly every measure, and every time the  
layout changes you need to revisit every single adjustment.


Below is an example of fixing a flat-collision problem using method  
(2). Although there is (IMO) a problem with every single measure in  
the default engraving, my favourite is m. 4, where the flat looks  
like it's part of the key signature...  =\


Hope this helps!
Kieren.
___

\version 2.11.23  % Mac OS X 10.4.9
\include english.ly

accTooClose = \relative
{
\time 4/4
\key af \major
\repeat unfold 32 { cf' df8 }
}

accPadded = \relative
{
\time 4/4
\key af \major

\override Accidental #'X-extent = #'(-0.75 . 0.85)
\repeat unfold 8 { cf' df8 }

\override Accidental #'X-extent = #'(-0.5 . 0.85)
\repeat unfold 16 { cf df8 }

\override Accidental #'X-extent = #'(-0.95 . 0.85)
\repeat unfold 8 { cf df8 }
}

\paper
{
ragged-right = ##t
printallheaders = ##t
}

\score
{
\accTooClose
\header
{
subtitle = Default
}
}

\score
{
\accPadded
\header
{
subtitle = Accidental Manually Padded (X-extent)
}
}


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: umlaut trouble; was Weird output

2007-05-11 Thread David Rogers
On Fri, 11 May 2007 17:32:03 +, David Bobroff wrote:

 In a lyric an umlaut-a had become an upper case A with tilde followed 
 by the universal currency symbol (I think).

This comment makes me think that your file got translated along the way 
by a text editor that didn't read Unicode properly.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: umlaut trouble; was Weird output

2007-05-11 Thread David Bobroff
David Rogers wrote:
 On Fri, 11 May 2007 17:32:03 +, David Bobroff wrote:
 
 In a lyric an umlaut-a had become an upper case A with tilde followed 
 by the universal currency symbol (I think).
 
 This comment makes me think that your file got translated along the way 
 by a text editor that didn't read Unicode properly.

It certainly looks that way.  The last editor that did anything to it
before being uploaded was Emacs.  Then it was downloaded and opened in
jEdit.  That's it.  Very puzzling.

-David
 
 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 http://lists.gnu.org/mailman/listinfo/lilypond-user
 



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


lilypond-book and latex

2007-05-11 Thread Sebastian Menge
Hi

I want to write a report using lily and latex.

Is there a way of using lilypond such that i dont have to interrupt my
normal editing process?

Normally i write tex documents with my preferred editor (vim with
latexsuite) with completion, syntax highlighting, have previews,
quickfix, etc.

If i use lilypond-book i have to call latex on the generated document,
find and fix errors in the original document, then call l-b again and so
on.

On the other hand i dislike to generate eps for the lily-snippets,
because thats inflexible.

Does anyone have an idea how to manage that in a clever way?

Thanks,

Sebastian



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: lilypond-book and latex

2007-05-11 Thread Laura Conrad
 Sebastian == Sebastian Menge [EMAIL PROTECTED] writes:

Sebastian Does anyone have an idea how to manage that in a clever
Sebastian way?

It's not especially clever, but I wouldn't dream of using
lilypond-book without a Makefile to run the commands.  So just set the
Makefile up and run that from emacs. (Or presumably jedit, but I don't
use that.)

My Makefile says:

%.pdf:  %.lytex *.ly *.bib Makefile
 lilypond-book --output=out --psfonts $*.lytex
 cd out;eps-fix-bounding.sh $*.tex;latex $*.tex;bibtex $*.aux;dvips 
$(DVIPSOPTS) -h $*.psfonts -o ../$*.ps $*.dvi
#cd out;latex $*.tex;bibtex $*.aux;dvips $(DVIPSOPTS) -h $*.psfonts -o 
../$*.ps $*.dvi
 ps2pdf $*.ps $*.pdf

You might not need to worry about the bibliography, and if you're
not printing double sided you might not have to do the workaround
(eps-fix-bounding.sh) for lilypond-book shifting everything to the
right of where it should be, but even without that, I wouldn't try to
do it without a Makefile.

If you don't need the eps-fix-bounding workaround, you may prefer to
use pdflatex rather than dvips and ps2pdf, but there's some reason I
couldn't get the workaround to work in that context.

-- 
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097  fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: sponsorship request: minimum-measure-left-padding

2007-05-11 Thread Adam Good

Thanks Kieren for brining this up.

I too would like to chip in some money for this. Let me know what I 
need to do.


Adam

On May 11, 2007, at 9:33 AM, Kieren MacMillan wrote:

Therefore, I would like a quote on what it would cost to include a 
user-adjustable property to set the minimum space which must appear in 
every measure between the last prefatory item (i.e., bar line, key 
signature, time signature, clef; is that it?) and the first musical 
element (i.e., notehead, accidental, arpeggio or other attachment, 
etc.).


--
Adam Good
[EMAIL PROTECTED]
www.adamgood.com
646.257.3797 ( US )
+31 642 58 90 42 (NL mobile)



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user