[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
LilyPond Enhancement Proposal (with Bounty)
From: |
Paul Tannous |
Subject: |
LilyPond Enhancement Proposal (with Bounty) |
Date: |
Mon, 29 Sep 2014 03:00:01 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
LilyPonders:
We are part of a startup company that wants to put LilyPond-generated
musical scores on tablets. We believe this will allow users to have
beautiful, readable scores on tablets and spread the usage of LilyPond to a
wider audience. We have completed the first version of an Android
application that does this. It dynamically repaginates the music score to
fill the tablet screen, and it supports written annotation.
We have a series of programs that run on a Mac or PC to generate the scores
to be rendered on tablets of different screen sizes. A tablet-format score
of our own design is built from LilyPond-generated score images so a tablet
page of any size or orientation can be built dynamically, using note sizes
that will be readable. If you’ve seen PDF scores reduced and displayed on
tablets, you’ll understand why we think we have a better approach.
Creating our tablet-format scores to support dynamic repagination means we
have to take steps to avoid having text directly above and below each of
the measure bars. We add measure bars back when rendering each line and
vary the bar widths in addition to adding space to fill out the lines. So
any text (tempo, dynamics, pedal instructions, etc.) spanning measures
would be split, pixels lost, and unwanted spacing added. We avoid this now
by writing the LilyPond source to avoid text above or below the measure
bars. However, this can be painstaking and time-consuming work.
We would therefore like to see an option added to LilyPond, that could be
set before processing, that would avoid placing text above or below measure
bars.
We believe there must be code already in the engravers to avoid splitting
text over measures at line ends. So, we are hoping our proposed enhancement
would be an extension of that code.
We would be willing to pay a bounty to have this feature added if no one
else is interested in this functionality, but we have no idea of how much
effort would be required. We would like to have some feedback on how long
this would take and what someone who could do it would charge for the
effort.
- LilyPond Enhancement Proposal (with Bounty),
Paul Tannous <=