Community Report 2025-09-12 - Tag, you're it: Favorites vs Filters, Step Input Tricks, and Eurorack Scopes

In non‑beta channels, users traded rapid-fire tips for Bitwig’s new Step Input workflow, discussed quicker ways to export audio, and shared practical Grid oscilloscope setups for visualizing Eurorack CV. Curves and automation got love too, from fast randomization with Spread to d

Bitwig Community Report 2025-09-12 #

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.

Step Input workflow: shortcuts, focus, and speed #

• Users shared efficient Step Input methods: hold a note and use arrow keys; hold+backward to delete; Shift+arrows to select in Step Input; Ctrl+T to toggle the tool; and using forward to advance as fast as needed.
• Undo can cause focus loss; switching cursor tools and back restores focus. People asked where to set a “lag”/speed parameter for faster entry.

Faster audio export from clips #

• A request to drag clips straight to the OS file browser for one‑step WAV export sparked workflow suggestions: Bounce, or Export via dialog; using Rolling Sampler to drag out audio; and leveraging external macro tools to automate export sequences.

Visualizing CV in Bitwig and Eurorack tips #

• To scope CV, route CV In (or HW In) to Oscilloscope in the FX Grid; use Stereo Split or the Oscilloscope’s stereo switch for L/R.
• Tips: Tweak inspector settings for stability; beware passing DC if you route track audio; overlay two oscilloscopes for multi‑channel views (two channels max). Users asked for a multi‑channel, colorized oscilloscope in the wishlist.

Curves and automation tools: Spread, .bwcurve, previews #

• Randomizing automation: use Spread (Ctrl+Alt+drag) on selected automation points.
• Loading saved curves: open the side browser’s Curves collection and drag into automation; automation clips vs curves differ in default length. Users noted curve previews appear in the side browser in newer versions and suggested improving the preview area.

Selecting and duplicating automation across lanes #

• Selecting multiple automation clips via drag can be inconsistent; the time‑selection tool (2) helps for copying/duplicating regions. The Detail Editor view can stack selected lanes from multiple tracks for coordinated edits.

Note expressions and plugin support #

• Gain and Pan note expressions are broadly supported in CLAP synths (e.g., u‑he). In VST3, pressure and timbre work in MPE mode where supported, while gain/pan often do not. Serum 2 has partial support depending on MPE state; users compared behaviors across formats.

Managing big live sets and smooth transitions #

• For live shows with many songs: place each song in a Group and deactivate until needed to save CPU; consider bouncing stems over heavy VST chains.
• Tempo transitions: automate tempo over bars for smooth shifts. Scene changes with empty clips can prematurely stop playback depending on launch settings; adjust per‑scene/clip launch quantization and content.

Browser indexing and missing presets #

• If presets vanish, use Reindex All Locations (and ensure no filters are active). This resolved missing factory/user presets for some users.

Linux performance troubleshooting #

• Heavy crackling under PipeWire led to checks on buffer size, kernel versions (upgrading from older LTS to latest stable), and NVIDIA driver quirks. Yabridge’s patched Wine (e.g., 9.21) was recommended; some opted to dual‑boot Windows after extensive testing.

Portable music‑making rigs #

• Suggestions ranged from OP‑1 field, iPad mini + Drambo, Koala/Korg Gadget/GarageBand, Sonicware Lofi‑12 XT, to Synthstrom Deluge. Users debated tactile feedback vs touch and ease of moving sketches into a DAW.

Community preset #

• A user shared a Bitwig Grid preset emulating Reason’s Quad Note Generator, inviting feedback for feature parity and improvements.

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.

Stability and crashes in Beta 3 #

• Mixed reports: some macOS users saw frequent crashes with Java heap space errors despite ample RAM; others reported hours of stability on Apple Silicon. Several hoped Beta 4 would land quickly with fixes.

Automation playback issues #

• Multiple users captured automation not playing back reliably in b3, plus a bug where global/track automation events trigger at half the expected beat time (read at 2× tempo). Bitwig support requested projects; users are awaiting a fix in the next beta.

Favorites removed: tags vs dynamic filtering debate #

• A long discussion weighed bringing back Favorites versus adopting tag‑based or dynamic filtering of automation lanes. Proposals included: color‑coded tags, global/track‑level filters, last‑touched parameter surfacing, and saving filters per project/template.
• Opponents argued manual starring/tagging is tedious and transient for automation; advocated dynamic filters (e.g., show all volume/pan lanes) and better discoverability of existing filters. Consensus: improve filtering ergonomics and visibility; consider both dynamic and light manual tools.

Tempo automation lane range UX #

• Default tempo lane range (e.g., 100–150) felt too narrow or arbitrary. Users suggested: dynamic range that adapts to content; allowing points to extend beyond current min/max to auto‑resize; and persisting custom ranges via templates. Drag behaviors on min/max were also critiqued.

Clip Launcher visibility: notes behind automation #

• On Windows, MIDI notes sometimes fail to display behind automation in the new upper detail editor, seemingly affected by zoom level and specific to the Clip Launcher (Arrangement ok). Users shared reproduction details.

Playhead movement during automation edits #

• Moving automation points can shift the playhead unexpectedly; users want a modifier to control when the playhead follows edits versus staying put.

UI/UX proposals for lanes and track headers #

• Community mockups explored: bringing back Favorites as tags, global/local filters, clearer last‑touched param behavior, moving the + button near the header, and refining VU meters vs faders at various track heights. Debates touched on visual density vs clarity and naming (“level meters” vs “VU”).

Selecting multiple automation clips #

• Users noted difficulty multi‑selecting automation clips across lanes with a single drag; current behavior feels inconsistent compared to audio/MIDI clips. Workarounds involve time‑selection and the Detail Editor, but a direct fix is desired.

Misc beta notes #

• Some copy/paste crashes were reported and later fixed. Performance impressions varied, with some users noting no change vs 5.3. Several threads tracked specific beta issues like “Not reading automation” and bugs with editing hidden/filtered note layers.