LOOM
CHAPTERS
  1. Welcome to LOOM
  2. Keyboard shortcuts
  3. MIDI mapping
  4. Privacy
  5. The window
  6. The top bar
  7. The globals row and the track strips
  8. The arrange view
  9. The mixer
  10. The side panel
  11. The bottom rails
  12. Dialogs
  13. Instrument tracks
  14. Where your recordings live
  15. Your licence
  16. Reporting a problem

CHAPTER 6 · LOOM 1.2.0 MANUAL

The top bar

The top bar reads left to right and is on screen in every view. It carries the song's identity, the transport, the tempo, the click, where you are in the song, which track your presses land on, and the switch between the three views.

For keys, see Keyboard shortcuts.

The top bar in the looper view, with no audio device open.
The top bar in the looper view, with no audio device open.
Number What it marks
1 SONG
2 The MOVE set: TO TOP, ROLL and STOP
3 RECORD
4 TEMPO
5 CLICK and the beat LEDs
6 BAR.BEAT.TICK
7 FOCUS
8 The panel toggle
9 The view switcher

The sections below follow the same order.

The middle of the top bar while a song plays: ROLL lit green, a recording running at REC 00:02, the tempo locked behind a dashed frame because the tracks hold loops, the third beat LED filled, and BAR.BEAT.TICK at 3.3.3.
The middle of the top bar while a song plays: ROLL lit green, a recording running at REC 00:02, the tempo locked behind a dashed frame because the tracks hold loops, the third beat LED filled, and BAR.BEAT.TICK at 3.3.3.

SONG

What it is. A readout of which song you are in, drawn centred inside a filled well.

What it does. Nothing. It only shows the name. To change the name, use Save As… and its dialog.

What it says.

Face Means
UNTITLED The song has no name yet.
name The name you typed, read from the file, spaces included.
name HH:MM The name, and the time of a save you made in this run of LOOM.

LOOM stamps the time when the write returns, instead of reading it back from the file. It tells you whether the save you just made worked, not when the file was last written.

What a screen reader adds. The description tells apart two states that the drawn word cannot. For an UNTITLED song whose previous session was restored, it says so: your tracks, tempo, click and routing are the ones you left, but nothing has been saved under a name. For a fresh, empty song, it says that instead. For a named song, it says whether the song has been saved in this run and where the writes go.

The MOVE set — TO TOP, ROLL and STOP

What it is. Three buttons under one spoken group name: "Move the playhead - never records." Each carries a small shape beside its word: ❙◀ for TO TOP, ▶ for ROLL, ■ for STOP. TO TOP sends the playhead back to bar 1 and starts nothing. ROLL starts the transport from wherever it already is. STOP stops it, and every track with it. None of the three writes to a track, arms anything, or starts an arrangement. That is why they are grouped and why the group is called MOVE. Before you press any of them, the name tells you that a press cannot affect your take.

ROLL and STOP show the transport's state. They sit together in one recessed frame, and exactly one of them is lit: STOP, with a raised ground, while the transport is stopped, and ROLL, filled green, while it rolls. Pressing the lit one does nothing, because the transport is already in that state. While the arrangement counts in before bar 1, ROLL is lit amber and reads COUNT and the number of beats left. TO TOP sits outside the frame because it is a command rather than a state. It flashes cyan while you press it and then returns to its normal face. At bar 1 it draws on a darker ground, because there is nowhere for it to send the playhead.

ROLL starts from where the transport is, and STOP leaves it there. Neither goes back to bar 1 on its own, and neither fires an arrangement. The exception is STOP during a count-in: stopping before the downbeat returns the transport to bar 1, because a count-in has nowhere else to leave it. To get back to bar 1 without starting anything, press TO TOP. Press it and then ROLL to audition from the top with nothing armed. In the arrange view you can put the transport anywhere with the playhead instead; see the playhead.

TO TOP is never disabled while the transport rolls. LOOM refuses to move the playhead while the transport rolls, with a sentence instead of a dead face, following its rule that a disabled control tells you why. If you see the refusal, halt the transport first.

While you are performing, TO TOP and ROLL go dead and STOP does not. The arrange view's own transport (PERFORM FROM TOP and PERFORM FROM HERE, see the arrange view) arms and rolls an arrangement. For as long as it is running, TO TOP and ROLL are unreachable by mouse and by keyboard, so you cannot seek by accident while a performance is writing to your tracks. STOP stays live throughout: it ends the performance and stops whatever is running. Press it and the whole set comes back live.

This is separate from the rolling-transport refusal described earlier. A plain ROLL with no arrangement armed leaves the MOVE set available as usual.

If the keyboard was on TO TOP or ROLL when a performance started, it moves to STOP rather than being dropped, so you land on the one control in the set you can still press.

What a screen reader says. The group announces "Move the playhead - never records" before any of the three. The buttons themselves are named Send the playhead to bar 1 without starting the arrangement, Roll transport and Stop transport.

Three different stops. All three carry the word, so a screen reader tells them apart by the noun beside it:

Control Spoken name What it stops
A strip's own STOP Stop track 3 That one track, on that track's stop quantize.
STOP in the top bar Stop transport The transport and everything — including a running arrangement.
ALL STOP in the globals row Stop all tracks Every track. The clock keeps running and the click keeps sounding.

For a screen reader, the accessible descriptions keep them apart.

A fourth control carries the word but is not a stop. PERFORMANCE STOP, on the arrange view's header row, releases the arrangement and leaves the song playing: the transport goes on rolling and every loop goes on playing. It is not in the table because it stops nothing. A screen reader names it Release the arrangement and keep playing, with no stop in the name. See the arrange view.

RECORD

What it is. A button between the MOVE set and the tempo field. It reads REC and a time, with a red dot, and it reads REC 00:00 when nothing is being recorded. It records your performance to disk: one WAV file for each stream ticked in File ▸ Record Setup…, in a new folder in your recordings folder. See Record setup and Performance recordings.

What it does. Press it to start recording. Press it again to stop. Every file is then closed and complete. Recording does not start or stop the transport, and it does not record into a loop track.

What it says. The words are always REC mm:ss, and the button stays the same size. The colour tells you the state. None of the states flash.

Face Means
REC 00:00, grey Nothing is being recorded.
REC mm:ss, red A recording is running. The time is how much audio the files hold.
REC mm:ss, amber A recording is running and has had at least one gap. It stays amber until you stop that recording.

If LOOM cannot start a recording, the notice line says why and what to do. For example, when nothing is ticked it reads "Tick a stream in File ▸ Record Setup, then press RECORD", followed by LOOM's reason.

Gaps. A gap is a moment when the disk could not keep up and LOOM dropped a block of audio. LOOM fills the gap with silence in every file, so the files stay in step with each other, and writes its time to Markers.txt in the recording's folder. When a gap happens, the button turns amber and the notice line gives its time, for example "A gap at 01:12 was filled with silence."

When you stop. The notice line gives the number of files, the full path of the recording's folder, and the time of every gap, for example "Recording stopped. 5 files in /Users/you/Music/LOOM/Recordings/Take 5 2026-09-19/. 2 gaps, filled with silence, at 01:12, 03:40. Markers.txt lists them." If the notice line has moved on, View ▸ Show Logs still has the message. To open the folder in Finder, use REVEAL IN FINDER in File ▸ Record Setup…, which names the last recording.

When a recording stops by itself. A recording stops, and its files are closed cleanly, when:

  • the disk is nearly full;
  • a file cannot be written;
  • the audio device restarts or you choose a different device;
  • you open a song, or start a new one.

The notice line says which of these happened. When you change songs, it reads "The recording stopped at the song change." Start a new recording in the new song if you want to keep recording.

What a screen reader adds. The button's name is always Record the performance. Its description says whether a recording is running, how long it is, how many files it is writing and how many gaps it has. Each new gap and the stop are announced from the notice line.

TEMPO

What it is. The project tempo in beats per minute, in one frame of three cells: −, the number and +. It is the only tempo control in LOOM, and it is one tab stop.

What it does. Sets the tempo the click and every bar line are counted against.

Four ways to change it.

  • Type it. Click the number to open the type-in editor. Return commits and Escape discards, and both take effect immediately, not a frame later.
  • Drag it. Two pixels of drag is one step. Dragging up is faster, as on every fader and every DAW tempo field. The drag is measured from where you pressed and is never accumulated, so a long drag cannot creep, and releasing where you started restores the exact value that was there.
  • Press − or +. They auto-repeat if you hold them.
  • Use the arrow keys with the field focused.

One step of the drag, the steppers or the arrow keys is one beat per minute. Hold Shift on any of the three and a step is a tenth of a beat per minute instead.

Stepping and typing are different operations. The tempo is held in thousandths of a beat per minute. Stepping is relative, so a song sitting at 137.4 becomes 137.4 plus one step and is not snapped to a whole number. Typing is absolute and rounds to the tenth that the field draws.

When it is locked. This field refuses a tempo you type, drag or step unless every track is empty and the transport is stopped. Having no audio device open does not lock it. When the field is locked, its frame goes from solid to dashed, the number and the steppers dim, and nothing moves by a pixel. Click the locked field, and the notice line says why it is locked.

