On 12/15/12 at 11:14am, Felix Janda wrote:
On 12/11/12 at 09:31pm, Federico Bruni wrote:
- The mutopiacomposer header field needs to be fixed for old scores
You mean it must be equal to the directory?
composer = GalileiV
Yes. You can/should also check with datafiles/composers.dat
Hi,
just some thoughts on the current header parsing of Mutopia's software
motivated by (not wanting to install java and) the thought that lilypond's
language is so complex that parsing it should be left to lilypond itself.
I noticed that lilypond has (since at least version 2.8.0) a --header
On 01/07/13 at 05:24pm, Glen Larsen wrote:
Very cool, David.
Felix, I knew you'd want something like this made out of that:
Simple python wrapper for this scheme code https://gist.github.com/4480245
Yeah, I think it still needs some processing. IMO, The header fields should be
checked for
On 01/09/13 at 10:54am, David Kastrup wrote:
Felix Janda felix.ja...@posteo.de
writes:
Do you have a (rough) estimate for what's the earliest lilypond
version which works with this command line?
Huh. Several functions are only available with
commit
Use
\relative c' {
{ c2 } \\ \\ { e2 } \\ \\ { g2 }
}
By default the odd numbered voices have their stems up and the even numbered
voices have their stems down. They are shifted more and more as the number
increases. In the example I'm only using voices 1, 3 and 5 so that all beams
go up.
git reset --hard should be able to fix up your master. Then make
new topic branches and git-cherry-pick your work into them. Then make
new pull-requests and close the old ones. (Can you really not do this
yourself? If not you could still add a comment to the pull-request.)
Felix