Track requests

What it is

Track requests let you publish a public brief. A remix contest, a "send me your demos" call, a sample pack request, and collect submissions into your team's demo inbox. Each request has its own public link you can share anywhere.

You can ask submitters to fill in specific details (track info, composer, publishing), require them to follow you on social platforms before they can submit, and share files (like stems for a remix) for them to download.

The checklist

A brief can carry a checklist: the things somebody has to do before the brief counts as done. Add the items when you create the request and mark the ones that are not optional. Anybody opening the link sees the list before they decide to take it on, and works through it inside the form: items tied to a part of the submission (adding the audio, filling in the composer or the publishing details, linking a playlist) tick themselves as that part gets filled in, so nobody confirms the same work twice. The rest they tick by hand.

Required items keep the submit button disabled until they are done, and the button says what is still missing rather than just refusing. When the submission lands, your demo inbox shows how many items were checked off, so a half-finished brief is visible without opening it.

This is what replaces a shared folder and a message thread for a class or a program: one link, the requirements attached to it, and the work coming back into one inbox.

Submitters can upload their audio file directly (MP3, WAV, … up to 200 MB) or paste a link (SoundCloud, Dropbox, Drive, …): uploaded files play inline in your demo inbox like any other submission.

Uploaded files are also saved to the submitter's own Aden library as a new track (private, with the audio as version 1), so their remix immediately lives in their workspace like any other track.

If the submitter's remix already lives on Aden as a track, they can pick it when submitting instead: either way the submission automatically requests a remix link to the original track. Accepting the submission approves the link, so the remix shows up as a linked track on both track pages (rejecting the submission rejects the link request). Approved entries on the public remixes page link to the remixer's track with an "Official remix" badge.

Remix contests on the track page

When a request is linked to a track, it becomes a remix contest with its own public page at /@team/track/{track}/remixes: fans see the brief, deadline and downloadable stems, and submit their remix right there. The public track page shows a "Remix contest open" card linking to it. Optionally enable public entries to list the submitted remixes on that page so anyone can listen to them (rejected entries stay hidden).

Using it

1. Open Track requests for your team and click New request.
2. Give it a title. The public URL tag is derived from the title.
3. Write a brief describing what you're looking for.
4. Optionally link a track (for remix contests, submissions attach to it).
5. Optionally pitch at a playlist: turn the request into a playlist submission channel (see the Playlist submissions feature) and, if you like, ask submitters for a link to their own playlist.
6. Set a max submissions per person.
7. Optionally add social follow gate links. Submitters must open every linked platform before the submission form unlocks.
8. Optionally pick files to share from the linked track (e.g. stems). When you share files you must confirm you hold the rights to distribute them.
9. Use Advanced settings to choose which fields submitters must provide.
10. Click Create, then share the request's public link.

Submitters open the link, follow your socials (if required), download any shared files, fill in the form, and submit. You get notified and the demo lands in your inbox.