Community Report 2025-09-16 - Shimmer chases, Drum Machine workflows, and Browser kung‑fu: Bitwig tips and wishes galore

Users traded practical workflows for drums, modulation, and browser navigation while swapping DIY shimmer reverbs and Grid ideas. Several handy solutions surfaced, such as post‑FX metering clarity, mid/side splitting, and Drum Machine routing into the mixer or separate tracks. Po

Bitwig Community Report 2025-09-16 #

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.

Post‑FX metering and monitoring clarity #

• Clarified that the mixer’s colored level meter shows post‑FX output; confusion often comes from monitoring input (Monitor enabled) rather than playback. Once monitoring was addressed, post‑FX levels behaved as expected.

Browser navigation: focusing folders vs files #

• Efficient keyboard workflow: right arrow to enter subfolders and again to move focus to the file list; left arrow to step back. Some users rely on the dedicated browser focus shortcuts (e.g., “Focus Browser File List” / “Focus Filters”) to jump between pane focus without expanding folders. Behavior varies slightly when folders contain subfolders, requiring an extra Right press.

Drum mixing workflows: Drum Machine, routing, and arranging #

• Approaches included: composing with a single Drum Machine then expanding/mixing cells in the Mixer, dragging individual cells out to their own tracks, or creating audio tracks that receive from specific Drum Machine cells. For arranging-only workflows, setting up a group of audio receiver tracks (kick/snare/etc.) and saving as a preset streamlines future projects.

Mid/Side processing #

• Split mid and side channels using Bitwig’s Mid/Side Split container, then process each path independently. General tip: search “split” in the browser for many helpful splitters.

Modulation wishes: triggers, stateful links, and parameter coupling #

• Users want a “trigger” modulator to fire/reset envelopes/Segments without relying on MIDI notes, and “stateful” modulation where one parameter directly conditions another (akin to Reaper’s parameter linking). Discussion touched on CPU/voice-lifetime considerations but the desire remains strong for richer inter‑modulator triggering and cross‑device links.

Organ instrument tricks and partial modulation #

• The Organ is praised for low CPU and voice stacking. Users explored audio‑rate modulation of partials (AM) for subtle overtones. FM-like effects would require phase access (not available); workaround strategies (layering organs and modulating pitch) were shared for more complex spectra.

DIY shimmer reverb and smoother pitch shifting #

• Several users built shimmer‑style reverbs using FX Grid + Pitch Shifter(+) and Delay+ space diffusion, taming graininess with all‑pass filters and feedback‑path low‑passes. Extra ideas: modulate grain rate over time, stereo‑offset grain rates, use frequency shifter for “wilder” shimmer, or sprinkle chorus. Many found the customized chains far more musical than the basic reverb defaults.

Grid UI/readouts and interface design wishes #

• Creators want simple numeric readouts, XY pads with trails (for scopes/visualizers), and a UI editor for Grid or complex chains (think FL Patcher‑like), to present user‑friendly macro panels. A general “display toolkit” would greatly aid sharing polished devices.

OSC with DrivenByMoss and SuperCollider #

• One user sought practical ways to name device/parameter addresses automatically and simplify device/parameter selection via OSC. Current flows feel cumbersome without parameter name extraction; M4L‑style “Grabber” convenience is desired.

Alias clip splitting behavior #

• Debate over whether splitting an aliased clip should keep both sides aliased or make the right side unique. Some prefer retaining aliasing on both halves (least surprise), others prefer immediate uniqueness for quick local edits.

Minor issues and cautions #

• A Windows-only “Pattern Display” bug was reported as confirmed. An “Editor spraycan misalignment” issue also confirmed. Sporadic modulator malfunctions noted in one project (possibly involving Aux Mod), and a cautionary tale: deleting the plugin cache can break plugin instance recall (IDs) for some plugins (e.g., FabFilter), forcing manual rebuilds.

Misc help and hardware #

• New users with no audio output were guided to check audio device/driver settings (and the manual). A question surfaced on controlling Main Out level via Mac keyboard keys alongside an interface knob (no definitive built-in solution shared).

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.

Automation smoothing vs. modulation: accuracy, clicks, and UX #

• A long debate compared Bitwig’s automation smoothing (to avoid clicks) with sample‑accurate modulation. Users demonstrated that automation can soften vertical steps while modulators remain tight, making identical shapes sound different depending on the path. Requests: a per‑automation (clip/inspector) “smoothing” knob (defaulted for new users, tweakable for power users), parity between automation and modulators, and the option to disable/adjust smoothing globally. Cross‑DAW notes: Live also smooths, Reaper offers low smoothing options; VST parameters often add their own smoothing.

6b3 regressions and issues called out #

• Arrange and editing: extreme slowdowns when drawing automation, paste/stretch time oddities, and broken “Duplicate Time” / “Cut Time” behavior (and ripple‑paste expectations) vs. 5.3. Some shortcuts act inconsistently, and “Toggle Expanded Device View” sometimes only undocks.
• Clip Launcher detail: starting playback from time selection via Space reportedly worked in b2 but not b3.
• Navigation/UI: auto‑zoom selected track occasionally resizes wrong tracks; select next/previous track jumps oddly around uncollapsed groups.
• Crashes and saves: multiple reports of b6 instability/crashes and at least one case where Save did nothing; crash recovery sometimes empty; one user found b3 more stable on EndeavourOS than prior updates.
• Device chains: opening the Master FX Layer from the mixer crashed Bitwig for one user.
• Modulators: “Modulation of a modulator” (e.g., Button1 modulating Button2’s amount) sometimes not saved/reloaded (also observed in v5 projects).
• VST timing: external plugins’ step edges can vary with buffer size; native Tool mod seemed tight in tests, while some VST3s sharpened with smaller buffers.
• Misc: question about arpeggiator preset packs; extremely deep zoom can lag; some preferences (e.g., select loop region fast) still feel fiddly.

Recording and compatibility notes #

• Osmose pitch data wasn’t recording as expected in 6b3 (drawing worked); users debated whether this is user error, configuration (e.g., MPE routing), or a beta bug.

Beta‑specific plugin UI issue #

• Report: in b3, parameters of third‑party plugins couldn’t be modified manually for some users; confirmed by others.

Community stance on improvements #

• Overall sentiment: Bitwig 6’s new automation features are a strong UX step, but technical parity with modulators (configurable smoothing/sample‑accuracy) would be a major win. Many flagged the above regressions as high‑priority fixes before release.