StitchAbleUser Manual · v1.0
Get StitchAble →
macOS · Ableton Live 11 & 12

StitchAble User Manual

Your finished songs → one gapless, show-ready setlist. Everything the app does, and why.

Section 01

What StitchAble is

StitchAble takes the finished Ableton Live songs you already have and stitches them into one gapless, show-ready setlist — running order, per-song transpose, tempo and meter changes, guide, click, and return routing all reconciled for you. Open the result in Live and run your set.

It doesn't write songs and it doesn't play them. It's the step in between: the hour you'd otherwise spend rebuilding a tempo map by hand on a Saturday night.

It builds the set — Live plays it. StitchAble is a preparation tool. It writes a finished Ableton Live session that you open and run in Ableton. It never modifies your original songs.

The two-app pair

StitchAble is the stitching half of a pair that shares one engine and one sound library:

StitchAble

Stitches finished songs into one setlist.

MultiConvert 12

Converts unconverted MultiTracks.com downloads into clean Live 12 song projects.

You don't strictly need MultiConvert 12 — StitchAble converts MultiTracks downloads on the fly at build time. But if you're building a library from scratch, MultiConvert 12 is the companion that makes the songs StitchAble stitches. A guide voice or click sound you set up in one app shows up in the other, because both read the same shared library.

Who it's for

Worship musicians, music directors, and playback operators running Ableton Live on stage. You should know Ableton basics — tracks, groups, returns, outputs — and nothing more technical than that.

Section 02

Install & activate

Three steps, once per Mac: install the app, activate your key, install the shared sound library. After that StitchAble runs offline.

Before you start

  • macOS 14.6 (Sonoma) or newer — Apple Silicon or Intel.
  • Ableton Live 11 or 12 to open the finished setlist. Suite is recommended; Standard works.
  • A song library folder — one folder whose immediate sub-folders are your songs (Section 04).
  • The MultiTracks Click and Guide Samples pack — free from MultiTracks.com. Download it before you install (Section 10).
  • Optional: a multi-output audio interface, if you want click, guide, and returns on separate physical outputs (Section 12).

Get the pack first. Technically StitchAble runs without it — every song can fall back to its own audio click and guide. But the pack is what makes the MIDI click and guide work: one unified click you can voice and pitch, and spoken cues on a single lane across the whole set. It's free, and it's the source of most of what you'll want from Section 10. Download it before you go on.

1 · Install

Open StitchAble-1.0.dmg, drag StitchAble into Applications, and launch it from there.

No security warning. The app and the disk image are Developer-ID signed, notarized by Apple, and stapled — so StitchAble opens on a normal double-click, on any Mac, even with no internet connection.

2 · Activate

On first launch, paste the license key from your purchase receipt. Activation is a one-time online check — after it succeeds, StitchAble never needs the internet again.

  • You do this once per Mac.
  • One license covers 5 activations — your studio Mac, your stage Mac, the spare.
  • Out of seats, reinstalling, or moving to a new machine? Email support from the address on the activation screen and a seat gets freed. Details in Section 16.

3 · Install the sound library

Open Settings (the gear, bottom-right) and press Setup. StitchAble finds a downloaded Click and Guide Samples pack — it checks Downloads, Desktop, Documents, and Music — and installs the guide voices and click sounds into your Ableton User Library. The button turns green once it's in.

One library, both apps

The guide and click sounds live in your Ableton User Library, shared with MultiConvert 12. Set a voice or a click sound up in either app and it shows up in the other. You install it once.

If you skip this, StitchAble still builds sets — every song just falls back to its own audio click and guide, and the MIDI click and guide sources in Section 10 have nothing to play. Run Setup.

Section 03

The main window

Two panes and one button do most of the work. Songs live on the left, the set you're building lives on the right, and Create Set turns the right-hand pane into an Ableton session.

The numbers on the screenshot below match the four headings on this page.

1 2 3 4

1Header

Three folder chips and a Scan button. Each chip shows the folder it's pointed at and has its own Browse button.

  • SONGS — the folder your songs live in. Everything in the Library pane comes from here.
  • OUTPUT — where finished sets get saved.
  • TEMPLATE — optional. A Live project whose AbleSet folder is carried into project builds. The small clears it.
  • Scan — re-reads the songs folder. Disabled until you've chosen one.

2Library

Every song in your folder, with a live count in the header ("78 songs", or "12 of 78" while a filter is on). Under the search field is the Compatibility box — tick Key or BPM to filter (Section 05). Each row's + adds that song to the set; you can also drag it across.

3Running order

Name the set at the top. Each row shows its position, the song, and the transpose stepper ( / value / +); the removes it. Transpose a song and its subtitle picks up the new key in gold — Fmaj → Gbmaj. Between rows, StitchAble tells you what happens at the seam: a + 1 bar gap, or a meter change → 6/8 when the next song's time signature differs (Section 06).

4Bottom bar

The status line sits just above it — what the last build did, and whether an AbleSet folder was carried over.

  • Save draft / Load draft — store a running order, transposes and all, and rebuild it another day (Section 06).
  • Ableton Live 12 — the version picker. Target Live 11 or Live 12 (Section 13).
  • Project folder — build a self-contained … Project/ instead of a loose .als.
  • Create Set — builds the merged session (Section 07).
  • Gear — Click & Guide settings and output routing (Sections 10 and 12).

Version badges

Every song row — in the Library and in the running order — carries a colored badge before its name, plus pills for key, BPM, and time signature. The badge tells you what the source song actually is:

11

A native Ableton Live 11 song.

12

A native Ableton Live 12 song.

MT

An unconverted MultiTracks.com download — converted to a clean Live project at build time (Section 14).

Section 04

Your song library

Direct StitchAble to one folder whose immediate sub-folders are songs. It reads the title, artist, key, BPM, and meter straight off the folder names — so a scan is instant, and your library is just a folder you already have.

Nothing gets renamed. StitchAble reads your folder names as they are and never writes to your source songs. It only writes a new merged set, where you told it to.

How to name a song folder

StitchAble reads two conventions, and a library can mix them freely. Name your songs the authored way — it's the only one that carries the artist and the time signature, and it's what the app is built around. The MultiTracks form is there so a download works untouched.

AUTHORED RECOMMENDED Alleluia - Elevation Worship | Bmaj | 125 BPM | 4/4 Title Artist Key BPM Meter MULTITRACKS WASHED-WASHED-B-139.00bpm Title Key BPM

Title and artist split on the first dash; key, BPM, and meter are the pipe segments. BPM parsing is forgiving (125bpm and 125 BPM both read), and a meter can be written 6/8 or 6:8.

A MultiTracks folder carries no meter, so StitchAble reads it from the .als at build time instead — which is why an MT song still shows a time signature in the running order even though its folder name never mentioned one.

Songs that modulate

Write the key as Abmaj-Amaj and StitchAble treats the song as modulating. The start key drives key matching and transposing; the end key is carried through and shown so you know where the song lands.

Inside a song folder

A song folder usually holds a … Project/ with the .als in it, plus _MultiTracks/, Album.jpg, an AbleSet folder, and whatever else you keep. StitchAble finds the right .als on its own: it looks up to three levels deep, prefers the one inside a Project folder whose name matches the song, takes the newest if there's more than one, and ignores backup, AbleSet, and Ableton Project Info folders.

Added songs to the folder since you opened the app? Press Scan in the header.

Section 05

Finding songs

Search finds a song you already have in mind. The filters answer a harder question — what could I put here? — by showing you every song that fits the key or the tempo you're building around, and how far it would have to move to get there.

Search

The field at the top of the Library matches on title, artist, or key. Type bethel, alle, or Bmaj.

The Key filter

Tick Key in the Compatibility box, choose a target note, and set a tolerance in semitones. The Library reorganizes itself around that key:

Library 40 of 78 COMPATIBILITY tick Key or BPM to filter Key C ± 2 semis BPM 72 ± 5 BPM 12 O Praise the Name Hillsong Worship Cmaj 72 4/4 + 12 Trust In God Elevation Worship Cmaj 74 6/8 + …the rest of your in-key songs LOWER −1 12 Alleluia Bmaj 125 + −1 12 King of My Heart Bmaj 68 + −2 MT WASHED Bbmaj 139 + HIGHER +1 12 Firm Foundation Dbmaj 75 + +1 12 Same God Dbmaj 72 + +2 12 At The Altar Dmaj 85 +
  • Songs already in your key list first, in full — nothing to do to them.
  • ▼ LOWER and ▲ HIGHER sit side by side underneath: everything within your tolerance that sits below or above the target.
  • The chip on the left is the song's distance from your target — not the transpose. With a target of C, a song in Bmaj reads −1 because B sits a semitone below C. A song in Dbmaj reads +1 because Db sits a semitone above it.

Add it and it arrives in key. Tap + and StitchAble applies the transpose that closes the gap — the opposite of the chip. That Bmaj song reading −1 lands in the running order at +1, in C. You read the distance; StitchAble does the arithmetic. And you can still change it afterwards.

The BPM filter

Tick BPM, set a target and a ± window, and the Library shows only songs inside it. Both filters can run at once — key and tempo — which is how you find the one song that can follow the one you just placed.

While either filter is on, the Library header counts what survived it: 40 of 78.

Section 06

Building the running order

The right-hand pane is the set. Whatever it looks like here is what the finished Ableton session will look like — in order, in key, with the seams already worked out.

Putting songs in it

  • Add — press + on a Library row, or drag the row across.
  • Reorder — drag a row by its handle on the left.
  • Remove — the at the end of the row.
  • Name the set — the field at the top. This becomes the file name.

Transposing a song

Each row has a / + stepper, good for ±12 semitones. As you move it, the row's subtitle shows where the song ends up — Fmaj → Gbmaj. The merged set shifts that song's audio and its MIDI to match.

Some lanes never move. Click, guide, and anything tagged [noshift] are left at their original pitch, no matter what you transpose the song by. A spoken cue that says "chorus" should not come out a minor third up.

What happens between songs

StitchAble tells you what it's doing at every seam, right in the running order:

Alleluia 125 BPM · 4/4 1 bar gap At The Altar 85 BPM · 6/8 meter change → 6/8 tempo steps at the boundary
  • + 1 bar gap — a bar of breathing room, counted in the current meter. In 6/8 that's three beats, not four.
  • meter change → 6/8 — shown instead of the gap note when the next song's time signature differs. The set changes meter at the boundary; you don't set anything up.

The amber audio note

A row may show a small amber audio guide, audio click, or audio guide + click tag. That means the song has no MIDI guide or click lane for StitchAble to pull — normal for a MultiTracks download — so it will use its own audio for that instead. It's information, not an error (Section 10).

Drafts

Save draft stores the running order, every transpose, and the set name. Load draft brings it back. Build the Sunday set on Thursday, reopen it Sunday morning, swap one song, rebuild.

Before you build

  • Ableton Live 12 / Live 11 — which version the finished set targets (Section 13).
  • Project folder — build a self-contained … Project/ folder rather than a loose .als. If you set a TEMPLATE, its AbleSet folder comes along.

Section 07

Create Set

One button. Everything the running order promised gets written into a single Ableton session, and Finder opens on the result.

1 Convert MultiTracks downloads become clean Live projects. Native songs are left alone. 2 Merge Everything is laid onto the first song's timeline, each song shifted in after the last. 3 Reconcile Guide and click choices, return routing, outputs, and colors are applied across the set. 4 Transpose Each song is shifted by its semitones — audio and MIDI. Click and guide stay put. Write The finished .als — or Project folder — is saved where you chose, and revealed in Finder. Your source songs are read, never written to.

The Returns review opens first — if your set has more than one return. It's a checkpoint, not an extra step: you confirm where every return lands before anything is written (Section 08). A set with a single return builds straight through without stopping.

What lands in the merge

