Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AlkanCV Op26 Marche Funebre #1104

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

thomasmorgan
Copy link
Contributor

@thomasmorgan thomasmorgan commented Mar 1, 2021

This is the sheet music for C-V Alkan's Marche Funebre, Op.26. It is based on F. Lucca's (~1847) source. However, I made a few edits as this was for my own pleasure that I list here for clarity:

  1. I halved the tempo and all note durations for a better fit with the mood of the piece.
  2. I changed key signature as appropriate whereas the source resolutely sticks with a single key signature despite clear and extended changes.
  3. To reduce the number of pages and generally improve layout, for some measures I make use of a single stave for both hands. I find this perfectly easy to read (and superior to the source), but I concede it is not conventional.

Beyond this it is broadly fastidious in adhering to the source.

As a note, I wrote this using my own python library. I have put the url as the maintainer, but if this is not acceptable, please use my name (Thomas Morgan).

Edit to add: Because this was written first in python and then compiled by a machine into lilypond it fails to meet best practices. If you want I can include the python code, which is more nicely formatted. I may also be able to tweak the python library to better approximate best practices in its output. I don't really fancy manually editing the lilypond code to bring it in to line though!

Thanks,
Tom

@thomasmorgan
Copy link
Contributor Author

I've updated the lilypond code. It is now much more in line with the original (only deviations are occasional uses of ottava markings which are absent in the source) and follows better mutopia practices. I have kept my more experimental (but in my opinion much easier to read) lilypond file separate - would it be possible to upload this also?

@thomasmorgan
Copy link
Contributor Author

I've fixed a final few issues I spotted.

I've also uploaded an alternative ly file that describes the same music, but I put my edits in there. If you are not interested in such a personal take on the typesetting feel free to delete it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants