Manual for PACER Looper 0.3.0
Nektar Pacer × Bitwig Studio

Pacer4Bitwig

The Nektar Pacer as a looper pedal and an effects pedalboard for Bitwig Studio. Every loop is a clip in Bitwig's launcher, so loops always land in time with each other and the project tempo, and the Pacer's LEDs blink with the beat.

PACER Looper 0.3.0 Preset PACER on D1 · modes LOOP FX MIX SONG CUST Talks on MIDI channel 16 Bitwig Studio 6
The Looper mode, its display naming the row. The LEDs show an example moment at 120 bpm: loop 1 playing, loop 2 stopped.
ROW 1
PRESET
PACER

SW 1

Loop switch · loop track 1
Tap
Smart loop: record on an empty slot, close the recording, stop a playing loop, play a stopped one
Double-tap
Nothing by default
Hold
Delete that loop

Playing: green, with a short gap on every downbeat

Loop switches fire on press, so timing stays tight. See Smart loop.

Part one

Set up

What you get

Bitwig has no looper device: the clip launcher is the looper. Pacer4Bitwig gives the Pacer the controls, the presets and the feedback to play it with your feet.

PACER Looper
The Bitwig controller extension (Pacer4Bitwig.bwextension). All behaviour lives here, and almost everything is configurable in Bitwig's controller settings.
One Pacer preset
PACER on slot D1. It only has to speak the right CCs: the extension writes the colours, the display name and what every switch does live while it plays.
Five modes
LOOP loops, FX the pedalboard for what you are playing, MIX solo, mute, monitoring and the click, SONG building a song out of rows, and CUST laid out however you like in the settings — or let those settings change one of the other four. Tap SW 6 to toggle, hold it for the menu, double-tap it for the shift layer, a second job on the same switches.
Pacer Studio
A preset editor that runs in Chrome or Edge, online or installed. It writes the preset, backs up the Pacer, and has an LED Lab and a MIDI monitor.
Command-line tools
In tools/: a read-only backup, the preset generator, a guarded preset writer and a MIDI monitor.

You need

  • Bitwig Studio 6 and a Nektar Pacer connected over USB.
  • Chrome, Edge or Opera on a desktop to write presets with Pacer Studio (it needs Web MIDI with SysEx).

Tested on Windows 11 with Windows MIDI Services, which lets Bitwig, Pacer Studio and the tools share the Pacer's ports.

Install the extension

Once per computer. Bitwig reloads the extension by itself whenever the file is replaced.

  1. Download Pacer4Bitwig.bwextension from the latest release, or build it from source with cd bitwig && mvn -q install.

  2. Copy it into Documents/Bitwig Studio/Extensions. A source build does this for you.

  3. Disable Nektar's own PACER script in Settings › Controllers. It claims the same MIDI port. PACER Looper can take over its Track and Transport presets (see DAW mode).

  4. Add the controller: Settings › Controllers › Add controller › Nektar › PACER Looper, then pick the ports.

    PortInputOutputUsed for
    Port 1PACERPACERThe preset, LEDs, pedals
    Port 2MIDIIN2 (PACER)MIDIOUT2 (PACER)Only the optional Nektar DAW mode
  5. Check the pop-up. Bitwig shows PACER Looper 0.3.0 ready on MIDI channel 16. No pop-up, or an older version number, means the file did not load.

Added the controller before 0.2?

PACER Looper has two ports since version 0.2. Open its entry in Settings › Controllers and pick the port 2 devices, or remove and re-add the controller.

Put the preset on the Pacer

One preset makes the Pacer send what the extension listens for: CC 102–119 on MIDI channel 16. Your other presets stay as they are.

With Pacer Studio

  1. Open Pacer Studio in Chrome or Edge, click the connection pill, then Allow MIDI access.

  2. Choose Templates › Bitwig Pacer and pick D1.

  3. Click Send changes. Before the first write of a session Pacer Studio asks you to save a full backup: save it, it is your undo.

From a terminal

The writer refuses a file that targets a different slot than --confirm names, and backs that slot up to backups/ before writing.

cd tools
node pacer-backup.mjs
node pacer-preset.mjs
node pacer-send.mjs ../presets/bitwig-pacer-D1.syx --confirm D1
SlotDisplayPresetAnnounces itself with
D1PACEREverything — the extension paints the restCC 119 = 127
Why only one preset

What each switch does, what colour it is and what the display says are written to the Pacer live while it plays, and they change with the extension's active mode. Those writes go to preset index 0 — the loaded preset's RAM copy — so your stored presets are never touched and nothing wears the EEPROM. Selecting any preset on the Pacer undoes the lot, and the extension simply writes it all again.

Keep off D6

The Pacer never answers read requests for D6, so that slot cannot be backed up on its own.

Prepare a Bitwig project

Loops need tracks to live on, and launch quantization to land on the grid.

  1. Create the loop tracks next to each other, e.g. Loop 1–4. The looper manages 1–8 tracks (setting Loop tracks). Audio tracks take your interface input; instrument tracks work too, and can overdub notes into a playing clip.

  2. Tell the extension where they are if they are not the first tracks: Looper › Loop tracks start at track. It applies to every project, so a template that starts with a group track only needs it once. Holding SW A or SW B in the Looper mode, or tapping them in the mode menu, moves the loop track window and writes the same setting.

  3. Set Launch quantization to 1 bar in the extension settings. That is what makes loops start and end on the grid.

  4. Set the tempo, or tap it in the Song mode by holding SW 5.

  5. Keep the audio buffer low, 64–256 samples. Bitwig compensates recording latency itself.