Some of this is worth knowing, because it's what makes the result a set rather than four songs in a row:

  • Header lanes union by name. Every song's SONG TITLE, CLICK, guide, section, and lyric lanes collapse into one lane each, running the length of the show — not one set of lanes per song.
  • Tempo and meter run end to end, with an explicit tempo step at every boundary, so the click is right the moment a song starts.
  • Each song gets a SONG TITLE marker and a SONG END locator, and its key label filled in — so you can see the shape of the set in the arrangement at a glance.
  • Anything hanging past a song's end is trimmed, so a long tail doesn't bleed into the next song.

Build time scales with the number of songs and whether any of them need converting. A MultiTracks song takes longer than a native one, because it's being rebuilt as it goes in.

Section 08

The Returns review

Four songs, each built by someone else, each with its own idea of what a return is. The Returns review is where those become your returns — named once, routed once, for the whole set. It opens automatically at Create Set whenever the set has more than one return.

Returns Route each song's return to a return. Each return sends to its own output. Defaults… Click Ext. Out 7 Guide Ext. Out 8 Alleluia TRACKS +G:TRACKS Route 24 tracks… ↗ DRUMS Route 6 tracks… ↗ Build My Life TRACKS +G:TRACKS Route 19 tracks… ↗ WASHED (empty · MultiTracks) A TRACKS +G:TRACKS Ext. 5/6 🗑 B DRUMS Ext. 7/8 🗑 + Add Return 4 song returns → 2 finals Cancel Build

Reading it

  • Left — each song's returns, under a collapsible header in that song's color. Under every return is a Route N tracks… link, which opens the focus board (Section 09).
  • Right — the returns the finished set will have. Each one has its Ableton A / B / C letter, an editable name, an output, and a delete button.
  • The wires run from a song's return to the final it feeds, colored by the destination — so one color traces every path into a given return.
  • Click and Guide get their outputs at the top (Section 12), and the footer counts the whole plan: 4 song returns → 2 finals.

What it does before you touch it

The default plan is usually the right one:

  • Returns match by name, ignoring case and spacing. Every song's TRACKS becomes one TRACKS. Every DRUMS becomes one DRUMS.
  • Empty and MultiTracks returns collapse into the shared TRACKS return, rather than cluttering the set with returns nothing feeds.
  • Outputs get assigned. A return already on a real hardware output keeps it. A return with nowhere real to go — one feeding Master, common in Live 11 songs — is given its own distinct output (1/2, then 3/4, then 5/6…) so returns never pile onto one.

The A / B / C letter isn't part of the name. Ableton adds it. StitchAble leaves it out, which is why you never end up with a return called "A A-TRACKS". The letter you see here is just showing you the position.

Section 08 · continued

Changing the plan

Everything in the review is editable. Nothing is written until you press Build.

  • Rename a final return — type the body of the name; the letter stays automatic.
  • Re-route a final return to any output, including outputs no song used. The full list comes from your channel count (Section 12).
  • Re-match — use a song return's menu to send it to a different final. You can merge returns that lived on different outputs in different songs; that's the whole point.
  • Add Return for a new bus, or remove one that nothing is feeding.
  • Defaults… throws away your edits and recomputes the clean by-name plan. It's the undo for this window.

It remembers

Your matching, renaming, and routing are saved per running order. Build the same songs again and the review comes back pre-filled with the plan you approved last time — so the second build of a set is a glance and a Build, not a re-do.

Defaults… ignores the saved plan, which is how you start over deliberately.

Finishing

Build writes the set. Cancel closes the review without building anything — your running order is untouched, and you can come back.

Why this window exists. Returns are the one thing a merged set can't guess at. Two songs can both have a return called TRACKS and mean different outputs; a Live 11 song can route a return to Master and mean nothing at all. Getting this wrong is what makes Live reset your routing — or refuse to open the file. So StitchAble shows you the plan and asks, once.

Section 09

Per-track routing

Under every song's return in the review is a Route N tracks… link. Click it and the view zooms into that song: the other songs fade back, the finals stay pinned, and you get every stem in the song, one row each.

