Skip to content

pianomanfrazier/lilypond-in-markdown-v2

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
css
 
 
img
 
 
js
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

LilyPond in Markdown Version 2

The reason for version 2 is to cleanup tracking git dependencies. In order for netlify to build the project I commited the cached audio and svg files. This was cluttering up the git repo and unnecessary. The plan going forward is to not use netlify but something else like a direct deploy of the build to AWS or surge.sh.

Initial Motivation

My previous way of blogging about music was too tedious. This is a proof of concept to show that LilyPond markup can be rendered to inline SVG for the web.

I wrote a blog post about what I did in version 1 here.

External Dependencies

  • LilyPond
  • Timidity
  • ffmpeg

TODO: Make a docker container with all dependencies to build the site.

In order to build the project the LilyPond extension assumes that lilypond is available in your path. So you must first install LilyPond.

In order to produce audio from the generated midi from LilyPond you will need timidity. ffmpeg is used to generate various audio formats for browser support from the timidity output (flac).

About

Improved version of 11ty markdown prefilter to render LilyPond in markdown

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published