Multitrack settings

A multitrack is Faircamp's generic abstraction for anything that can contain multiple tracks: An album, a podcast, a playlist, etc.

A multitrack is an entity with its own page, and all tracks inside it are their own entities with their own page too, and both notably have different settings.

To implicitly create a multitrack, create a directory that contains multiple audio files – it will automatically be considered a multitrack. Additionally or alternatively create a (plain text) file called multitrack.eno inside this directory to make the multitrack explicit – if a directory contains only a single audio file it is implicitly considered a track otherwise.

Note that if you want to release a single, stand-alone track you don't need to wrap it into a multitrack, you can just use a track of its own.

An example multitrack.eno file:

title: Ape Affairs (Bonus Track Edition)
permalink: ape-affairs-bonus-track-edition
released: 2019-11-03

artists:
- Heston Exchange

download_formats:
- flac
- mp3
- opus

m3u: disabled
more_label: Liner Notes
track.numbering: arabic-dotted

cover: cover.jpg
cover_description: An ink drawing of a barren tree with monkeys in its branches

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

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

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

theme.dark:
accent_brightening = 85
accent_chroma = 50
accent_hue = 23
base = light
base_chroma = 34
base_hue = 180

The remainder of this page alphabetically lists all available settings for multitracks.

artists

Default-able Use the prefixed form multitrack.artists outside of multitrack manifests

If your audio files are not tagged, or the tags contain inaccurate values, or for any other reason, you can use the artists option to explicitly set one or multiple artists for this multitrack release. Note that this does not set the artists on the tracks themselves (for this use the track.artists setting) but rather the "album artists", so to speak.

To set a single artist for a multitrack release:

artists:
- Alice

To set multiple artist for a multitrack release:

artists:
- Alice
- Bob

copy_link

Default-able Use the prefixed form multitrack.copy_link outside of multitrack manifests

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

cover

Local-only This multitrack setting can not inherit default values from other manifests

cover: cover.jpg

Provide the path of the image, relative from the manifest's location (i.e. if the image is in the same directory as the manifest, provide just the filename).

Note that multitrack cover images are always displayed in square aspect ratio. If you supply a non-square image it will be square-cropped for display.

Note that if there are multiple images in the multitrack directory and you don't explicitly choose which of them is the cover in your manifest, faircamp will use a simple heuristic to choose which of them it picks as the cover: "cover.jpg" before "front.jpg" before "album.jpg", and after that it will pick randomly. Note that it can also be ".png" or another format, only the filename before the extension is considered. Case is disregarded as well, so it can also be "Cover.jpg", for instance.

cover_description

Local-only This multitrack setting can not inherit default values from other manifests

-- cover_description
Alice with her guitar collection
-- cover_description

If you use a cover image, make sure to include a cover_description so that visually impaired people can also make sense of it (this description is used as the alt text for the image).

You can either provide a multiline or inline value according to your preference and required length for the description. A multiline example:

-- cover_description
A photograph separated into two planes:
In the foreground, an old lady, smiling into the camera.
In the background, an unrecognizable mechanical contraption.
-- cover_description

An inline example:

cover_description: A photograph of a cat, tiptoeing over modular synthesizer panels

download_access

Default-able Use the prefixed form multitrack.download_access outside of multitrack manifests

By default your visitors can only stream your releases.

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

Beyond this, the 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:

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 release(s) can be downloaded or purchased, external downloads allow you to reconfigure the download button so that it displays one or multiple links that take people to external pages.

For example, to point people to the external page https://example.com/artist/purchase/ when they click the download button, first set the download_access setting to external:

download_access: external

Then additionally use the download_links setting to specify the download link:

download_links:
- 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:

download_access: code

In combination with this use the download_codes 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:

download_access: paycurtain

In combination with this option, use the 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):

download_access: disabled

download_codes

Default-able Use the prefixed form multitrack.download_codes outside of multitrack manifests

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

download_codes:
- 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 download_access option (e.g. 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.

download_formats

Default-able Use the prefixed form multitrack.download_formats outside of multitrack manifests

Sets the formats in which an entire multitrack release can be downloaded as a (zip) archive. By default none are specified, so this needs to be set in order to enable downloads for multitrack releases at all.

To set a single download format:

download_formats:
- flac

To set multiple download formats:

download_formats:
- flac
- mp3
- opus

To offer downloads in their original format and quality (without transcoding, exactly as you provided the audio, but potentially with tag remapping):

download_formats:
- original

To disable all download formats:

download_formats: none

All currently available formats:

• aac
• aiff
• alac
• flac
• mp3
• ogg_vorbis
• opus_48
• opus_96
• opus_128
• original
• wav

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 but compressed format (e.g. flac) is recommended.

download_links

Default-able Use the prefixed form multitrack.download_links outside of multitrack manifests

download_links:
- Platform A https://example.com/release/download/
- Platform B https://...
- https://...

You can supply any number of links to allow your listeners to download the release from other sites. Links can only be full urls (e.g. "https://example.com").

For each link you can supply either just the bare link (e.g. - https://..., or (more commonly) add a label for the link, which can be put before or after the link itself (- Example Label https://... or - https://... Example Label).

Note that you also need to use the download_access option to actually enable download links, for instance:

download_access: external

download_links:
- https://example.com/release/download/
- https://...

embedding

Default-able Use the prefixed form multitrack.embedding outside of multitrack manifests

This allows external sites to embed a widget that lets people play back the multitrack release from your site. The embed code can be copied from a page that is linked to on the multitrack page.

Embedding is disabled by default. If you want to enable it you also need to set the site's site.base_url setting (embeds work by displaying something from your site on another site, for this the other site needs to point to your site's address).

embedding: enabled

external_page

Local-only This multitrack setting can not inherit default values from other manifests

external_page: https://example.com

With this option set, the multitrack is linked to an external page wherever it appears on the faircamp site. The multitrack page itself is not generated in that case, or rather: It becomes a redirect to the external page.

extra_downloads

Default-able Use the prefixed form multitrack.extra_downloads outside of multitrack manifests

Any additional files in a multitrack directory besides the audio files, cover image and multitrack.eno manifest (e.g. artwork, liner notes, lyrics, etc.) are considered "extras" and by default bundled in the zip archives for multitrack downloads (if downloads are configured/enabled) as well as being provided for separate download (bundled+separate option).

To turn this off and entirely disable multitrack extras:

extra_downloads: disabled

To provide multitrack extras as bundled downloads only:

extra_downloads: bundled

To provide multitrack extras as separate downloads only:

extra_downloads: separate

To restore the default behavior:

extra_downloads: bundled+separate

extras_label

Default-able Use the prefixed form multitrack.extras_label outside of multitrack manifests

If you provide additional files for download with a multitrack release (e.g. sheet music or liner notes as a PDF), those will, by default, be labelled as "Extras", both on the site, as well as potentially as a folder name in downloadable zip archives of your release.

The extras_label setting allows you to customize the wording for this for your usecase (e.g. "Goodies", "Liner Notes", "Bonus material", etc.).

extras_label: Bonus content

feeds

Default-able Use the prefixed form multitrack.feeds outside of multitrack manifests

Heads up: You need to set site.base_url so that faircamp can generate feeds.

By default faircamp provides two feeds that your visitors can subscribe to: An Atom feed and a plain RSS feed (RSS 2.0 without media or podcast extensions), both of which are simple "blog-like" (purely text and image based) feeds that provide updates linking to your new releases so that people can listen to new material on your site only (this is the textual feeds setting).

If you are publishing a podcast, set the feeds option to either podcast (to provide only a single, Podcast RSS based feed), to media (to provide only a Media RSS and Podcast RSS feed) or to all (to provide all textual and media feed types), for instance:

feeds: podcast

If you want to disable all feeds you can use this option:

feeds: disabled

If you need a very specific feed configuration, you can also use the discrete atom, media_rss, plain_rss and podcast_rss options in a list. For instance to provide only an atom feed:

feeds:
- atom

Or, to provide only plain RSS and Podcast RSS feeds:

feeds:
- plain_rss
- podcast_rss

homepage

Local-only This multitrack setting can not inherit default values from other manifests

homepage

Makes this multitrack release page the homepage of your site. There is only one homepage, so this setting can only be used in one place at a time.

links

Local-only This multitrack setting can not inherit default values from other manifests

links:
- Album review https://example.com/some-blog/some-review/
- Another review https://example.com/another-blog/another-review/
- Production credits #credits
- https://example.com/something/else/

You can supply any number of links, these are prominently displayed in the header/landing area of your multitrack page. Links can be full urls (e.g. "https://example.com") or references to anchors within the page (e.g. "#about").

For each link you can supply either just the bare link (e.g. - https://example.com, or (more commonly) add a label for the link, which can be put before or after the link itself (- Example Label https://example.com or - https://example.com Example Label).

m3u

Default-able Use the prefixed form multitrack.m3u outside of multitrack manifests

This controls the generation of an M3U playlist for the release (provided on the release page) - it is disabled by default.

To enable the M3U playlist for a release:

m3u: enabled

To disable the M3U playlist for a release:

m3u: disabled

more

Local-only This multitrack setting can not inherit default values from other manifests

-- 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 release page with: Liner notes, production staff credits, lyrics, making of stories, etc. When provided, this content appears right after the tracks on the release page.

The more field supports Markdown.

more_label

Default-able Use the prefixed form multitrack.more_label outside of multitrack manifests

more_label: Liner Notes

If you provide long-form content for your release (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 release page, leading to the section containing that content. 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 release: "Details", "Liner Notes", "Staff", "Lyrics", "About" etc.

order

Default-able Use the prefixed form multitrack.order outside of multitrack manifests

order: released_asc

Specifies how the tracks in a multitrack release are ordered.

Tracks in a multitrack release use auto ordering by default, which analyzes the available metadata and interacts with the presentation setting:

• If most of the tracks have a track number, tracks are sorted by track number
• If most of the tracks have a release date, tracks are sorted by release date
• If most of the tracks have both a track and release date, the one with more complete coverage is used, with track numbers being preferred in case of a tie
• If neither track numbers nor release dates are provided on most tracks, sorting uses the source path of the tracks, that is, the audio file name or the relative path of the audio file within the multitrack directory (depending if you use track directories and/or further directory nesting for your tracks)
• Lastly, with album presentation, tracks are sorted in ascending order (e.g. #1, #2, #3), while podcast presentation uses descending order (e.g. Dec 2001, Jul 2000, Jan 1999)

Supported values:

• auto (Default, see description above)
• file_name_asc – File Name Ascending (a.mp3, b.mp3, c.mp3)
• file_name_desc – File Name Descending (c.mp3, b.mp3, a.mp3)
• published_asc – Publication Date/Time Ascending (Jan, Feb, Mar)
• published_desc – Publication Date/Time Descending (Mar, Feb, Jan)
• released_asc – Release Date Ascending (1999, 2000, 2001)
• released_desc – Release Date Descending (2001, 2000, 1999)
• source_path_asc – Source Path Ascending (dir_a/xx.mp3, dir_b/xx.mp3, dir_c/xx.mp3)
• source_path_desc – Source Path Descending (dir_c/xx.mp3, dir_b/xx.mp3, dir_a/xx.mp3)
• title_asc – Title Ascending (A, B, C)
• title_desc – Title Descending (C, B, A)
• track_number_asc – Track Number Ascending (#1, #2, #3)
• track_number_desc – Track Number Descending (#3, #2, #1)
• updated_asc – Update Date/Time Ascending (Mon, Tue, Wed)
• updated_desc – Update Date/Time Descending (Wed, Tue, Mon)

payment_info

Default-able Use the prefixed form multitrack.payment_info outside of multitrack manifests

This is used together with the paycurtain setting of the download_access and/or track.download_access options (e.g. 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

permalink

Local-only This multitrack setting can not inherit default values from other manifests

permalink: example-album

The permalink is a short, unique text fragment (for instance: example-album) that forms a part of the permanent address of a multitrack page. For an online faircamp site, the permalink is appended to the site.base_url to construct the full address of the page.

For instance: https://example.com (the site.base_url) + example-album (the permalink) = https://example.com/example-album – this is the link that you can share with your visitors to point them to the multitrack page.

Permalinks may only contain the following characters:

• a-z (lowercase letters only)
• 0-9
• - (dash)

If you don't specify your own permalink, faircamp auto-generates one from the title (for instance the title Example Album becomes the permalink example-album then). Note that in this case when the title changes, the permalink does too. This can lead to other people's bookmarks or links to your site becoming invalidated. Therefore it's generally recommended to specify your own permalinks – at least for the most important things on your site.

If you set/enable either external_page or homepage for your multitrack, the permalink is still relevant: The page address (part of which is the permalink) then becomes a redirect to either the external page or the homepage. Furthermore, the permalink is always part of the address of your RSS feeds, M3U playlists, etc. – even if your multitrack page is set as the homepage.

platform_integration

Default-able Use the prefixed form multitrack.platform_integration outside of multitrack manifests

Facebook's Open Graph metadata (and other adjacent protocols) are used by platforms to crawl and harvest content from (linked) websites in order to present them using a uniform "card" design pattern inside social feeds and timelines.

By default, faircamp only renders metadata that is used to generate link previews whenever someone links to things on your faircamp site. This can be disabled with:

platform_integration: disabled

Open Graph properties that get rendered (when link previews are enabled) are the mandatory og:title, og:image (including alt, height and width), og:type (always as website) and og:url properties, as well as og:locale and og:site_name. Where present, the synopsis field is rendered as the og:description property additionally.

In the near future faircamp will also gain support for rendering content embeds, that is, metadata and embed code that allows platforms to directly integrate a media player for your audio material in user timelines. You can already configure this with the setting below, but until it's implemented this will act identically to the link_previews setting.

platform_integration: content_embeds

The factory setting (in case you need to reset your own inherited default) can be set with:

platform_integration: link_previews

podcast.categories

Default-able Use the prefixed form multitrack.podcast.categories outside of multitrack manifests

podcast.categories:
- History
- Arts > Design

Use this to set podcast categories for this multitrack feed. You can either set a top level category only, or separate top-level and subcategory with a greater-than sign (>), for example Arts > Design for the top-level category Arts and subcategory Design.

podcast.explicit

Default-able Use the prefixed form multitrack.podcast.explicit outside of multitrack manifests

podcast.explicit: yes

Set this to yes if the podcast feed for this multitrack release contains explicit language or adult content.

presentation

Default-able Use the prefixed form multitrack.presentation outside of multitrack manifests

presentation: podcast

This allows you to choose between the default album and alternative podcast presentation for a multitrack page.

Album presentation features your tracks as a compact track list, generally ordered by their track number, similar to other music or streaming sites.

presentation: album

Podcast presentation features your tracks in a spacious timeline, generally ordered by release date (going from newest to oldest), with synopsis texts and release dates being displayed with each track, similar to other podcast sites.

presentation: podcast

price

Default-able Use the prefixed form multitrack.price outside of multitrack manifests

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

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

price: EUR 4+

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

• USD 0+ (Name your price, including zero dollars as a valid option)
• 3.50 GBP (Exactly 3.50 Pounds)
• KRW 9080 (Exactly 9080 south korean won)
• INR 230+ (230 indian rupees or more)
• JPY 400-800 (Between 400 and 800 japanese yen)

published

Local-only This multitrack setting can not inherit default values from other manifests

published: 2024-12-19T16:39:57-08:00

A date/time specifying when this multitrack release was first published on the faircamp site. This will be primarily used in your Atom/RSS feeds as metadata for feed consumers.

Also see these related settings:

• released – Date when this multitrack release was first released anywhere.
• updated – Date/time when this multitrack release was last updated on the faircamp site.

released

Local-only This multitrack setting can not inherit default values from other manifests

released: 1999-12-31

A date specifying when this multitrack release was released on the faircamp site or anywhere else. This date can be used for sorting and can also be shown on the site as information for listeners.

The date must be supplied strictly in the format YYYY-MM-DD.

Also see these related settings:

• published – Date/time when this multitrack release was first published on the faircamp site.
• updated – Date/time when this multitrack release was last updated on the faircamp site.

synopsis

Local-only This multitrack setting can not inherit default values from other manifests

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

A short (256 characters max), plaintext introduction text for your release, this is prominently featured atop your release page.

theme.cover_generator

Default-able Use the prefixed form multitrack.theme.cover_generator outside of multitrack manifests

theme.cover_generator: space_time_rupture_light

Faircamp generates procedural cover images for all releases for which you do not provide your own cover image. With this setting you can choose from a set of algorithms. Note that procedural covers will probably undergo bigger changes in the future – this is still open and ongoing experimentation.

Available cover generators:

• best_rillen_dark
• best_rillen_light
• blocks_dark
• blocks_light
• glass_splinters_dark
• glass_splinters_light
• lovely_tunes_dark (default)
• lovely_tunes_light
• scratchy_faint_rillen_dark
• scratchy_faint_rillen_light
• space_time_rupture_dark
• space_time_rupture_light

theme.dark

Default-able Use the prefixed form multitrack.theme.dark outside of multitrack manifests

theme.dark:
accent_brightening = 85
accent_chroma = 50
accent_hue = 23
base_chroma = 34
base_hue = 180
background_alpha = 23
background_image = simple_texture.jpg

Adjusts the colors and/or background image of the dark theme. Note that theme.mode needs to be either adaptive or dark for this to have any effect, otherwise the dark theme is never displayed.

Tip: With the --theming-widget CLI option you can interactively explore the theme.dark and theme.light theme settings. Build your site with this option enabled and every page will contain the theming widget (don't forget to turn it off before deployment).

Dynamic range

theme.dark:
dynamic_range = 24

At the highest dynamic_range (100%) the dark theme is darkest and the least colorful (depending on chroma settings, see below). The lower the dynamic_range (0% being the default) the more it will have a differentiated dark grey feeling and become more colorfully tinted with rising base_chroma levels.

Tip: By interatively exploring different values with the --theming-widget option you can get a good feeling of what this does and how you want to set it.

Base and accent colors

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

The theme is initially monochromatic (without color).

With base_chroma (0-100 (%)) you control the colorfulness of the theme, while the base_hue (0-360 (degrees)) setting sets the shade of the color.

Some elements on the page are accentuated (prominent buttons and the "timeline" of the audio player). The colorfulness of the accentuation is 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.dark:
background_alpha = 23
background_image = simple_texture.jpg

The previously described theme.dark 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.

theme.font

Default-able Use the prefixed form multitrack.theme.font outside of multitrack manifests

By default, faircamp bundles and uses the Barlow font on a generated site, but alternatively you can also configure your site to only use your visitors' system font(s):

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

theme.font: system-sans

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

theme.font: system-serif

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

theme.font: system-mono

To reset to faircamp's bundled default font:

theme.font: bundled-default

Usage of custom fonts entails complexities and responsibilities that faircamp can not generically automate away, therefore this requires manual integration through the site.assets and site.metadata options - this also gives a great amount of flexibility, including the possibility to use multiple fonts and tweak their integration down to the last detail where needed.

theme.light

Default-able Use the prefixed form multitrack.theme.light outside of multitrack manifests

theme.light:
accent_brightening = 85
accent_chroma = 50
accent_hue = 23
base_chroma = 34
base_hue = 180
background_alpha = 23
background_image = simple_texture.jpg

Adjusts the colors and/or background image of the light theme. Note that theme.mode needs to be either adaptive or light for this to have any effect, otherwise the light theme is never displayed.

Tip: With the --theming-widget CLI option you can interactively explore the theme.dark and theme.light theme settings. Build your site with this option enabled and every page will contain the theming widget (don't forget to turn it off before deployment).

Dynamic range

theme.light:
dynamic_range = 24

At the highest dynamic_range (100%) the light theme is the most bright and the least colorful (depending on chroma settings, see below). The lower the dynamic_range (0% being the default) the more it will have a differentiated light grey feeling and become more colorfully tinted with rising base_chroma levels.

Tip: By interatively exploring different values with the --theming-widget option you can get a good feeling of what this does and how you want to set it.

Base and accent colors

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

The theme is initially monochromatic (without color).

With base_chroma (0-100 (%)) you control the colorfulness of the theme, while the base_hue (0-360 (degrees)) setting sets the shade of the color.

Some elements on the page are accentuated (prominent buttons and the "timeline" of the audio player). The colorfulness of the accentuation is 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.light:
background_alpha = 23
background_image = simple_texture.jpg

The previously described theme.light 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.

theme.mode

Default-able Use the prefixed form multitrack.theme.mode outside of multitrack manifests

theme.mode: light

This controls the overall theme appearance – dark, light or adaptive.

The default setting is adaptive, which means that a dark or light theme will be displayed automatically, based on browser/system preferences of each site visitor.

With dark and light you can instead opt for a fixed dark or light appearance for all visitors.

theme.round_corners

Default-able Use the prefixed form multitrack.theme.round_corners outside of multitrack manifests

To give a softer feel to your page, set the round_corners option to enabled, this will add a round corner to your cover images:

theme.round_corners: enabled

By setting it to disabled you can restore the default behavior:

theme.round_corners: enabled

theme.waveforms

Default-able Use the prefixed form multitrack.theme.waveforms outside of multitrack manifests

By default, the width of each track's waveform on a multitrack 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

You can also disable waveforms altogether, resulting in a more compact layout:

theme.waveforms: disabled

With relative you can restore the default waveform behavior:

theme.waveforms: relative

title

Local-only This multitrack setting can not inherit default values from other manifests

The release title is automatically derived from the audio file metadata (album tags) on the tracks, however you can also override it with this option.

title: Ape Affairs (Bonus Track Edition)

unlock_info

Default-able Use the prefixed form multitrack.unlock_info outside of multitrack manifests

In combination with the code setting of the download_access and/or track.download.access options (e.g. download_access: code) and download_codes 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

updated

Local-only This multitrack setting can not inherit default values from other manifests

updated: 2024-12-19T16:39:57-08:00

A date/time specifying when this multitrack release was last updated on the faircamp site. This will be primarily used in your Atom/RSS feeds as metadata for feed consumers.

Also see these related settings:

• published – Date/time when this multitrack release was first published on the faircamp site.
• released – Date when this multitrack release was first released anywhere.

visibility

Default-able Use the prefixed form multitrack.visibility outside of multitrack manifests

visibility: featured

Controls the visibility level of this multitrack (default: featured).

Available options:

• featured (default) – The multitrack is openly accessible, listed everywhere and included in the browse/search navigation
• public – The multitrack is openly accessible, listed everywhere, but excluded from the browse/search navigation
• unlisted – The multitrack is not publicly listed anywhere, visitors need to know and directly enter the URL to get to its page. Tracks within a multitrack release automatically inherit this: If the multitrack is unlisted, its tracks are only accessible through the multitrack page or by directly entering their page address (which requires knowing it). You can also explicitly unlist a track that is inside a multitrack, but that removes it from the track list and download archives, which is a different form of unlisting.
• offline – The multitrack is entirely omitted when generating the site and does not appear anywhere on it