How you hear yourself

Recommended for guitar and vocals

Dedicated input track

One track per instrument with the interface input, monitoring On and your live effects. Set each loop track's input to that track (post-FX) and its monitoring to Off. You always hear the live sound, loops record what you hear, and arming never changes it. These are the tracks the FX mode controls.

Simplest

Monitor through the loop tracks

Loop tracks take the interface input with monitoring Auto. The looper arms the track it records on; Exclusive arm keeps only the latest one armed, so you hear your input once, through that track's effects.

Synths

MIDI loops

Instrument tracks with input PACER or your keyboard. Arm follows the loop you record, and launcher overdub layers notes into a playing clip.

Playing a Push at the same time

The looper selects the loop track it records on, and a Push follows Bitwig's selection. Pin the Push's track (DrivenByMoss: press Select, then Pin Track), or switch off Select the track on press. The FX mode never changes the selection.

Part two

Play

The Looper mode

Select D1 on the Pacer: the extension writes the whole board, and a new project starts in this mode, with the row on the display (ROW 1). Each loop switch runs one loop track like a looper pedal, the rest of the Pacer moves you around the song. SW 6 is the mode switch — tap it to go back to the mode you were in before, hold it for the menu, double-tap it for the shift layer.

SW 6 and the mode menu

Hold SW 6 and the menu opens; it stays open when your foot comes off. Tap a mode and you are there. Tap SW 6 again to close the menu without changing anything; with the menu shut, a tap goes back to the mode you were in before.

Double-tap SW 6 runs whatever SW 6 double-tap says: any action, by default the shift layer on/off. So that a double-tap never toggles the mode first, SW 6's tap then waits out the Double-tap speed window before it toggles; set SW 6 double-tap to Nothing for an instant tap. With the menu open, a tap closes it at once.

In the menuTap
SW 1–SW 5Looper · FX · Mixer · Song · Custom, lit green, magenta, blue, gold and cyan; the active one is bright. Custom goes dark while the custom layout changes another mode.
SW A / SW BMove the loop track window left / right
SW C / SW DNext / previous scene row — the panel prints ▼ and ▲ on them

Navigation leaves the menu open, so you can step through rows or tracks with repeated taps.

The display

The display names the mode, or what the mode is doing when that says more: the FX mode names the focused instrument, the Looper and Song modes the row you are on — the scene's name in Bitwig, its name from Names for new rows, or ROW 3. Show what the mode is doing on the display turns that off.

Events take the display for a moment and then give it back (Show events on the display, on by default):

WordWhen
REC 2Loop 2 starts recording (COUNT while a count-in runs)
4 BARA loop closed, and how long it is
CLR 2 · CLEARLoop 2 was cleared · the whole row was
UNDO · REDOUndo, redo
MUTE2 · UNMT2Loop 2 muted or unmuted, as asked for: a waiting mute shows it when you press
MUTED · UNMUTAll loops muted or unmuted
STOP · PLAYStop all, play the row
FDOUT · FD INA fade started
RESETThe looper was reset
SNAP2 · SAVE2FX snapshot 2 recalled · stored
SHIFTThe shift layer went up

Each event costs two name writes — the word, then the name again 1.5 s later — and each flashes LOAD SYS.

Another preset loaded. The extension paints whatever preset is loaded, so it checks first that it is still its own: it reads the loaded preset's name back (a read-only request) before painting when its last answer is more than 1.5 s old, and every 5 s. On another preset it leaves the Pacer alone — Bitwig says so once — until you select the Bitwig preset again, or press one of its switches (a press on the Bitwig preset is proof enough). At startup it paints once the first answer is in (after a second, if the Pacer does not answer at all). The same check notices a Pacer that was unplugged and plugged back in, and paints it again. Check the Pacer is on its preset sets how: every 5 s and before painting (the default), only before painting, or off.

Not tried on hardware yet

Whether the Pacer shows the preset check's request on its display has not been tested. If the display flashes LOAD SYS every five seconds, choose Check the Pacer is on its preset = Only before painting.

Three gestures on every switch

Tap
Runs on press whenever timing matters (loops, the one-button looper, tap tempo) or when the switch has no hold action; otherwise on release, so a hold never runs the tap first.
Double-tap
The first tap always runs straight away. A second tap within the Double-tap speed window (0.25, 0.35 or 0.5 s) runs the double-tap action instead of a second tap. Double-taps are built in only on the FX mode's switches and on SW 6, where one raises the shift layer.
Hold
Half a second. Actions that delete loops ask for 1.5 s by default, or 2.5 s (Hold time for clearing actions), so a heavy foot never clears a take.

Default layout

ControlTapHold
SW 1–SW 4Smart loop on loop track 1–4Delete that loop
SW 5UndoRedo
SW 6Close the menu, or go back to the mode you were in before · double-tap: the shift layer on/offThe mode menu — it stays open when your foot comes off
SW APrevious scene rowMove the loop track window left
SW BNext scene row, adding one after the lastMove the loop track window right
SW CStop all loops, or play the whole row when nothing playsClear every loop in the row
SW DLauncher overdub on/offMetronome on/off
FS 1One-button looper: record the next layerClear the last recorded loop
FS 2Stop all loops / play the rowClear every loop in the row
FS 3Focus the next FX instrument–
FS 4Next FX snapshot–
EXP 1Volume of the selected track
EXP 2Master volume

