Faircamp 1.2 Faircamp ☰

Track manifests – track.eno

All options at a glance: copy_link, download_code(s), embedding, link, more, more_label, payment_info, streaming_quality, synopsis, tags, theme, track_artist(s), track_download_access, track_downloads, track_extras, track_price, unlock_info

Track manifests are an optional way to specify metadata and settings at the track level. A track.eno manifest must be placed inside a track directory. To set up a track directory simply take the audio file of the respective track and put it into its own directory (the naming of that directory is entirely up to you, it does not affect anything). That is then your track directory, where you also put the track.eno manifest in. For example:

Example EP/               <--- Release directory
├─ cover.jpg                 <--- Release cover image
├─ release.eno               <--- Release manifest
├─ 01 First Track/           <--- Track directory
│  ├─ cover.jpg                 <--- Track cover image
│  ├─ track.eno                 <--- Track manifest
│  └─ 01 First Track.mp3        <--- Track audio file
├─ 02 Second Track.mp3       <--- Track audio file
└─ 03 Third Track.mp3        <--- Track audio file

As you can see, in a track directory you can also put an image file to be used as cover for that track - this is picked up automatically! Additionally, extra files in a track directory will be treated as track extras, by default separately downloadable from the track's download page.

For all the things that can be customized in a track.eno manifest, see the options documented below (and the "at a glance" overview at the top of the page).

copy_link

To disable the "Copy link" button (by default it's enabled) you can use the copy_link option, with either enabled or disabled as value.

copy_link: disabled

download_code(s)

To set a single download code that can be entered to access downloads:

download_code: crowdfunding2023

To set multiple download codes that can be entered to access downloads:

download_codes:
- GOLDsupporter
- SILVERsupporter

Note that you also need to use the track_download_access option (track_download_access: code) to activate download codes. In addition it is highly recommended to use the unlock_info option to provide a text that is displayed alongside the code input prompt.

embedding

This allows external sites to embed a widget that lets people play back the track from your site. The embed code can be copied from a page that is linked from each release or track page where embedding is enabled.

Embedding is disabled by default. If you want to enable it you also need to set the catalog's base_url (embeds work by displaying something from your site on another site, for this the other site needs to point to your site's address), and then set embedding: enabled, either in a catalog, artist, release or track manifest. If you set it enabled at the catalog level, you can also use disabled at lower level to re-disable it for specific releases.

embedding: enabled

link

link: https://example.com/this/track/elsewhere/

link:
url = https://example.com/this/track/elsewhere/

link:
label = A review for this track
url = https://example.com/some-blog/some-review/

You can supply any number of link fields, these are prominently displayed in the header/landing area of your track page. A link must at least provide a url, either as a simple value or as an url attribute. Optionally you can also supply a label which is what is visibly displayed instead of the url, when given.

more

-- more
Recorded in the summer of '94 at West Callaghan Ranch, XE.

Featuring Ted Tukowsky on Trombone and Lisa Merringfield on Theremin.
-- more

This field lets you provide long-form content of any kind to augment the track page with: Liner notes, production staff credits, lyrics, making of stories, etc. When provided, this content appears right after the track player/waveform on the track page.

The more field supports Markdown.

more_label

more_label: Lyrics

If you provide long-form content for your track (which can be anything you want, content-wise) through the more field, by default there will be a link with the label "More" on your track page, leading to the section containing that content. This link and label will also appear right by the track where it appears on the release page. If you want to customize that label so it specifically refers to the type of content you are providing there, the more_label field allows you to do that. Some typical examples of custom labels one might use in the context of a track: "Lyrics", "Details", "Liner Notes", "About" etc.

payment_info

This is used together with the paycurtain setting of the track_download_access option (track_download_access: paycurtain) to set the text that is displayed before downloads are accessed.

The general idea here is to provide external links to one or more payment, donation or patronage platforms that you use, be it liberapay, ko-fi, paypal, stripe, etc. You can use Markdown to place links, bullet points, etc. in the text.

-- payment_info
Most easily you can transfer the money for your purchase
via my [liberapay account](https://liberapay.com/somewhatsynthwave)

Another option is supporting me through my [ko-fi page](https://ko-fi.com/satanclaus92)

If you're in europe you can send the money via SEPA, contact me at
[lila@thatawesomeartist42.com](mailto:lila@thatawesomeartist42.com) and I'll
send you the account details.

On Dec 19th I'm playing a show at *Substage Indenhoven* - you can get the
digital album now and meet me at the merch stand in december in person to give
me the money yourself as well, make sure to make a note of it though! :)
-- payment_info

streaming_quality

streaming_quality: frugal

You can set the encoding quality for streaming from standard (the default) to frugal. This uses considerably less bandwidth, reduces emissions and improves load times for listeners, especially on slow connections.

synopsis

-- synopsis
Nobody thought it possible, until somebody did it. The track that started it all!
-- synopsis

A short (256 characters max), plain-text introduction text for your track, this is prominently featured atop your track page.

tags

By default faircamp strips all metadata off the audio files that you supply when it transcodes them for streaming and downloading, only adding back those tags that it needs and manages itself, i.e. the title, track number, artist (s), release artist(s) and release title. The tags option lets you control this behavior:

Set it to copy and faircamp will transfer all tags 1:1 from the source file onto the transcoded files, as you provided them.

tags: copy

Set it to remove and faircamp will produce entirely untagged files for streaming and download.

tags: remove

In order to assert fine-grained control over tags, you can also specify precise behavior per tag. The available tags at this point are album, album_artist, artist, image, title and track (= track number). The available actions for each tag are copy (copy 1:1 from the source audio files) and rewrite (set it from whichever information you implicitly or explicitly gave faircamp that would override the original tag, or fall back to the original tag value if there is no override). There is also remove, but as any tag you don't explicitly provide in this form is implicitly set to be removed, this is redundant. Note that support for writing embedded cover images differs wildly between target formats, at this point pretty much only the flac and mp3 formats can be expected to reliably contain them, no matter what you specify for image.

A random example of this:

tags:
album = rewrite
album_artist = remove
artist = rewrite
image = copy
title = copy
track = copy

The default behavior can be explicitly (re-)applied with the normalize option.

tags: normalize

When written out explicitly using the fine-grained notation, the default behavior (that is, tags: normalize) corresponds to the following settings:

tags:
album = rewrite
album_artist = rewrite
artist = rewrite
image = remove
title = rewrite
track = rewrite

theme

With this you can adjust the visual appearance of your faircamp site.

Theme customizations can be made in a top-level manifest at the root of the catalog (setting the theme for the homepage and all release pages), but they can also be made locally for a group of releases or for each release on its own.

Tip: There is a --theming-widget CLI option that lets you interactively explore color-related theme settings. Just build your catalog with the option enabled and every page will then contain the theming widget (don't forget to turn it off before deployment).

Base

theme:
base = light

This sets the overall appearance, choose between dark (the default) and light.

Dynamic range

theme:
dynamic_range = 24

At the highest dynamic range (100%) the theme appears the most "black" or "white" (depending on your theme base) and the least colorful (depending on your chroma settings, see below). The lower the dynamic range (0% being the default) the more it will have a differentiated gray feeling (again interacting with your theme base), and become over-all more colorfully tinted with rising base chroma levels. Tip: By trying different values with the --theming-widget option you can interactively get a good feeling of what this does and how you want to set it.

Detail color adjustments

theme:
accent_brightening = 85
accent_chroma = 50
accent_hue = 23
base_chroma = 34
base_hue = 180

A site's theme is initially monochromatic (without color).

With base_chroma (0-100 (%)) you can control the overall "colorfulness" of your site, while the base_hue (0-360 (degrees)) setting adjusts what base color the theme is built on.

Some elements on the page are accentuated (prominent buttons and the "timeline" of the audio player). The colorfulness of the accentuation can be customized with the accent_chroma (0-100 (%)) setting, while the accent_hue (0-360 (degrees)) setting adjusts its shade. The accent_brightening (0-100 (%)) setting allows you to brighten or darken this color accent (it's at 50% by default), which allows for stronger and deeper colors still.

Background image

theme:
background_alpha = 23
background_image = squiggly_monsters_texture.jpg

The previously described settings can be handled carefree - no matter the settings, your site will stay readable (at worst it may look funny). When you set a background image however, choose carefully what image you use and how opaque you make it. Sharp details and strong contrasts within the image and against the text of the site will render the site hard to read or even unreadable. That said, background_image lets you reference the image to use, and with background_alpha (0-100 (%)) you can optionally control its opaqueness.

Round corners on release covers

To give a softer feel to your page, set the round_corners option to enabled. This will visually round off the corners of covers on all pages. By setting it back to disabled (the default) you can disable it for specific releases again.

theme:
round_corners = enabled

Disabling relative waveform lengths

By default, the width of each track's waveform on a release page will render at a different length, reflecting the duration of the track in relation to the longest track on the release - for instance if the longest track on a release is about two minutes long, that one will span the full width, but another track that is only about one minute long will span only half of that width. If you publish releases whose tracks have wildly varying lengths, shorter tracks might get very narrow in the interface. If this is a concern to you, or you just generally want all tracks to be full-width as an aesthetic choice, you can enable this alternative behavior with this setting:

theme:
waveforms = absolute

Disabling waveforms altogether

This will not display waveforms on the release page, resulting in a more compact layout.

theme:
waveforms = disabled

With waveforms = enabled you can turn this back on for specific releases if you want.

Font

By default, faircamp bundles and uses the Barlow font on a generated site, but this can be configured.

Using the standard sans serif font from the system of the visitor:

theme:
system_font = sans

Using the standard monospace font from the system of the visitor:

theme:
system_font = mono

Using a specific font (by font name) from the system of the visitor (this should have a rather specific reason, normally you probably don't want to do that):

theme:
system_font = Arial

Bundling and using a custom font (put a .woff or .woff2 file in the same directory as the manifest - other font file types are not supported!):

theme:
custom_font = MyCustomSans.woff2

track_artist(s)

If your audio file is not tagged, or the tags contain inaccurate values, or for any other reason, you can use the track_artist and track_artists option to explicitly set one or multiple main artists for the track. Note that this can implicitly affect the release artist (which can be explicitly set with the release_artist(s) option in the release.eno manifest too).

To set a single artist for tracks on a release:

track_artist: Alice

To set a multiple artist for tracks on a release:

track_artists:
- Alice
- Bob

track_download_access

By default your visitors can only stream your tracks.

To enable free downloads of a track all you need to do is set one or more download formats with the track_downloads option.

Beyond this, the track_download_access option controls how visitors can access downloads - by default as free downloads - but this can be changed to external downloads, downloads accessible through download codes, or downloads placed behind a soft paycurtain, and you can also disable access to downloads here.

Free downloads

This is the default (you don't need to set it yourself), but in case you want to re-enable it in a manifest:

track_download_access: free

External downloads

If you want to use your faircamp site purely to let people stream your audio, but there is another place on the web where your track(s) can be downloaded, external downloads allow you to display a download button that merely takes people to the external download page.

For example, to display a download button that takes people to https://example.com/artist/purchase/, simply use that url as the value for this setting:

track_download_access: https://example.com/artist/purchase/

Download code(s)

A download code (like a coupon/token) needs to be entered to access downloads.

To protect downloads with a code:

track_download_access: code

In combination with this use the download_code(s) option to set the codes for accessing downloads and the payment_info option to provide a text that is displayed with the code input field (to give your audience directions on how to obtain a download code).

Soft Paycurtain

A soft (i.e. not technically enforced) paycurtain needs to be passed before downloading.

To provide downloads behind a soft paycurtain:

track_download_access: paycurtain

In combination with this option, use the track_price and payment_info options to set a price and give instructions for where the payment can be made.

Disable downloads

Downloads can also be disabled explicitly (e.g. if you quickly want to take them offline at some point):

track_download_access: disabled

track_downloads

Sets the formats in which single tracks can be separately downloaded. By default none are specified, so this needs to be set in order to enable separate downloads for single tracks.

To set a single download format:

track_downloads: flac

To set multiple download formats:

track_downloads:
- flac
- mp3
- opus

All currently available formats:

In practice a minimal combination of a lossy state of the art format (e.g. opus), a lossy format with high compatibility (e.g. mp3) and a lossless format (e.g. flac) is recommended.

track_extras

Any additional files in a track directory besides the audio file, cover image and track.eno manifest are considered "extras" and by default offered as separate downloads on the track download page (think artwork, liner notes, lyrics, etc.).

To turn this off and entirely omit track extras:

track_extras: disabled

To provide track extras as separate downloads (default behavior):

track_extras: enabled

Release downloads (zip archives) that include a track will also include the extras of that track if track_extras is enabled for the track and the release_extras option for the release is (or includes) bundled.

track_price

This is used together with the paycurtain setting of the track_download_access option (track_download_access: paycurtain) to set the price for track downloads that is displayed before the downloads are accessed.

For example in order to ask for 4€ for accessing the downloads of a track:

price: EUR 4+

The price option accepts an ISO 4217 currency code and a price range such as:

unlock_info

In combination with the code setting of the track_download_access option (track_download_access: code) and download_code(s) option, this option lets you set the text that is displayed to your visitors when they are prompted for a download code. Usually you will want to put instructions in the text that tell your visitors how they can obtain a download code.

-- unlock_info
You should have received a download code in your confirmation mail
for this year's crowdfunding. Stay tuned in case you missed it,
we're currently planning the next run!
-- unlock_info