This guide establishes Ableton Live 12 as the central "hub" and source of truth for arrangement, tempo, and project coordination, while leveraging Bitwig Studio for specialized synthesis/sound design and Studio One Pro 7 for its unique lyrics management features (Global Lyrics Track, Lyrics Display, Lyric Lanes, and Show Page integration) AND vocal recording capabilities.
Architectural Philosophy:
- Ableton = Main Timeline: All arrangement decisions, tempo changes, and project structure
- Bitwig = Specialized Instruments: Advanced synthesis, modular routing, creative sound design
- Studio One = Lyrical Excellence & Vocal Recording: Unique lyrics management capabilities — Global Lyrics Track, synchronized Lyrics Display, Lyric Lanes for melodic alignment, and Show Page for live performance — features not available in any other DAW. Also serves as dedicated vocal recording environment with lyrics display integration.
- OMNIBUS 3.0 = Audio Router: Bidirectional, bit-perfect audio routing between all DAWs
- LISTENTO = MIDI Coordinator: Low-latency MIDI streaming for instrument control across DAWs
- Hub Architecture Overview
- System-Wide Prerequisites
- OMNIBUS 3.0 Hub Configuration
- LISTENTO Hub Configuration
- Ableton Live 12: Main Hub Setup
- Bitwig Studio: Instrument Satellite Setup
- Studio One Pro 7: Lyrics & Vocal Recording Satellite Setup
- Complete Hub Workflow Examples
- Advanced Routing Matrices
- Troubleshooting
In this configuration, Ableton Live 12 serves as the central hub that coordinates all aspects of music production across three professional DAWs:
╔═══════════════════════════════╗
║ ABLETON LIVE 12 (HUB) ║
║ • Main Arrangement ║
║ • Tempo & Time Signature ║
║ • Main Mix Bus ║
║ • MIDI Coordination ║
║ • Audio Consolidation ║
╚═══════════════════════════════╝
▲ ▲
OMNIBUS │ │ OMNIBUS
+ LISTENTO │ │ + LISTENTO
│ │
╔══════════════════╩═╗ ╔═╩══════════════════════════════════════╗
║ BITWIG STUDIO ║ ║ STUDIO ONE PRO 7 ║
║ (Instrument ║ ║ (Lyrics & ║
║ Satellite) ║ ║ Vocal Recording ║
║ • Synthesis ║ ║ Satellite) ║
║ • Sound Design ║ ║ • Global Lyrics Track ║
║ • Modular FX ║ ║ • Lyrics Display ║
║ ║ ║ • Lyric Lanes ║
║ ║ ║ • Show Page (Live) ║
╚════════════════════╝ ╚════════════════════════════════════════╝
Audio Flow:
- Bitwig → OMNIBUS → Ableton (Instruments/FX send audio to main timeline)
- Studio One → OMNIBUS → Ableton (Vocals/instruments recorded in Studio One)
- Ableton → OMNIBUS → Bitwig (Reference/backing tracks for context)
- Ableton → OMNIBUS → Studio One (Mix/backing track for lyrics synchronization and vocal monitoring)
MIDI Flow:
- Ableton → LISTENTO → Bitwig (Control Bitwig instruments from Ableton arrangement)
- Ableton → LISTENTO → Studio One (Sync tempo/time signature for lyrics alignment, control Studio One instruments)
- Bitwig → LISTENTO → Ableton (Bitwig controllers can trigger Ableton instruments)
- Studio One → LISTENTO → Ableton (Studio One controllers can trigger Ableton instruments)
Ableton Live 12 (Main Hub):
- Holds the authoritative project arrangement and structure
- Defines all tempo, time signature, and timing changes
- Receives audio from all satellite DAWs via OMNIBUS
- Sends MIDI to control instruments in satellite DAWs via LISTENTO
- Performs final mixing
- Exports final rendered audio
Bitwig Studio (Instrument Satellite):
- Provides specialized synthesis (The Grid, Polymer, Phase-4)
- Generates audio sent to Ableton via OMNIBUS
- Receives MIDI control from Ableton via LISTENTO
- Can optionally receive Ableton's backing track for context
Studio One Pro 7 (Lyrics & Vocal Recording Satellite):
- Primary Functions: Lyrics management AND vocal recording with integrated lyrics display
- Global Lyrics Track: Create and manage lyrics directly on the Song timeline with beat-based or second-based synchronization
- Lyrics Display: Synchronized lyrics display window for vocalist reference during recording or live performance
- Lyric Lanes: Tie syllables to MIDI notes for precise melodic alignment in Piano Roll and Score View
- Show Page Integration: Extend lyrics features to live performance teleprompter-style displays
- Vocal Recording Environment: Record vocals with integrated lyrics display, send recorded audio to Ableton via OMNIBUS
- Receives tempo/time signature sync from Ableton via LISTENTO for lyrics alignment
- Receives backing track from Ableton via OMNIBUS for lyrics synchronization reference
- See Studio One Pro 7 — Lyrics-Specific Features for detailed implementation
Critical: All three DAWs must use identical sample rates for bit-perfect audio routing.
Recommended Setting: 48000 Hz
Configuration Locations:
Ableton: Preferences → Audio → Sample Rate: 48000 Hz
Bitwig: Settings → Audio → Sample Rate: 48000 Hz
Studio One: Options → Audio Setup → Sample Rate: 48000 Hz
OMNIBUS: Settings → Audio Settings → Sample Rate: 48000 Hz
For Ableton (Main Hub):
Standard Work: 128 samples
Mixing: 256-512 samples
Reason: Hub processes audio from multiple sources, needs CPU headroom
For Bitwig (Instrument Satellite):
Playing Instruments: 64 samples
Sound Design: 128 samples
Reason: Low latency needed for real-time instrument performance
For Studio One (Lyrics & Vocal Recording Satellite):
Vocal Recording: 64-128 samples
Lyrics Management: 128-256 samples
Reason: Low latency for real-time vocal monitoring; standard buffer sufficient for lyrics sync
For OMNIBUS:
Standard: 64 samples
High-Performance: 128 samples
Total Roundtrip: DAW buffer + OMNIBUS buffer
Location: OMNIBUS menu → Settings → Audio Settings
-
Sample Rate: 48000 Hz
- Must match all three DAWs exactly
-
Buffer Size: 64 samples
- Optimal for hub architecture
- Total latency with 128-sample DAW buffer: ~4ms @ 48kHz
-
Clock Drift Compensation: DISABLED
- Critical: Must be disabled for bit-perfect audio
-
MIDI Input: Select MIDI device (optional for snapshot switching)
Visual Settings:
UI Scaling: 100% (adjust for display)
Device Coloring: ENABLED
Show Routing Matrix: ENABLED
Keep Always on Top: ENABLED (during initial setup)
Runtime Settings:
Run at Startup: ENABLED
Turn off Audio Engine when quitting: DISABLED
Lock I/O Levels: ENABLED (after calibration)
Location: OMNIBUS → Add button → OMNIBUS Virtual Devices
Name: OMNIBUS Device A
Channels: 64 channels (32 stereo pairs)
Purpose: Bidirectional audio between Bitwig and Ableton
Architecture:
├─ Channels 1-32: Bitwig → Ableton (Instruments)
└─ Channels 33-64: Ableton → Bitwig (Reference/Backing)
Usage Breakdown:
Bitwig → Ableton (Ch 1-32):
├─ Ch 1-2: The Grid Output 1
├─ Ch 3-4: The Grid Output 2
├─ Ch 5-6: Polymer Synth
├─ Ch 7-8: Phase-4 Synth
├─ Ch 9-10: Bass Instrument
├─ Ch 11-12: Pad/Atmosphere
└─ Ch 13-32: Additional instruments (10 stereo pairs available)
Ableton → Bitwig (Ch 33-64):
├─ Ch 33-34: Main Reference Mix
├─ Ch 35-36: Drums/Rhythm Section
├─ Ch 37-38: Bass Reference
└─ Ch 39-64: Additional backing tracks (13 stereo pairs available)
Setup Steps:
- Click "Add" in OMNIBUS device list
- Select "OMNIBUS Virtual Devices"
- Channel count: 64
- Name: "Bitwig ↔ Ableton Hub"
- Click OK
Name: OMNIBUS Device B
Channels: 64 channels (32 stereo pairs)
Purpose: Audio routing from Ableton to Studio One for lyrics synchronization reference
Architecture:
├─ Channels 1-32: Reserved for future expansion (if needed)
└─ Channels 33-64: Ableton → Studio One (Mix/Reference for lyrics sync)
Usage Breakdown:
Ableton → Studio One (Ch 33-64):
├─ Ch 33-34: Main Mix (for lyrics synchronization reference)
├─ Ch 35-36: Minus-One Mix (mix without vocals, for reference)
├─ Ch 37-38: Click/Metronome (for timing reference)
└─ Ch 39-64: Stem sends (13 stereo pairs available for reference)
Setup Steps:
- Click "Add" in OMNIBUS device list
- Select "OMNIBUS Virtual Devices"
- Channel count: 64
- Name: "Studio One ↔ Ableton Hub"
- Click OK
Name: OMNIBUS Device C
Channels: 32 channels (16 stereo pairs)
Status: Reserved for future expansion (not needed for lyrics and vocal recording Studio One workflow)
Purpose: Could be used for specialized workflows if needed
Note: Since Studio One is used for lyrics management and vocal recording management in this hub architecture,
direct routing between Bitwig and Studio One is not required. This device can be created
but will typically remain unused in the lyrics-focused workflow.
Setup Steps:
- Click "Add" in OMNIBUS device list
- Select "OMNIBUS Virtual Devices"
- Channel count: 32
- Name: "Bitwig ↔ Studio One Direct"
- Click OK
Name: OMNIBUS Device D
Status: Can be created as needed
Purpose: Additional routing or hardware integration
Suggested Uses:
├─ External hardware synthesizers
├─ Outboard effects processors
├─ Additional computer routing
└─ Network audio via AVB/NDI
Note: Up to 4 OMNIBUS virtual devices can be created total
Location: OMNIBUS main window → Routing Matrix
Location: OMNIBUS → Add button (top of devices window)
Add the following:
- All hardware audio interfaces
- OMNIBUS Device A (Bitwig ↔ Ableton Hub)
- OMNIBUS Device B (Studio One ↔ Ableton Hub)
- OMNIBUS Device C (Bitwig ↔ Studio One Direct)
- (Optional) Application Capture sources
How to Create Routes:
- Hover over cell: See source → destination
- Click cell: Create single route
- Click + Drag: Create multiple contiguous routes
- Diagonal Drag: Route multiple channels in series
Matrix Configuration for "Full Hub Production" mode:
═══════════════════════════════════════════════════════════
BITWIG → ABLETON ROUTING
═══════════════════════════════════════════════════════════
Source: Bitwig Output → OMNIBUS Device A Input Ch 1-32
Destination: OMNIBUS Device A Output Ch 1-32 → Ableton Input
Actions in Matrix:
1. Locate Bitwig output rows in left column
2. Locate OMNIBUS Device A Output columns at top
3. Click cells to route:
- Bitwig Out 1 → Device A Out Ch 1
- Bitwig Out 2 → Device A Out Ch 2
- Bitwig Out 3 → Device A Out Ch 3
- Continue for all 32 channels
4. Use click-drag for faster multi-channel routing
═══════════════════════════════════════════════════════════
ABLETON → BITWIG ROUTING
═══════════════════════════════════════════════════════════
Source: Ableton Output → OMNIBUS Device A Input Ch 33-64
Destination: OMNIBUS Device A Output Ch 33-64 → Bitwig Input
Actions in Matrix:
1. Locate Ableton output rows designated for Bitwig
2. Locate OMNIBUS Device A Output Ch 33-34, 35-36, etc.
3. Click cells to route backing tracks to Bitwig
═══════════════════════════════════════════════════════════
STUDIO ONE → ABLETON ROUTING
═══════════════════════════════════════════════════════════
Source: Studio One Output → OMNIBUS Device B Input Ch 1-32
Destination: OMNIBUS Device B Output Ch 1-32 → Ableton Input
Actions in Matrix:
1. Locate Studio One output rows
2. Locate OMNIBUS Device B Output columns
3. Click cells to route vocals/audio to Ableton
═══════════════════════════════════════════════════════════
ABLETON → STUDIO ONE ROUTING
═══════════════════════════════════════════════════════════
Source: Ableton Output → OMNIBUS Device B Input Ch 33-64
Destination: OMNIBUS Device B Output Ch 33-64 → Studio One Input
Actions in Matrix:
1. Locate Ableton outputs for Studio One monitoring
2. Locate OMNIBUS Device B Output Ch 33-34, etc.
3. Click cells to route mix to Studio One for vocal monitoring
═══════════════════════════════════════════════════════════
BITWIG ↔ STUDIO ONE DIRECT (Optional)
═══════════════════════════════════════════════════════════
Source: Bitwig/Studio One → OMNIBUS Device C
Destination: OMNIBUS Device C → Studio One/Bitwig
Note: Create these routes only when direct satellite-to-satellite
routing is needed for specialized workflows
Visual Confirmation:
- Routed cells show colored indicators
- Device coloring helps identify connection paths
- Matrix displays all active routes
Location: OMNIBUS → Snapshots tab
Description: All three DAWs active with full bidirectional routing
Configuration:
Active Routes:
✓ Bitwig → Ableton (All 32 channels)
✓ Ableton → Bitwig (Backing tracks Ch 33-40)
✓ Studio One → Ableton (All 32 channels)
✓ Ableton → Studio One (Mix + Click Ch 33-38)
✗ Bitwig ↔ Studio One Direct (Disabled for hub-centric routing)
Purpose: Complete multi-DAW production with Ableton as hub
CPU Load: High (all routing active)
Use Case: Full production sessions
Steps to Create:
- Configure all routes as described above in matrix
- Click "Save As" button in Snapshots tab
- Name: "Full Hub Production"
- Right-click snapshot number
- Select "Assign Hotkey"
- Choose: Cmd+1 (Mac) / Ctrl+1 (Win)
Description: Optimize routing for Bitwig instrument creation
Configuration:
Active Routes:
✓ Bitwig → Ableton (Instruments Ch 1-16 only, 8 stereo pairs)
✓ Ableton → Bitwig (Reference mix Ch 33-34)
✗ Studio One routes (Disabled)
✗ Ableton → Studio One (Disabled)
Purpose: Focus on Bitwig synthesis with minimal Ableton backing
CPU Load: Medium (reduced routing)
Use Case: Sound design sessions, creating new instruments
Description: Optimize for lyrics management and vocal recording workflow with Studio One
Configuration:
Active Routes:
✗ Bitwig routes (Disabled)
✗ Studio One → Ableton routes (Disabled - Studio One used only for lyrics)
✓ Ableton → Studio One (Mix + Click Ch 33-38)
Purpose: Lyrics synchronization reference from Ableton to Studio One
CPU Load: Low (minimal routing)
Use Case: Vocal recording sessions in Ableton with lyrics display from Studio One
Description: Ableton-only mode, all satellites disabled
Configuration:
Active Routes:
✗ All OMNIBUS virtual device routes disabled
✓ Hardware interface only (direct monitoring)
Purpose: Work exclusively in Ableton without satellite DAWs
CPU Load: Minimal (no virtual routing)
Use Case: Ableton-native instrument sessions, arrangement work
Description: Route Ableton tracks through Bitwig effects chains
Configuration:
Active Routes:
✓ Ableton → Bitwig (Sends Ch 33-48, 8 stereo pairs)
✓ Bitwig → Ableton (Returns Ch 1-16, 8 stereo pairs)
✗ Studio One routes (Disabled)
Purpose: Use Bitwig's modular FX on Ableton tracks
CPU Load: Medium
Use Case: Creative effects processing, Grid-based effects
| Snapshot | Hotkey | Bitwig→Abl | Abl→Bitwig | S1→Abl | Abl→S1 | CPU | Use Case |
|---|---|---|---|---|---|---|---|
| Full Hub Production | Cmd+1 | ✓ Full | ✓ Partial | ✓ Full | ✓ Partial | High | Complete production |
| Bitwig Sound Design | Cmd+2 | ✓ Partial | ✓ Ref | ✗ | ✗ | Med | Synthesis focus |
| S1 Lyrics Sync | Cmd+3 | ✗ | ✗ | ✗ | ✓ Partial | Low | Lyrics management sessions |
| Ableton Hub Solo | Cmd+4 | ✗ | ✗ | ✗ | ✗ | Min | Ableton-only work |
| Bitwig FX Processing | Cmd+5 | ✓ Partial | ✓ Partial | ✗ | ✗ | Med | Effects routing |
Snapshot Management:
Using MIDI for Snapshot Switching:
Location: OMNIBUS → File menu → Save Session As...
Save Hub Configuration:
- Click OMNIBUS menu → Save Session As...
- Name: "Multi-DAW-Hub-Config-[Date].omnibus"
- Location: Dedicated project config folder
- Include: All devices, routes, and snapshots
Backup Strategy:
├─ Save after initial setup complete
├─ Save after major routing changes
├─ Save snapshot variations for different projects
└─ Export/backup .omnibus files to cloud storage
Loading Sessions:
- OMNIBUS menu → Open Session...
- Select .omnibus file
- All routes and snapshots restored
In the hub configuration, LISTENTO coordinates MIDI communication so that:
- Ableton can control instruments in Bitwig and Studio One
- Bitwig and Studio One can send MIDI back to control Ableton
- All MIDI is routed with minimal latency (typically 100-200ms)
Key Principle: Each MIDI connection requires:
- LISTENTO Instrument on the sending track (transmitter)
- LISTENTO Receiver on the receiving track (receiver)
- Matching session name between transmitter and receiver
- Virtual MIDI port configured in receiving DAW
Installation:
- Download LISTENTO from Audiomovers account
- Install plugins for all three DAWs
- Authorize with Audiomovers account
Installed Components:
- LISTENTO Plugin (audio transmission)
- LISTENTO Instrument Plugin (MIDI transmission)
- LISTENTO Receiver Plugin (audio + MIDI reception)
- LISTENTO Application (standalone, optional)
Plugin Formats:
- macOS: VST3, AU, AAX
- Windows: VST3, AAX
Standardized Naming System for Hub Architecture:
Format: [Source]-[Instrument/Purpose]-To[Destination]
Examples:
├─ "Abl-Grid-ToBitwig" → Ableton controls The Grid in Bitwig
├─ "Abl-Poly-ToBitwig" → Ableton controls Polymer in Bitwig
├─ "Bit-Grid-ToAbl" → Bitwig sends Grid notes to Ableton instrument
├─ "Abl-Bass-ToS1" → Ableton controls bass instrument in Studio One
└─ "S1-Vocal-ToAbl" → Studio One sends vocal MIDI to Ableton (for triggers)
Abbreviations:
- Abl = Ableton
- Bit = Bitwig
- S1 = Studio One
- Grid = The Grid
- Poly = Polymer
- P4 = Phase-4
Hub-Specific Recommendations:
For Ableton → Satellite MIDI:
"Hub-[InstrumentName]-To[DAW]"
Examples:
├─ "Hub-GridLead-ToBitwig"
├─ "Hub-PolyPad-ToBitwig"
└─ "Hub-VocalSynth-ToS1"
For Satellite → Ableton MIDI:
"[DAW]-Return-ToHub"
Examples:
├─ "Bitwig-Return-ToHub"
└─ "S1-Return-ToHub"
Location: LISTENTO Plugin → Security icon
Recommended Settings:
Session Password: Optional (use for project security)
Session Lock: DISABLED (allow dynamic connections)
Allow Recording: ENABLED (receivers can record streams)
For Hub Architecture:
- Password: Use if working with multiple collaborators
- No Password: Simpler for single-user multi-DAW setup
- Consistent Passwords: Use same password across all hub sessions for simplicity
Recommended Latency Settings:
Local Network (Same Computer):
├─ MIDI Latency: 100-150ms
├─ Audio Latency: 200ms
└─ Reasoning: Minimize latency for same-machine routing
Remote Collaboration:
├─ MIDI Latency: 200-300ms
├─ Audio Latency: 400-600ms
└─ Reasoning: Compensate for internet latency
Latency Adjustment Strategy:
- Start High: Begin with 200ms MIDI latency
- Test Stability: Play complex MIDI patterns
- Reduce Gradually: Lower by 25ms increments
- Monitor Dropouts: Watch MIDI Activity Indicator
- Find Sweet Spot: Use lowest stable latency
macOS:
- LISTENTO automatically creates virtual MIDI ports
- Each LISTENTO Receiver instance creates its own port
- Ports appear in DAW MIDI device lists
Virtual MIDI Port Naming:
Automatically created by LISTENTO Receiver:
├─ "LISTENTO Receiver Port 1"
├─ "LISTENTO Receiver Port 2"
├─ "LISTENTO Receiver Port 3"
└─ etc.
Configuration in DAWs:
- Ableton: Enable in Link, Tempo & MIDI preferences
- Bitwig: Add in Controllers preferences
- Studio One: Add in External Devices preferences
For Multiple Simultaneous Instruments:
Strategy 1: Individual Sessions (Recommended for Hub)
Each instrument = Unique session name
Advantages:
├─ Independent latency control per instrument
├─ Selective routing (only load sessions you need)
├─ Easier troubleshooting
└─ Lower CPU when not using all satellites
Example:
├─ MIDI Track 1: "Hub-Grid1-ToBitwig"
├─ MIDI Track 2: "Hub-Grid2-ToBitwig"
└─ MIDI Track 3: "Hub-Poly-ToBitwig"
Strategy 2: Shared Session
Multiple instruments = Same session name
Advantages:
├─ Single link for multiple instruments
├─ Receiver can switch between streams
└─ Simpler session management
Example:
├─ MIDI Track 1, 2, 3: "Hub-Multi-ToBitwig"
└─ Receiver switches between Track 1/2/3 streams
Ableton Live 12 serves as the main coordinator for the entire multi-DAW production system:
Responsibilities:
- Main Arrangement: All clips, scenes, and timeline structure
- Tempo & Time Signature: Authoritative source for project timing
- MIDI Transmission: Sends MIDI to control satellite DAW instruments
- Audio Aggregation: Receives audio from all satellite DAWs
- Mixing: Final mix bus processing
- Export: Renders final audio files
Data Inputs:
- OMNIBUS Device A Output Ch 1-32 (from Bitwig)
- OMNIBUS Device B Output Ch 1-32 (from Studio One)
- LISTENTO Receiver virtual MIDI (from Bitwig/Studio One for return control)
Data Outputs:
- LISTENTO Instrument (MIDI to Bitwig/Studio One)
- OMNIBUS Device A Input Ch 33-64 (audio to Bitwig)
- OMNIBUS Device B Input Ch 33-64 (audio to Studio One)
Location: Ableton → Preferences (Cmd+,) → Audio tab
Recommendation: Use Aggregate Device or OMNIBUS Virtual Devices
Option A: Macrouter/Aggregate Device (Recommended)
Audio Device: Create Aggregate Device in Audio MIDI Setup
Includes:
├─ OMNIBUS Device A
├─ OMNIBUS Device B
├─ Your hardware audio interface
└─ Allows simultaneous access to all devices
Option B: OMNIBUS Virtual Device Only
Audio Device: OMNIBUS Device A
Note: Limits hardware I/O but simplifies routing
Suitable for: Projects primarily using virtual routing
Configuration:
Sample Rate: 48000 Hz
Buffer Size: 128 samples (standard) to 256 samples (mixing)
Latency Compensation:
├─ Driver Error Compensation: ENABLED
├─ Reduce Latency When Monitoring: ENABLED
└─ Purpose: Maintain timing accuracy across satellites
Buffer Size Strategy:
Recording Satellite Instruments: 128 samples
Mixing with Effects: 256 samples
Final Mixing: 512 samples (maximum stability)
Location: Preferences → Audio → Input Config / Output Config
Enable OMNIBUS Virtual Device Channels:
- Click "Input Config" button
- Enable all channels from OMNIBUS Devices (yellow = active)
Channel Setup:
OMNIBUS Device A (Bitwig → Ableton):
✓ Ch 1-2, 3-4, 5-6, 7-8, 9-10, 11-12, 13-14, 15-16
✓ Ch 17-18, 19-20, 21-22, 23-24, 25-26, 27-28, 29-30, 31-32
Total: 16 stereo pairs from Bitwig
OMNIBUS Device B (Studio One → Ableton):
✓ Ch 1-2, 3-4, 5-6, 7-8, 9-10, 11-12, 13-14, 15-16
✓ Ch 17-18, 19-20, 21-22, 23-24, 25-26, 27-28, 29-30, 31-32
Total: 16 stereo pairs from Studio One
Hardware Interface Inputs (if using Aggregate):
✓ Physical inputs 1-8 (for direct recording if needed)
Enable OMNIBUS Virtual Device Outputs:
- Click "Output Config" button
- Enable channels for sending to satellites
Channel Setup:
OMNIBUS Device A Ch 33-64 (Ableton → Bitwig):
✓ Ch 33-34: Main Reference Mix
✓ Ch 35-36: Drums Reference
✓ Ch 37-38: Bass Reference
✓ Ch 39-40: Additional backing
Total: 16 stereo pairs to Bitwig
OMNIBUS Device B Ch 33-64 (Ableton → Studio One):
✓ Ch 33-34: Main Mix for monitoring
✓ Ch 35-36: Minus-One Mix (no vocals)
✓ Ch 37-38: Click/Metronome
✓ Ch 39-64: Stem sends (13 stereo pairs)
Total: 16 stereo pairs to Studio One
Hardware Interface Outputs:
✓ Physical outputs 1-2 (Main monitoring)
✓ Physical outputs 3-4 (Headphone monitoring)
Location: Preferences → Audio → Input/Output Config → Right-click channel
Recommended Names:
Inputs (from satellites):
├─ "Bitwig Grid 1" (Device A Ch 1-2)
├─ "Bitwig Grid 2" (Device A Ch 3-4)
├─ "Bitwig Polymer" (Device A Ch 5-6)
├─ "S1 Lead Vocal" (Device B Ch 1-2)
├─ "S1 Harmony 1" (Device B Ch 3-4)
└─ etc.
Outputs (to satellites):
├─ "To Bitwig Mix" (Device A Ch 33-34)
├─ "To S1 Monitor" (Device B Ch 33-34)
├─ "To S1 Click" (Device B Ch 37-38)
└─ etc.
Location: Preferences → Link, Tempo & MIDI
MIDI Ports Table Configuration:
┌─────────────────────┬───────┬──────┬────────┬─────┐
│ Port Name │ Track │ Sync │ Remote │ MPE │
├─────────────────────┼───────┼──────┼────────┼─────┤
│ LISTENTO Port 1 │ ON │ OFF │ OFF │ OFF │ ← For receiving from Bitwig
│ LISTENTO Port 2 │ ON │ OFF │ OFF │ OFF │ ← For receiving from S1
│ LISTENTO Port 3 │ ON │ OFF │ OFF │ OFF │ ← Additional receives
│ Your MIDI Keyboard │ ON │ OFF │ OFF │ OFF │ ← Physical controller
└─────────────────────┴───────┴──────┴────────┴─────┘
Configuration:
- Track: ON (enables MIDI for track routing)
- Sync: OFF (manual transport, no MIDI clock sync)
- Remote: OFF (not using for parameter control)
- MPE: OFF (unless using MPE-capable controller)
Why Sync = OFF:
In hub architecture, Ableton is the main timeline. Satellite DAWs do NOT need to sync transport via MIDI Clock. Instead:
- You manually start/stop playback in each DAW as needed
- MIDI notes stream via LISTENTO for instrument control
- Audio routing via OMNIBUS maintains phase coherence
Recommended Track Layout in Ableton Session View:
════════════════════════════════════════════════════
GROUP 1: SATELLITE AUDIO RETURNS
════════════════════════════════════════════════════
│
├─ Return Track 1: "Bitwig Grid 1"
│ ├─ Type: Return Track
│ ├─ Input: Ext. In → OMNIBUS Device A → Ch 1-2
│ ├─ Monitor: In
│ └─ Purpose: Receive Bitwig The Grid Output 1
│
├─ Return Track 2: "Bitwig Grid 2"
│ ├─ Type: Return Track
│ ├─ Input: Ext. In → OMNIBUS Device A → Ch 3-4
│ ├─ Monitor: In
│ └─ Purpose: Receive Bitwig The Grid Output 2
│
├─ Return Track 3: "Bitwig Polymer"
│ ├─ Type: Return Track
│ ├─ Input: Ext. In → OMNIBUS Device A → Ch 5-6
│ ├─ Monitor: In
│ └─ Purpose: Receive Bitwig Polymer Synth
│
├─ Return Track 4: "Bitwig Phase-4"
│ ├─ Type: Return Track
│ ├─ Input: Ext. In → OMNIBUS Device A → Ch 7-8
│ ├─ Monitor: In
│ └─ Purpose: Receive Bitwig Phase-4 Synth
│
├─ [Additional Bitwig return tracks...]
│
├─ Return Track 9: "S1 Lead Vocal"
│ ├─ Type: Return Track
│ ├─ Input: Ext. In → OMNIBUS Device B → Ch 1-2
│ ├─ Monitor: In
│ └─ Purpose: Receive Studio One lead vocal
│
├─ Return Track 10: "S1 Harmony 1"
│ ├─ Type: Return Track
│ ├─ Input: Ext. In → OMNIBUS Device B → Ch 3-4
│ ├─ Monitor: In
│ └─ Purpose: Receive Studio One harmony vocal 1
│
└─ [Additional Studio One return tracks...]
════════════════════════════════════════════════════
GROUP 2: MIDI CONTROL TO SATELLITES
════════════════════════════════════════════════════
│
├─ MIDI Track 1: "Control Bitwig Grid 1"
│ ├─ Type: MIDI Track (no instrument loaded)
│ ├─ Plugin: LISTENTO Instrument
│ ├─ Session: "Hub-Grid1-ToBitwig"
│ ├─ Latency: 150ms
│ ├─ Password: [Optional]
│ └─ Purpose: Send MIDI notes to control Bitwig The Grid instance 1
│
├─ MIDI Track 2: "Control Bitwig Grid 2"
│ ├─ Type: MIDI Track
│ ├─ Plugin: LISTENTO Instrument
│ ├─ Session: "Hub-Grid2-ToBitwig"
│ └─ Purpose: Control Bitwig The Grid instance 2
│
├─ MIDI Track 3: "Control Bitwig Polymer"
│ ├─ Type: MIDI Track
│ ├─ Plugin: LISTENTO Instrument
│ ├─ Session: "Hub-Poly-ToBitwig"
│ └─ Purpose: Control Bitwig Polymer synth
│
├─ MIDI Track 4: "Control Bitwig Phase-4"
│ ├─ Type: MIDI Track
│ ├─ Plugin: LISTENTO Instrument
│ ├─ Session: "Hub-P4-ToBitwig"
│ └─ Purpose: Control Bitwig Phase-4 synth
│
├─ MIDI Track 5: "Control S1 Bass"
│ ├─ Type: MIDI Track
│ ├─ Plugin: LISTENTO Instrument
│ ├─ Session: "Hub-Bass-ToS1"
│ └─ Purpose: Control Studio One bass instrument
│
└─ [Additional satellite control MIDI tracks...]
════════════════════════════════════════════════════
GROUP 3: ABLETON-NATIVE INSTRUMENTS
════════════════════════════════════════════════════
│
├─ Instrument Track 1: "Ableton Drums"
│ ├─ Type: MIDI/Instrument Track
│ ├─ Instrument: Drum Rack
│ └─ Purpose: Native Ableton drum programming
│
├─ Instrument Track 2: "Ableton Bass"
│ ├─ Type: MIDI/Instrument Track
│ ├─ Instrument: Wavetable
│ └─ Purpose: Native Ableton bass sounds
│
├─ Instrument Track 3: "Ableton Lead"
│ ├─ Type: MIDI/Instrument Track
│ ├─ Instrument: Operator
│ ├─ Plugin: LISTENTO Receiver (optional, for Bitwig control)
│ └─ Purpose: Native lead, can be controlled from satellites
│
└─ [Additional native Ableton tracks...]
════════════════════════════════════════════════════
GROUP 4: SATELLITE AUDIO SENDS
════════════════════════════════════════════════════
│
├─ Audio Track 1: "To Bitwig Mix"
│ ├─ Type: Audio Track
│ ├─ Receives: Mix sends from other tracks
│ ├─ Output: Ext. Out → OMNIBUS Device A → Ch 33-34
│ ├─ Monitor: Off
│ └─ Purpose: Send reference mix to Bitwig for context
│
├─ Audio Track 2: "To S1 Monitor Mix"
│ ├─ Type: Audio Track
│ ├─ Receives: Mix sends from other tracks
│ ├─ Output: Ext. Out → OMNIBUS Device B → Ch 33-34
│ ├─ Monitor: Off
│ └─ Purpose: Send monitoring mix to Studio One for vocal recording
│
├─ Audio Track 3: "To S1 Minus-One"
│ ├─ Type: Audio Track
│ ├─ Receives: Mix sends WITHOUT vocals
│ ├─ Output: Ext. Out → OMNIBUS Device B → Ch 35-36
│ ├─ Monitor: Off
│ └─ Purpose: Send backing track (no vocals) for practice/recording
│
├─ Audio Track 4: "To S1 Click"
│ ├─ Type: Audio Track
│ ├─ Receives: Metronome/Click
│ ├─ Output: Ext. Out → OMNIBUS Device B → Ch 37-38
│ ├─ Monitor: Off
│ └─ Purpose: Send click track to Studio One for timing reference
│
└─ [Additional send tracks for stems, effects returns, etc...]
════════════════════════════════════════════════════
GROUP 5: PROCESSING & MASTER
════════════════════════════════════════════════════
│
├─ Return Track: "Reverb"
├─ Return Track: "Delay"
├─ Return Track: "Main Compression"
└─ Master Track
├─ Master effects chain
├─ Master metering
└─ Export destination
Creating Return Tracks for Incoming Audio:
Steps:
- Right-click in return tracks section → Insert Return Track
- Name: "Bitwig Grid 1"
- Set Input:
- Click "Audio From" dropdown
- Select: Ext. In → OMNIBUS Device A → Ch 1-2
- Set Monitor: In (always monitor input)
- Output: Master (routes to master bus)
Configuration:
Track Name: Bitwig Grid 1
Type: Return Track
Input: Ext. In → OMNIBUS Device A → 1/2
Monitor: In
Output: Master
Arm: Not needed (return tracks auto-receive)
Insert effects as needed:
├─ EQ Eight (corrective EQ)
├─ Compressor (dynamics)
└─ Utility (width, gain staging)
Monitor Setting Explanation:
- In: Always hear the input (recommended for return tracks)
- Auto: Hear input when armed, playback when playing
- Off: Never monitor input
Create Additional Return Tracks:
Repeat the process for each satellite output:
- Bitwig Grid 2 (Device A Ch 3-4)
- Bitwig Polymer (Device A Ch 5-6)
- Bitwig Phase-4 (Device A Ch 7-8)
- Bitwig Bass (Device A Ch 9-10)
- ...continue for all Bitwig instruments
- S1 Lead Vocal (Device B Ch 1-2)
- S1 Harmony 1 (Device B Ch 3-4)
- ...continue for all Studio One tracks
Creating MIDI Tracks to Control Satellite Instruments:
Steps:
- Create MIDI Track (Cmd+T)
- Name: "Control Bitwig Grid 1"
- Do NOT load any instrument (this track only sends MIDI)
- Add LISTENTO Instrument plugin to track
- Configure LISTENTO Instrument:
LISTENTO Instrument Configuration:
Session Name: "Hub-Grid1-ToBitwig"
Security: Optional password
Latency: 150ms (start here, optimize later)
Quality: Standard
Status: Start Streaming → Copy Link
Steps in Plugin:
- Open LISTENTO Instrument on track
- Click "Login" (if not already logged in)
- Enter Session Name: "Hub-Grid1-ToBitwig"
- Set Latency: 150ms
- Click "Start Streaming"
- Copy the link (optional, for reference)
Recording MIDI Clips:
- Arm track (click arm button)
- Record MIDI notes from your controller
- MIDI automatically streams to Bitwig
- Bitwig plays the corresponding instrument
- Audio returns to Ableton via OMNIBUS
Complete Track Configuration:
Track Name: Control Bitwig Grid 1
Type: MIDI Track
Instrument: None (only LISTENTO Instrument plugin)
MIDI From: All Ins / Your MIDI Keyboard
MIDI Output: Not needed (LISTENTO handles routing)
Monitor: Auto
Arm: As needed for recording
Plugin Chain:
└─ LISTENTO Instrument
├─ Session: "Hub-Grid1-ToBitwig"
├─ Latency: 150ms
└─ Status: Streaming (green indicator)
Create Additional Control Tracks:
Repeat for each satellite instrument you want to control:
- Control Bitwig Grid 2 (Session: "Hub-Grid2-ToBitwig")
- Control Bitwig Polymer (Session: "Hub-Poly-ToBitwig")
- Control Bitwig Phase-4 (Session: "Hub-P4-ToBitwig")
- Control Bitwig Bass (Session: "Hub-Bass-ToBitwig")
- Control S1 Bass (Session: "Hub-Bass-ToS1")
- Control S1 Piano (Session: "Hub-Piano-ToS1")
- etc.
Creating Tracks to Send Audio to Satellites:
Purpose: Send Ableton's mix to Studio One for vocal monitoring during recording
Steps:
- Create Audio Track (Cmd+T)
- Name: "To S1 Monitor Mix"
- Set Output:
- Click "Audio To" dropdown
- Select: Ext. Out → OMNIBUS Device B → 33/34
- Configure Receives: Use track sends from other tracks
Configuration:
Track Name: To S1 Monitor Mix
Type: Audio Track
Input: Not used (receives via sends)
Output: Ext. Out → OMNIBUS Device B → 33/34
Monitor: Off (not monitoring this track)
Arm: No
Receives Audio From:
├─ All satellite return tracks (Bitwig/S1 instruments)
├─ Ableton-native instrument tracks
├─ Any tracks needed in vocalist's monitor mix
└─ Configure using Send knobs on source tracks
How to Route Audio to This Track:
- On each source track (e.g., "Bitwig Grid 1"):
- Locate the Send knobs (A, B, C, D, etc.)
- Assign one send (e.g., Send A) to "To S1 Monitor Mix"
- Adjust send level (0-100%)
- This creates a custom monitor mix for Studio One
Alternative: Use Pre-Fader Sends
For monitor mixes, use Pre-Fader sends so mix changes don't affect monitoring:
- Right-click Send knob → Set to Pre-Fader
- Now send level is independent of track fader
Purpose: Send metronome/click to Studio One for timing reference
Steps:
- Create Audio Track
- Name: "To S1 Click"
- Output: Ext. Out → OMNIBUS Device B → 37/38
- Load metronome sample or use Impulse with click sound
- Create MIDI clip with quarter notes on beats
- Send routed to Studio One automatically
Configuration:
Track Name: To S1 Click
Type: Audio Track
Instrument: Impulse (or audio clip of click sound)
Output: Ext. Out → OMNIBUS Device B → 37/38
MIDI: Quarter note pattern
Arrangement: Always playing during Studio One sessions
Purpose: Send reference mix to Bitwig for context during sound design
Steps:
- Create Audio Track
- Name: "To Bitwig Mix"
- Output: Ext. Out → OMNIBUS Device A → 33/34
- Receive audio from master bus or selected tracks
Configuration:
Track Name: To Bitwig Mix
Type: Audio Track
Output: Ext. Out → OMNIBUS Device A → 33/34
Purpose: Optional reference for Bitwig to hear arrangement context
Recommended Approach:
Session View (Clip Launching):
- Use for initial composition and idea generation
- Launch MIDI clips to control satellite instruments
- Experiment with different satellite sounds
- Record improvisations and performances
Arrangement View (Timeline):
- Use for final arrangement and structure
- All satellite audio return tracks appear as individual tracks
- Edit and arrange timing of satellite performances
- Apply effects and automation
- Create final mix and master
Transitioning from Session to Arrangement:
- Work in Session View with clips
- Press Global Record button
- Launch clips and record performance to Arrangement
- Switch to Arrangement View (Tab key)
- Edit and refine the recorded performance
Ableton's Latency Compensation:
Hub-Specific Latency Considerations:
-
OMNIBUS Latency: Added to total system latency
- Buffer size set in OMNIBUS (e.g., 64 samples)
- Ableton accounts for this automatically
-
LISTENTO MIDI Latency: 100-200ms typical
- NOT compensated automatically
- Perceptible delay when playing satellites from Ableton
- Adjust by pre-recording MIDI or manual timing offset
-
Total Roundtrip Latency:
Ableton buffer (128) + OMNIBUS buffer (64) + Bitwig buffer (64)
= 256 samples = ~5.3ms @ 48kHz (audio)
+ LISTENTO MIDI latency (150ms)
= ~155ms total for MIDI → Audio roundtrip
Dealing with MIDI Latency:
Option 1: Pre-Record MIDI
- Record MIDI clips in advance
- Playback is latency-compensated by LISTENTO
Option 2: Live Performance with Latency
- Accept the ~150ms delay when playing
- Compensate by playing slightly ahead
Option 3: Nudge MIDI Clips Earlier
- Record live MIDI performance
- Shift MIDI clips earlier by ~150ms in Arrangement
- Audio timing will be correct on playback
Save Ableton Hub Configuration as Template:
- Configure all return tracks, MIDI tracks, and send tracks
- Save as template: File → Save Live Set as Template
- Name: "Multi-DAW Hub Template"
- Future projects load with all routing pre-configured
Template Contents:
└─ Multi-DAW Hub Template.als
├─ All satellite return tracks
├─ All MIDI control tracks with LISTENTO Instrument
├─ All send tracks for satellite monitoring
├─ Group organization (folders)
├─ Color coding
└─ Basic effects chains
Loading Template:
- File → New Live Set from Template
- Select: "Multi-DAW Hub Template"
- All routing instantly available
- Start composing immediately
Bitwig Studio serves as the specialized synthesis and sound design satellite:
Responsibilities:
- Advanced Synthesis: The Grid, Polymer, Phase-4, modular devices
- Sound Design: Create unique timbres and textures
- Audio Generation: Send rendered audio to Ableton hub via OMNIBUS
- MIDI Reception: Receive note data from Ableton via LISTENTO
- Optional Reference: Receive Ableton mix for context
Data Inputs:
- LISTENTO Receiver virtual MIDI (from Ableton hub)
- OMNIBUS Device A Output Ch 33-64 (audio reference from Ableton, optional)
Data Outputs:
- Instrument audio to OMNIBUS Device A Input Ch 1-32
- Optional MIDI back to Ableton via LISTENTO Instrument
Location: File → Settings → Audio (Win) / Bitwig Studio → Settings → Audio (Mac)
Configuration:
Audio Device: OMNIBUS Device A
Sample Rate: 48000 Hz (must match Ableton and OMNIBUS)
Buffer Size: 64 samples (low latency for instruments)
Sample Format: 32-bit float (highest quality)
Audio Engine:
├─ Play in Background: ENABLED (continue playing when unfocused)
├─ Suspend Audio Engine: DISABLED
└─ Audio Engine Process Priority: High
Why Use OMNIBUS Device A:
- Provides both input (from Ableton) and output (to Ableton)
- Dedicated device for Bitwig ↔ Ableton routing
- Channels 1-32 for Bitwig → Ableton
- Channels 33-64 for Ableton → Bitwig
Location: Settings → Audio → Channels
Configuration:
Active Channels: 32 output channels (16 stereo pairs)
Enable: Channels 1-32
Purpose: Each instrument can have dedicated stereo output to Ableton
Channel Mapping:
├─ Out 1-2: The Grid instance 1
├─ Out 3-4: The Grid instance 2
├─ Out 5-6: Polymer synth
├─ Out 7-8: Phase-4 synth
├─ Out 9-10: Bass instrument
└─ Out 11-32: Additional instruments (11 stereo pairs)
Location: Settings → Controllers
Purpose: Enable Bitwig to receive MIDI from Ableton via LISTENTO
Steps:
- Click "Add Controller" button
- Select: Generic → MIDI Keyboard
- Choose MIDI Input: LISTENTO Receiver Port 1, 2, 3, etc.
- MIDI Output: None (we only receive from Ableton)
- Click "Add"
Add Multiple LISTENTO Ports:
Repeat the process for each LISTENTO Receiver instance you'll use:
Controller 1: LISTENTO Receiver Port 1 (for Grid 1)
Controller 2: LISTENTO Receiver Port 2 (for Grid 2)
Controller 3: LISTENTO Receiver Port 3 (for Polymer)
etc.
Track Example: "The Grid to Ableton"
Purpose: The Grid synthesizer controlled by Ableton, audio sent to Ableton hub
Steps:
- Create Instrument Track (Cmd/Ctrl+T)
- Name: "The Grid to Ableton"
- Load The Grid device
- Add LISTENTO Receiver BEFORE the instrument:
- Insert LISTENTO Receiver plugin at start of chain
- Configure to receive from Ableton session
- Set Track Output:
- Click track output selector
- Choose: OMNIBUS Device A → Stereo Out 1-2
Complete Configuration:
Track Name: The Grid to Ableton
Type: Instrument Track
Device Chain:
├─ 1. LISTENTO Receiver
│ ├─ Paste Link: "Hub-Grid1-ToBitwig"
│ ├─ MIDI Output: LISTENTO Receiver Port 1
│ ├─ MIDI Latency: 150ms
│ └─ Status: Connected (green)
│
├─ 2. The Grid
│ ├─ Patch: [Your sound design]
│ └─ Parameters: [Customized]
│
└─ 3. Effects (optional)
├─ EQ-5
├─ Compressor
└─ Limiter
Track Output: OMNIBUS Device A → 1/2
MIDI Input: LISTENTO Receiver Port 1
Monitor: Auto
Arm: Not needed (LISTENTO handles MIDI input)
LISTENTO Receiver Configuration:
-
Insert LISTENTO Receiver Plugin:
- Click device browser
- Navigate to: Audio FX → Audiomovers → LISTENTO Receiver
- Drag onto track (BEFORE The Grid device)
-
Paste Ableton's Session Link:
- Copy link from Ableton's LISTENTO Instrument ("Hub-Grid1-ToBitwig")
- Paste into LISTENTO Receiver
-
Configure MIDI Output:
- MIDI Output: Select "LISTENTO Receiver Port 1"
- This creates virtual MIDI port for track
-
Set MIDI Latency:
- MIDI Latency: 150ms (match Ableton's setting)
- Adjust based on stability
-
Set Track MIDI Input:
- Track MIDI Input: LISTENTO Receiver Port 1
- Channel: All Channels
- Now The Grid receives MIDI from Ableton
Check MIDI Connection:
- Play notes in Ableton on corresponding MIDI track
- LISTENTO Receiver MIDI Activity Indicator should flash red
- The Grid should produce sound
- Audio should appear in Ableton's return track
Repeat the track setup for each instrument:
Device Chain:
├─ LISTENTO Receiver (Session: "Hub-Grid2-ToBitwig", Port 2)
├─ The Grid (Instance 2, different patch)
└─ Effects
Track Output: OMNIBUS Device A → 3/4
Device Chain:
├─ LISTENTO Receiver (Session: "Hub-Poly-ToBitwig", Port 3)
├─ Polymer (Synth)
└─ Effects
Track Output: OMNIBUS Device A → 5/6
Device Chain:
├─ LISTENTO Receiver (Session: "Hub-P4-ToBitwig", Port 4)
├─ Phase-4 (Synth)
└─ Effects
Track Output: OMNIBUS Device A → 7/8
Device Chain:
├─ LISTENTO Receiver (Session: "Hub-Bass-ToBitwig", Port 5)
├─ Polysynth (Bass patch)
└─ Effects
Track Output: OMNIBUS Device A → 9/10
Continue for all instruments you want to use...
Purpose: Hear Ableton's mix in Bitwig for context during sound design
Track: "Ableton Reference"
Steps:
- Create Audio Track
- Name: "Ableton Reference"
- Input: OMNIBUS Device A → Ch 33-34 (from Ableton)
- Monitor: In
- Solo Safe: ENABLED (so you can solo instruments without losing reference)
Configuration:
Track Name: Ableton Reference
Type: Audio Track
Input: OMNIBUS Device A → 33/34
Monitor: In
Solo Safe: ENABLED
Output: Master (or dedicated headphone output)
Volume: Adjust for comfortable monitoring
When to Use:
- Sound design sessions (hear how instrument fits in mix)
- Adjusting instrument tone relative to backing track
- Checking phase relationship with Ableton tracks
Recommended Track Layout:
════════════════════════════════════════════
BITWIG STUDIO PROJECT STRUCTURE
════════════════════════════════════════════
│
├─ TRACK 1: "Reference from Ableton"
│ └─ Audio input from OMNIBUS Device A Ch 33-34
│
├─ TRACK 2: "Grid 1 to Ableton"
│ └─ LISTENTO Receiver → The Grid → OMNIBUS Out 1-2
│
├─ TRACK 3: "Grid 2 to Ableton"
│ └─ LISTENTO Receiver → The Grid → OMNIBUS Out 3-4
│
├─ TRACK 4: "Polymer to Ableton"
│ └─ LISTENTO Receiver → Polymer → OMNIBUS Out 5-6
│
├─ TRACK 5: "Phase-4 to Ableton"
│ └─ LISTENTO Receiver → Phase-4 → OMNIBUS Out 7-8
│
├─ TRACK 6: "Bass to Ableton"
│ └─ LISTENTO Receiver → Polysynth → OMNIBUS Out 9-10
│
├─ TRACK 7: "Pad to Ableton"
│ └─ LISTENTO Receiver → Sampler → OMNIBUS Out 11-12
│
└─ [Additional instrument tracks...]
Location: Settings → Behavior
Recommended Settings:
Clip Launching:
├─ Start Recording on Scene Launch: ENABLED
├─ Overdub Clips: ENABLED
└─ Quantization: 1 Bar
Audio Import:
├─ Default Import: Arranger Timeline
├─ Resample on Import: OFF
└─ Preserve file quality
MIDI:
├─ Note Input: All channels
├─ Omni Mode: ENABLED
└─ MPE: OFF (unless using MPE controller)
Transport Synchronization:
In satellite architecture, Bitwig does NOT sync transport with Ableton via MIDI Clock. Instead:
Manual Transport Control:
- You manually start/stop playback in Bitwig when needed
- Focus on sound design, not timeline synchronization
- MIDI note streams happen independently of transport state
When to Play in Bitwig:
- When actively designing sounds and testing MIDI from Ableton
- When recording audio internally for bouncing
- Not required for live MIDI streaming (LISTENTO works with transport stopped)
Save Bitwig Configuration as Template:
- Configure all instrument tracks with LISTENTO Receivers
- Set all track outputs to OMNIBUS channels
- Save project: File → Save As Template
- Name: "Ableton-Satellite-Instruments"
Template Contents:
└─ Ableton-Satellite-Instruments.bwtemplate
├─ Reference track from Ableton
├─ 8-16 instrument tracks with LISTENTO Receivers
├─ OMNIBUS output routing configured
├─ Color coding for organization
└─ Basic effect chains
Sound Design Workflow:
- Create Patch in Bitwig: Design sound in The Grid, Polymer, etc.
- Test with Local MIDI: Use Bitwig's piano roll to test locally
- Connect to Ableton: Configure LISTENTO Receiver, test connection
- Record in Ableton: Play notes from Ableton, record to Arrangement
- Iterate: Adjust Bitwig patch based on mix context
CPU Optimization:
- Disable LISTENTO Receivers for unused instruments
- Freeze tracks in Bitwig if needed
- Increase buffer size if experiencing dropouts
Multiple Grid Instances:
- Create variations of The Grid with different patches
- Each gets its own LISTENTO session and OMNIBUS output
- Allows A/B comparison of sounds directly in Ableton
Studio One Pro 7 is included in this hub architecture for two primary purposes: its unique lyrics management capabilities AND as a dedicated vocal recording environment with integrated lyrics display. The lyrics features are not available in Ableton Live 12 or Bitwig Studio, and the combination of lyrics display with vocal recording provides an unmatched workflow for vocal production.
Why Studio One Pro 7 is Essential:
Studio One Pro 7 offers comprehensive lyrics management features AND serves as an optimal vocal recording environment:
- Lyrics Management: Unique features not available in Ableton or Bitwig
- Vocal Recording: Integrated lyrics display during recording for vocalist reference
- Workflow Integration: Record vocals while viewing synchronized lyrics, then send audio to Ableton for mixing
- Global Lyrics Track: Create lyric events directly on the Song timeline with beat-based or second-based synchronization
- Lyrics Display Window: Synchronized lyrics display for vocalist reference during recording or live performance, with customizable font, alignment, and read-ahead timing
- Lyric Lanes: Tie syllables to MIDI notes for precise melodic alignment in Piano Roll and Score View
- Show Page Integration: Extend lyrics features to live performance teleprompter-style displays for stage use
Reference: For detailed information about Studio One Pro 7's lyrics features, see the companion document: Studio One Pro 7 — Lyrics-Specific Features
Responsibilities:
- Lyrics Management: Create, edit, and synchronize lyrics with Ableton's tempo and arrangement
- Lyrics Display: Provide synchronized lyrics display for vocalists during recording sessions
- Lyrics Synchronization: Align lyrics with Ableton's backing track and tempo changes
- Live Performance: Export lyrics to Show Page for stage teleprompter use
- Lyrics Import/Export: Support
.TXTand.MIDIlyric file formats
Data Inputs:
- OMNIBUS Device B Output Ch 33-64 (mix from Ableton for lyrics synchronization reference)
- LISTENTO Receiver virtual MIDI (from Ableton for tempo/time signature sync)
- Ableton's tempo and arrangement changes (for lyrics alignment)
Data Outputs:
- Lyrics data synchronized with Ableton's timeline (via beat-based timebase)
- Lyrics Display window for vocalist reference
- Show Page exports for live performance
Location: Studio One → Options (Win) / Preferences (Mac) → Audio Setup
Configuration:
Audio Device: OMNIBUS Device B (or Aggregate Device including OMNIBUS B)
Sample Rate: 48000 Hz (must match Ableton and OMNIBUS)
Device Block Size: 64 samples (vocal recording)
OR 256 samples (mixing/processing)
Processing: High precision (64-bit floating point)
Options:
├─ Release Audio Device in Background: DISABLED
├─ Drop-Out Protection: Medium
└─ Multi-Processing: ENABLED
Device Block Size Strategy:
Vocal Recording Session:
└─ 64 samples
└─ Low latency for comfortable monitoring
└─ Typical latency: ~1.3ms @ 48kHz
Mixing/Processing Session:
└─ 256 samples
└─ More CPU headroom for effects
└─ Latency less critical (not monitoring input)
Location: Song → Song Setup → Audio I/O Setup
Purpose: Enable OMNIBUS channels for monitoring Ableton's mix
Location: Song Setup → Audio I/O Setup → Inputs tab
Add Inputs:
Input 1-2: "Ableton Monitor Mix"
Source: OMNIBUS Device B Ch 33-34
Purpose: Main monitoring mix from Ableton
Input 3-4: "Ableton Minus-One"
Source: OMNIBUS Device B Ch 35-36
Purpose: Backing track without vocals (for practice)
Input 5-6: "Ableton Click"
Source: OMNIBUS Device B Ch 37-38
Purpose: Metronome/click from Ableton
Input 7-8: "Ableton Stem 1"
Source: OMNIBUS Device B Ch 39-40
Purpose: Individual stem from Ableton (drums, bass, etc.)
[Continue for additional stems...]
Hardware Inputs:
Input 1 (physical): "Microphone"
Source: Hardware Interface Input 1
Purpose: Vocal recording
Steps to Add:
- Click "+ Add Channel" button
- Select: Stereo or Mono
- Choose: OMNIBUS Device B → Channels
- Name appropriately
- Repeat for all needed inputs
Purpose: Route Studio One vocal/instrument tracks to Ableton hub via OMNIBUS for final mixing
Location: Song Setup → Audio I/O Setup → Outputs tab
Add Outputs:
Output 1-2: "To Ableton Lead Vocal"
Destination: OMNIBUS Device B Ch 1-2
Purpose: Send lead vocal to Ableton
Output 3-4: "To Ableton Harmony 1"
Destination: OMNIBUS Device B Ch 3-4
Purpose: Send harmony vocal 1 to Ableton
Output 5-6: "To Ableton Harmony 2"
Destination: OMNIBUS Device B Ch 5-6
Purpose: Send harmony vocal 2 to Ableton
Output 7-8: "To Ableton Backing Vox"
Destination: OMNIBUS Device B Ch 7-8
Purpose: Send backing vocals to Ableton
Output 9-10: "To Ableton Guitar"
Destination: OMNIBUS Device B Ch 9-10
Purpose: Send guitar to Ableton
[Continue for all tracks you'll send to Ableton...]
Hardware Outputs:
Main Out 1-2: Hardware Interface Out 1-2
Purpose: Direct monitoring via studio monitors
Steps to Add:
- Click "+ Add Channel" button in Outputs tab
- Select: Stereo
- Choose: OMNIBUS Device B → Channels
- Name: "To Ableton [Track Name]"
- Repeat for all tracks
Location: Studio One → Options → External Devices (Win) / Preferences → External Devices (Mac)
Purpose: Enable Studio One to receive MIDI from Ableton
Steps:
- Click "Add..." button
- Select: "New Keyboard"
- Configure:
Keyboard 1: LISTENTO from Ableton
Manufacturer: Audiomovers
Device Name: LISTENTO Hub Control
Receive From: LISTENTO Receiver Port 1
Send To: None (we only receive)
All Channels: ENABLED
Splits: None
Create Additional Keyboards as Needed:
Keyboard 2: LISTENTO Receiver Port 2
Keyboard 3: LISTENTO Receiver Port 3
etc.
Track Example: "Lead Vocal to Ableton"
Purpose: Record vocals, process, send to Ableton hub
Steps:
- Track → Add Audio Track (T key)
- Name: "Lead Vocal to Ableton"
- Set Input:
- Track Input: Hardware Interface Input 1 (microphone)
- Or: "Microphone" (configured in I/O Setup)
- Set Output:
- Track Output: "To Ableton Lead Vocal" (OMNIBUS Device B Ch 1-2)
- Enable Monitoring:
- Click Monitor button (turns blue)
Complete Configuration:
Track Name: Lead Vocal to Ableton
Type: Audio Track
Input Configuration:
├─ Input: Hardware Interface Input 1 (Microphone)
├─ Monitor: ENABLED (blue)
├─ Input Gain: Set appropriate level
└─ Phantom Power: ENABLED (if needed for condenser mic)
Monitor Mix:
├─ Create headphone mix with Ableton backing track
├─ Use "Ableton Monitor Mix" input on separate track
└─ Adjust blend of mic input vs. backing track
Effects Chain (optional):
├─ 1. Fat Channel (EQ, Compression, Gate)
├─ 2. DeEsser
├─ 3. Reverb (for monitoring comfort)
└─ 4. Effects printed to recording or applied non-destructively
Output Configuration:
├─ Track Output: "To Ableton Lead Vocal" (OMNIBUS B Ch 1-2)
├─ Automatically routes to Ableton
└─ Appears in Ableton's return track
Recording:
├─ Arm Track (R key)
├─ Press record in Studio One
├─ Audio captured locally in Studio One
└─ Simultaneously streamed to Ableton via OMNIBUS
Track: "Ableton Backing Track"
Purpose: Hear Ableton's mix for timing/pitch reference while recording
Steps:
- Add Audio Track
- Name: "Ableton Backing Track"
- Input: "Ableton Monitor Mix" (OMNIBUS Device B Ch 33-34)
- Monitor: ENABLED
- Do NOT arm for recording (monitor only)
- Output: Main (or headphone output)
Configuration:
Track Name: Ableton Backing Track
Type: Audio Track
Input: "Ableton Monitor Mix" (OMNIBUS B Ch 33-34)
Monitor: ENABLED
Arm: NO (monitoring only, not recording)
Output: Main (for speakers/headphones)
Volume: Adjust for comfortable monitoring balance
Track: "Ableton Click"
Purpose: Hear Ableton's click/metronome for timing
Steps:
- Add Audio Track
- Name: "Ableton Click"
- Input: "Ableton Click" (OMNIBUS Device B Ch 37-38)
- Monitor: ENABLED
- Output: Headphone output (not main speakers)
Configuration:
Track Name: Ableton Click
Type: Audio Track
Input: "Ableton Click" (OMNIBUS B Ch 37-38)
Monitor: ENABLED
Output: Headphone mix (separate from main monitoring)
Volume: Adjust for comfortable click level
Repeat for all audio sources you'll send to Ableton:
Input: Hardware mic or input
Output: "To Ableton Harmony 1" (OMNIBUS B Ch 3-4)
Purpose: Second vocal track
Input: Hardware mic or input
Output: "To Ableton Harmony 2" (OMNIBUS B Ch 5-6)
Purpose: Third vocal track
Input: Hardware mic or input
Output: "To Ableton Backing Vox" (OMNIBUS B Ch 7-8)
Purpose: Group backing vocal track
Input: DI or mic input
Output: "To Ableton Guitar" (OMNIBUS B Ch 9-10)
Purpose: Live guitar recording
Purpose: Control Studio One instruments from Ableton (less common in vocal-focused workflow)
Instrument Track Example: "S1 Bass from Ableton"
Steps:
- Track → Add Instrument Track
- Load Studio One instrument (Presence XT, Mai Tai, etc.)
- Add LISTENTO Receiver Before Instrument:
- Effects → Audiomovers → LISTENTO Receiver
- Place BEFORE instrument in chain
- Configure LISTENTO Receiver:
- Paste link from Ableton: "Hub-Bass-ToS1"
- MIDI Output: LISTENTO Receiver Port 1
- MIDI Latency: 150ms
- Set Track Input:
- Track Input: LISTENTO Receiver Port 1
- All Channels
Configuration:
Track Name: S1 Bass from Ableton
Type: Instrument Track
Insert Chain:
├─ 1. LISTENTO Receiver
│ ├─ Session: "Hub-Bass-ToS1"
│ ├─ MIDI Output: LISTENTO Receiver Port 1
│ └─ MIDI Latency: 150ms
│
├─ 2. Presence XT (Bass patch)
│ └─ Patch: [Bass sound]
│
└─ 3. Effects (optional)
└─ Compressor, EQ, etc.
Track Input: LISTENTO Receiver Port 1
Track Output: "To Ableton Bass" (OMNIBUS B Ch 9-10)
Monitor: Auto
Recommended Track Layout:
════════════════════════════════════════════════════
STUDIO ONE PRO 7 PROJECT STRUCTURE
════════════════════════════════════════════════════
│
├─ MONITORING TRACKS (No recording, monitoring only)
│ ├─ Track 1: "Ableton Backing Track"
│ │ └─ Input: OMNIBUS B Ch 33-34, Monitor: ON
│ ├─ Track 2: "Ableton Click"
│ │ └─ Input: OMNIBUS B Ch 37-38, Monitor: ON
│ └─ Track 3: "Ableton Stem 1"
│ └─ Input: OMNIBUS B Ch 39-40, Monitor: ON
│
├─ RECORDING TRACKS (Send to Ableton)
│ ├─ Track 4: "Lead Vocal to Ableton"
│ │ └─ Input: Mic 1, Output: OMNIBUS B Ch 1-2
│ ├─ Track 5: "Harmony 1 to Ableton"
│ │ └─ Input: Mic 1, Output: OMNIBUS B Ch 3-4
│ ├─ Track 6: "Harmony 2 to Ableton"
│ │ └─ Input: Mic 1, Output: OMNIBUS B Ch 5-6
│ ├─ Track 7: "Backing Vocals to Ableton"
│ │ └─ Input: Mic 1, Output: OMNIBUS B Ch 7-8
│ ├─ Track 8: "Guitar to Ableton"
│ │ └─ Input: DI/Mic 2, Output: OMNIBUS B Ch 9-10
│ └─ Track 9: "Bass to Ableton"
│ └─ Input: DI, Output: OMNIBUS B Ch 11-12
│
└─ OPTIONAL INSTRUMENT TRACKS (Ableton MIDI control)
└─ Track 10: "S1 Bass from Ableton"
└─ LISTENTO Receiver → Presence XT → OMNIBUS B Out
Complete Lyrics Management Process:
-
Open Studio One and Ableton:
- Launch both DAWs
- Load appropriate project/template in each
- In Ableton: Create vocal recording track (if recording vocals)
-
Verify OMNIBUS Routing:
- Switch to OMNIBUS snapshot "Studio One Lyrics Sync" (Cmd+3)
- Check routing matrix for Ableton → Studio One connections (for backing track sync reference)
-
Configure Monitoring in Studio One:
- Enable "Ableton Backing Track" monitor track (for lyrics synchronization reference)
- Enable "Ableton Click" monitor track (for timing reference)
- These tracks help Studio One sync lyrics with Ableton's timeline
-
Set Up Lyrics Features:
- Add Global Lyrics Track in Studio One
- Configure Lyrics Display window
- Set beat-based timebase to sync with Ableton's tempo
- See Step 10 for detailed lyrics feature setup
-
Prepare for Recording:
- Arm vocal track in Ableton
- Set up microphone input in Ableton
- Display Studio One Lyrics Display window on second screen/tablet for vocalist
-
Start Recording:
- Start playback in Ableton (spacebar)
- Start recording in Ableton (spacebar with track armed)
- Vocalist follows Studio One Lyrics Display while recording
- Performer hears Ableton backing track + their voice (monitored in Ableton)
-
During Recording:
- Audio recorded locally in Ableton
- Studio One Lyrics Display shows synchronized lyrics
- Lyrics remain aligned with Ableton's tempo via LISTENTO sync
-
After Recording:
- Stop recording in Ableton
- Lyrics remain in Studio One (synchronized with Ableton's timeline)
- Process vocals in Ableton as needed
Lyrics Alignment:
1. After major arrangement edits in Ableton, verify lyric timing in Studio One
2. Use Arranger Track in Studio One to keep lyrics aligned with song sections
3. Lyrics automatically sync with Ableton's tempo changes (beat-based timebase)
4. Export lyrics to Show Page for live performance versions (if needed)
Location: View → Performance Monitor
Purpose: Check CPU usage, track DSP load, optimize performance
Monitoring:
CPU Usage: Keep below 70% for stable recording
Disk Usage: Monitor during recording to prevent dropouts
Track DSP: Identify CPU-heavy plugins
Audio Dropout Indicator: Should remain green
Optimization Tips:
- Freeze tracks with heavy processing
- Increase buffer size if seeing dropouts
- Disable effects during recording, add in mixing
Why Studio One Pro 7's Lyrics Features Are Essential:
Studio One Pro 7 offers unique lyrics management capabilities that are not available in Ableton Live 12 or Bitwig Studio. These features make Studio One the essential addition to this hub architecture for any production workflow requiring integrated lyrics management.
Reference Document: For comprehensive details about Studio One Pro 7's lyrics features, workflow recommendations, and limitations, see the companion document: Studio One Pro 7 — Lyrics-Specific Features
Key Lyrics Features:
The following sections outline how Studio One Pro 7's lyrics features integrate with the hub architecture:
Location: Global Track list → Click Lyrics icon [L]
Features:
- Create lyric events directly on the Song timeline
- Double-click at bar/beat to add lyrics
- Spacebar: Advance to next word
- Return/Enter: New line (advances to next bar)
- Tab: Next lyric event without new line
- Import
.TXTor.MIDIfiles to auto-populate lyrics - Choose Timebase:
- Beat-based: Lyrics tied to musical bars/beats (recommended for hub workflow)
- Second-based: Lyrics tied to absolute time
Hub Workflow Integration:
- Add lyrics before or during vocal recording sessions (record vocals in Ableton)
- Lyrics sync with Ableton's tempo (when using beat-based timebase)
- Keep lyrics visible during recording for vocalist reference
- Lyrics remain aligned with Ableton's arrangement via tempo synchronization
Location: View → Lyrics Display (or dedicated Lyrics Display window)
Features:
- Highlights lyrics in sync with playback
- Edit Mode: Quick text editing (pencil icon)
- Customizable:
- Font size & alignment (left/center)
- "Read-ahead" timing (preview next lyric)
- Inverted colors (white on black, etc.)
- Extends to Show Page for live performance setups
Hub Workflow Integration:
- Display lyrics on second screen or tablet in vocal booth
- Vocalist can see lyrics while hearing Ableton backing track (via OMNIBUS monitoring)
- Producer can monitor lyrics display while recording vocals in Ableton
- Live performance use: Show Page acts as teleprompter for stage performances
Location: Instrument Track → Piano Roll → Lyric Lane
Features:
- Each Instrument Track can open a Lyric Lane in Piano Roll
- Tie syllables to MIDI notes for precise melodic alignment
- Score View supports lyric-note attachment (via "Lyr" text symbols)
Hub Workflow Integration:
- Align sung melodies precisely with MIDI notes
- Ideal for structured vocals (verse/chorus)
- Less necessary for FX-heavy or chopped vocals
- Complements Ableton's MIDI control via LISTENTO
Features:
- Import
.TXTand.MIDIlyric files - Lyrics are not automatically linked to audio/MIDI clips
- Use Arranger Track to keep lyrics aligned when rearranging sections
Hub Workflow Integration:
- Import lyrics prepared in text editors or other software
- After major edits or rearrangements, verify lyric timing with Arranger Track
- Lyrics move with song sections when using Arranger Track
- Export lyrics for reference or live performance documentation
Pre-Recording Setup:
- Create Global Lyrics Track in Studio One
- Enter or import lyrics before recording sessions
- Set Lyrics Display visible for vocalist
- Use beat-based timebase to sync with Ableton's tempo
During Recording:
- Keep Lyrics Display visible (second screen/tablet recommended)
- Vocalist follows lyrics while hearing Ableton backing track via OMNIBUS monitoring
- Record vocals with lyrics as reference for timing and phrasing
After Recording:
- Use Lyric Lanes for precise melodic alignment (if needed)
- After major arrangement edits, verify lyric timing with Arranger Track
- Export lyrics to Show Page for live performance versions
Why This Matters for Hub Architecture:
- Unique Capability: Ableton Live 12 and Bitwig Studio do not offer integrated lyrics management
- Seamless Integration: Lyrics sync with Ableton's tempo and arrangement
- Enhanced Workflow: Vocalists can see lyrics while monitoring Ableton's mix
- Live Performance: Show Page extends lyrics features to stage use
- Professional Standard: Industry-standard lyric management for vocal production
Save Studio One Configuration as Template:
- Configure I/O routing to OMNIBUS (for receiving Ableton's backing track)
- Set up LISTENTO Receiver (for tempo/time signature sync from Ableton)
- Add Global Lyrics Track (primary feature)
- Configure Lyrics Display settings
- Save as template: File → Save As Template
- Name: "Ableton-Hub-Lyrics-Management"
Template Contents:
└─ Ableton-Hub-Lyrics-Management.template
├─ Input routing (Ableton backing track via OMNIBUS for sync reference)
├─ LISTENTO Receiver setup (tempo sync from Ableton)
├─ Global Lyrics Track (empty, ready for lyrics)
├─ Lyrics Display window configuration
└─ Beat-based timebase preset (syncs with Ableton tempo)
Loading Template:
- File → New Song From Template
- Select: "Ableton-Hub-Lyrics-Management"
- All routing pre-configured and ready for lyrics management
- Lyrics Track ready for lyric entry or import
- Lyrics Display ready for vocalist reference
Scenario: Creating a complete track using all three DAWs with Ableton as the central hub
-
Open Ableton:
- Load "Multi-DAW Hub Template"
- Set project tempo (e.g., 120 BPM)
- Set time signature (e.g., 4/4)
-
Create Basic Arrangement:
- Program drums using Ableton's Drum Rack
- Create bass line with Wavetable
- Add chord progression with Operator
- Build 8-16 bar loop structure
-
Establish Project Structure:
- Session View: Create scenes for Intro, Verse, Chorus, Bridge, Outro
- Arrangement View: Rough out timeline structure
-
Switch to Bitwig:
- Open "Ableton-Satellite-Instruments" template
- Load The Grid on Track 1 ("Grid 1 to Ableton")
-
Design Lead Synth Patch:
- Create modular synthesis patch in The Grid
- Test locally with Bitwig's piano roll
- Adjust filter, envelopes, modulation
-
Connect to Ableton:
- Verify LISTENTO Receiver: Session "Hub-Grid1-ToBitwig"
- Check MIDI Activity Indicator (should flash red when playing from Ableton)
- Verify OMNIBUS output: Device A Ch 1-2
-
Record Lead in Ableton:
- Return to Ableton
- Arm MIDI track: "Control Bitwig Grid 1"
- Record MIDI clip for lead melody
- Audio automatically appears in return track "Bitwig Grid 1"
-
Add More Bitwig Instruments:
- Create pad sound with Polymer (Track 2)
- Session: "Hub-Poly-ToBitwig"
- Record MIDI in Ableton on "Control Bitwig Polymer" track
- Create bass wobble with Phase-4 (Track 3)
- Record MIDI in Ableton on "Control Bitwig Phase-4" track
-
Prepare Studio One for Vocal Recording:
- Create vocal recording track in Studio One (routed to OMNIBUS Device B → Ableton)
- Load lyrics into Global Lyrics Track
- Enable Lyrics Display window for vocalist reference
- Set up microphone input on Ableton track
- Create send track: "To S1 Monitor Mix" (for lyrics sync reference)
- Route all current tracks to this send (Send A)
- Output: OMNIBUS Device B Ch 33-34
- Create click track: "To S1 Click" (for timing reference)
- Output: OMNIBUS Device B Ch 37-38
-
Switch to Studio One:
- Open "Ableton-Hub-Lyrics-Management" template
- Verify monitoring tracks receiving Ableton mix (for lyrics synchronization reference)
- Verify LISTENTO Receiver syncing tempo from Ableton
-
Set Up Lyrics Features (Studio One Unique Capability):
- Add Global Lyrics Track (click Lyrics icon
[L]in Global Tracks) - Enter or import lyrics for the song
- Set Lyrics Display window visible (second screen/tablet recommended)
- Configure Lyrics Display settings (font size, read-ahead timing)
- Use beat-based timebase to sync with Ableton's tempo
- Note: This lyrics management is unique to Studio One Pro 7 and not available in Ableton or Bitwig
- Add Global Lyrics Track (click Lyrics icon
-
Record Lead Vocal in Ableton (with Lyrics Display Reference):
- Set up headphone mix in Ableton (backing track + click)
- Display Studio One Lyrics Display window on second screen/tablet for vocalist
- Arm vocal track in Ableton
- Start playback in Ableton
- Start recording in Ableton
- Vocalist follows Lyrics Display while recording vocals in Ableton
- Record multiple takes in Ableton
-
Manage Lyrics in Studio One:
- Use Lyric Lanes (if needed) for precise melodic alignment
- After major arrangement edits in Ableton, verify lyric timing with Arranger Track
- Lyrics remain synchronized with Ableton's tempo via LISTENTO
- Export lyrics to Show Page for live performance versions (if needed)
-
Additional Vocals:
- Record harmony vocals in Ableton (same process)
- Lyrics Display continues to provide reference for all vocal recordings
- Lyrics remain aligned with Ableton's arrangement via tempo synchronization
-
Return to Ableton:
- All satellite audio present in return tracks:
- Bitwig Grid 1, Polymer, Phase-4 (return tracks 1-3)
- S1 Lead Vocal, Harmony 1, Harmony 2 (return tracks 9-11)
- All Ableton-native tracks (drums, bass, chords)
- All satellite audio present in return tracks:
-
Arrange in Arrangement View:
- Press Tab to switch to Arrangement View
- Drag clips and audio from return tracks to timeline
- Structure full arrangement: Intro → Verse → Chorus → Verse → Chorus → Bridge → Chorus → Outro
-
Mix:
- Set levels for all tracks
- Apply EQ and compression to individual tracks
- Add reverb and delay sends
- Apply master bus processing
-
Automate:
- Automate volume for dynamics
- Automate filter sweeps for Bitwig synths
- Automate effects sends for creative transitions
-
Export:
- File → Export Audio/Video
- Select: Master
- Format: WAV, 48kHz, 24-bit
- Render final mixdown
Total Session Time: 3-6 hours Result: Complete track with synthesis from Bitwig, vocals recorded in Studio One with integrated lyrics display, all audio consolidated and mixed in Ableton
Scenario: Quickly create 10 new synth patches in Bitwig for use in Ableton projects
Workflow:
-
Set OMNIBUS Snapshot:
- Press Cmd+2: "Bitwig Sound Design Focus"
- Only Bitwig ↔ Ableton routing active
-
Open Ableton:
- Create 10 MIDI tracks
- Each with LISTENTO Instrument, unique sessions
- Add MIDI loops for testing patches
-
Open Bitwig:
- Create 10 instrument tracks
- Each with LISTENTO Receiver + The Grid
- Connect to Ableton's LISTENTO sessions
-
Design Patches:
- Focus on Bitwig window
- Create modular synthesis patches in The Grid
- Test by playing MIDI from Ableton (automatic via LISTENTO)
- Iterate quickly with both DAWs visible
-
Save Patches:
- Save each Grid patch in Bitwig
- Can reuse in future sessions
-
Record Results in Ableton:
- Record audio from Bitwig return tracks to Ableton clips
- Freeze/flatten for use without Bitwig
Session Time: 1-2 hours Result: 10 unique synth sounds available for Ableton projects
Scenario: Record and comp lead vocal in Studio One with synchronized lyrics display, send recorded audio to Ableton for arrangement and mixing
Workflow:
-
Set OMNIBUS Snapshot:
- Press Cmd+3: "Studio One Lyrics Sync" (or create appropriate snapshot)
- Studio One ↔ Ableton routing active (for backing track sync reference)
-
Prepare Ableton:
- Open project with complete backing track
- Create vocal recording track in Ableton
- Set up microphone input on Ableton track
- Create send track: "To S1 Monitor Mix" (for lyrics sync reference)
- Route all backing tracks to send
- Create click track: "To S1 Click" (for timing reference)
- Ensure mix is ready for vocalist
-
Open Studio One:
- Load "Ableton-Hub-Lyrics-Management" template
- Verify monitoring: hearing Ableton backing track (for lyrics sync reference)
- Verify LISTENTO Receiver syncing tempo from Ableton
- Set comfortable headphone mix level in Ableton
-
Set Up Lyrics Features (Studio One Unique Capability):
- Add Global Lyrics Track (if not already in template)
- Enter or import lyrics for the song
- Open Lyrics Display window (View → Lyrics Display)
- Configure display settings:
- Font size: Large enough for vocalist to read
- Alignment: Center (recommended)
- Read-ahead timing: Enable for preview
- Display on second screen or tablet in vocal booth
- Set Lyrics Track to beat-based timebase (syncs with Ableton tempo)
- Note: This integrated lyrics management is exclusive to Studio One Pro 7
-
Record Multiple Takes in Ableton:
- Arm vocal track in Ableton
- Start Ableton playback (spacebar)
- Start Ableton recording (spacebar)
- Vocalist follows Studio One Lyrics Display while recording vocals in Ableton
- Record take 1
- Stop recording
- Repeat 3-5 times for multiple takes
-
Comp in Ableton:
- Use Ableton's comping tools
- Select best phrases from each take
- Create master comp take
- Process vocals in Ableton as needed
-
Manage Lyrics in Studio One:
- Verify lyrics remain aligned with comped vocal (use Arranger Track if needed)
- Optionally use Lyric Lanes for precise melodic alignment (if needed)
- Lyrics remain synchronized with Ableton's tempo via LISTENTO
-
Final Mix in Ableton:
- Balance vocal with backing track
- Apply additional mix-bus processing if needed
- Lyrics remain in Studio One (not transferred to Ableton)
- Export lyrics from Studio One Show Page for live performance (if needed)
Session Time: 1-2 hours Result: Professional vocal recorded in Studio One with synchronized lyrics display and sent to Ableton for processing and mixing. Studio One's unique lyrics display features provide optimal vocalist reference during recording, while Ableton handles the final arrangement and mixing.
Scenario: Simultaneously control 6 different Bitwig instruments from Ableton arrangement for complex production
Workflow:
-
Set OMNIBUS Snapshot:
- Press Cmd+1: "Full Hub Production"
- All routing active
-
Configure Bitwig (6 Instruments):
Track 1: The Grid - Rhythmic Arp (Session: "Hub-Grid1-ToBitwig") Track 2: The Grid - Bass Wobble (Session: "Hub-Grid2-ToBitwig") Track 3: Polymer - Lead Synth (Session: "Hub-Poly-ToBitwig") Track 4: Phase-4 - Pad (Session: "Hub-P4-ToBitwig") Track 5: Sampler - Percussion (Session: "Hub-Perc-ToBitwig") Track 6: FM-4 - Bell Tones (Session: "Hub-Bell-ToBitwig") Outputs: Track 1 → OMNIBUS Device A Ch 1-2 Track 2 → OMNIBUS Device A Ch 3-4 Track 3 → OMNIBUS Device A Ch 5-6 Track 4 → OMNIBUS Device A Ch 7-8 Track 5 → OMNIBUS Device A Ch 9-10 Track 6 → OMNIBUS Device A Ch 11-12 -
Configure Ableton (6 MIDI Control + 6 Return Tracks):
MIDI Tracks: Track 1: "Control Grid 1" → LISTENTO Inst (Hub-Grid1-ToBitwig) Track 2: "Control Grid 2" → LISTENTO Inst (Hub-Grid2-ToBitwig) Track 3: "Control Polymer" → LISTENTO Inst (Hub-Poly-ToBitwig) Track 4: "Control Phase-4" → LISTENTO Inst (Hub-P4-ToBitwig) Track 5: "Control Percussion" → LISTENTO Inst (Hub-Perc-ToBitwig) Track 6: "Control Bells" → LISTENTO Inst (Hub-Bell-ToBitwig) Return Tracks: Return 1: "Bitwig Grid 1" ← OMNIBUS Device A Ch 1-2 Return 2: "Bitwig Grid 2" ← OMNIBUS Device A Ch 3-4 Return 3: "Bitwig Polymer" ← OMNIBUS Device A Ch 5-6 Return 4: "Bitwig Phase-4" ← OMNIBUS Device A Ch 7-8 Return 5: "Bitwig Percussion" ← OMNIBUS Device A Ch 9-10 Return 6: "Bitwig Bells" ← OMNIBUS Device A Ch 11-12 -
Compose in Ableton:
- Create MIDI clips on each of 6 control tracks
- Arrange in Session View or Arrangement View
- All 6 instruments respond simultaneously
- Audio from all 6 instruments returns via OMNIBUS
-
Mix and Process:
- Each Bitwig instrument appears as separate track in Ableton
- Apply individual EQ, compression, effects
- Create complex mix with all satellite instruments
Session Time: 2-4 hours Result: Complex arrangement using 6 simultaneous Bitwig instruments, all controlled from Ableton timeline
Visual Routing Diagram:
╔═══════════════════════════════════════════════════════════╗
║ OMNIBUS ROUTING MATRIX ║
║ Complete Hub Configuration ║
╚═══════════════════════════════════════════════════════════╝
INPUT SOURCES (Left Side) → OUTPUT DESTINATIONS (Top)
───────────────────────── ───────────────────────────
BITWIG OUTPUTS OMNIBUS Device A
├─ Out 1-2: Grid 1 ────→ Input Ch 1-2 ────┐
├─ Out 3-4: Grid 2 ────→ Input Ch 3-4 ────┤
├─ Out 5-6: Polymer ────→ Input Ch 5-6 ────┤
├─ Out 7-8: Phase-4 ────→ Input Ch 7-8 ────┤──→ [OMNIBUS Device A]
├─ Out 9-10: Bass ────→ Input Ch 9-10 ────┤ Output Ch 1-32
├─ Out 11-12: Pad ────→ Input Ch 11-12 ────┤ ↓
└─ [Additional outs...] ────→ [Ch 13-32...] ────┘ ABLETON INPUTS
(Return Tracks)
ABLETON OUTPUTS OMNIBUS Device A
├─ Send: To Bitwig Mix ────→ Input Ch 33-34 ────┐
├─ Send: Drums Ref ────→ Input Ch 35-36 ────┤
├─ Send: Bass Ref ────→ Input Ch 37-38 ────┤──→ [OMNIBUS Device A]
└─ [Additional sends...] ────→ [Ch 39-64...] ────┘ Output Ch 33-64
↓
BITWIG INPUTS
(Reference Tracks)
STUDIO ONE OUTPUTS OMNIBUS Device B
├─ Out 1-2: Lead Vocal ────→ Input Ch 1-2 ────┐
├─ Out 3-4: Harmony 1 ────→ Input Ch 3-4 ────┤
├─ Out 5-6: Harmony 2 ────→ Input Ch 5-6 ────┤
├─ Out 7-8: Backing Vox ────→ Input Ch 7-8 ────┤──→ [OMNIBUS Device B]
├─ Out 9-10: Guitar ────→ Input Ch 9-10 ────┤ Output Ch 1-32
├─ Out 11-12: Bass ────→ Input Ch 11-12 ────┤ ↓
└─ [Additional outs...] ────→ [Ch 13-32...] ────┘ ABLETON INPUTS
(Return Tracks)
ABLETON OUTPUTS OMNIBUS Device B
├─ Send: To S1 Monitor ────→ Input Ch 33-34 ────┐
├─ Send: Minus-One Mix ────→ Input Ch 35-36 ────┤
├─ Send: Click Track ────→ Input Ch 37-38 ────┤──→ [OMNIBUS Device B]
├─ Stem: Drums ────→ Input Ch 39-40 ────┤ Output Ch 33-64
├─ Stem: Bass ────→ Input Ch 41-42 ────┤ ↓
└─ [Additional stems...] ────→ [Ch 43-64...] ────┘ STUDIO ONE INPUTS
(Monitoring/Recording)
Routing Rules:
- Ch 1-32 of each device: Satellite → Ableton (audio generation)
- Ch 33-64 of each device: Ableton → Satellite (monitoring/reference)
- All routing is parallel: No serial routing through multiple devices
- Sample rate must match: 48000 Hz across all devices
MIDI Session Architecture:
╔═══════════════════════════════════════════════════════════╗
║ LISTENTO MIDI SESSION MAP ║
║ Hub-to-Satellite & Satellite-to-Hub ║
╚═══════════════════════════════════════════════════════════╝
ABLETON → BITWIG SESSIONS
──────────────────────────────────────────────────────────
Session Name Ableton Track Bitwig Track
─────────────────────────────────────────────────────────
Hub-Grid1-ToBitwig "Control Grid 1" → "Grid 1 to Abl"
(LISTENTO Inst) (LISTENTO Rcv)
Hub-Grid2-ToBitwig "Control Grid 2" → "Grid 2 to Abl"
(LISTENTO Inst) (LISTENTO Rcv)
Hub-Poly-ToBitwig "Control Polymer" → "Polymer to Abl"
(LISTENTO Inst) (LISTENTO Rcv)
Hub-P4-ToBitwig "Control Phase-4" → "Phase-4 to Abl"
(LISTENTO Inst) (LISTENTO Rcv)
Hub-Bass-ToBitwig "Control Bass" → "Bass to Abl"
(LISTENTO Inst) (LISTENTO Rcv)
BITWIG → ABLETON SESSIONS (Optional Return Control)
──────────────────────────────────────────────────────────
Session Name Bitwig Track Ableton Track
─────────────────────────────────────────────────────────
Bit-Return-ToHub "Control Abl Inst" → "Abl Lead Synth"
(LISTENTO Inst) (LISTENTO Rcv)
ABLETON → STUDIO ONE SESSIONS
──────────────────────────────────────────────────────────
Session Name Ableton Track S1 Track
─────────────────────────────────────────────────────────
Hub-Bass-ToS1 "Control S1 Bass" → "Bass from Abl"
(LISTENTO Inst) (LISTENTO Rcv)
Hub-Piano-ToS1 "Control S1 Piano" → "Piano from Abl"
(LISTENTO Inst) (LISTENTO Rcv)
STUDIO ONE → ABLETON SESSIONS (Rare, for MIDI triggers)
──────────────────────────────────────────────────────────
Session Name S1 Track Ableton Track
─────────────────────────────────────────────────────────
S1-Trigger-ToHub "Trigger Abl" → "Triggered Inst"
(LISTENTO Inst) (LISTENTO Rcv)
Session Configuration Requirements:
For each MIDI connection:
- Sender: LISTENTO Instrument plugin, Start Streaming, Copy link
- Receiver: LISTENTO Receiver plugin, Paste link, Set MIDI output to virtual port
- Latency: 100-200ms, matched between sender and receiver
- Activity: MIDI Activity Indicator should flash red when notes transmitted
OMNIBUS Snapshot Comparison Table:
| Feature | Snapshot 1: Full Hub | Snapshot 2: Bitwig Focus | Snapshot 3: S1 Vocal | Snapshot 4: Abl Solo | Snapshot 5: Bitwig FX |
|---|---|---|---|---|---|
| Bitwig → Abl | ✓ All 32 ch | ✓ Ch 1-16 | ✗ Disabled | ✗ Disabled | ✓ Ch 1-16 |
| Abl → Bitwig | ✓ Ch 33-40 | ✓ Ch 33-34 | ✗ Disabled | ✗ Disabled | ✓ Ch 33-48 |
| S1 → Abl | ✓ All 32 ch | ✗ Disabled | ✓ Ch 1-8 | ✗ Disabled | ✗ Disabled |
| Abl → S1 | ✓ Ch 33-40 | ✗ Disabled | ✓ Ch 33-38 | ✗ Disabled | ✗ Disabled |
| Bitwig ↔ S1 | ✗ Disabled | ✗ Disabled | ✗ Disabled | ✗ Disabled | ✗ Disabled |
| CPU Load | High | Medium | Low | Minimal | Medium |
| Latency | ~5ms | ~4ms | ~3ms | <1ms | ~5ms |
| Use Case | Complete production | Sound design | Vocal recording | Ableton only | Creative FX |
Snapshot Switching Strategy:
During Session:
├─ Start with Snapshot 1 (Full Hub)
├─ Switch to Snapshot 2 for focused Bitwig work
├─ Switch to Snapshot 3 for vocal recording
├─ Return to Snapshot 1 for final mixing
└─ Use Snapshot 5 for creative effects processing
Keyboard Shortcuts:
├─ Cmd/Ctrl+1: Instant switch to full production
├─ Cmd/Ctrl+2: Instant switch to Bitwig focus
├─ Cmd/Ctrl+3: Instant switch to S1 vocal
└─ Cmd/Ctrl+4: Instant switch to Ableton solo
Complete Hub Project Structure:
╔═══════════════════════════════════════════════════════════╗
║ ABLETON HUB PROJECT LAYOUT ║
╚═══════════════════════════════════════════════════════════╝
┌─────────────────────────────────────────────────────────┐
│ GROUP 1: SATELLITE AUDIO RETURNS │
│ Purpose: Receive audio from Bitwig & Studio One │
└─────────────────────────────────────────────────────────┘
├─ Return 1: "Bitwig Grid 1" ← Device A Ch 1-2
├─ Return 2: "Bitwig Grid 2" ← Device A Ch 3-4
├─ Return 3: "Bitwig Polymer" ← Device A Ch 5-6
├─ Return 4: "Bitwig Phase-4" ← Device A Ch 7-8
├─ Return 5: "Bitwig Bass" ← Device A Ch 9-10
├─ Return 6: "Bitwig Pad" ← Device A Ch 11-12
├─ Return 7: "Bitwig Perc" ← Device A Ch 13-14
├─ Return 8: "Bitwig FX" ← Device A Ch 15-16
├─ Return 9: "S1 Lead Vocal" ← Device B Ch 1-2
├─ Return 10: "S1 Harmony 1" ← Device B Ch 3-4
├─ Return 11: "S1 Harmony 2" ← Device B Ch 5-6
├─ Return 12: "S1 Backing Vox" ← Device B Ch 7-8
├─ Return 13: "S1 Guitar" ← Device B Ch 9-10
└─ Return 14: "S1 Bass" ← Device B Ch 11-12
┌─────────────────────────────────────────────────────────┐
│ GROUP 2: MIDI CONTROL TO SATELLITES │
│ Purpose: Send MIDI to control satellite instruments │
└─────────────────────────────────────────────────────────┘
├─ MIDI 1: "Control Bitwig Grid 1" → Hub-Grid1-ToBitwig
├─ MIDI 2: "Control Bitwig Grid 2" → Hub-Grid2-ToBitwig
├─ MIDI 3: "Control Bitwig Polymer" → Hub-Poly-ToBitwig
├─ MIDI 4: "Control Bitwig Phase-4" → Hub-P4-ToBitwig
├─ MIDI 5: "Control Bitwig Bass" → Hub-Bass-ToBitwig
├─ MIDI 6: "Control Bitwig Pad" → Hub-Pad-ToBitwig
├─ MIDI 7: "Control S1 Bass" → Hub-Bass-ToS1
└─ MIDI 8: "Control S1 Piano" → Hub-Piano-ToS1
┌─────────────────────────────────────────────────────────┐
│ GROUP 3: ABLETON-NATIVE INSTRUMENTS │
│ Purpose: Instruments running directly in Ableton │
└─────────────────────────────────────────────────────────┘
├─ Inst 1: "Ableton Drums" → Drum Rack
├─ Inst 2: "Ableton Bass" → Wavetable
├─ Inst 3: "Ableton Lead" → Operator (can receive MIDI from satellites)
├─ Inst 4: "Ableton Pad" → Analog
├─ Inst 5: "Ableton Arp" → Wavetable
└─ Inst 6: "Ableton FX" → Simpler
┌─────────────────────────────────────────────────────────┐
│ GROUP 4: AUDIO SENDS TO SATELLITES │
│ Purpose: Send audio from Ableton to satellites │
└─────────────────────────────────────────────────────────┘
├─ Send 1: "To Bitwig Mix" → Device A Ch 33-34
├─ Send 2: "To S1 Monitor Mix" → Device B Ch 33-34
├─ Send 3: "To S1 Minus-One" → Device B Ch 35-36
├─ Send 4: "To S1 Click" → Device B Ch 37-38
├─ Stem 1: "To S1 Drums" → Device B Ch 39-40
├─ Stem 2: "To S1 Bass" → Device B Ch 41-42
├─ Stem 3: "To S1 Synths" → Device B Ch 43-44
└─ Stem 4: "To S1 Vocals" → Device B Ch 45-46
┌─────────────────────────────────────────────────────────┐
│ GROUP 5: PROCESSING & MASTER │
│ Purpose: Effects returns and master bus │
└─────────────────────────────────────────────────────────┘
├─ Return A: "Reverb"
├─ Return B: "Delay"
├─ Return C: "Main Comp"
└─ Master Track
├─ EQ Eight (Main EQ)
├─ Glue Compressor (Mix glue)
├─ Limiter (Final limiting)
└─ Utility (Metering)
Color Coding Scheme:
Group 1 (Satellite Returns): Blue tones (incoming audio)
Group 2 (MIDI Control): Orange tones (MIDI sending)
Group 3 (Native Instruments): Green tones (Ableton instruments)
Group 4 (Sends to Satellites): Purple tones (outgoing audio)
Group 5 (Processing): Grey/White (effects/main)
Checklist:
- OMNIBUS is running (check system tray/menu bar)
- Sample rates match across OMNIBUS and all DAWs (48000 Hz)
- Clock Drift Compensation is DISABLED
- Virtual devices created (Device A, B, C)
- Routing matrix connections made (click cells to route)
- Correct OMNIBUS snapshot loaded
- Track outputs in sending DAW set to correct OMNIBUS channels
- Track inputs in receiving DAW set to correct OMNIBUS channels
Solutions:
-
Verify OMNIBUS is Running:
- macOS: Check menu bar for OMNIBUS icon
- If not running: Launch OMNIBUS application
-
Check Sample Rate Mismatch:
- OMNIBUS Settings → Sample Rate: 48000 Hz
- Each DAW's audio preferences → Sample Rate: 48000 Hz
- Restart all applications after changing
-
Rebuild Routing Matrix:
- Delete all routes (click cells again to remove)
- Add devices to matrix (if missing)
- Recreate routes one at a time
- Test after each route creation
-
Test with Simple Route:
- Create single stereo route: Source Ch 1-2 → Destination Ch 1-2
- Generate test tone in source DAW
- Listen in destination DAW
- If working, expand to full routing
Causes:
- Buffer size too low
- CPU overload
- Competing audio processes
Solutions:
-
Increase Buffer Sizes:
OMNIBUS: 64 → 128 samples DAWs: 128 → 256 samples Trade-off: Higher latency, but more stability -
Check CPU Usage:
- Close unnecessary applications
- Disable resource-heavy plugins
- Freeze tracks in DAWs
-
Optimize OMNIBUS:
- Disable unused virtual device routing
- Switch to simpler snapshot with fewer active routes
-
Enable Drop-Out Protection:
- In each DAW's audio settings
- May add slight latency but improves stability
Solutions:
-
Refresh Audio Device List:
- Close DAW
- Launch OMNIBUS
- Wait 5 seconds
- Relaunch DAW
- Check audio device list again
-
Recreate Virtual Device:
- In OMNIBUS, remove virtual device
- Create new virtual device with same channel count
- Assign same name
- Reconfigure routing matrix
-
Check System Permissions (macOS):
- System Preferences → Security & Privacy → Privacy
- Microphone access for OMNIBUS: ENABLED
- Restart computer if changed
Checklist:
- LISTENTO Instrument plugin on sending track
- LISTENTO Receiver plugin on receiving track
- Session names match exactly (case-sensitive)
- Both plugins show "Connected" status (green indicator)
- MIDI Activity Indicator flashing red when notes played
- Virtual MIDI port created by receiver
- Receiving track input set to LISTENTO virtual port
- LISTENTO ports enabled in DAW MIDI preferences
Solutions:
-
Verify Session Names:
- Check sender: exact session name
- Check receiver: paste exact same session name
- Session names are case-sensitive: "Hub-Grid1-ToBitwig" ≠ "hub-grid1-tobitwig"
-
Check MIDI Activity:
- Play notes on sending track
- Watch LISTENTO Instrument: MIDI meter should move
- Watch LISTENTO Receiver: MIDI Activity Indicator should flash red
- If not flashing, MIDI not reaching receiver
-
Recreate MIDI Routing:
- Remove LISTENTO Receiver from track
- Add LISTENTO Receiver again
- Paste session link
- Create new virtual MIDI port
- Set track input to new port
-
Enable LISTENTO Ports in DAW:
Ableton:
- Preferences → Link, Tempo & MIDI
- Find LISTENTO ports
- Enable "Track" column (make yellow)
Bitwig:
- Settings → Controllers
- Add: Generic → MIDI Keyboard
- Select LISTENTO port as input
Studio One:
- Options → External Devices
- Add: New Keyboard
- Receive From: LISTENTO port
Symptoms:
- Noticeable delay between playing note and hearing sound
- MIDI feels sluggish
Solutions:
-
Reduce LISTENTO Latency:
Starting: 200ms Test: 150ms Optimize: 100ms (if stable) Minimum: 50ms (may be unstable)- Lower incrementally and test stability
- Watch for MIDI dropouts (indicator flickering)
-
Check Internet Connection:
- Use wired Ethernet instead of WiFi
- Close bandwidth-heavy applications (streaming, downloads)
- Test during off-peak hours
-
Optimize MIDI Density:
- Reduce number of simultaneous MIDI notes
- Avoid dense polyphonic chords
- Quantize MIDI for more predictable timing
-
Pre-Record MIDI:
- Record MIDI in advance rather than playing live
- Playback latency is compensated by LISTENTO
- Only affects live performance, not recorded clips
Error Message: "Unable to connect to session"
Solutions:
-
Verify Account Login:
- Both plugins logged into Audiomovers account
- Check internet connection active
-
Check Session Password:
- If password enabled, enter correctly on receiver
- Password is case-sensitive
- Try disabling password temporarily to test
-
Restart Streaming:
- Stop streaming on LISTENTO Instrument
- Wait 5 seconds
- Start streaming again
- Copy new link
- Paste into receiver
-
Check LISTENTO Server Status:
- Visit Audiomovers website for status updates
- Temporary server issues may occur
Solution:
-
Enable OMNIBUS Channels:
- Preferences → Audio → Input Config
- Click cells for OMNIBUS channels until yellow
- Preferences → Audio → Output Config
- Enable output channels
-
Select Correct Audio Device:
- Preferences → Audio → Audio Device
- Select: OMNIBUS Device A (or Aggregate Device)
- Sample Rate: 48000 Hz
- Restart Ableton
-
Recreate Aggregate Device (macOS):
- Audio MIDI Setup application
- Create new Aggregate Device
- Include: OMNIBUS Device A, OMNIBUS Device B, Hardware Interface
- Set Aggregate as Ableton's audio device
Solution:
-
Check Plugin Load Order:
- LISTENTO Receiver must be FIRST in device chain
- Before instrument, before effects
- Move to start of chain if needed
-
Verify MIDI Output Selection:
- Open LISTENTO Receiver settings
- MIDI Output: Select specific port name
- Create new virtual port if needed
-
Add Port to Controllers:
- Settings → Controllers
- Add controller: Generic → MIDI Keyboard
- Input: LISTENTO Receiver virtual port
- Now port available to tracks
Solution:
-
Check Monitor Button:
- Track should have blue Monitor button (enabled)
- Click to toggle monitoring
-
Verify Audio I/O Setup:
- Song → Song Setup → Audio I/O Setup
- Inputs tab: Correct OMNIBUS channels added
- Named appropriately
-
Check Audio Device:
- Options → Audio Setup
- Audio Device: OMNIBUS Device B (or Aggregate)
- Sample Rate: 48000 Hz
-
Test with Different Input:
- Temporarily change track input to different source
- If monitoring works, issue is with specific input configuration
- Recreate I/O Setup entry for problematic input
Recording/Playing Instruments:
All DAWs: 64 samples
OMNIBUS: 64 samples
Total latency: ~2.7ms @ 48kHz
Acceptable for real-time playing
Mixing:
All DAWs: 256-512 samples
OMNIBUS: 128 samples
More CPU headroom for plugins
Higher latency acceptable (not monitoring input)
Ableton:
- View CPU meter in top right corner
- Enable: Cmd+, → Audio → "Driver Error Compensation"
Bitwig:
- Settings → Audio → Check "Automatic" settings
Studio One:
- View → Performance Monitor
When CPU usage high:
-
Freeze Tracks in Sending DAW:
- Bitwig: Right-click track → Freeze
- Studio One: Track → Freeze Track
- Reduces CPU, audio still routes to Ableton
-
Bounce to Audio in Receiving DAW:
- Ableton: Select return track → Consolidate
- Creates audio clip, can disable OMNIBUS routing
-
Disable Unused LISTENTO Sessions:
- Stop streaming on unused LISTENTO Instrument plugins
- Disconnect unused LISTENTO Receivers
- Reduces network overhead
If nothing works, perform full reset:
-
Quit All Applications:
- Close Ableton, Bitwig, Studio One
- Quit OMNIBUS
- Wait 30 seconds
-
Restart OMNIBUS:
- Launch OMNIBUS
- Load saved session: "Multi-DAW-Hub-Config"
- Or manually reconfigure routing matrix
-
Restart DAWs in Order:
- First: Launch Ableton
- Second: Launch Bitwig (wait for Ableton to initialize)
- Third: Launch Studio One
- Reason: Staggered launch prevents audio driver conflicts
-
Test Signal Flow:
- Create test tone in Bitwig
- Should appear in Ableton return track
- If working, configuration restored
Backup Strategy:
OMNIBUS Sessions:
├─ Save As: "Multi-DAW-Hub-Config-[Date].omnibus"
├─ Location: Project folder or cloud storage
└─ Frequency: After any routing changes
DAW Templates:
├─ Ableton: "Multi-DAW Hub Template.als"
├─ Bitwig: "Ableton-Satellite-Instruments.bwtemplate"
├─ Studio One: "Ableton-Hub-Vocal-Recording.template"
└─ Frequency: After finalizing routing configurations
| DAW | Location | Setting |
|---|---|---|
| Ableton | Preferences → Audio | 48000 Hz |
| Bitwig | Settings → Audio | 48000 Hz |
| Studio One | Options → Audio Setup | 48000 Hz |
| OMNIBUS | Settings → Audio Settings | 48000 Hz |
| Purpose | DAW Buffer | OMNIBUS Buffer | Total Latency (@48kHz) |
|---|---|---|---|
| Recording/Playing | 64 | 64 | ~2.7ms |
| Standard Work | 128 | 64 | ~4ms |
| Mixing (CPU headroom) | 256 | 128 | ~8ms |
| Safety/Stability | 512 | 256 | ~16ms |
| Device | Channels | Direction | Purpose |
|---|---|---|---|
| Device A | 64 (32 stereo) | Bitwig ↔ Ableton | Bidirectional hub routing |
| Device B | 64 (32 stereo) | Studio One ↔ Ableton | Bidirectional hub routing |
| Device C | 32 (16 stereo) | Bitwig ↔ Studio One | Direct satellite routing (optional) |
| Device D | (Optional) | Reserved | Expansion/hardware integration |
OMNIBUS Device A (Bitwig ↔ Ableton):
| Channels | Direction | Purpose |
|---|---|---|
| 1-32 | Bitwig → Ableton | Instrument audio from Bitwig |
| 33-64 | Ableton → Bitwig | Reference mix/backing tracks |
OMNIBUS Device B (Studio One ↔ Ableton):
| Channels | Direction | Purpose |
|---|---|---|
| 1-32 | Studio One → Ableton | Vocals/instruments from Studio One |
| 33-38 | Ableton → Studio One | Monitor mix, click, stems |
| 39-64 | Ableton → Studio One | Individual stem sends for processing |
| Direction | Session Name | Purpose |
|---|---|---|
| Abl → Bitwig | "Hub-[Inst]-ToBitwig" | Control Bitwig instruments from Ableton |
| Bitwig → Abl | "Bit-Return-ToHub" | Return control to Ableton (optional) |
| Abl → S1 | "Hub-[Inst]-ToS1" | Control Studio One instruments from Ableton |
| S1 → Abl | "S1-Return-ToHub" | Return control to Ableton (optional) |
- Cmd/Ctrl + 1: Full Hub Production (all routing)
- Cmd/Ctrl + 2: Bitwig Sound Design Focus
- Cmd/Ctrl + 3: Studio One Lyrics Sync
- Cmd/Ctrl + 4: Ableton Hub Solo (no satellites)
- Cmd/Ctrl + 5: Bitwig FX Processing
- Ableton: Cmd/Ctrl + ,
- Bitwig: Bitwig Studio → Settings (Mac) / File → Settings (Win)
- Studio One: Studio One → Preferences (Mac) / Options (Win)
- Ableton: Cmd/Ctrl + T (track), Cmd/Ctrl + Shift + T (return track)
- Bitwig: Cmd/Ctrl + T (track)
- Studio One: T (audio track), Shift + T (instrument track)
- Ableton: Cmd+Option+I (Mac) / Ctrl+Alt+I (Win)
- Bitwig: Tab (cycle views)
- Studio One: View → Console → Show Inputs/Outputs
- Sample rate matching: p. 14
- Buffer size configuration: p. 14
- Clock drift compensation: p. 14
- Virtual device creation: pp. 9, 11, 17
- Virtual device channel configuration: p. 17
- Routing matrix operation: pp. 11-12
- Multi-channel routing: p. 12
- Device coloring and visual settings: pp. 9, 14
- Snapshot management: pp. 14-16
- Snapshot hotkey assignment: p. 15
- Configuration save/load: pp. 26-27
- Run at startup: p. 14
- Lock I/O levels: p. 14
- Plugin installation and authorization: p. 7
- MIDI transmission setup: p. 28
- MIDI reception on receiver plugin: pp. 15, 35
- MIDI Activity Indicator: p. 35
- Virtual MIDI port creation: pp. 16, 31, 35
- Session naming: p. 25
- Session security/passwords: p. 26
- Latency adjustment: pp. 13, 16
- Multi-instance streaming: p. 28
- MIDI routing to destination: p. 35
- Audio preferences and device selection: help.ableton.com/hc/en-us/articles/211476789
- Driver Error Compensation: help.ableton.com/hc/en-us/articles/211476789
- Channel configuration (Input/Output Config): Routing and I/O documentation
- Renaming channels: Routing and I/O documentation
- Track input/output selection: Routing and I/O documentation
- Return tracks input selection: Routing and I/O documentation
- Link, Tempo & MIDI settings: First Steps documentation
- MIDI port configuration: Routing and I/O documentation
- Latency compensation: Routing and I/O documentation
- Monitor modes (In/Auto/Off): Routing and I/O documentation
- Dashboard settings overview: bitwig.com/userguide/latest/the_dashboard/
- Audio device configuration: bax-shop.co.uk/blog/studio-recording/bitwig
- Buffer size and latency: Bitwig User Guide
- Automatic audio engine settings: bitwig.com/userguide
- Controller configuration: bitwig.com/userguide/latest/the_dashboard/
- Audio Setup configuration: PreSonus Quick Start Guide, PreSonus Support
- Song Setup - Audio I/O Setup: PreSonus Support
- External Devices configuration: PreSonus Support (multiple articles)
- Block size strategy (recording vs. mixing): PreSonus Support
- Performance monitoring: PreSonus Support
- Track input monitoring: manua.ls/presonus/studio-one-pro-7
- Audition channel configuration: PreSonus Reference Manual
- Lyrics Track: s1manual.presonus.com/en/Content/Arranging_Topics/Lyrics%20Track.htm
- Lyrics Display and Show Page: Studio One Pro 7 User Manual
- Lyric Lanes integration: Studio One Pro 7 User Manual
Version: 1.0 - Hub-Centric Architecture with Full Bidirectional Routing
Date: November 1, 2025
Author: Compiled from official manufacturer documentation
Architecture: Ableton Live 12 as Central Hub, Bitwig Studio & Studio One Pro 7 as Satellites
This hub-centric configuration establishes Ableton Live 12 as the authoritative source of truth for arrangement, tempo, and project coordination, while leveraging Bitwig Studio's synthesis capabilities and Studio One Pro 7's unique lyrics management features (Global Lyrics Track, Lyrics Display, Lyric Lanes, and Show Page integration). All routing is bidirectional, bit-perfect, and backed by official manufacturer documentation.