Tap tempo and transport play/stop are on the shift layer's SW D, and on the Song mode's SW 5. To change a switch, point the custom layout at this mode and set only what differs (see Your own layout). The footswitch jacks have settings of their own and do the same in every mode.

The shift layer

Every mode can have a second layer on the same switches. Double-tap SW 6 (the default SW 6 double-tap) and SW 6 turns gold, the display says SHIFT for a moment, and every switch with something on its shift layer does that instead; double-tap again to go back. A switch with nothing on its shift layer keeps its normal job, and SW 6 stays the mode switch. Changing mode drops the shift layer.

Three actions raise it, for SW 6's double-tap, a footswitch jack, or any switch in your own layout:

ActionWhat it does
Shift layer on/offLatches it until the same action again. The default on SW 6's double-tap.
Shift layer for the next pressUp for one switch press, then back; SW 6 blinks gold meanwhile. Asking again before that press cancels it.
Shift layer while heldUp while that switch or jack stays down: hold a footswitch on FS 1 with one foot, play the shifted switches with the other.

The Looper's shift layer is where loop tracks 5–8 live; set Loop tracks to 8 to use them.

ShiftedTapHold
SW 1–SW 4Smart loop on loop track 5–8. They are loop switches, resting in cyan so they look different from loops 1–4.Delete that loop
SW 5Mute/unmute all loopsReset the looper
SW ADuplicate the row–
SW BShow looper status–
SW CFade out and stop all loopsFade the row in
SW DTransport play/stopTap tempo

The FX mode's shift layer puts FX 5 and FX 6 on SW A and SW B (hold: momentary) and previous / next instrument on SW C and SW D. The Mixer and Song modes have none yet: their switches keep their jobs when shifted. The custom layout lays out the shift layer too (Custom layout: shift layer, see Your own layout), so this is the place to build your own workflow.

Smart loop

One switch per loop. What a tap does depends on the slot in the current scene row:

The slot isA tapLED
emptyarms the track and records from the next quantization point, or after the count-in the mode colour, dimmed
recordingcloses the loop: stops recording and plays it red, gap on the downbeat
playingstops it (or, by setting, mutes/unmutes it, toggles overdub, or does nothing) green, gap on the downbeat
stoppedplays it, and unmutes the track if it was muted amber
waiting, counting incancels fast blink in the colour it is heading for
waiting to stopkeeps it playing fast blink, amber

Loop switches fire on press. A hold therefore runs the tap first, which is harmless with the default hold: whatever the tap started is deleted.

Shaping the loop switches

How many
Loop tracks: 1–8, default 4. SW 1–4 are the Looper mode's loop switches for loop tracks 1–4, and the same switches on the shift layer for 5–8. A loop switch beyond the project's loop tracks does nothing: with three tracks, SW 4 is idle. For loops somewhere else, give any switch, shift gesture or footswitch jack the tap Loop track 1–8 (see Your own layout). FS 1 and the row actions run every loop track.
Hold to record
Loop switch mode = Hold to record, release to close: press and hold an empty loop to record, let go to close it, like a punch-in. Let go before recording started and it closes one quantization step after it starts. Loops that already exist keep tap and hold.
Double-tap
Double-tap a loop switch: stop, mute/unmute, clear or undo. Clear turns an accidental record into "never mind".

Building a performance

One-button looper
The classic single-pedal looper spread over the loop tracks: each tap closes the loop that is recording, or starts one on the first empty track of the row. Hold clears the most recent loop.
Mute, don't stop
Tap on a playing loop = Mute/unmute keeps the clip running silently, so it comes back exactly in time. Mute/unmute all loops makes a break; Solo/unsolo selected loop isolates a layer.
Mute on the one
Mute timing = On the next beat / bar holds a mute until the next beat or downbeat, even if your foot is early. A waiting mute blinks fast; tap again to cancel it.
Count-in
Count-in from a stopped transport = 1 or 2 bars starts the transport with the metronome, counts in and records on the next bar. Tap the same switch again to cancel.
Beat counter
In the Looper mode, while counting in or waiting to record (amber) and while recording (red), SW A–D show the beat of the bar: A = 1, B = 2, C = 3, D = 4. With While recording, SW A-D count = Bars since the recording started they count bars instead once the recording runs — A = bar 1, B = bar 2 … and A again for bar 5; count-ins always count beats. It runs on the Looper whether the custom layout changed it or not, and on a custom mode of its own once it has loop switches — never over a loop switch on the top row.
Match the first loop
Loop length = Match the first loop of the row: the first loop of a row is free, and its length in bars becomes the length of every later loop in that row, which then close by themselves.
Double and halve
Double selected loop duplicates the clip's content (2 bars become 4 of the same material); Halve shortens the loop to its first half.
Rows as song sections
Each scene row is a set of loops. Record the verse in row 1, tap SW B and record the chorus in row 2, launch rows with SW C. Duplicate row copies a row with its loops and moves there. With Previous / next row while loops play = Move to it and play it, moving to a row that has loops while the song plays launches it on the launch quantization, so a section change is one press; an empty row is left alone, so the old loops play on while you record the new section.
Row names
Names for new rows such as Intro, Verse, Chorus, Bridge, Outro name rows created from the Pacer by position, and notifications show them: Row 3: Chorus.
Fades
Fade out and stop all loops ramps the loop tracks down over the Fade length (1, 2, 4 or 8 bars), stops them and restores their volumes. Fade in the row launches it from silence. Tap again during a fade to cancel.
Status at a glance
Show looper status pops up Row 2: Verse | 1 ▶ (muted) 2 ● 3 ■ 4 –: ▶ playing, ● recording, ■ stopped, – empty. It shows even with notifications off.
Panic
Reset the looper stops every loop, cancels count-ins, fades and waiting mutes, unmutes, unsolos and disarms the loop tracks and turns launcher overdub off.

