Lamy Jean-Baptiste wrote:
> - default string tuning is now at the right octavo
Eh, no, you transposed the wrong direction, now it is TWO octaves off.
The high e-string should end up between the two upper note-lines when
notated in the "G_8"-clef.
-Rune
__
Dear list, sorry to be nagging you once again.
:-(
I know that I have been flooding this list with my own problems lately.
But this time is the most serious problem I have ever had.
My music studies are about to be over, and on thursday morning (yikes!)
I have to hand in a written musical assign
The concert went well.
I talked to the composer and he agreed to include the score in lilypond
as long as his name was maintained and as long as he kept the copyrights
- that is people are not allowed to make changes to the score.
I think including CLA(O)P II is a Good Thing because it stress t
> I have a tiny annoyance in the emacs mode which usually makes revert
> to the command line: when I have lily-tex-xdvi'd a file, I usually
> make some edits to the .ly file. When I press C-c C-c I would expect
> the emacs mode to detect the edits, and suggest that I run LilyPond
> again. Curren
[EMAIL PROTECTED] writes:
> Hi !
>
> This patch (intended to be applied to the CVS) fix the following bugs :
>
> - stringTunings property is now declared
> - Accidental are now totally removed (before, there were just transparent,
> but it seems it can cause crash)
> - default string tuning i
Hi !
This patch (intended to be applied to the CVS) fix the following bugs :
- stringTunings property is now declared
- Accidental are now totally removed (before, there were just transparent,
but it seems it can cause crash)
- default string tuning is now at the right octavo
- up-to-staff S
[EMAIL PROTECTED] writes:
> Rune> Because you just before the \repeat-statement has a \bar statement
> Rune> which in effect overrides the repeat bar.
>
> Rune> Just remove the \bar "|" before the repeat-command.
>
> Yes, but is that really what's supposed to happen? I would think t
