Re: Place to write piano dynamics

2008-06-16 Thread Valentin Villenave
2008/6/16 Michael Pozhidaev <[EMAIL PROTECTED]>: > One more thing, there was information in the lilypond-user list how to force > lilypond to process \repeat{} block > twice for the midi output. I am sorry, I moved this message into one of my > mail folders and then simply lost. > Now this magic

Re: Place to write piano dynamics

2008-06-09 Thread Mats Bengtsson
Valentin Villenave wrote: BTW: I read, lilypond originally was written in C++, but during the developing process the authors hdecided schema is more suitable for this task. No. LilyPond was originally written in some other language (I don't know... Python? TeX?) No, the main part

Re: Place to write piano dynamics

2008-06-09 Thread Valentin Villenave
2008/6/9 Michael Pozhidaev <[EMAIL PROTECTED]>: > So, if I put dynamics in the melody variable, they will be placed near > right hand stave and there is no way to move them to the center? Actually, there is a way to use your "right hand" variable in the Dynamics context: since the Dynamics contex

Re: Place to write piano dynamics

2008-06-09 Thread Valentin Villenave
2008/6/9 Michael Pozhidaev <[EMAIL PROTECTED]>: > Hello, everybody! Greetings, and welcome on the list! > There is one thing I cannot understand . In many examples > notes are not written in "\new Staff" block directly, > but placed in something like > upper = \relative c'' { >

Place to write piano dynamics

2008-06-08 Thread Michael Pozhidaev
Hello, everybody! It is my first posting to this list. I am blind programmer from Russia and music takes a very important part in my life. Lilypond is just brilliant software for me. Now I can make my own music publications by myself. Great thanks to everybody, who made it possible! There is o