Your own layout: change a mode, or build a fifth

Settings › Custom layout lays out one board, switch by switch. The custom layout changes decides whose board it is:

Its own mode
The default: the fifth menu slot, CUST, starting from an empty board, with pedals of its own (EXP 1 · Custom, EXP 2 · Custom).
The Looper, FX, Mixer or Song mode
That mode, changed in place. It starts from the mode's own board and keeps its menu slot, its name, its pedals and (the Looper) its beat counter; the CUST slot goes dark meanwhile.

Every switch except SW 6 has five settings, and each one starts at As in the mode, so you only set what differs:

SettingOptions
SW n · tap / double-tap / holdAs in the mode, or any of the actions, exactly like a footswitch jack. Nothing empties the gesture.
SW n · colourAutomatic — the mode's own colour for a switch you did not change, otherwise one picked from its action — or Off, or one of the Pacer's twelve
SW n · LEDAs in the mode, or which of the switch's LEDs lights: the colour strip, the icon row or the word row. SW A–D have no word row, so they fall back to the strip.

Plus Name on the display: five characters; blank keeps the mode's own name, CUST for a mode of its own. Changing any of it repaints the Pacer at once while you are standing in the mode.

The shift layer has its own category, Custom layout: shift layer: SW n · shift tap / shift double-tap / shift hold, each starting at As in the mode — the mode's own shift layer, which for most switches means "keeps its normal job". Set any of them and the switch does that while shift is up; its colour then comes from the action, and it lights the same LED as normally. A switch whose shift gestures all do Nothing keeps its normal job.

Example: tap tempo back on the Looper's SW D

The custom layout changes = The Looper mode (changes it), SW D · tap = Tap tempo, SW D · hold = Transport play/stop. Everything else stays the Looper.

Loops anywhere
Give a switch the tap Loop track 1 … Loop track 8 and it is a full loop switch for that track: the smart loop, Hold a loop switch, Double-tap a loop switch, hold to record and the loop LED all apply, and its own hold and double-tap settings are ignored. So loops can sit on the top row, on the shift layer, and a footswitch jack set to Loop track n is a loop switch too.
A mute per loop
Mute/unmute loop track 1–8 gives each loop a mute switch of its own, looper-pedal style. It honours Mute timing, lights blue while the loop is muted and blinks while the mute waits for its beat.

Actions you can assign

These actions are available as tap, double-tap and hold in the custom layout (its shift layer included) and on the footswitch jacks, and any of them can be SW 6's double-tap.

GroupActions
LoopsLoop track 1–8 (as a tap: makes the switch or jack a loop switch) · mute/unmute loop track 1–8 · one-button looper · clear the last recorded loop · smart loop, stop, mute, solo or clear the selected track · input monitoring on/off · double / halve the selected loop · select previous / next loop track
RowPlay row / stop all · stop all · play row · clear row · mute/unmute all loops · fade out and stop · fade in the row · reset the looper
NavigationPrevious / next row · duplicate row · move loop tracks left / right · loop tracks start at the selected track
TransportUndo · redo · launcher overdub · metronome · tap tempo · transport play/stop · show looper status · test the LEDs
FXFX 1–6 on/off · focus instrument A–D · focus next / previous instrument · mute/unmute instrument A–D or the focused one · assign the selected track to instrument A–D · next snapshot · back to snapshot 1 · store the snapshot
ModesNext mode · previous mode (toggle) · go to the Looper, FX, Mixer, Song or Custom mode (the Custom one goes to the mode the custom layout changes, if it changes one)
ShiftShift layer on/off · shift layer for the next press · shift layer while held (see The shift layer)
Hold onlyMomentary: tap again on release turns any on/off tap into a momentary switch

The FX mode

Hold SW 6 and tap SW 2: the display reads FX and the board repaints. The Pacer becomes a pedalboard for whatever you play through Bitwig, and your loops keep playing — nothing about the Pacer's preset changed, only what the extension makes of it.

One board, many instruments
Switching instrument is one tap on the bottom row (SW 1–4), so you can put the guitar back on the stand and pick up the bass mid-song.
The meaning lives in Bitwig
A switch controls the focused instrument's track remote controls page named Pacer, or, without one, the devices of its chain in order. Changing an effects rack never needs a new preset.
Hands off your selection
The FX mode follows instruments with its own cursor, so it never changes Bitwig's selected track, and neither the mouse nor a pinned Push moves it.

Set up your instruments

  1. One track per live instrument, e.g. Vocal, Guitar, Bass, with the interface input, monitoring On and its effects: the dedicated input track setup.

  2. Optional: add a remote controls page named Pacer to each track and map

    • slots 1–4 to what SW A–D switch (FX 1–4), such as an effect's mix or a chain's volume. The mapping's range is what the switch toggles between, so delay mix 0–35 % is set up in Bitwig. Slots 5–6 are FX 5 and FX 6, on the shift layer's SW A and SW B;
    • slots 7–8 to what EXP 1 and EXP 2 move: wah frequency, delay feedback, reverb size.

    Save the track as a preset (Guitar rig, Bass rig, Vocal chain) to bring it to any project.

  3. Assign the tracks: select the guitar track in Bitwig and hold SW 1 until Bitwig shows Instrument A is now Guitar. Repeat with SW 2, SW 3 and SW 4.

