Split a track into separate instrument stems, optionally retimed and rekeyed.

Use for a full song or mix when the user wants vocals, drums, bass or an instrumental on their own. For tempo and key alone use analyze; for sections use segment. Takes a few minutes and counts as one run. Stems go to a new results folder; the source is unchanged.

Analyze a track: BPM, key, loudness and other characteristics.

Use this first whenever the user asks for tempo, key or loudness. It is the fastest tool (seconds), does not count as a run, and changes nothing. The answer is in metadata and the same data is saved to the results folder.

Find song sections, tempo and bars (about half a minute).

Use for song structure. Send the mix: no stems needed, and it counts as one run. The result has the sections (with their phrases) and a tempo map. Beats and bars are not listed one by one: grid describes them -- where each constant-tempo piece starts, its BPM, and its bar and beat. Every beat time is start + k * 60 / bpm, and most tracks have one piece. The analysis_id it returns adds audio_features, tag_audio, get_lyrics or generate_samples to this analysis without another run. For tempo and key alone, analyze is quicker.

Measure energy, danceability, loudness, mode, key and tatum, for the song and each section.

Give the analysis_id from segment: nothing is uploaded and it is included in that analysis's run. A file_path runs segment first (one run). Needs no stems, so it can run straight after segment. Energy and danceability run 0-1: energy reflects loudness, rhythmic activity and low end; danceability, how strong and regular the beat is. Both are measured per section, so a drop reads higher than its breakdown. Loudness is in LUFS. The values are in metadata (song, sections) and saved to the results folder.

Tag a track: genre, moods, instruments and artist tags for the mix and each part, plus a written description.

Give the analysis_id from segment: nothing is uploaded and it is included in that analysis's run. A file_path runs segment first (one run). Tags read the track's stems, which Audial makes automatically after each analysis: right after a new analysis this waits for them (a few minutes). The tags are in metadata (genre, song_tags, description) and saved to the results folder.

Transcribe a track's lyrics as timed lines.

Give the analysis_id from segment: nothing is uploaded and it is included in that analysis's run. A file_path runs segment first (one run). Lyrics read the vocal stem, which Audial makes automatically after each analysis: right after a new analysis this waits for it (a few minutes). metadata.lines has one {start, end, text} per line in seconds on the track's timeline, lyrics the whole text and section_lyrics one entry per section. Word timings are in the saved lyrics.json. An instrumental comes back with is_instrumental true.

Master a mix, optionally matching a reference track.

Use for a finished stereo mix, not for separate stems. Pass a reference track when the user names one. Takes a few minutes and counts as one run. The master goes to a new results folder; the source is unchanged.

Extract a sample pack (one-shots and loops) from a track.

Use when the user wants drum hits or loops taken from a finished track. With the analysis_id from segment, the pack is built from that analysis's sections and the stems Audial made for it: nothing is uploaded and it is included in the analysis's run (right after a new analysis it waits a few minutes for the stems). With file_path it runs the sample-pack pipeline: prepares the track (analysis and stems together), then builds the pack; one call, counted as one run, each step reported as it starts and finishes. If that call times out the job keeps running: pipeline_status finds it. Samples go to a new results folder.

Transcribe an audio file to MIDI.

Use to get notes out of audio. On a full mix, run stem_split first and transcribe the stem you want. Counts as one run. MIDI files go to a new results folder; the source is unchanged.

Generate music with the Audial music model.

Text to music, covers, remixes, lego (re-render with one track emphasised), or analysis (understand). Use for new or transformed music, not to edit an existing mix: that is master or stem_split. Takes a few minutes and counts as one run, and audio goes to a new results folder.

Turn one isolated sound into an editable Audial Synth preset.

Not for loops or melodies, which give a poor preset. If the result's summary says the match is weak, tell the user and suggest trimming the input to one note.

Turn one isolated sound into an editable Xfer Serum 2 preset.

Not for loops or melodies, which give a poor preset. If the result's summary says the match is weak, tell the user and suggest trimming the input to one note.

Synthesize a sung vocal (and MIDI) from lyrics, a melody and a reference voice.

Needs both a reference clip of the voice and a melody, as MIDI or audio. lyrics_mode decides how the lyrics are lined up with the melody's notes; "per_note" is the one that gives exact control. See the lyrics_mode and lyrics descriptions. Takes a few minutes and counts as one run. Audio and MIDI go to a new results folder.

Which Audial tools have a worker awake right now, and what a cold one will cost.

Audial's GPU workers scale to zero. A tool reported warm: false will spend expectedColdStartMs starting a worker before it does any work -- a few minutes, once -- on top of the job's own expectedRunMs. Worth checking before starting a long job, and worth telling the user about with the notice text when something is cold: otherwise the wait looks like a hang. Nothing here starts a job or costs anything.

Look up an Audial pipeline by id: its state, each step, and the outputs so far.

Useful when a generate_samples call on a file, or a segment call with features, timed out: the pipeline keeps running on Audial's side and this says how far it got.

List previous Audial results in the results folder, newest first.

Use when the user asks where an earlier output went. Reads the local folder only: no account needed and nothing is sent anywhere.

Show whether this computer is signed in to Audial, and as whom.

Use when a tool reports a credentials problem or the user asks which account is in use. Reads local settings only.

Sign in to Audial through the user's browser. Opens an approval page and waits for it.

Not needed before other tools: they start the same sign-in when nobody is signed in.

Sign out of Audial on this computer and disconnect it from the account.

Only when the user asks to sign out or switch accounts. The next job asks them to sign in again. Results already downloaded stay where they are.