‹ All returns Alleluia route each track TRACKS THE SONG'S RETURN FINAL Drums [noshift]Perc 1 [noshift]Loop [noshift]BanjoAG 1AG 2AG GroupEG 1EG 2BassOrganPianoSynth Group …and the rest of the song's stems TRACKS Ext. Out 5/6 A TRACKS 5/6 — — — a skipped track, sent straight to the final

How it reads

Left to right: the song's tracks → the return they ride → the final that return feeds. Indentation shows Ableton's group nesting, so an AG Group and its children read the way they do in Live.

  • By default every track follows its own return — the solid fan in the middle. You don't have to touch anything here; the focus board is for the exceptions.
  • Ride a different return — a track's menu can move it to any of the song's other returns.
  • Skip to a final — send a track straight past the returns to any final, or make a New return… for it on the spot. A skipped track draws a dashed wire that arcs over the return pill, so it stays readable in the fan.
  • Everything is colored by its destination, the same as the main review.

Why you'd bother. One stem in one song wants its own output — a click-adjacent loop that shouldn't hit the house, a cue track for the drummer, a pad you want on its own fader at FOH. Without this board, your only options are to route the whole song's return or to fix it by hand in Live after every build. This is the escape hatch, and it's remembered with the rest of the plan.

‹ All returns takes you back out to the full patchbay.

On [noshift] tracks

Stems tagged [noshift] — drums, percussion, loops — show up here and route like any other track. The tag only means StitchAble won't transpose them when the song is keyed up or down. It has nothing to do with where they go.

Section 10

Guide & Click

Open the gear, bottom-right. Everything in here persists between sets and is shared with MultiConvert 12 — set a voice or a click sound up in either app and it's there in the other.

Setup

Setup installs the shared guide and click pack into your Ableton User Library. It finds a downloaded Click and Guide Samples pack on its own — Downloads, Desktop, Documents, Music — copies it in, gives the guide cues their proper names, and builds a browsable drum rack. The button's check turns green once it's done. Run it once per Mac (Section 02).

Audio or MIDI — for click and guide, separately

Each has a green Audio | MIDI switch. This is the single most consequential choice in Settings, so it's worth being clear about what it does:

AUDIO MIDI AUDIO Each song keeps its own recorded click and guide audio. Whatever the download came with is what you hear. MIDI Every song's CLICK, +GUIDE and +LOOPGUIDE lanes collapse into one lane each, playing the sounds you chose.

MIDI is the better answer when your songs have MIDI guide and click lanes, because you get one click sound and one guide voice across a set built from a dozen different sources. Not every song does — a MultiTracks download, for one, ships with audio and nothing else. StitchAble tells you which songs those are with the amber note in the running order, and quietly lets them play their own audio (Section 06).

The click

On MIDI, each click pad — Accent, Quarter, Eighth, Sixteenth — gets its own sound, chosen from your installed click library, and its own pitch (−24 to +24 semitones). So you can build a click that cuts through a loud stage without being ugly, once, and have it for every set after that.

Show click folder opens the installed clicks in Finder.

Section 10 · continued

The guide

Here's the thing to understand, because everything else follows from it: the cues are already in your songs. StitchAble doesn't write them, move them, or invent them. It merges the guide lanes your songs already have and decides what those notes sound like.

FROM YOUR SONGS FROM YOU WHAT YOU HEAR +GUIDE note C1 note D1 note E1 note F1 The notes were already there. StitchAble just merged the lanes. DRUM RACK C1“three, two, one…” D1“verse” E1“chorus” F1“bridge” You choose the family, the cues, and which pad each one sits on. One voice, the whole set

What you're actually choosing

  • Family — the voice: English, Spanish, French, Portuguese, or one of your own. A chosen family stays entirely inside itself; cues never leak in from another language.
  • Cue Library… — browse and audition every cue in the family, including your own imports. Add Cue… brings in your own recordings — your voice, your wording.
  • Order Cues… → Reorder drum rack… — which pad each cue sits on. This is the part that matters most: your songs send notes, and the pad order decides which cue each note fires. Get it right once and every set after that is right.
  • Build Test Set — drops a set on your Desktop that fires every pad in turn, so you can hear the whole voice in ten seconds instead of guessing.