Default layout

ControlTapDouble-tapHold
SW 1–SW 4Focus instrument A–DMute/unmute that instrumentAssign the track selected in Bitwig
SW 5Next snapshotBack to snapshot 1Store the current sound
SW 6Previous modeShift layer on/off (setting SW 6 double-tap)The mode menu
SW A–SW DFX 1–4 on/off–On only while held
FS 1, FS 2Same as in the Looper mode: one-button looper and play/stop all, so you can keep looping
FS 3, FS 4Focus the next instrument · next snapshot
EXP 1, EXP 2Remote controls 7 and 8 of the focused instrument's Pacer page

The shift layer (double-tap SW 6; SW 6 turns gold) reaches the rest. SW 1–5 keep their jobs.

ShiftedTapHold
SW A, SW BFX 5, FX 6 on/offOn only while held
SW C, SW DFocus the previous / next instrument–

To change this layout, point the custom layout at the FX mode (see Your own layout), shift layer included. FX 5 and FX 6 can also go on a footswitch jack, which keeps its own settings in every mode.

What an FX switch controls

The track has a Pacer page

Remote controls

FX N toggles remote control N between the two ends of its mapping, and counts as on from the middle of the range. A slot you did not map does nothing, and devices are left alone.

No Pacer page

Devices in order

FX N switches the Nth device of the track's chain on and off. Only top-level devices count, so a container is one device; devices after the sixth are out of reach.

Tap latches, hold is momentary, on the same switch: the effect flips on press with no delay, and if you held the switch longer than half a second it flips back when you let go. That is a delay throw on one word of a vocal.

Snapshots

What is stored
The state of FX 1–6 for the focused instrument: each device on or off, or each remote control's exact value, so a delay mix set to 35 % with a knob comes back at 35 %. Remote controls 7–8 stay with the pedals.
How many
Snapshots per instrument: 2 by default (an A/B pair such as rhythm and lead), up to 4. Saved per project.
Using them
Tap SW 5 for the next snapshot, double-tap to go back to the first, hold to store the current sound in the snapshot you are on. An empty snapshot changes nothing until you store into it. The display shows SNAP2 for a moment when snapshot 2 is recalled, SAVE2 when it is stored.
Changed since
SW 5 blinks when you have switched something since the snapshot was recalled or stored.

Instruments

By name
An instrument is remembered by its track name, saved with the project. After renaming a track, assign it again. Instruments are found among the first 64 tracks, group members included.
Safe assignments
Assigning uses Hold time for clearing actions, so choose Long if you tend to rest a foot on a switch.
Swapping guitars
Double-tap the instrument's switch to mute its track while you unplug; its LED blinks until you unmute.
Selecting too
Switch on Focusing an instrument selects its track in Bitwig if you want the mixer and devices to follow.

Example Pacer pages

Starting points only; map whatever your rig uses.

Example

Guitar

  • 1 drive, 2 chorus, 3 delay, 4 reverb, 5 boost, 6 octave
  • EXP 1 wah frequency, EXP 2 volume
  • Snapshots: rhythm, lead
Example

Bass

  • 1 compressor, 2 fuzz blend (FX Layer mix), 3 octaver, 4 envelope filter
  • EXP 1 filter cutoff
  • Snapshots: clean, dirty
Example

Vocal

  • 1 delay throw and 2 reverb throw (hold them), 3 doubler, 4 harmonizer, 5 megaphone
  • EXP 1 delay feedback
  • Snapshots: verse, chorus

Expression pedals

Each pedal has one target per mode, plus a response curve and a range that every mode shares.

KindTargets
Bitwig parametersSelected track volume, pan, send 1, send 2 · master volume · selected device remote controls 1–2 · project remote controls 1–2
Focused instrumentRemote controls 1–8 of its Pacer page (FX mode defaults: 7 and 8)
LoopsLoop track 1–8: volume (follows the loop track window) · the loop being recorded, else the one recorded last in the row, else the selected loop track: volume · all loop tracks: volume, keeping their balance
Per modeEach mode has its own target for each pedal — ten settings, EXP 1 · Looper through EXP 2 · Custom. Defaults, EXP 1 / EXP 2: Looper selected track volume / master volume · FX focused instrument remote control 7 / 8 · Mixer selected track volume / send 1 · Song master volume / project remote control 1 · Custom nothing. A custom layout that changes a built-in mode keeps that mode's pedals. Response curve and heel/toe are shared.
MIDIMod wheel (CC 1) · breath (CC 2) · channel volume (CC 7) · expression (CC 11) · brightness / MPE timbre (CC 74) · channel pressure · pitch bend up (heel centre, toe full up)

MIDI targets go into the note input PACER, on the channel set in MIDI channel for pedal messages (default 1). An instrument only hears them on a track whose input is PACER or All ins, armed or monitoring. The Pacer's display keeps showing CC 116 and 117: that is correct, the extension converts them inside Bitwig.

100 % 50 % 0 % heel half way toe pedal position
Linear Inverted Slow start (output = position²) Fast start (output = √position) Linear, heel 20 %, toe 70 %
Slow start gives fine control near the heel, good for volume swells; fast start near the toe. Heel and toe set the range, e.g. 20–70 % keeps a filter in its sweet spot; a heel above the toe reverses the pedal.

A parameter target with a linear response and the full range is bound directly, so Bitwig's own pickup behaviour applies. Every other combination is calculated by the extension.

