Community Report 2025-09-23 - Relative Automation Rabbit Holes, Linux Reverbs, and Theme Tweaks — While Beta 4 Is “Any Minute Now”

The community dug deep into relative and multiplicative automation in the beta chat, debating macros, aux modulation, and better modulator organization. In stable channels, users looked for ways to annotate lyrics, clarified Bitwig’s UI braces, and troubleshot clip desync tied to

Bitwig Community Report 2025-09-23 #

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.

Lyrics and Note Annotations #

Users asked about attaching text directly to MIDI notes for lyric planning; current workarounds include track comment fields, project-level notes for TODOs/lyrics, and recording guide vocals. A dedicated lyrics track or MIDI clip comments were suggested as future feature ideas.

Browser UI: Curly-Brace Indicators #

Questions about “semi-curly braces” in the device browser were clarified: they indicate grouped subcategories (e.g., Bitwig Devices and Plugins under All Devices), not a visual glitch.

Clips Desync and Play Behavior #

Some experienced clips starting mid-clip or desyncing. A key culprit was keyboard mappings: mapping Space to the correct Play/Pause transport action (like in Ableton) resolved behavior for some, though a few still needed to retrigger the specific clip or scene to re-align.

Linux: Native Reverbs and Sampling Workflows #

Linux users compared native reverbs (Sinevibes Luminance shimmer, Albedo granular; Audio Damage Eos 2/ADverb2) and lamented overall reverb scarcity. Drum sampling came up: Analogue Drums samples require manual preset building; Bitwig Sampler supports round-robin (hidden in the inspector when stacking layers) but lacks easy random pools and separate attack/sustain layers; alternatives like Floe (Lua-based) and Redux were discussed with trade-offs (e.g., no disk streaming in Redux). Some considered the “real drum kit” solution.

Theming: .bte Workflow and Cross-Version Themes #

The theming patch generates default.bte alongside bitwig.jar; create theme.bte by copying from default.bte. On Windows, run Bitwig (and cmd) as Administrator so the file can be written. Shared scripts and repos help convert/apply community themes; v5 themes can be adapted to v6 via the provided Python script, though perfection isn’t guaranteed.

Plogue CLAP Plugin Load Reports #

One user reported chipsynth MD/C64 not loading as CLAP (VST3 was fine). Another user couldn’t reproduce (on macOS). Results are mixed; environment and version differences likely matter.

Shares and Giveaways #

A “Triadizer” preset pack for Unfiltered Audio Triad was shared for free, plus some general resource videos that may spark ideas.

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.

Stuck Notes, Automation Lanes, and “Any Minute” Beta 4 #

Users noted stuck notes requiring device power-cycling and automation randomly starting from different positions. Hints suggest the return of a “favorite” or “last touched parameter” automation lane, with some preferring it pinned atop automation views and others hoping for tags or filterable favorites. Timing chatter claimed Beta 4 could arrive “any minute,” prompting stream-readiness jokes.

Relative and Multiplicative Automation: Macros vs. Old System #

A major thread explored achieving relative automation via unipolar macros: automate the macro mapped to a target instead of the parameter directly to preserve base control changes. For multiplicative behavior, users suggested using an additional macro as an aux modulator (by selecting another mod mapping in the inspector) or the Math modulator; visualization becomes split across lanes and can overshoot ranges. Opinions differed on usefulness in the Arranger vs. Launcher and whether the old relative clip automation was more convoluted than macro-based workflows.

Modulation Architecture Wishes #

Participants wished for multiple aux modulators, modulator grouping/containers, a modulator grid with presets, and clearer sidechain/routing selection. The goal is powerful yet understandable setups that remain debuggable when revisiting old projects.

Mixing and Sends: Trim, Prefader, and Intercepting Sends #

Without a native trim, users rely on tools or relative-like approaches to adjust balances without rewriting automation. Prefader sends and per-send processing (like time shifts or summing emulations) were requested; partial workarounds exist but require extra setup and may sidestep FX tracks.

Practical Tips and Trade-offs #

Using track/preset remotes to “replace” underlying controls with macros helps keep relative behavior consistent, but it demands discipline not to touch the original controls. Users acknowledged the complexity trade-offs: macros make most tasks doable within existing lanes, but organization and clear visualization remain pain points.