The lock only stops you changing the tempo by hand. The number can still change by itself: The first free loop sets the tempo is the one thing that changes it while the transport rolls.

The reasons below form a chain, and you have to clear all of them. Finishing a take leaves a track holding a loop, and clearing every track with the transport still rolling leaves the transport rolling. To type a tempo, you need both: every track empty and the transport stopped. To have LOOM derive one, the transport can be rolling, but every other track must be empty. You play the first free loop.

Locked because What to do
A track holds a recorded loop A tempo typed under one moves every bar-quantized press against it. Clear every track and halt the transport.
A track is recording or waiting to Finish or stop the take. If it lands a loop, the field stays locked because a track holds a loop.
The transport is rolling Press STOP, or close your first free loop, which sets the tempo without stopping.
The engine's state could not be read Nothing in the window changes this.

If you are dragging when the lock arrives, the drag is cancelled rather than left tracking your finger over a box that has gone dead.

What a screen reader gets. The control is named Project tempo and has the role of a slider with a real, settable value. A screen reader can read the number and set it, and is told the range and that one step is one beat per minute. When the field is locked, the value reports itself as read-only and the reason is added to the end of its description. The name stays Project tempo in both states.

When the field locks, LOOM says why on the notice line. A locked field leaves the tab order, because Tab should not stop on a control that cannot act, so the reason goes where the keyboard already goes. The notice line shows, word for word, the sentence the field holds.

LOOM says it once, as the lock arrives, and does not repeat it. It also says nothing when one reason replaces another: when you finish a take, the reason changes from recording to holding a loop without a word. The reason is a long sentence, and hearing it again in the middle of playing is worse than not hearing it. To see the current reason again, click the locked field.

VoiceOver: the notice line is spoken as the lock arrives. VoiceOver navigation also reaches the locked field itself, reports it unavailable, and reads the reason at the end of its description. Use this to find out why the field will not move after the announcement has passed.

The two stepper buttons are named Tempo down and Tempo up and are not tab stops, because the field's own arrow keys do the same thing. A screen reader's element navigation still finds them.

With no audio device open the tempo still works. The field shows the tempo the session will start at. If you type a tempo before you plug in an interface, LOOM builds its first tempo map from that value when the device opens. This state is not locked, and it is when the setting matters most, because the tempo has to be set before the first loop.

The box is sized to the widest value it could ever draw, so it never changes width.

The first free loop sets the tempo

What it does. Record the first loop of a song on a free-length track whose launch and stop quantize are both immediate. When you close it, LOOM reads the tempo off that loop and makes it the song's, so the grid fits what you played instead of your playing having to fit the grid. A hardware looper works the same way when its first loop becomes the clock.

Your loop starts on a bar line, but usually not bar 1. The grid runs through the whole session instead of starting at your loop, so the bars that went by before you pressed record are counted: if two bars' worth of time passed first, your loop begins at bar 3, beat 1. The bar number is how many whole derived bars fit before your loop, plus one. The ruler shows the audible time before your loop, and this keeps every bar number in the arrange view positive. What matters musically is that your loop starts on a bar line, on beat 1, and is a whole number of bars long, so everything you overdub against it lands where you expect, whatever BAR.BEAT.TICK calls the first bar.

It happens while the transport rolls, and you press nothing extra. Closing a loop leaves the transport rolling, which is the state this works in. Do not halt the transport to make it fire: halting closes the take and derives nothing. Nothing new sounds at the moment it lands. No loop is touched, and the click picks up the new grid with no stutter and no doubled beat at the seam. In the same frame the TEMPO field shows the new number, and the notice line at the bottom of the window says what was derived.

VoiceOver: the tempo moves on a control you cannot tab to. Recording a loop leaves the field locked, so the notice line is where LOOM tells you the new tempo and the bar count it read.

What the notice says. It names the bar count first, "assuming 4 bars of 4/4", because that is the assumption LOOM made and the only part of the sentence you might disagree with.

What it does not say. LOOM reads a phrase as 1, 2, 4, 8 or 16 bars. A loop that is really 3, 5 or 6 bars long is read as one of those, and its tempo is out by that ratio. This applies to every derivation, so the notice line leaves it out. Otherwise the line would repeat the same sentence on every loop, and you would have to re-read it to find the two numbers that had changed. See What the line does and does not say.

If it read the wrong number of bars, the tempo is out by that ratio: a 2-bar phrase read as 4 is half the tempo you played. There is no halve or double button. Instead, set the other tracks to twice or half the bars you meant, which costs nothing and keeps the take.