Pedal takeover
What the first move does after a pedal got its target: a mode change, a new target in the settings, startup. Jump (the default) sets the target to where the pedal is. Pick up leaves the target where it is until the pedal reaches it, or passes it between two moves, and follows from then on: switch from the Looper (master volume) to the FX mode and back with the pedal at the heel, and the master stays put until you bring the pedal up to it. MIDI targets pick up from the last value the pedal sent them. With pick-up every target is calculated by the extension, none is bound directly.
All loop tracks
One fader over the loops that keeps their balance: at the toe every loop track is at its own level, at the heel all are silent, in between each is its level times the pedal. The levels are taken from the tracks the first time the pedal moves. Change a level in Bitwig while the pedal rests (half a second is enough) and the fader keeps it, at the pedal's position; moving the loop track window gives the tracks their own levels back.
The loop being recorded
Follows the recording from track to track; with nothing recording, the loop recorded last in the row, else the selected loop track. With pick-up, a new recording is picked up again.

LEDs

While the transport runs, blinking follows the beat (setting Blink in time with the transport); when it is stopped, LEDs blink on the wall clock. The demos below run at 120 bpm.

SolidOn: a stopped or muted loop, a switch whose action is on
Gap on the downbeatPlaying, recording or overdubbing loop
Blink every beatA fade running, a muted FX instrument, a snapshot changed since it was recalled
Fast blink, eighth notesWaiting for its quantization point, counting in, a mute waiting for its beat
Flash on the downbeatAn assigned FX instrument that is not focused
Flash every beatA switch whose tap is Tap tempo, in green

Loop switches

LoopLED
empty the mode colour, dimmed
stopped amber
playing green, with a short gap on every downbeat
muted blue
recording, overdubbing red, with a gap on the downbeat
waiting fast blink in the colour it is heading for

A switch whose tap is Loop track 1–8 lights the same way; the Looper's shifted loop switches (loop tracks 5–8) rest in cyan instead of the mode colour. The four loop colours can be changed in Pacer LEDs. Every switch rests at its mode's colour, dimmed, and lights in the colour of whatever it is doing, so the board reads even when nothing is playing. Colours are written to the Pacer as SysEx, which flashes LOAD SYS on its display for a moment; the extension only writes one when a colour really changes.

Other switches

A switch lights when its tap action has something to do: undo or redo possible, loops playing (play/stop all is green while playing, amber when loops are loaded), another row to go to (next row shows blue when it would add a scene), overdub on (red), metronome on, transport running (green), a loop muted (blue), the selected loop soloed (amber), input monitoring on (green), something to reset (purple). The one-button looper shows the loop it is busy with; fade actions blink while a fade runs; Mute/unmute loop track n is blue while that loop is muted and blinks while its mute waits for the beat. In the Looper mode, and in a custom mode of its own with loop switches, the beat counter takes over SW A–D while counting in and recording (beats, or bars with While recording, SW A-D count = Bars), except a top-row switch that is a loop switch itself.

SW 6 is white, gold while the shift layer is up, and blinking gold while it is up for the next press only. A switch whose tap raises the shift layer lights gold the same way.

FX mode

SwitchLED
FX on green
FX off, or nothing to control the mode colour, dimmed
Instrument focused the nearest Pacer colour to the track colour
Instrument assigned, not focused a flash in the track colour on the downbeat
Instrument muted red, blinking
Snapshot 1 / 2 / 3 / 4
Snapshot changed since blinking in its colour
LED test

Settings › Pacer LEDs › Test the LEDs, or the Test the LEDs action, lights every switch white, red, green, amber, blue and purple for a second each. It never runs by itself.

Other presets and Nektar DAW mode

Your other Pacer presets keep working next to PACER Looper.

Channel 16 is the looper's
PACER Looper only reacts to MIDI channel 16 on port 1. Everything else the Pacer sends reaches Bitwig through the note input PACER: pick it or All ins as a track input to play instruments, or use it for MIDI mapping. Keep other presets off channel 16, where CC 102–119 belong to the looper.
Going to another preset and back
Selecting any preset on the Pacer throws away the extension's live edits — that is what makes them free. While another preset is loaded the extension leaves it alone (the preset check). Coming back to D1 makes the preset announce itself, and the extension writes the whole board again, in the mode you were in.
When Bitwig lets go
Switching the extension off, or closing Bitwig, darkens the board and writes OFF on the display, so a Pacer nobody drives does not look live. Selecting any preset brings its own colours back.

Nektar DAW mode

Switch on Nektar DAW mode (USB port 2) › Serve the Track and Transport presets and assign port 2. The Pacer's built-in DAW presets then work as they did with Nektar's script.