Pad order, and songs you've already built

New guide lanes use your current pad order. A song that was already converted keeps the layout it was built with — so reordering pads doesn't silently rewrite work you've already done.

The same is true of the click

The click notes come from the songs; you choose the sound and the pitch of each pad. StitchAble is picking the voice, not writing the part.

No MIDI, no unified lane. A MultiTracks download ships with a recorded click and a recorded guide and nothing else — there's no MIDI for StitchAble to merge, so that song uses its own audio and the running order flags it in amber. It doesn't break the set; that one song just speaks in its own voice.

Cues, count-ins, and section markers get created by MultiConvert 12, which is what turns a MultiTracks download into a song with real guide and click lanes. Convert it there, and StitchAble can fold it into the unified lanes like anything else. That's why the two apps share one sound library.

Section 11

Transpose method

Transposing a song means shifting its audio. There are two honest ways to do that, and they fail in different directions — so StitchAble lets you pick. Settings → Transpose → "Use an AUPitch plugin on every stem."

DEFAULT

Clip warp

The switch is off. Ableton's own clip pitch and warp engine does the shifting.

OPTIONAL

AUPitch plugin

The switch is on. An Apple AUPitch device goes on every transposed stem; the clips are left alone.

Sound Best available. It's Ableton's own engine. Good, but it can smear on dense full stems.
CPU & latency None added. Nothing is running in real time. A device per track — real CPU, and some latency.
If you change the song's tempo Pitch rides the warp engine, so warp has to stretch the audio to follow — and stems don't always take it well. Pitch is independent of the warp engine. Slow a song down and it holds.
Control in Live It's baked into the clips. One device per track you can tweak or bypass on the fly.
On someone else's Mac Opens anywhere. No plugins involved. Opens anywhere — AUPitch ships with macOS.

Which one

Leave it off. At the tempo a song was built at, clip warp sounds better and costs nothing.

Turn it on when you want to run a song slower or faster than it was recorded. That's the one case clip warp can't be trusted with. Ableton has to warp the stems to follow the new tempo, and multitrack stems don't always take it — the warp can go wrong badly enough that a song comes out audibly longer or shorter than it should be. AUPitch sidesteps the warp engine entirely, so the song plays at the tempo you asked for and keeps its key.

About the latency

AUPitch adds some. Live compensates by delaying everything else to match — which you'll feel if you're playing instruments out of the same computer. In that case, Bounce in Place on the transposed tracks: the audio is rendered with the shift baked in, the device comes off, and the delay goes with it. If the computer is only running tracks, the latency doesn't matter and it isn't worth the trouble.

Two things are true either way. MIDI tracks are always transposed by note — a pitch plugin only touches audio. And click, guide, and any [noshift] lane are never transposed at all, on either setting.

Why AUPitch, specifically

It ships with macOS. A set built with AUPitch opens correctly on any Mac you hand it to — the keyboard player's, the church's, the one you borrow at 9am on a Sunday. A third-party pitch plugin would sound better and would silently fail to load on a machine that doesn't have it.

Section 12

Output routing

Twelve songs from twelve sources have twelve ideas about signal flow. StitchAble imposes one, so that a merged set is predictable on any rig — yours, the church's, or the one you're walking into for the first time on a Friday.

STEMS Drums Bass Keys Vocals SONG GROUP organizational RETURNS A · TRACKS B · DRUMS OUTPUTS Ext. Out 1/2 Ext. Out 3/4 CLICK +GUIDE Ext. Out 3 Ext. Out 4 straight out — no group, no return, never transposed The same shape, every song, every set — so a merged set behaves the same on any rig.