What has to be true for it to fire.

  • The track's length is free and both quantize settings are immediate. A track that quantizes to a bar line already has a grid. A free, immediate one does not, so that is when deriving one is useful.
  • Every other track is empty. That is what makes it the first loop. A second free loop does not re-derive, because the first one is still there.
  • The loop is closed plainly: the ring press that ends the recording is PLAY or RECORD. Ending the recording into an overdub, a multiply or a mute derives nothing.
  • No arrangement is armed.
  • The setting first free immediate loop sets song tempo is on. It is on by default and there is no control for it in the window. It is a preference rather than a song setting, so it is restored at launch whatever song you open.

It comes back when you clear. Clear every track and the next free loop you close derives the tempo again. LOOM does not remember whether this song has ever derived one. Only what is in the tracks right now counts.

When it cannot. If no whole bar count fits your phrase, or the tempo it would land on is outside the range the field accepts, nothing is changed and nothing is snapped. The notice line says which of the two happened.

CLICK and the beat LEDs

What CLICK does. Turns the click's audio on and off. It is saved with the song, so a song you open comes back with the setting it was saved with. It is in the top bar because you reach for it mid-set. It is named Click audible, and the notice line reports click audible or click silent.

The beat LEDs are inside the button, to the right of the word, and pressing anywhere on the button toggles the click. The word is dim when the click is silent and bright when it is audible. The LEDs carry the colour that shows the click will be heard.

The button says whether the click is running, not whether you can hear it. The click's level and its MAIN and CUE sends are on the click strip in the mixer's MASTER bank, and with both sends off the click runs and nothing comes out. This button does not change to reflect that; see The mixer.

What the LEDs do. They show two things, each in its own way.

The outlines say whether the click is on. They are amber when it is and grey when it is not, in every state, so an armed click shows as armed even with the transport stopped and nothing moving. Like CLICK itself, they follow the switch, not the routing.

The fill says where you are in the bar. One LED is filled and the others are hollow. The downbeat is always drawn as a wider bar and the others as squares, not only when the beat lands on them, so you can tell which beat it is, and whether it is the downbeat, without colour. During a count-in, ROLL shows how many beats are left before bar one.

The LEDs flash whether or not the click is audible, so you can still see the beat with the metronome out of the front-of-house mix. With CLICK off, the filled LED is grey instead of amber and keeps moving.

What a screen reader reads. The group is named Click beat. Its description is beat 2 of 4, plus count-in N beats remaining while a count-in is running, plus click audible or click silent. With the transport stopped it reads transport stopped, no beat.

BAR.BEAT.TICK

The musical position, drawn as 12.3.480. It is a readout and is not a tab stop. It shows an em dash when there is no tempo grid.

FOCUS

What it is. A readout of which strip a press lands on. The focused strip also shows this in three other ways: a filled cap across its top edge, a tinted border, and a caret before its number.

Two faces. At a comfortable width it draws TRACK 3 of 5. When the top bar runs short it draws T3/5. Only the drawn word shortens. The accessible sentence is Track 3 of 5 is focused. Presses that name no track land on it. at every width.

The panel toggle

What it is. A square button just left of the view switcher, drawn as a window with a panel on its right. It shows and hides the side panel on every view, and hiding the panel widens the view. It is in the top bar because a control that hides a panel has to stay reachable while the panel is hidden.

What it shows. While the panel is on screen the button is lit cyan and the panel in its drawing is filled. While the panel is hidden the button is grey and the drawing is hollow. The panel comes back in the mode you left it in: GLOBAL, TRACK n or SONG.

When the window is narrower than about 1400 px, the mixer's effect drawer takes the panel's place, and the button is grey while it does. Pressing it then closes the drawer and brings the panel back.

What a screen reader gets. It is named Toggle side panel in every state and is one tab stop, after the view switcher. Its description says which panel is showing or will come back, because the drawing cannot.

The view switcher

What it is. A three-cell segmented row at the right end of the top bar: LOOPER, ARRANGE and MIXER. It chooses which surface the body of the window shows, and it shows the same state as the View menu. See Keyboard shortcuts for the keys.

With the switcher focused, the arrow keys move the selection and Home and End jump to the ends. It takes no modifiers.

What a screen reader gets. The row is named VIEW and is one tab stop. Each cell is a radio button, VIEW: LOOPER, VIEW: ARRANGE and VIEW: MIXER, reported as checkable and checked, so a screen reader says which one is selected. The same description sentence is set on the row and on every cell, because a screen reader lands on a cell and a container's description is not inherited by its children.

The selected cell is lit and carries a 3 px rule under it, so the selection does not rely on colour alone.

The view changes only what is on screen. It changes no setting and is not saved. Every session starts on the looper.

The row keeps its full width however narrow the window gets. See The mixer for what is behind the third cell.

Tab does not switch views. It moves through the controls, here as everywhere else.