Pacer DAW functionIn BitwigLED
Play · Stop · RecordTransport play/stop · stop · arranger recordPlaying · stopped · recording
Loop · Metronome · Pre-roll · OverdubArranger loop · metronome · pre-roll off or 1 bar · arranger overdubOn/off
Rewind · Fast forwardMove the play position, repeating while heldWhile held
Go to loop startStop and jump to the loop start–
Mute · Solo · ArmSelected trackState
UndoUndo–
Track − / +Previous / next track, repeating while heldWhile held
Patch − / +Previous / next device (Nektar's script browsed presets)While held
Track / master volumeSelected track / master volume–

Moving the loop region left or right is not supported yet.

Part three

Reference

Settings

Bitwig: Settings › Controllers › PACER Looper. The Project category at the end is saved with each project; Bitwig 6 does not show project settings in its own panels, so instruments are assigned from the Pacer (hold SW 1–4 in the FX mode). The loop track position is a normal setting under Looper and applies to every project.

SettingOptions
Looper
Looper MIDI channel (must match the Pacer preset)1–16, default 16. Changing it restarts the extension.
Loop tracks1–8, default 4. Loop tracks 5–8 are on the Looper's shift layer. A loop switch beyond them does nothing.
Loop switch modeTap to record, tap again to close · Hold to record, release to close
Loop switch fires on press (off: on release)On · Off
Tap on a playing loopStop · Mute/unmute · Toggle launcher overdub (note clips) · Nothing
Hold a loop switchDelete the clip · Stop · Nothing
Double-tap a loop switchNothing · Stop · Mute/unmute · Clear · Undo
Double-tap speedFast (0.25 s) · Normal (0.35 s) · Relaxed (0.5 s)
Hold time for clearing actionsNormal (0.5 s) · Long (1.5 s, default) · Very long (2.5 s). Also used for assigning FX instruments and storing snapshots.
Arm the track when recordingOn · Off
Exclusive arm (disarm finished loops)On · Off
Select the track on pressOn · Off. Pedals aimed at the selected track follow it.
Count-in from a stopped transportOff · 1 bar · 2 bars
Mute timingImmediately · On the next beat · On the next bar
Fade length1 · 2 · 4 · 8 bars
Previous / next row while loops playOnly move to it (default; play it with Play row / stop all) · Move to it and play it, when loops play and it has loops. An empty row is left alone, so the old loops play on while you record the next section.
Names for new rows (comma separated)Text, e.g. Intro, Verse, Chorus
Loop tracks start at track1–128, one value for every project. Holding SW A / SW B in the Looper mode, or tapping them in the mode menu, writes it.
Modes
Mode at startupWhatever this project used last (default) · Looper · FX pedalboard · Mixer · Song · Custom
Put the mode name back on the display after a pressOn · Off. Each restore is one SysEx, which flashes LOAD SYS.
Show what the mode is doing on the displayOn · Off. The FX mode names the focused instrument, the Looper and Song modes name the row (the scene's name, its name from Names for new rows, or ROW 3).
Show events on the display (REC 2, 4 BAR, UNDO, SNAP2...)On (default) · Off. Each event is two name writes. The words are listed under The display.
SW 6 double-tapAny action, default Shift layer on/off. Nothing makes SW 6's tap instant again.
Custom layout
The custom layout changesIts own mode (CUST, starts empty; default) · The Looper / FX / Mixer / Song mode (changes it)
Name on the display (blank: the mode's own)5 characters; blank keeps the mode's own name, CUST for a mode of its own
SW n · tap / double-tap / hold (SW 1–5, SW A–D)As in the mode (default) · any action, including Loop track 1–8, which makes it a loop switch · Nothing empties the gesture
SW n · colourAutomatic (as in the mode, or from the action; default) · Off · the Pacer's twelve colours
SW n · LEDAs in the mode (default) · Colour strip · Icon row · Word row (SW A–D have none and use the strip)
Custom layout: shift layer
SW n · shift tap / shift double-tap / shift hold (SW 1–5, SW A–D)As in the mode (default: the mode's own shift layer) · any action. A switch whose shift gestures all do Nothing keeps its normal job.
FX mode
Snapshots per instrument2 · 3 · 4
Focusing an instrument selects its track in BitwigOff · On
Remote controls page nameText, default Pacer
Footswitch jacks
FS 1–4 tap / double-tap / holdAny action, including Next mode, Go to the … mode and the shift layer actions. A tap of Loop track 1–8 makes the jack a loop switch. The same in every mode.
Expression pedals
EXP 1 · Looper / FX pedalboard / Mixer / Song / Custom, and the same for EXP 2Any pedal target, one per mode: ten settings. Defaults under Expression pedals.
EXP 1, EXP 2 responseLinear · Inverted · Slow start · Fast start
EXP 1, EXP 2 heel (minimum) / toe (maximum)0–100 %
MIDI channel for pedal messages1–16, default 1
Pedal takeover (after a mode change or a new target)Jump to the pedal (absolute, default) · Pick up: wait until the pedal passes the current value
Pacer LEDs
Blink in time with the transportOn · Off
Count beats on SW A-D (count-in and recording)On · Off
While recording, SW A-D countBeats of the bar (default) · Bars since the recording started. Count-ins always count beats.
Check the Pacer is on its presetBefore painting, and every 5 s (default) · Only before painting · Off: paint whatever preset is loaded. See The display.
Loop colour: stopped / playing / recording / mutedWhite · Red · Green · Amber · Blue · Purple
Cycle every LED through all coloursButton: Test the LEDs
Clip launcher (pushed into the project)
Launch quantizationKeep project setting · None · 1/16 · 1/8 · 1/4 · 1/2 · 1 bar · 2 bars · 4 bars · 8 bars
Loop lengthKeep project setting · Free: press again to close the loop · Match the first loop of the row · 1 / 2 / 4 / 8 bars (4/4)
Nektar DAW mode (USB port 2)
Serve the Track and Transport presets (replaces Nektar's script)Off · On
Feedback
Pop-up notificationsAll · Only important ones · Off. "Only important ones" keeps navigation, warnings, count-ins, loop lengths, resets and focus changes.
Log to the controller console (for bug reports)Off (default) · Presses, actions and modes · Everything, with every SysEx message
Project: PACER FX
Instrument A–D (track name)Text; holding SW 1–4 in the FX mode fills it in
Focused instrumentA · B · C · D

MIDI map

What the preset sends, for anyone building their own preset or script. Everything is on MIDI channel 16 (configurable), port 1. The CC numbers never change, not even between modes: a mode is a lookup table inside the extension.

ControlCCLooper modeFX mode
SW 1–SW 4102–105Loop 1–4Instrument A–D
SW 5106Undo · hold: redoSnapshots
SW 6107The mode switch, in every mode
SW A, SW B108, 109Previous / next row · hold: move the loop tracksFX 1, FX 2
SW C110Play / stop all · hold: clear rowFX 3
SW D111Overdub · hold: metronomeFX 4
FS 1–FS 4112–115Footswitch jacks, the same in every mode
EXP 1, EXP 2116, 1170–127, a target per mode
Preset loaded119127: the extension writes the whole board again
  • Switches send CC Trigger: 127 on press, 0 on release. The extension measures holds itself, so both edges matter.
  • LEDs: the extension echoes a switch's own CC back, 127 for the on colour and 0 for the off colour. Which colours those are is written live as SysEx, and changes with the mode.
  • Older presets announced themselves with 2, 17 or 18. Those values still count, so a Pacer that has not been rewritten keeps working: 17 and 18 (the retired FX preset) switch to the FX mode, anything else repaints the board and keeps the mode.
  • The full contract, including the SysEx layout of a preset, is docs/PACER-MAP.md.

Troubleshooting

Most problems are a port, a channel or a track input.

SymptomFix
"MIDI input PACER is currently being used"Nektar's own PACER script, or another controller, holds the port. Disable it in Settings › Controllers.
The pop-up shows an older versionBitwig loaded an old file. Replace Pacer4Bitwig.bwextension in Documents/Bitwig Studio/Extensions; Bitwig reloads it.
Switches do nothingIs the Pacer on D1? Does Looper MIDI channel match the preset (16)? Is port 1 set to PACER?
A switch does something unexpectedCheck the mode on the display, and hold SW 6 for the menu to pick another. Selecting D1 again repaints the board and keeps the mode.
LEDs never lightSelect the preset again on the Pacer: it announces itself and the extension writes the whole board. Then run Test the LEDs.
The display says LOAD SYS and stays thereSomething is writing SysEx continuously. The extension only writes a colour when it really changes, so a stuck display means another tool is talking to the Pacer.
The display lost the mode nameA switch press replaces it with that switch's CC readout; the extension writes the name (or the row, the instrument) back shortly after (Put the mode name back on the display after a press). Switching mode always rewrites it.
Loop switches control the wrong tracksCheck Loop tracks start at track (one value for every project), or move the loop track window from the Pacer: hold SW A / SW B in the Looper mode, or tap SW A / SW B in the mode menu.
A loop switch does nothingThe project has fewer loop tracks than that switch: with Loop tracks = 3, SW 4 does nothing, and the shifted SW 1–4 need loop tracks 5–8. Raise Loop tracks.
I hear my input twiceSeveral armed tracks with auto monitoring. Keep Exclusive arm on, or use a dedicated input track.
My Push jumps to the loop trackThe looper selects the track it records on. Pin the Push's track, or switch off Select the track on press.
Other presets do not reach instrumentsThe track's input must be PACER or All ins, and the preset must not use channel 16.
A pedal set to mod wheel or expression does nothingThe Pacer always shows CC 116/117; the conversion happens in Bitwig. The instrument's track needs input PACER or All ins, must be armed or monitoring, and the patch must respond to that controller.
FX switches all stay dimNo instrument is focused, or its track was renamed. Select the track in Bitwig and hold its instrument switch (SW 1–4) again.
An FX switch does nothingThe track has a Pacer page and that slot is not mapped, or the track has fewer devices than the switch number.
Track and Transport presets do nothingSwitch on Nektar DAW mode and assign port 2 (MIDIIN2 (PACER) / MIDIOUT2 (PACER)).
I cannot find the project settingsBitwig 6 shows a controller's project settings nowhere in its panels (older versions listed them in the Studio I/O panel). They are still saved with the project; set them from the Pacer: in the FX mode, hold SW 1–4 to assign an instrument. The loop track position is not one of them: it is Looper › Loop tracks start at track.
A setting does not seem to applyMost apply immediately; Looper MIDI channel restarts the extension. Check Bitwig's controller console for errors.
"The Pacer is on another preset" and the board stays as it isThe extension leaves other presets alone. Select the Bitwig preset (D1) again, or press any of its switches. If that keeps happening on D1, set Check the Pacer is on its preset to Off and report it.
The display flashes LOAD SYS every five secondsThe preset check's regular question shows on the Pacer. Set Check the Pacer is on its preset to Only before painting.
SW 6 takes a moment to change the modeIt waits to see whether a double-tap follows. Set SW 6 double-tap to Nothing for an instant tap; the shift layer can go on a jack instead.
"PACER Looper caught an error … and carried on"Something went wrong and was contained. Set Log to the controller console to Presses, actions and modes, do it again, and send the lines from Bitwig's controller console with the report.
Part four

Test

Hardware checklists

Run these once with the Pacer next to you. Tick what works, and write down what you saw when something does not, so it can be fixed.

Saved in this browser

Looper mode: basics

0/10

Looper mode: performance features

0/10

Looper mode: settings, DAW mode and LEDs

0/7

Modes

0/10

Custom layout

0/6

Shift layer, pedals, display

0/14

FX mode

0/13