The shape

  • Stems go to their song's group.
  • With one return, the group is the mix bus and sends to it.
  • With two or more returns, the group becomes organizational — a folder, not a bus. Every stem is set Sends-Only and sends to its own return. Stems that used to run through the group are sent to the song's first return, so nothing gets orphaned.
  • Each return goes to its own output, chosen in the Returns review (Section 08).
  • Click and guide go straight out — their own outputs, no group, no return. Both the audio lanes and the unified MIDI CLICK / +GUIDE / +LOOPGUIDE lanes.

Channel count

Settings → Output routing → Outputs: pick 8 / 16 / 32 / 64 / 128 — the number of hardware output channels on your interface. That single number drives every output menu in the app: stems, click, guide, and every return. On a big interface, every bus can have its own pair.

Outputs read as Main, Ext. Out 3/4 for a stereo pair, or Ext. Out 3 for a single mono channel.

Defaults

Channel count 16 · stems to Main · click to Ext. Out 3 · guide to Ext. Out 4. Set them once; they persist across every set you build.

Section 13

Live 11 vs Live 12

Set the target with the Live version picker in the bottom bar, before you press Create Set. It's asking one question: which version of Ableton is going to open this file?

It's about the destination, not the sources

Your library can mix Live 11 songs, Live 12 songs, and unconverted MultiTracks downloads freely — StitchAble reconciles them either way. The picker isn't describing what went in. It's deciding what comes out.

  • Live 12 — the default, and the right answer if you're running Live 12.
  • Live 11 — StitchAble strips the Live-12-only data that Live 11 would refuse, and writes the file in the form Live 11 opens cleanly.

Either way, everything else — returns, routing, guide and click, colors, the send lists — is written correctly for the version you chose. A Live 11 set isn't a downgraded Live 12 set with its fingers crossed; it's written for Live 11.

Pick the version of Live you'll actually open it in. A Live 12 file will not open in Live 11 — that's Ableton's rule, not StitchAble's. If the machine at the venue runs 11, build for 11.

Section 14

MultiTracks songs

You can drop an unconverted MultiTracks.com download straight into your library and put it in a set. StitchAble converts it as it builds — you never open it in Live first.

Unzip it, and leave it alone

A MultiTracks download arrives as a zip. Unzip it into your songs folder and change nothing. What you get is a folder named for the song, and inside it the Ableton set and a MultiTracks folder of stems:

WASHED-WASHED-B-139.00bpmthe song folder MultiTrack.alsa Live 8 set MultiTracksthe stems

That shape is what StitchAble looks for: a Live 8 set next to a MultiTracks folder. Find it, and the song gets the gold MT badge and is converted at build time. Everything else — including anything MultiConvert 12 has already built — merges directly, like any other song.

What conversion does to it

  • Builds it as a clean Live project rather than upgrading the Live 8 file.
  • Groups the stems, colored by instrument family, in the track order the download had.
  • Routes the group to a single TRACKS return.
  • Sends its click and guide audio to your click and guide outputs (Section 12).
  • Reads the sections, tempo, and meter out of the Live 8 set, so the locators and the tempo map come across.
In the Returns review

A MultiTracks song shows up as one TRACKS return, which merges with everyone else's TRACKS. A song MultiConvert 12 finished behaves the same way — its leftover empty returns collapse into the shared TRACKS return instead of cluttering the set.

What it doesn't get

A MultiTracks download has a recorded click and a recorded guide and no MIDI, so it can't join the unified MIDI click and guide lanes — it plays its own audio, and the running order says so in amber (Section 10). If you want it in those lanes, convert it with MultiConvert 12 first; that's the app that builds the click, guide, and section cues a MultiTracks download never had.

Converting on the fly costs time at build. A set full of unconverted MultiTracks songs takes noticeably longer to build than a set of native Live songs, because each one is being rebuilt as it goes in. If you're going to play a song more than once, it's worth converting it properly and keeping it.

Section 15

What the finished set contains

Everything you already built. StitchAble doesn't recreate your songs — it carries them across as they are and consolidates them into one session that's organized enough to run a show from.

