Understanding the Clip Launcher
Bitwig's clip launcher is a grid-based workspace where each cell holds a clip (a musical phrase, loop, or pattern). Tracks run vertically, scenes run horizontally. Launch a clip and it plays, looping until you stop it or replace it with another clip on the same track. Launch a scene and all clips in that row start simultaneously. This non-linear approach lets you build beats by combining and recombining musical elements freely.
The clip launcher panel sits on the left side of Bitwig's main window. Toggle between the clip launcher and the arranger using the panel buttons at the top of the editor area, or display both simultaneously in a split view. The split view is particularly useful during production: build ideas in the clip launcher, then drag finalized clips into the arranger.
Each clip in the launcher contains MIDI notes, audio, or both. Clips have their own loop settings, playback modes, and launch quantization. This means a drum clip can loop every 2 bars while a melody clip loops every 8 bars, creating evolving patterns from the interaction of different cycle lengths.
Creating and Recording Clips
Drawing Clips
Double-click an empty cell in the clip launcher to create a new clip. Set the clip length (1, 2, 4, or 8 bars are common). The clip editor opens at the bottom of the screen, showing a MIDI note grid or audio waveform. Draw notes directly in the grid or record from a MIDI controller. Each clip is self-contained with its own content and loop settings.
Recording into Clips
Arm a track for recording, then click an empty clip slot. Bitwig records your performance into that clip. Set the recording length in advance or record freely and trim afterward. Overdub mode lets you add notes to an existing clip while it plays, building up patterns layer by layer. This is the most musical way to build clips because you hear the result in context as you record.
Audio Clips
Drag audio files from the browser or your file system directly into clip launcher cells. Audio clips support time-stretching to match your project tempo, pitch shifting, and loop point editing. Bitwig's stretch modes (Stretch, Repitch, Slice, Raw) determine how the audio adapts to tempo changes. The Slice mode is particularly useful for drum loops, automatically dividing the audio into individual hits.
Clip Properties
| Property | Function | Production Use |
|---|---|---|
| Length | Number of bars the clip spans | Set shorter for loops, longer for phrases |
| Loop | Whether the clip repeats | On for grooves, off for one-shot transitions |
| Launch Quantize | When the clip starts after triggering | 1 bar for tight sync, none for immediate |
| Color | Visual identification | Color-code by element (red drums, blue bass) |
| Follow Action | What happens when clip ends | Chain clips for automated sequences |
Working with Scenes
What Scenes Represent
A scene is a horizontal row in the clip launcher. Each scene contains one clip per track (or empty slots for tracks that should be silent). Think of scenes as song sections: Scene 1 is your verse, Scene 2 is your chorus, Scene 3 is your bridge. Launching a scene triggers all its clips simultaneously, transitioning your entire arrangement in one action.
Building Scenes for Song Sections
Create your fullest section first (all instruments playing). Duplicate the scene and modify it: remove the bass clip for an intro scene, change the drum pattern for a chorus scene, thin out elements for a breakdown scene. Each scene becomes a self-contained section of your song that you can trigger at will.
Scene Launch Behavior
When you launch a scene, clips on each track transition according to the launch quantization setting. Global launch quantization (set in the transport bar) determines the grid. With 1-bar quantization, launched clips wait until the next bar line to start, keeping everything in sync. With no quantization, clips start immediately when triggered.
Scene Follow Actions
Scenes support follow actions that automatically advance to the next scene after the current one plays for a set number of bars. Set your verse scene to play for 8 bars then advance to the chorus scene. This creates an automated arrangement playback from the clip launcher without manual triggering.
Clip Launcher Production Workflow
Step 1: Set Up Tracks
Create tracks for each element of your beat: drums, bass, chords, melody, effects. Load instruments or audio inputs on each track. Name and color-code tracks for visual clarity. This setup is the same whether you work in the clip launcher or the arranger.
Step 2: Build Core Clips
Create a clip on each track for your main groove. Program a drum pattern, record a bass line, draw a chord progression, and add a melody. Launch all clips to hear the full combination. Adjust individual clips until the core groove feels right.
Step 3: Create Variations
Duplicate your core clips into new scenes and create variations. Change the drum pattern for the second scene, shift the bass line for the third, add a counter-melody in the fourth. Each scene becomes a different flavor of your beat that you can combine and trigger.
Step 4: Experiment with Combinations
Launch individual clips from different scenes to discover unexpected combinations. A drum pattern from Scene 3 might work better with the bass from Scene 1 and the melody from Scene 4. The clip launcher makes this experimentation instant. Mark combinations that work by creating new scenes from those clip selections.
Step 5: Arrange and Finalize
Once you have your sections defined as scenes, use the arranger to build the final song structure. Drag clips from the launcher into the arranger timeline, or use the Record to Arrangement function to capture a live performance of your scene transitions.
From Clips to Arrangement
Record to Arrangement
Enable the arranger recording while triggering scenes in the clip launcher. Bitwig captures every clip launch, scene change, and timing into the arranger timeline as a linear arrangement. This is the fastest way to turn a clip launcher session into a finished song: perform your arrangement in real time, and Bitwig writes it down for you.
Manual Arrangement
Drag individual clips from the launcher directly into specific positions on the arranger timeline. This gives you precise control over where each clip appears. Copy and paste clips to extend sections. Use the arranger's editing tools to trim, split, and crossfade clips at section boundaries.
Hybrid Workflow
Many producers use the clip launcher for the creative phase and the arranger for the finalization phase. Build all your musical ideas as clips, experiment with combinations, then switch to the arranger to create the definitive arrangement with precise transitions, automation, and structural refinements that the clip launcher cannot provide.
Live Performance with the Clip Launcher
Performance Setup
For live performance, organize your clip launcher with scenes representing song sections in performance order. Color-code scenes consistently across your set. Set launch quantization to 1 bar for safe transitions that always land on beat. Pre-listen to clips using the cue output before launching them to the main mix.
Follow Actions for Automation
Set follow actions on clips to create automated sequences within your performance. A clip can play for 4 bars, then automatically trigger the next clip in the column. This frees your hands for other performance tasks while the clip launcher advances through sections on its own. Combine manual scene launches for major transitions with follow actions for smaller variations.
Controller Mapping
Map clip launcher cells to pads on a hardware controller. Each pad triggers a clip, and LED feedback shows clip status (playing, queued, stopped). Launchpad-style controllers are designed for this workflow, but any MIDI controller with pads or buttons can be mapped. The physical interface makes live clip launching feel more like an instrument and less like clicking a mouse.
Controller Integration
Supported Controllers
Bitwig provides dedicated controller scripts for Novation Launchpad, Ableton Push (used as a generic controller), Akai APC series, and many others. These scripts map the clip launcher grid directly to the controller's pad grid with visual feedback. Load the controller script in Bitwig's Controller Preferences, and the clip launcher becomes a tactile, physical instrument.
Custom MIDI Mapping
For controllers without dedicated scripts, use Bitwig's generic MIDI mapping. Enter MIDI learn mode, click a clip launcher cell, and press the corresponding pad on your controller. Map scene launch buttons, stop buttons, and transport controls the same way. Custom mappings are saved with your project or as global controller templates.
Keyboard Shortcuts
Without a controller, use keyboard shortcuts for fast clip launching. Number keys trigger scenes, and you can assign keys to individual clip slots. The Space bar starts and stops playback. Enter launches the selected scene. Arrow keys navigate the clip launcher grid. Master these shortcuts for efficient clip-based production without any hardware beyond your keyboard.
Frequently Asked Questions
What is the difference between the clip launcher and the arranger in Bitwig?
The clip launcher is a non-linear workspace where clips exist in a grid of tracks and scenes. You trigger clips manually or by launching scenes, and they loop until you stop them or launch different clips. The arranger is a traditional linear timeline where clips are placed at specific positions and play back in sequence. The clip launcher is ideal for experimentation and live performance. The arranger is ideal for final arrangement and mixing. Bitwig lets you switch between them or use both simultaneously.
Can I use the clip launcher for live performance?
Yes. The clip launcher is designed for live performance workflows. Assign clips to controller pads, set up scenes for song sections, and trigger them in real time. Bitwig's clip launcher supports follow actions (clips automatically trigger other clips after playing), which lets you create semi-automated live sets. Combine with hardware controllers like Launchpad, Push, or any MIDI controller for hands-on clip launching.
How do I convert clip launcher sessions into a linear arrangement?
Bitwig provides a direct workflow for this. Select scenes in the clip launcher and use the Record to Arrangement function. Bitwig records your clip launching performance into the arranger timeline in real time. Alternatively, drag individual clips from the launcher directly into the arranger at specific positions. Both methods transfer your session ideas into a finalized arrangement.
Can clips have different lengths on the same scene?
Yes. Each clip in a scene can have a different length. A drum clip might be 4 bars while a bass clip is 2 bars and a melody clip is 8 bars. When launched together in a scene, each clip loops independently at its own length, creating polyrhythmic interactions. This is a powerful technique for creating evolving patterns from simple elements.
Does Bitwig's clip launcher support follow actions?
Yes. Bitwig supports follow actions that determine what happens when a clip finishes playing. Options include playing the next clip, playing a random clip, stopping, or returning to a specific clip. Follow actions enable automated clip sequences that can run without manual triggering, useful for both live performance and generative music approaches.