Community Report 2025-09-28 - Remotes, Reverbs, and Themes; Beta Brings Hidden Knobs and Twin 3 Beef
The community focused on controller mapping workflows, project/manageability quirks, and live-vocal latency practices. Users traded tips on Remote Controls for NI Komplete Kontrol and LinnStrument setup constraints, while others flagged issues like undo spam from SurgeXT and miss
Bitwig Community Report 2025-09-28 #
This page summarizes recent discussions in the Bitwig Community Forums and Beta forums, highlighting user questions, solutions, and workflow tips. This is updated periodically as new topics arise.
Controller and Remote Mapping Workflows #
Discussion covered NI Komplete Kontrol M32 integration using Bitwig Remote Controls and the DrivenByMoss script, with advice to use device/track remotes and preset/device remote pages to contextually reuse knobs per selected track. LinnStrument users explored a split setup with CC faders and MPE notes; a key limitation noted was Flexi updating only CC1–8 on channel 1, implying a custom controller script is needed if using channel 7 for faders. One user reported an odd arpeggiator-like behavior on the note split despite no arp being enabled.
Track and Project Management Hiccups #
Users missed the right‑click "Add Track" at the insertion point; workarounds included Ctrl/Cmd+T and right‑clicking blank space (which adds at the bottom), though precise placement still felt slower. Moving a sound between Drum Machine slots does not relocate the associated MIDI; users asked if there’s a way to move the matching MIDI lane with the pad. A brief routing glitch where a crash wasn’t sent to FX resolved on its own. Another thread described projects failing to reactivate after deactivation; the recommendation was to report via email for official handling.
Live Vocals and Latency Practices #
Members confirmed live DAW vocal processing is feasible if you audit latency across tracks. Shared thresholds: under 20 ms is ideal, 20–50 ms acceptable, and over 50 ms too high for comfort. Spectral processors and some plugins can add notable latency; alternatives with lower latency were suggested in practice.
Plugins and Undo History #
A user found SurgeXT spamming the undo history immediately upon loading. Others noted Bitwig cannot exclude a specific plugin from undo tracking, suggesting opening an issue with the plugin’s maintainers.
Reverb Send Tails and Automation #
A user sought a method to automate a reverb send so the effect stops instantly (rather than tailing) when returning the send to zero. The discussion highlighted the problem but did not reach a confirmed solution within the thread.
Osmose Presets App: First Release Notes #
A new terminal-based Osmose Presets browser was shared, installable via UV, with steps for selecting the correct MIDI port (typically “Osmose Port 2”), filtering by pack/type/character, keyboard-driven selection, and a basic search supporting logical operators. On Linux Mint, installation succeeded but the app had issues; further investigation was planned.
Community Shares and Theming #
Theme enthusiasts exchanged custom palettes and high-contrast setups, with questions about using the DEV2 theme editor and sharing color templates. A guitar arrangement share added to the community showcase.
Cultural Studies Thesis Poll #
A call for user-submitted questions for a cultural studies bachelor thesis targeting plugin developers invited broader perspectives. Follow-ups clarified the scope (not just AI tools), noting measurement challenges for some culture/algorithm questions.
Bitwig Beta Corner #
If there is a BETA version available, users are encouraged to test new features and report bugs in the Beta forum. Here are some recent topics.
Inspector and Hidden Device Settings #
Beta testers discussed missing or inconvenient parameters in the inspector (e.g., Polymer sub‑oscillator options and clipping modes in Filter+, Sweep, Polymer), noting some controls are only accessible after converting to Grid—at the cost of losing the chain device context. A useful tip surfaced: right‑clicking the body of modules like Polymer/Filter+/Sweep reveals a "Resonance Limit" (Q limit) control.
Filter+ Noise Floor, Resonance, and Self‑Oscillation #
Reports highlighted an audible noise floor in Filter+ when cranking resonance, which becomes clear after heavy dynamics processing like OTT. Some speculated noise may be introduced to aid self‑oscillation; users debated whether that trade‑off is desirable, given you can add noise deliberately if needed. Anecdotes from hardware (e.g., Polaris eurorack) noted that input clipping can kill resonance, drawing parallels to Filter+ behavior with its clipping stage.
Automation Clips: Hands‑on Impressions #
Testers praised the new automation system and automation clips, noting how quickly recording points, reassigning targets, and bending/editing curves feel—especially being able to move a single point across others and reshape naturally. The general sentiment was that automation clips fill a major workflow gap.
FabFilter Twin 3 Giveaway and Mixed Reception #
A promotion granting Twin 3 to new subscribers stirred FOMO and frustration among recent renewals. Opinions on Twin 3 skewed negative—criticisms included a confusing UI and sloppy modulation timing—despite many users liking FabFilter’s mixing tools. Some noted that praise on FabFilter’s Twin page references Twin 2, not 3, reinforcing the mixed reception.
Beta Stability and Project Opening Issues #
Typical beta rough edges were reported: annoyance at instability, questions about opening older beta-made projects, and a theory about corrupt characters (e.g., a null byte) in project names requiring a hex editor fix. Suggestions included trying backups in different versions and checking for sanitized naming.
Long‑form Feedback Video Applauded #
A community member’s 1.5‑hour improvement proposal video and companion website were warmly received, with viewers praising the depth, clarity, and actionable suggestions.
Bitwig Connect Hype #
Early remarks were enthusiastic about pairing Bitwig Connect with write automation, anticipating a powerful workflow combo.