ALLELUIA ALWAYS ON TIME AT THE ALTAR SONG END SONG TITLE CLICK +GUIDE GROUPS RETURNS TEMPO one lane, whole set stems · Bmaj · 125 stems · Gbmaj · 68 stems · Dbmaj · 85 gap gap A · TRACKS → Ext. Out 5/6 B · DRUMS → Ext. Out 7/8 1256885 an explicit tempo step at every boundary — the click is right the moment a song starts

What comes across

Your songs arrive intact. The stems, the groups, the section locators, the lyrics, the cues, the automation, the tempo maps — whatever was in the project is in the set. Nothing is flattened, rebuilt, or approximated, and your originals aren't touched.

What gets consolidated

The scattered parts become single, set-wide ones:

  • One click lane and one guide lane for the whole show, instead of one pair per song — playing the sounds you chose.
  • One set of returns, on the outputs you approved, instead of four songs' worth of near-duplicates.
  • One tempo and meter timeline running end to end, with an explicit step at every boundary — so the click is right the moment a song starts.
  • One SONG TITLE lane, one lyrics lane, one of each header lane, unioned by name.

What gets organized

  • Each song sits in its own group, colored, and labeled with its key.
  • SONG TITLE and SONG END markers per song, so you can navigate the set by name.
  • Anything hanging past a song's end is trimmed, so no tail bleeds into the next song.
  • Nothing left soloed. No missing media. Every track's sends consistent with the document's send list — which is what makes Live open the file without resetting your routing.

It's an Ableton session, not a black box. Everything in it is an ordinary track, clip, locator, and return. Move a song, redraw a fade, drop a plugin on a return — it's yours now, and StitchAble is out of the loop.

Section 16

Licensing

One purchase, five machines, no subscription. Activate once per Mac and StitchAble never asks again.

Activating

On first launch, paste the license key from your purchase receipt. That's a one-time online check — after it goes through, StitchAble works offline, permanently.

Five seats

A license activates on 5 Macs. The studio machine, the stage machine, the laptop you keep in the case — and two more when you need them.

When you need a seat back

Reinstalling, replacing a machine, or out of activations? Email support — the address is on the activation screen — and a seat gets freed, or more get added. It's a person on the other end, not a form.

Refunded purchases can't be activated. That's the only thing that permanently stops a key from working.

Section 17

Troubleshooting

Most of what looks like a bug is StitchAble telling you something. Here's the translation.

What you're seeing
What it means
A song isn't showing up in the Library
Its folder has to be an immediate sub-folder of the songs folder — not nested two deep. Press Scan after adding it. If the name doesn't parse, check it against Section 04.
A MultiTracks song has no MT badge
It's still zipped, or the folder was rearranged. StitchAble looks for a Live 8 set sitting next to a MultiTracks folder (Section 14). Unzip it and leave the contents where they landed.
Returns are on the wrong outputs
Open the Returns review and set each return's output. Defaults… recomputes the clean plan. Returns whose source fed Master get assigned their own distinct outputs, which is why they may not be where the original song had them.
An amber “audio guide + click” note on a song
Expected. That song has no MIDI guide or click for StitchAble to merge — normal for a MultiTracks download. It plays its own audio. Convert it with MultiConvert 12 to bring it into the unified lanes (Section 10).
Guide or click is silent in Live
The sound library isn't installed. Run Setup in Settings (Section 02).
The guide fires the wrong cues
Your pad order doesn't match what the songs are sending. Open Order Cues… → Reorder drum rack… and set it, then rebuild (Section 10).
A transposed song sounds stretched, or runs long
That's the warp engine struggling with the stems. Switch on the AUPitch plugin in Settings → Transpose and rebuild (Section 11).
The set won't open in Ableton
Check the Live version you built for. A Live 12 file will not open in Live 11 — rebuild with the picker set to Live 11 (Section 13).
It's not doing what this manual says
Rebuild the set from scratch after updating. An .als you built with an older version won't have the fixes in it — the file was written, not linked.

Still stuck? Email support — the address is on the activation screen. Tell me what the set was made of (Live 11, Live 12, MultiTracks) and what you'd chosen in Settings, and that's usually enough to find it.