Quoting Myron Marston [EMAIL PROTECTED]:
Isn't there a midi-to-lily converter? I figure that must have an algorithm
like this...
Yes, midi2ly does include such an algorithm and this is one of the
main reasons that midi2ly isn't as useful as it otherwise might be. Of
course, an added
2008/6/4 Jonathan Kulp [EMAIL PROTECTED]:
Well, since no one is going to answer this I guess I'll answer it myself:
RTFM (the Learning Manual, that is) :D
I have encountered similar problems with dynamics colliding with
cross-staff barlines, but I never really found a way to get rid of
this
In what format are the templates? I mean could they be easily converted
to LilyPondTool's Velocity templates?
Wilbert Berendsen wrote:
Hi all,
LilyKDE 0.6.0beta has been released. This is a beta release, featuring a
powerful new score wizard (ctrl+shift+n). In three tabs, it allows you to
Hi evverybody,
are there plans to make a debian-package of this tool?
I don't like installing from source, I tried it several times, but without
success!
___
lilypond-user mailing list
lilypond-user@gnu.org
Op woensdag 4 juni 2008, schreef Stefan Thomas:
Hi evverybody,
are there plans to make a debian-package of this tool?
I don't like installing from source, I tried it several times, but without
success!
Unfortunately I don't know how to create debian packages.
What problems do you encounter?
2008/6/4 Wilbert Berendsen [EMAIL PROTECTED]:
Unfortunately I don't know how to create debian packages.
What problems do you encounter? You should install KDE, sip, PyKDE and PyQt
from recent distro packages. Pate might need to be compiled from source.
Silly question:
any plans for KDE 4.1?
How about the following example of how to get an ossia stave for
alternative versions of the music.
The method described in the manual is somewhat clumsy since you have to
count the number of
bars to know what \skip commands to insert between each ossia. Here, you
can enter the two
versions of
Well, it's not very elegant but it works o.k. I just override the
dynamics positioning each time I need it. I just experimented to find
the right values. To make life easier I define the override as a variable:
nuj = \once \override DynamicText #'extra-offset = #'(+1.0 . -0.0)
Then I just
Op woensdag 4 juni 2008, schreef Valentin Villenave:
2008/6/4 Wilbert Berendsen [EMAIL PROTECTED]:
Unfortunately I don't know how to create debian packages.
What problems do you encounter? You should install KDE, sip, PyKDE and
PyQt from recent distro packages. Pate might need to be
Hey 'Ponders!
1. Can anyone explain the odd behaviour of the attached snippet? In
the output I get, the absence of the \set subdivideBeams... line in
the second example results in the music being in two different Staff
(as opposed to Voice) contexts!!
2. I discovered this issue while
Op woensdag 4 juni 2008, schreef Bertalan Fodor (LilyPondTool):
In what format are the templates? I mean could they be easily converted
to LilyPondTool's Velocity templates?
The templates (or part types) are currently just a class hierarchy in Python
code, living in lilykde/parts.py[1] As this
Am 04.06.2008 um 13:42 schrieb Jonathan Kulp:
Well, it's not very elegant but it works o.k. I just override the
dynamics positioning each time I need it. I just experimented to
find the right values. To make life easier I define the override as
a variable:
nuj = \once \override
This is a known problem that has not made it into the bug tracker, as
far as I can see.
See http://lists.gnu.org/archive/html/lilypond-devel/2007-04/msg00136.html
Also, as you can see later in the same thread, it doesn't help to add
the bar engraver
to the context. Here comes a somewhat
I'm trying some things and I expected a flat symbol on the bottom line
but got nothing.
{
\override Staff.Clef #'stencil = #ly:text-interface::print
\override Staff.Clef #'text = \markup \musicglyph #clefs.C
\override Staff.KeySignature #'stencil = #ly:text-interface::print
\override
Here's a minimal example that produces the collision for me. In the
meantime, any way to move that clef around which will force more space
at the end of that line? Is the end-of-line clef change clef symbol
referenced differently than just Clef?
\version 2.11.37
bottom = \relative c {
15 matches
Mail list logo
