tymbalodeon / scores

Library of LilyPond music score files, with a development environment for editing scores and generating output files.

Scores

Library of LilyPond music score files, with a development environment for editing scores and generating output files.

Installation

Nix

The recommended way to install the build and development dependencies is with Nix. On non-NixOS systems, use the Determinate Systems Nix Installer.

Once Nix is installed, use nix develop to download the dependencies and activate the development shell, or, preferably, install direnv (for example, using these dotfiles) to automatically activate the environment when cd-ing into the project directory. Assuming you installed direnv, as well as just, and nushell (which will be installed when running nix develop), a automatic development environment can be created by running:

just init

Manual

If not using Nix, install the following dependencies via your preferred method. More information about each dependency can be found by clicking the "Homepage" link on each page listed below.

• fd-10.1.0
• gh-2.52.0
• gyre-fonts-2.005
• just-1.29.1
• lilypond-2.25.17
• lychee-0.15.1
• nushell-0.95.0
• pre-commit-3.7.1
• python3.12-pre-commit-hooks-4.6.0
• ripgrep-14.1.0
• tokei-12.1.2
• watchexec-2.1.1
• zathura-with-plugins-0.5.6
• zellij-0.40.1

Recommended extra dependencies

For PDF viewing (macOS only):

• Skim

Development

Development commands are provided through just. Run just to see available "recipes," and just <recipe> --help/-h to get more information about a particular recipe.

Available recipes:
(run `just <recipe> --help/-h` for more info)
    check *hooks             # Run pre-commit hooks
    clean *search_term       # Remove pdfs
    compile *search_term     # Compile pdfs
    create *args             # Create new score
    deps *args               # List dependencies
    edit *args               # Open <score> in  and pdf viewer, recompiling on file changes
    find-recipe *search_term # Search available `just` recipes
    history *search_term     # Search project history
    info *search_term        # Get info about scores
    init *help               # Initialize direnv environment
    issue *args              # View issues
    open *search_term        # Open pdfs
    remote *web              # View remote repository
    settings *args           # View project settings
    stats *help              # View repository analytics
    templates *args          # View available templates
    update *help             # Update dependencies and score LilyPond version
    view-source *recipe      # View the source code for a recipe

scores's Issues

rhizome

• Make phrase markings stay above the harmonics (e.g., measure 5)
• Make phrase markings stay above tuplet (e.g., measure 9)
• Make accent stay close to grace note (e.g., measure 11)
• Should the ties always stay on the same side of the note? (e.g., measure 9)
• Should the glissando point down even when the notehead doesn't change? (e.g., measure 19)
• Fix tuplet position (measure 34)

update piano template

Should the piano template use a separate file for upper and lower staves, which seems to be helpful for big scores?

Should it remove the instrument name, which is often omitted in real scores? Or is it better to include with the idea that it's easier to delete something unneeded than to add it in if you can't remember how to do it...

just status improvements

• Is it possible to choose sorting options for just status? For example, sort by Artist (what it does now by default), sort by title, and sort by status?
• Should it also display which output files it uses? Like whether it includes a "-form" or "-video" pdf in addition to the main one?
• What should be done with just list? Is this still necessary? Should just status replace it?

prefer just commands to zsh

String and path commands from just might be more readable than zsh:
https://github.com/casey/just#string-manipulation

Prefer these when available?

branches for scores

Should the just create command create a new branch for each score? and just edit switches to it?

Should there be other just commands for working with git?

make just list show all scores

Currently just list shows only pdfs. Maybe it should show all scores in the repo? It can show all titles in title case and whether there is a pdf or it's outdated.

add makefile for lilypond workflow

Read about Makefiles in LilyPond here and make appropriate updates for my workflow.

Improve Makefile help function

For reference/inspiration: ludicrous makefiles

Ideas:

• Put long commands (awk) into separate files that are included
• Multiline comments?

allow creation of multiple output files

For some charts, it make sense to have a more detailed transcription of the complete melody with cue parts showing important aspects of the arrangement, but at the same time have a simpler form chart that just shows the sections with chords and number of bars.

This can be done using "\book" blocks in LilyPond.

See: https://lilypond.org/doc/v2.23/Documentation/notation/output-file-names

make sure update command updates templates

^title.

Plus: is it possible to only have update run if the version is out of date?

add lyrics to templates

• Include lyrics in charts/lead
• add --lyrics option to just create command

Add create command

For example:
make create type=chart artist=beatles name=eleanor-rigby would create charts/beatles/eleanor-rigby directory and eleanor-rigby.ly, eleanor-rigby-melody.ily, and eleanor-rigyb-chords.ily inside of that. It would also include the version number and basic setup inside the lilypond files.

establish system for separating out cue parts

• Use a cue.ily file (or backing.ily).
• Find a way to compile with or without cues without having to comment anything out
• Figure out musically what kind of notation makes sense
• If using extra staff, figure out how to put chords below the ossia staff

score directory structure

Should scores still be separated into "charts," "scores," "transcriptions," and "arrangements"? Maybe it's better to have things be flatter and more consistent. For example, all scores go in scores//<title>, where is either the composer or the band or the soloist for a transcription (the entity one is most likely to think of as the identifier for the score). A transcription of a solo over a standard goes under the soloist's name, but a chart for the tune goes under the composer's name, etc...

add option to create chart with chords only

just create chart will output two pdfs by default. Provide an option to choose 1) melody chart only, 2) chord chart only or 3) both

write function to pass articulations and flip direction

add video-slides settings

Figure out the best way to compile a version in letter size and a version in youtube video size. Can this be done with \book? Should they be different output file names?

replace loop in justfile

Instead of looping through the glob and calling watchexec, just choose the first file found in the glob and call watchexec on that, since it doesn't really make sense to do so in a loop.

See: https://unix.stackexchange.com/questions/156205/how-can-i-get-the-first-match-from-wildcard-expansion

just compile search for scores

since you can call just status <composer> to display the scores matching that composer/artist, should you be able to call just compile <composer> and have all the matching scores compiled?